idnits 2.17.1 draft-ietf-rohc-rtp-lla-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3242 5 Title: RObust Header Compression (ROHC): 6 A Link-Layer Assisted Profile for IP/UDP/RTP 7 Author(s): L-E. Jonsson, G. Pelletier 8 Status: Standards Track 9 Date: April 2002 10 Mailbox: lars-erik.jonsson@ericsson.com, 11 ghyslain.pelletier@epl.ericsson.se 12 Pages: 21 13 Characters: 49007 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-rohc-rtp-lla-03.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3242.txt 20 This document defines a ROHC (Robust Header Compression) profile for 21 compression of IP/UDP/RTP (Internet Protocol/User Datagram 22 Protocol/Real-Time Transport Protocol) packets, utilizing 23 functionality provided by the lower layers to increase compression 24 efficiency by completely eliminating the header for most packets 25 during optimal operation. The profile is built as an extension to the 26 ROHC RTP profile. It defines additional mechanisms needed in ROHC, 27 states requirements on the assisting layer to guarantee transparency, 28 and specifies general logic for compression and decompression making 29 use of this header-free packet. 31 This document is a product of the Robust Header Compression Working 32 Group of the IETF. 34 This is now a Proposed Standard Protocol. 36 This document specifies an Internet standards track protocol for the 37 Internet community, and requests discussion and suggestions for 38 improvements. Please refer to the current edition of the "Internet 39 Official Protocol Standards" (STD 1) for the standardization state 40 and status of this protocol. Distribution of this memo is unlimited. 42 This announcement is sent to the IETF list and the RFC-DIST list. 43 Requests to be added to or deleted from the IETF distribution list 44 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 45 added to or deleted from the RFC-DIST distribution list should 46 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 48 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 49 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 50 help: ways_to_get_rfcs. For example: 52 To: rfc-info@RFC-EDITOR.ORG 53 Subject: getting rfcs 55 help: ways_to_get_rfcs 57 Requests for special distribution should be addressed to either the 58 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 59 specifically noted otherwise on the RFC itself, all RFCs are for 60 unlimited distribution.echo 61 Submissions for Requests for Comments should be sent to 62 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 63 Authors, for further information.