RFC 5172 on Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol

rfc-editor@rfc-editor.org Fri, 28 March 2008 21:13 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F55528CAB2; Fri, 28 Mar 2008 14:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.984
X-Spam-Level:
X-Spam-Status: No, score=-99.984 tagged_above=-999 required=5 tests=[AWL=-0.747, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_32=0.6, J_CHICKENPOX_93=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FS7FL3TcBkgs; Fri, 28 Mar 2008 14:13:36 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DA0628CA12; Fri, 28 Mar 2008 14:11:22 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A2143A6D4F; Fri, 28 Mar 2008 14:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fj+rA0aGeySD; Fri, 28 Mar 2008 14:11:17 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id A109428C287; Fri, 28 Mar 2008 14:10:50 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 495A012172D; Fri, 28 Mar 2008 14:10:50 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5172 on Negotiation for IPv6 Datagram Compression Using IPv6 Control Protocol
From: rfc-editor@rfc-editor.org
Message-Id: <20080328211050.495A012172D@bosco.isi.edu>
Date: Fri, 28 Mar 2008 14:10:50 -0700
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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@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
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]

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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

help: ways_to_get_rfcs. For example:

        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce