RFC 2436: Collaboration between ISOC/IETF and ITU-T
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3356.
Current document in this lineage: RFC 6756 — Internet Engineering Task Force and International Telecommunication Union - Telecommunication Standardization Sector Collaboration Guidelines
In plain English — editorial summary, not part of the RFC
This document describes the collaboration process between the ITU-T and ISOC/IETF. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2436
- Published
- October 1998
- Authors
- R. Brett; S. Bradner; G. Parsons
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 14
- Also known as
- —
- Obsoleted by:
- RFC 3356
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2436 (1998)
- RFC 3356 (2002)
- RFC 6756 (2012) ✓
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.
- RFC 2031IETF-ISOC relationshipObsoleted
October 1996
- RFC 2357IETF Criteria for Evaluating Reliable Multicast Transport and Application ProtocolsCurrent
June 1998
- RFC 2339An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 ProtocolsCurrent
May 1998
- RFC 31133GPP-IETF Standardization CollaborationCurrent
June 2001
- RFC 31313GPP2-IETF Standardization CollaborationCurrent
June 2001
- RFC 1718The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task ForceObsoleted
November 1994
- RFC 3233Defining the IETFCurrent
February 2002
- RFC 2438Advancement of MIB specifications on the IETF Standards TrackCurrent
October 1998
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?