idnits 2.17.1 draft-ietf-rohc-rtp-09.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 3095 5 Title: RObust Header Compression (ROHC): Framework and 6 four profiles: RTP, UDP, ESP, and uncompressed 7 Author(s): C. Bormann, C. Burmeister, M. Degermark, 8 H. Fukushima, H. Hannu, L-E. Jonsson, 9 R. Hakenberg, T. Koren, K. Le, Z. Liu, 10 A. Martensson, A. Miyazaki, K. Svanbro, T. Wiebke, 11 T. Yoshimura, H. Zheng 12 Status: Standards Track 13 Date: July 2001 14 Mailbox: cabo@tzi.org, burmeister@panasonic.de, 15 micke@cs.arizona.edu, fukusima@isl.mei.co.jp, 16 hans.hannu@ericsson.com, 17 lars-erik.jonsson@ericsson.com, 18 hakenberg@panasonic.de, tmima@cisco.com, 19 khiem.le@nokia.com, zhigang.liu@nokia.com, 20 anton.martensson@era.ericsson.se, 21 akihiro@isl.mei.co.jp, 22 krister.svanbro@ericsson.com, wiebke@panasonic.de, 23 yoshi@spg.yrp.nttdocomo.co.jp, 24 haihong.zheng@nokia.com 25 Pages: 169 26 Characters: 368746 27 Updates/Obsoletes/SeeAlso: None 29 I-D Tag: draft-ietf-rohc-rtp-09.txt 31 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3095.txt 33 This document specifies a highly robust and efficient header 34 compression scheme for RTP/UDP/IP (Real-Time Transport Protocol, User 35 Datagram Protocol, Internet Protocol), UDP/IP, and ESP/IP 36 (Encapsulating Security Payload) headers. 38 This document is a product of the Robust Header Compression Working 39 Group of the IETF. 41 This is now a Proposed Standard Protocol. 43 This document specifies an Internet standards track protocol for 44 the Internet community, and requests discussion and suggestions 45 for improvements. Please refer to the current edition of the 46 "Internet Official Protocol Standards" (STD 1) for the 47 standardization state and status of this protocol. Distribution 48 of this memo is unlimited. 50 This announcement is sent to the IETF list and the RFC-DIST list. 51 Requests to be added to or deleted from the IETF distribution list 52 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 53 added to or deleted from the RFC-DIST distribution list should 54 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 56 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 57 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 58 help: ways_to_get_rfcs. For example: 60 To: rfc-info@RFC-EDITOR.ORG 61 Subject: getting rfcs 63 help: ways_to_get_rfcs 65 Requests for special distribution should be addressed to either the 66 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 67 specifically noted otherwise on the RFC itself, all RFCs are for 68 unlimited distribution.echo 69 Submissions for Requests for Comments should be sent to 70 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 71 Authors, for further information.