ObsoletedINFORMATIONALLegacy stream

RFC 3356: Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines

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

Current document in this lineage: RFC 6756Internet Engineering Task Force and International Telecommunication Union - Telecommunication Standardization Sector Collaboration Guidelines

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

This document provides guidance to aid in the understanding of collaboration on standards development between the International Telecommunication Union -- Telecommunication Standardization Sector (ITU-T) and the Internet Society (ISOC) / Internet Engineering Task Force (IETF). It is an update of and obsoletes [RFC 2436]. The updates reflect changes in the IETF and ITU-T since RFC 2436 was written. The bulk of this document is common text with ITU-T Supplement 3 to the ITU-T A-Series Recommendations. This was approved by TUT-T TSAG on 30 November 2001 as a supplement to the ITU-T A-Series of recommendations (will be numbered as A- Series Supplement 3)

Document record

Document ID
RFC3356
Published
August 2002
Authors
G. Fishman; S. Bradner
Status
INFORMATIONAL
Stream
Legacy
Area
Pages
12
Also known as
Obsoletes:
RFC 2436
Obsoleted by:
RFC 6756

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 2436 (1998)
  2. RFC 3356 (2002)
  3. RFC 6756 (2012)

Read the full history of Internet Engineering Task Force and International Telecommunication Union - Telecommunication Standardization Sector Collaboration Guidelines

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/3356-internet-engineering-task-force-and-international-telecommunication-union-teleco