RFC 2023: IP Version 6 over PPP
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2472.
Current document in this lineage: RFC 5072 — IP Version 6 over PPP; RFC 5172 — Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol
In plain English — editorial summary, not part of the RFC
This document defines the method for transmission of IP Version 6 [2] packets over PPP links as well as the Network Control Protocol (NCP) for establishing and configuring the IPv6 over PPP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2023
- Published
- October 1996
- Authors
- D. Haskin; E. Allen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
- Obsoleted by:
- RFC 2472
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2023 (1996)
- RFC 2472 (1998)
- RFC 5072 (2007)
- RFC 5172 (2008) ✓
Read the full history of Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol →
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 5072IP Version 6 over PPPUpdated
September 2007
- RFC 5172Negotiation for IPv6 Datagram Compression Using IPv6 Control ProtocolCurrent
March 2008
- RFC 2452IP Version 6 Management Information Base for the Transmission Control ProtocolObsoleted
December 1998
- RFC 2460Internet Protocol, Version 6 (IPv6) SpecificationObsoleted
December 1998
- RFC 2465Management Information Base for IP Version 6: Textual Conventions and General GroupObsoleted
December 1998
- RFC 2466Management Information Base for IP Version 6: ICMPv6 GroupObsoleted
December 1998
- RFC 4293Management Information Base for the Internet Protocol (IP)Current
April 2006
- RFC 8200Internet Protocol, Version 6 (IPv6) SpecificationUpdated
July 2017
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?