idnits 2.17.1 draft-ietf-avt-profile-new-13.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 3551 5 Title: RTP Profile for Audio and Video Conferences 6 with Minimal Control 7 Author(s): H. Schulzrinne, S. Casner 8 Status: Standards Track 9 Date: July 2003 10 Mailbox: schulzrinne@cs.columbia.edu, casner@acm.org 11 Pages: 44 12 Characters: 106621 13 Obsoletes: 1890 15 I-D Tag: draft-ietf-avt-profile-new-13.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3551.txt 18 ftp://ftp.rfc-editor.org/in-notes/rfc3551.ps 20 This document describes a profile called "RTP/AVP" for the use of the 21 real-time transport protocol (RTP), version 2, and the associated 22 control protocol, RTCP, within audio and video multiparticipant 23 conferences with minimal control. It provides interpretations of 24 generic fields within the RTP specification suitable for audio and 25 video conferences. In particular, this document defines a set of 26 default mappings from payload type numbers to encodings. 28 This document also describes how audio and video data may be carried 29 within RTP. It defines a set of standard encodings and their names 30 when used within RTP. The descriptions provide pointers to reference 31 implementations and the detailed standards. This document is meant 32 as an aid for implementors of audio, video and other real-time 33 multimedia applications. 35 This memorandum obsoletes RFC 1890. It is mostly backwards-compatible 36 except for functions removed because two interoperable implementations 37 were not found. The additions to RFC 1890 codify existing practice in 38 the use of payload formats under this profile and include new payload 39 formats defined since RFC 1890 was published. 41 This document is a product of the Audio/Video Transport Working Group 42 of the IETF. 44 This is now a Draft Standard Protocol. 46 This document specifies an Internet standards track protocol for 47 the Internet community, and requests discussion and suggestions 48 for improvements. Please refer to the current edition of the 49 "Internet Official Protocol Standards" (STD 1) for the 50 standardization state and status of this protocol. Distribution 51 of this memo is unlimited. 53 This announcement is sent to the IETF list and the RFC-DIST list. 54 Requests to be added to or deleted from the IETF distribution list 55 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 56 added to or deleted from the RFC-DIST distribution list should 57 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 59 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 60 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 61 help: ways_to_get_rfcs. For example: 63 To: rfc-info@RFC-EDITOR.ORG 64 Subject: getting rfcs 66 help: ways_to_get_rfcs 68 Requests for special distribution should be addressed to either the 69 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 70 specifically noted otherwise on the RFC itself, all RFCs are for 71 unlimited distribution.echo 72 Submissions for Requests for Comments should be sent to 73 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 74 Authors, for further information.