IP Header Compression over PPP
draft-koren-pppext-rfc2509bis-03
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3544.
|
|
---|---|---|---|
Authors | Stephen L. Casner , Thima Koren , Carsten Bormann | ||
Last updated | 2022-07-06 (Latest revision 2003-03-03) | ||
Replaces | draft-koren-avt-crtp-ipcp | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Proposed Standard | ||
Formats | |||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 3544 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Allison J. Mankin | ||
IESG note | |||
Send notices to | <engan@sm.luth.se> |
draft-koren-pppext-rfc2509bis-03
A new Request for Comments is now available in online RFC libraries. RFC 3544 Title: IP Header Compression over PPP Author(s): T. Koren, S. Casner, C. Bormann Status: Standards Track Date: July 2003 Mailbox: tmima@cisco.com, casner@packetdesign.com, cabo@tzi.org Pages: 14 Characters: 27627 Obsoletes: 2509 I-D Tag: draft-koren-pppext-rfc2509bis-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3544.txt This document describes an option for negotiating the use of header compression on IP datagrams transmitted over the Point-to-Point Protocol (RFC 1661). It defines extensions to the PPP Control Protocols for IPv4 and IPv6 (RFC 1332, RFC 2472). Header compression may be applied to IPv4 and IPv6 datagrams in combination with TCP, UDP and RTP transport protocols as specified in RFC 2507, RFC 2508 and RFC 3545. 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.