Protocol Action: 'RTP: A Transport Protocol for Real-Time Applications' to Full Standard
The IESG <iesg-secretary@ietf.org> Mon, 17 May 2004 21:36 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 RAA02450 for <ietf-announce-archive@ietf.org>; Mon, 17 May 2004 17:36:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPpmm-0004VD-5W for ietf-announce-archive@ietf.org; Mon, 17 May 2004 17:36:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPpjt-0003cL-00 for ietf-announce-archive@ietf.org; Mon, 17 May 2004 17:33:38 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPphR-0002gO-00 for ietf-announce-archive@ietf.org; Mon, 17 May 2004 17:31:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPozu-0005ny-9w; Mon, 17 May 2004 16:46:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BPo9Y-0001Lm-PN for ietf-announce@optimus.ietf.org; Mon, 17 May 2004 15:52:00 -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 PAA19989 for <ietf-announce@ietf.org>; Mon, 17 May 2004 15:51:59 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BPo9X-00011Z-9o for ietf-announce@ietf.org; Mon, 17 May 2004 15:51:59 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BPo8Y-0000dK-00 for ietf-announce@ietf.org; Mon, 17 May 2004 15:50:58 -0400
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1BPo7R-0000Bl-00; Mon, 17 May 2004 15:49:49 -0400
Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1BPnty-0003M3-Ai; Mon, 17 May 2004 15:35:54 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>, avt mailing list <avt@ietf.org>, avt chair <csp@csperkins.org>, avt chair <magnus.westerlund@ericsson.com>
Subject: Protocol Action: 'RTP: A Transport Protocol for Real-Time Applications' to Full Standard
Message-Id: <E1BPnty-0003M3-Ai@optimus.ietf.org>
Date: Mon, 17 May 2004 15:35:54 -0400
Sender: ietf-announce-admin@ietf.org
Errors-To: ietf-announce-admin@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Id: <ietf-announce.ietf.org>
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>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
The IESG has approved the following documents: - 'RTP: A Transport Protocol for Real-Time Applications ' RFC 3550 as a Full Standard - 'RTP Profile for Audio and Video Conferences with Minimal Control ' RFC 3551 as a Full Standard These documents are products of the Audio/Video Transport Working Group. The IESG contact persons are Allison Mankin and Jon Peterson. Technical Summary RFC 3550 describes RTP, the real-time transport protocol. RTP provides end-to-end network transport functions suitable for applications transmitting real-time data, such as audio, video or simulation data, over multicast or unicast network services. RTP does not address resource reservation and does not guarantee quality-of-service for real-time services. The data transport is augmented by a control protocol (RTCP) to allow monitoring of the data delivery in a manner scalable to large multicast networks, and to provide minimal control and identification functionality. RTP and RTCP are designed to be independent of the underlying transport and network layers. The protocol supports the use of RTP-level translators and mixers. RFC 3551 describes the Audio-Video Profile of RTP, "RTP/AVP", providing interpretations of generic fields within the RTP specification suitable for audio and video conferences with minimal control. It defines a set of default mappings from payload type numbers to encodings, pointers to reference implementations and standards, and registrations of mediatypes. Working Group Summary The Working Group whole-heartedly supported RTP's advancement to Full Standard as soon as it had spent the minimum period in Draft Standard. Protocol Quality RTP is a mature protocol. There are dozens of full implementations. The implementation report for Draft Standard was assessed to be very complete. The determination of RTP going to Full Standard was evaluated by Allison Mankin for the IESG. There were several messages for support for this in response to the IETF Last Call, and no negative messages. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce