ObsoletedINFORMATIONALIETF stream

RFC 2031: IETF-ISOC relationship

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8712.

Current version: RFC 8712The IETF-ISOC Relationship

In plain English — editorial summary, not part of the RFC

This memo summarises the issues on IETF - ISOC relationships as the have been discussed by the Poised Working Group. The purpose of the document is to gauge consensus on these issues. And to allow further discussions where necessary. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

Document record

Document ID
RFC2031
Published
October 1996
Authors
E. Huizer
Status
INFORMATIONAL
Stream
IETF
Area
gen
Pages
4
Also known as
Obsoleted by:
RFC 8712

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/2031-ietf-isoc-relationship