IETF-ISOC relationship
RFC 2031, “IETF-ISOC relationship”, is an Informational document published in October 1996 by E. Huizer. It has been obsoleted by RFC 8712 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 2031 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 2030 Simple Network Time Protocol Version 4 for IPv4, IPv6 and OSI
- RFC 2032 RTP Payload Format for H.261 Video Streams
- RFC 2029 RTP Payload Format of Sun's CellB Video Encoding
- RFC 2033 Local Mail Transfer Protocol
- RFC 2028 The Organizations Involved in the IETF Standards Process
- RFC 2034 SMTP Service Extension for Returning Enhanced Error Codes
- RFC 2027 IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees
- RFC 2035 RTP Payload Format for JPEG-compressed Video