idnits 2.17.1 draft-ietf-rohc-rtp-lla-r-mode-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 3408 5 Title: Zero-byte Support for Reliable 6 Bidirectional Mode (R-mode) in Extended Link-Layer 7 Assisted RObust Header Compression (ROHC) Profile 8 Author(s): Z. Liu, K. Le 9 Status: Standards Track 10 Date: December 2002 11 Mailbox: zhigang.c.liu@nokia.com, khiem.le@nokia.com 12 Pages: 7 13 Characters: 14805 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-rohc-rtp-lla-r-mode-03.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3408.txt 20 This document defines an additional mode of the link-layer assisted 21 RObust Header Compression (ROHC) profile, also known as the zero-byte 22 profile, beyond the two defined in RFC 3242. Zero-byte header 23 compression exists in order to prevent the single-octet ROHC header 24 from pushing a packet voice stream into the next higher fixed packet 25 size for the radio. It is usable in certain widely deployed older 26 air interfaces. This document adds the zero-byte operation for ROHC 27 Bidirectional Reliable mode (R-mode) to the ones specified for 28 Unidirectional (U-mode) and Bidirectional Optimistic (O-mode) modes 29 of header compression in RFC 3242. 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 37 the Internet community, and requests discussion and suggestions 38 for improvements. Please refer to the current edition of the 39 "Internet Official Protocol Standards" (STD 1) for the 40 standardization state and status of this protocol. Distribution 41 of this memo is unlimited. 43 This announcement is sent to the IETF list and the RFC-DIST list. 44 Requests to be added to or deleted from the IETF distribution list 45 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 46 added to or deleted from the RFC-DIST distribution list should 47 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 49 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 50 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 51 help: ways_to_get_rfcs. For example: 53 To: rfc-info@RFC-EDITOR.ORG 54 Subject: getting rfcs 56 help: ways_to_get_rfcs 58 Requests for special distribution should be addressed to either the 59 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 60 specifically noted otherwise on the RFC itself, all RFCs are for 61 unlimited distribution.echo 62 Submissions for Requests for Comments should be sent to 63 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 64 Authors, for further information.