Re: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-usage-01.txt

Colin Perkins <csp@csperkins.org> Mon, 31 October 2011 23:12 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6D0B11E8371 for <rtcweb@ietfa.amsl.com>; Mon, 31 Oct 2011 16:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level:
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=1.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KDQ8qssF-bb for <rtcweb@ietfa.amsl.com>; Mon, 31 Oct 2011 16:12:41 -0700 (PDT)
Received: from lon1-msapost-1.mail.demon.net (lon1-msapost-1.mail.demon.net [195.173.77.180]) by ietfa.amsl.com (Postfix) with ESMTP id 1A5F511E836E for <rtcweb@ietf.org>; Mon, 31 Oct 2011 16:12:41 -0700 (PDT)
Received: from starkperkins.demon.co.uk ([80.176.158.71] helo=[192.168.0.26]) by lon1-post-1.mail.demon.net with esmtpsa (AUTH csperkins-dwh) (TLSv1:AES128-SHA:128) (Exim 4.69) id 1RL11z-0005Lv-Yb for rtcweb@ietf.org; Mon, 31 Oct 2011 23:12:39 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20111031222443.4893.89089.idtracker@ietfa.amsl.com>
Date: Mon, 31 Oct 2011 23:12:37 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <0AAEA389-AA57-4212-BE69-4A56122F57F4@csperkins.org>
References: <20111031222443.4893.89089.idtracker@ietfa.amsl.com>
To: rtcweb@ietf.org
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-usage-01.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Oct 2011 23:12:42 -0000

On 31 Oct 2011, at 22:24, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Real-Time Communication in WEB-browsers Working Group of the IETF.
> 
> 	Title           : Web Real-Time Communication (WebRTC): Media Transport and Use of RTP
> 	Author(s)       : Colin Perkins
>                          Magnus Westerlund
>                          Joerg Ott
> 	Filename        : draft-ietf-rtcweb-rtp-usage-01.txt
> 	Pages           : 28
> 	Date            : 2011-10-31
> 
>   The Web Real-Time Communication (WebRTC) framework aims to provide
>   support for direct interactive rich communication using audio, video,
>   collaboration, games, etc. between two peers&#39; web-browsers.  This
>   memo describes the media transport aspects of the WebRTC framework.
>   It specifies how the Real-time Transport Protocol (RTP) is used in
>   the WebRTC context, and gives requirements for which RTP features,
>   profiles, and extensions need to be supported.
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-rtcweb-rtp-usage-01.txt


We've updated our draft on RTP Requirements for RTC-Web, and renamed it to better reflect the content. Changes in this version include:

- Update title, rewrite Abstract and Introduction, and restructure the draft
- Update section on Rate Control and Media Adaptation
- Update section on Use of RTP: Core Protocols
- Add some initial discussion of multiplexing several RTP sessions onto a single lower-layer transport, primarily referencing other drafts for the content.
- Address comments by Harald Alvestrand from the mailing list (29 August 2011)
- Update Security Considerations

The main technical changes are in Section 8, and focus on the requirements for Rate Control and Media Adaptation, the limitations of RTCP when used for this purpose without RTP/AVPF, and interoperability with legacy systems. There are also smaller technical changes, and numerious editorial fixes, throughout.

-- 
Colin Perkins
http://csperkins.org/