RFC 1680: IPng Support for ATM Services
In plain English — editorial summary, not part of the RFC
This white paper describes engineering considerations for IPng as solicited by RFC 1550 [1]. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1680
- Published
- August 1994
- Authors
- C. Brazdziunas
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1681On Many Addresses per HostCurrent
August 1994
- RFC 1679HPN Working Group Input to the IPng Requirements SolicitationCurrent
August 1994
- RFC 1678IPng Requirements of Large Corporate NetworksCurrent
August 1994
- RFC 1682IPng BSD Host Implementation AnalysisCurrent
August 1994
- RFC 1683Multiprotocol Interoperability In IPngCurrent
August 1994
- RFC 1677Tactical Radio Frequency Communication Requirements for IPngCurrent
August 1994
- RFC 1676INFN Requirements for an IPngCurrent
August 1994
- RFC 1675Security Concerns for IPngCurrent
August 1994
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?