RFC 5172: Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol
In plain English — editorial summary, not part of the RFC
The Point-to-Point Protocol (PPP) provides a standard method of encapsulating network-layer protocol information over point-to-point links. PPP also defines an extensible Link Control Protocol, and proposes a family of Network Control Protocols (NCPs) for establishing and configuring different network-layer protocols. The IPv6 Control Protocol (IPV6CP), which is an NCP for a PPP link, allows for the negotiation of desirable parameters for an IPv6 interface over PPP. This document defines the IPv6 datagram compression option that can be negotiated by a node on the link through the IPV6CP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5172
- Published
- March 2008
- Authors
- S. Varada
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
- Obsoletes:
- 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 →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5072IP Version 6 over PPPUpdated
September 2007
- RFC 2023IP Version 6 over PPPObsoleted
October 1996
- RFC 4293Management Information Base for the Internet Protocol (IP)Current
April 2006
- RFC 2509IP Header Compression over PPPObsoleted
February 1999
- RFC 2466Management Information Base for IP Version 6: ICMPv6 GroupObsoleted
December 1998
- RFC 2465Management Information Base for IP Version 6: Textual Conventions and General GroupObsoleted
December 1998
- RFC 2460Internet Protocol, Version 6 (IPv6) SpecificationObsoleted
December 1998
- RFC 2452IP Version 6 Management Information Base for the Transmission Control ProtocolObsoleted
December 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?