[rfc-dist] RFC 5172 on Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Mar 28 14:10:50 PDT 2008

A new Request for Comments is now available in online RFC libraries.

        RFC 5172

        Title:      Negotiation for IPv6 Datagram Compression 
                    Using IPv6 Control Protocol 
        Author:     S. Varada, Ed.
        Status:     Standards Track
        Date:       March 2008
        Mailbox:    varada at ieee.org
        Pages:      7
        Characters: 14646
        Obsoletes:  RFC2472

        I-D Tag:    draft-ietf-ipv6-compression-nego-v2-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5172.txt

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

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]

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list