RFC 1358: Charter of the Internet Architecture Board (IAB)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1601.
Current document in this lineage: RFC 2850 — Charter of the Internet Architecture Board (IAB)
In plain English — editorial summary, not part of the RFC
The Internet Architecture Board (IAB) shall be constituted and shall operate as a technical advisory group of the Internet Society. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1358
- Published
- August 1992
- Authors
- L. Chapin
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 5
- Also known as
- —
- Obsoleted by:
- RFC 1601
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1358 (1992)
- RFC 1601 (1994)
- RFC 2850 (2000) ✓
Read the full history of Charter of the Internet Architecture Board (IAB) →
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 2850Charter of the Internet Architecture Board (IAB)Updated
May 2000
- RFC 1640The Process for Organization of Internet Standards Working Group (POISED)Current
June 1994
- RFC 1822A Grant of Rights to Use a Specific IBM patent with PhoturisCurrent
August 1995
- RFC 2339An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 ProtocolsCurrent
May 1998
- RFC 2436Collaboration between ISOC/IETF and ITU-TObsoleted
October 1998
- RFC 3356Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration GuidelinesObsoleted
August 2002
- RFC 2031IETF-ISOC relationshipObsoleted
October 1996
- RFC 2777Publicly Verifiable Nomcom Random SelectionObsoleted
February 2000
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?