From wwwrun@core3.amsl.com Tue Jan 25 15:23:33 2011 Return-Path: X-Original-To: payload@ietf.org Delivered-To: payload@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id D23DD3A68F1; Tue, 25 Jan 2011 15:23:33 -0800 (PST) From: IESG Secretary To: IETF Announcement list Cc: even.roni@huawei.com, abegen@cisco.com, payload@ietf.org Content-Type: text/plain; charset="utf-8" Mime-Version: 1.0 Message-Id: <20110125232333.D23DD3A68F1@core3.amsl.com> Date: Tue, 25 Jan 2011 15:23:33 -0800 (PST) Subject: [payload] WG Action: Audio/Video Transport Payloads (PAYLOAD) X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2011 23:23:34 -0000 A new IETF working group has been formed in the Real-time Applications and Infrastructure Area. For additional information, please contact the Area Directors or the WG Chairs. Audio/Video Transport Payloads (PAYLOAD) --------------------------------------------------- Current Status: Active Working Group Chairs: * Roni Even * Ali Begen Real-time Applications and Infrastructure Area Director(s): * Gonzalo Camarillo * Robert Sparks Real-time Applications and Infrastructure Area Advisor: * Robert Sparks Mailing Lists: General Discussion: payload@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/payload Archive: http://www.ietf.org/mail-archive/web/payload/index.html Description of Working Group: The PAYLOAD working group is tasked with the specification and maintenance of payload formats for use with the Real-Time Transport Protocol, RTP [RFC3550]. The group will follow the guidelines established in "Guidelines for Writers of RTP Payload Format Specifications" [BCP 36], the "How to Write an RTP Payload Format" (under development) and is responsible for maintaining those guidelines. This working group will develop RTP payload formats for new media codecs, review and revise existing payload formats to advance those which are useful to Draft Standard or Standard, and declare others Historic. Goals and Milestones: Jan 2011 Submit RTP Payload Format for MIDI for Proposed Standard Feb 2011 Submit How to Write an RTP Payload Format for Informational Feb 2011 Submit RTP Payload Format for MPEG-4 Audio/Visual Streams for Proposed Standard Mar 2011 Submit RTP Payload Format for EVBR/G.718 for Proposed Standard Mar 2011 Submit RTP Payload Format for Enhanced Variable Rate Narrowband-Wideband Codec (EVRC-NW) for Proposed Standard Mar 2011 Submit RTP Payload Format for Bluetooth's SBC audio codec for Proposed Standard Apr 2011 Submit RTP Payload Format for MPEG2-TS preamble for Proposed Standard Apr 2011 Submit RTP Payload Format for DV (IEC 61834) Video for Proposed Standard Apr 2011 Submit RTP Payload Format for the iSAC codec for Proposed Standard Apr 2011 Submit RTP profile for the carriage of SMPTE 336M data for Proposed Standard Jun 2011 Submit RTP Payload Format for MVC Video for Proposed Standard From Internet-Drafts@ietf.org Fri Jan 28 10:30:04 2011 Return-Path: X-Original-To: payload@core3.amsl.com Delivered-To: payload@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA3603A68D7; Fri, 28 Jan 2011 10:30:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.576 X-Spam-Level: X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQbPxg6Lc2Qh; Fri, 28 Jan 2011 10:30:01 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA4783A67D1; Fri, 28 Jan 2011 10:30:01 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.10 Message-ID: <20110128183001.5824.42100.idtracker@localhost> Date: Fri, 28 Jan 2011 10:30:01 -0800 Cc: payload@ietf.org Subject: [payload] I-D Action:draft-ietf-payload-rfc4695-bis-00.txt X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Jan 2011 18:30:04 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Payloads Working Group of the IETF. Title : RTP Payload Format for MIDI Author(s) : J. Lazzaro, J. Wawrzynek Filename : draft-ietf-payload-rfc4695-bis-00.txt Pages : 171 Date : 2011-01-28 This memo describes a Real-time Transport Protocol (RTP) payload format for the MIDI (Musical Instrument Digital Interface) command language. The format encodes all commands that may legally appear on a MIDI 1.0 DIN cable. The format is suitable for interactive applications (such as network musical performance) and content- delivery applications (such as file streaming). The format may be used over unicast and multicast UDP and TCP, and it defines tools for graceful recovery from packet loss. Stream behavior, including the MIDI rendering method, may be customized during session setup. The format also serves as a mode for the mpeg4-generic format, to support the MPEG 4 Audio Object Types for General MIDI, Downloadable Sounds Level 2, and Structured Audio. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-payload-rfc4695-bis-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-payload-rfc4695-bis-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-01-28102920.I-D@ietf.org> --NextPart-- From Internet-Drafts@ietf.org Mon Jan 31 11:45:03 2011 Return-Path: X-Original-To: payload@core3.amsl.com Delivered-To: payload@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 538F53A6C46; Mon, 31 Jan 2011 11:45:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.553 X-Spam-Level: X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id REggsh9BNeE1; Mon, 31 Jan 2011 11:45:02 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E493F3A6C52; Mon, 31 Jan 2011 11:45:01 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 3.11 Message-ID: <20110131194501.29579.99234.idtracker@localhost> Date: Mon, 31 Jan 2011 11:45:01 -0800 Cc: payload@ietf.org Subject: [payload] I-D Action:draft-ietf-avt-rtp-svc-26.txt X-BeenThere: payload@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Audio/Video Transport Payloads working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2011 19:45:03 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Payloads Working Group of the IETF. Title : RTP Payload Format for Scalable Video Coding Author(s) : S. Wenger, et al. Filename : draft-ietf-avt-rtp-svc-26.txt Pages : 105 Date : 2011-01-31 This memo describes an RTP payload format for Scalable Video Coding (SVC) as defined in Annex G of ITU-T Recommendation H.264, which is technically identical to Amendment 3 of ISO/IEC International Standard 14496-10. The RTP payload format allows for packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload, as well as fragmentation of a NAL unit in multiple RTP packets. Furthermore, it supports transmission of an SVC stream over a single as well as multiple RTP sessions. The payload format defines a new media subtype name "H264-SVC", but is still backwards compatible to [I-D.ietf-avt-rtp-rfc3984bis] since the base layer, when encapsulated in its own RTP stream, must use the H.264 media subtype name ("H264") and the packetization method specified in [I- D.ietf-avt-rtp-rfc3984bis]. The payload format has wide applicability in videoconferencing, Internet video streaming, and high bit-rate entertainment-quality video, among others.Table of Contents A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-svc-26.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-avt-rtp-svc-26.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2011-01-31114438.I-D@ietf.org> --NextPart--