idnits 2.17.1 draft-ietf-avt-crtp-enhance-07.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 3545 5 Title: Enhanced Compressed RTP (CRTP) for Links with High 6 Delay, Packet Loss and Reordering 7 Author(s): T. Koren, S. Casner, J. Geevarghese, B. Thompson, 8 P. Ruddy 9 Status: Standards Track 10 Date: July 2003 11 Mailbox: tmima@cisco.com, casner@acm.org, 12 geevjohn@hotmail.com, brucet@cisco.com, 13 pruddy@cisco.com 14 Pages: 22 15 Characters: 48278 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-avt-crtp-enhance-07.txt 20 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3545.txt 22 This document describes a header compression scheme for point to 23 point links with packet loss and long delays. It is based on 24 Compressed Real-time Transport Protocol (CRTP), the IP/UDP/RTP 25 header compression described in RFC 2508. CRTP does not perform well 26 on such links: packet loss results in context corruption and due to 27 the long delay, many more packets are discarded before the context 28 is repaired. To correct the behavior of CRTP over such links, a few 29 extensions to the protocol are specified here. The extensions aim to 30 reduce context corruption by changing the way the compressor updates 31 the context at the decompressor: updates are repeated and include 32 updates to full and differential context parameters. With these 33 extensions, CRTP performs well over links with packet loss, packet 34 reordering and long delays. 36 This document is a product of the Audio Video Transport Working Group 37 of the IETF. 39 This is now a Proposed Standard Protocol. 41 This document specifies an Internet standards track protocol for 42 the Internet community, and requests discussion and suggestions 43 for improvements. Please refer to the current edition of the 44 "Internet Official Protocol Standards" (STD 1) for the 45 standardization state and status of this protocol. Distribution 46 of this memo is unlimited. 48 This announcement is sent to the IETF list and the RFC-DIST list. 49 Requests to be added to or deleted from the IETF distribution list 50 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 51 added to or deleted from the RFC-DIST distribution list should 52 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 54 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 55 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 56 help: ways_to_get_rfcs. For example: 58 To: rfc-info@RFC-EDITOR.ORG 59 Subject: getting rfcs 61 help: ways_to_get_rfcs 63 Requests for special distribution should be addressed to either the 64 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 65 specifically noted otherwise on the RFC itself, all RFCs are for 66 unlimited distribution.echo 67 Submissions for Requests for Comments should be sent to 68 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 69 Authors, for further information.