idnits 2.17.1 draft-ietf-avt-rtp-new-12.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 3550 5 Title: RTP: A Transport Protocol for Real-Time 6 Applications 7 Author(s): H. Schulzrinne, S. Casner, R. Frederick, 8 V. Jacobson 9 Status: Standards Track 10 Date: July 2003 11 Mailbox: schulzrinne@cs.columbia.edu, casner@acm.org, 12 ronf@bluecoat.com, van@packetdesign.com 13 Pages: 104 14 Characters: 259985 15 Obsoletes: 1889 17 I-D Tag: draft-ietf-avt-rtp-new-12.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3550.txt 20 ftp://ftp.rfc-editor.org/in-notes/rfc3550.ps 22 This memorandum describes RTP, the real-time transport protocol. RTP 23 provides end-to-end network transport functions suitable for 24 applications transmitting real-time data, such as audio, video or 25 simulation data, over multicast or unicast network services. RTP 26 does not address resource reservation and does not guarantee 27 quality-of-service for real-time services. The data transport is 28 augmented by a control protocol (RTCP) to allow monitoring of the 29 data delivery in a manner scalable to large multicast networks, and 30 to provide minimal control and identification functionality. RTP and 31 RTCP are designed to be independent of the underlying transport and 32 network layers. The protocol supports the use of RTP-level 33 translators and mixers. 35 Most of the text in this memorandum is identical to RFC 1889 which it 36 obsoletes. There are no changes in the packet formats on the wire, 37 only changes to the rules and algorithms governing how the protocol 38 is used. The biggest change is an enhancement to the scalable timer 39 algorithm for calculating when to send RTCP packets in order to 40 minimize transmission in excess of the intended rate when many 41 participants join a session simultaneously. 43 This document is a product of the Audio/Video Tranposrt Working Group 44 of the IETF. 46 This is now a Draft Standard Protocol. 48 This document specifies an Internet standards track protocol for 49 the Internet community, and requests discussion and suggestions 50 for improvements. Please refer to the current edition of the 51 "Internet Official Protocol Standards" (STD 1) for the 52 standardization state and status of this protocol. Distribution 53 of this memo is unlimited. 55 This announcement is sent to the IETF list and the RFC-DIST list. 56 Requests to be added to or deleted from the IETF distribution list 57 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 58 added to or deleted from the RFC-DIST distribution list should 59 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 61 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 62 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 63 help: ways_to_get_rfcs. For example: 65 To: rfc-info@RFC-EDITOR.ORG 66 Subject: getting rfcs 68 help: ways_to_get_rfcs 70 Requests for special distribution should be addressed to either the 71 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 72 specifically noted otherwise on the RFC itself, all RFCs are for 73 unlimited distribution.echo 74 Submissions for Requests for Comments should be sent to 75 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 76 Authors, for further information.