STD 65, RFC 3551 on RTP Profile for Audio and Video Conferences with Minimal Control
rfc-editor@rfc-editor.org Fri, 04 June 2004 12:55 UTC
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04898 for <ietf-announce-archive@ietf.org>; Fri, 4 Jun 2004 08:55:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BWEEQ-0005cY-LP for ietf-announce-archive@ietf.org; Fri, 04 Jun 2004 08:55:34 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BWEDJ-0005Cq-00 for ietf-announce-archive@ietf.org; Fri, 04 Jun 2004 08:54:26 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1BWECK-0004Q7-00; Fri, 04 Jun 2004 08:53:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BWDtw-0004ZG-B2; Fri, 04 Jun 2004 08:34:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BVzt7-0002KT-D3 for ietf-announce@megatron.ietf.org; Thu, 03 Jun 2004 17:36:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21104 for <ietf-announce@ietf.org>; Thu, 3 Jun 2004 17:36:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BVzt6-0000ea-7n for ietf-announce@ietf.org; Thu, 03 Jun 2004 17:36:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BVziY-0005vp-00 for ietf-announce@ietf.org; Thu, 03 Jun 2004 17:25:43 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BVzX4-0003EA-00; Thu, 03 Jun 2004 17:13:51 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i53LCxJ01801; Thu, 3 Jun 2004 14:12:59 -0700 (PDT)
Message-Id: <200406032112.i53LCxJ01801@boreas.isi.edu>
To: IETF-Announce:;
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 03 Jun 2004 14:12:59 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Mailman-Approved-At: Fri, 04 Jun 2004 08:34:20 -0400
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: STD 65, RFC 3551 on RTP Profile for Audio and Video Conferences with Minimal Control
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60
A new Request for Comments is now available in online RFC libraries. STD 65 RFC 3551 Title: RTP Profile for Audio and Video Conferences with Minimal Control Author(s): H. Schulzrinne, S. Casner Status: Standards Track Date: July 2003 Mailbox: schulzrinne@cs.columbia.edu, casner@acm.org Pages: 44 Characters: 106621 Obsoletes: 1890 See Also: STD 65 I-D Tag: draft-ietf-avt-profile-new-13.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3551.txt This document describes a profile called "RTP/AVP" for the use of the real-time transport protocol (RTP), version 2, and the associated control protocol, RTCP, within audio and video multiparticipant conferences with minimal control. It provides interpretations of generic fields within the RTP specification suitable for audio and video conferences. In particular, this document defines a set of default mappings from payload type numbers to encodings. This document also describes how audio and video data may be carried within RTP. It defines a set of standard encodings and their names when used within RTP. The descriptions provide pointers to reference implementations and the detailed standards. This document is meant as an aid for implementors of audio, video and other real-time multimedia applications. This memorandum obsoletes RFC 1890. It is mostly backwards-compatible except for functions removed because two interoperable implementations were not found. The additions to RFC 1890 codify existing practice in the use of payload formats under this profile and include new payload formats defined since RFC 1890 was published. This document is a product of the Audio/Video Transport Working Group of the IETF. This document has been elevated to a full Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
_______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce