One document matched: draft-engan-ip-compress-02.txt

Differences from draft-engan-ip-compress-01.txt

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


        RFC 2509: 

        Title:	    IP Header Compression over PPP
	Author(s):  M. Engan, S. Casner, C. Bormann
	Status:     Proposed Standard
	Date:       February 1999
        Mailbox:    engan@effnet.com, casner@cisco.com, cabo@tzi.org
	Pages:      10
        Characters: 18676
        Updates/Obsoletes/See Also: None    
        I-D Tag:    draft-engan-ip-compress-02.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2509.txt

This document describes an option for negotiating the use of header
compression on IP datagrams transmitted over the Point-to-Point
Protocol [RFC1661]. It defines extensions to the PPP Control Protocols
for IPv4 and IPv6 [RFC1332, RFC2023]. Header compression may be
applied to IPv4 and IPv6 datagrams in combination with TCP, UDP and
for IPv4 and IPv6 [RFC1332, RFC2023]. Header compression may be
applied to IPv4 and IPv6 datagrams in combination with TCP, UDP and
RTP transport protocols as specified in [IPHC] and [CRTP].

This document is a product of the Point-to-Point Protocol Extensions
Working Group of the IETF.

This is now a Proposed Standard Protocol.

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.echo 
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.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute