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

Colin Perkins <csp@csperkins.org> Wed, 26 November 2014 16:47 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F37FD1A014C for <rtcweb@ietfa.amsl.com>; Wed, 26 Nov 2014 08:47:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y8HT3di9EoA7 for <rtcweb@ietfa.amsl.com>; Wed, 26 Nov 2014 08:47:38 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32CA91A0149 for <rtcweb@ietf.org>; Wed, 26 Nov 2014 08:47:38 -0800 (PST)
Received: from [130.209.247.112] (port=49325 helo=mangole.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1Xtfke-0004Lc-6S for rtcweb@ietf.org; Wed, 26 Nov 2014 16:47:36 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <20141126163215.6289.51533.idtracker@ietfa.amsl.com>
Date: Wed, 26 Nov 2014 16:47:32 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <EB463631-1EF1-441E-8BF0-F7A4B6B605E7@csperkins.org>
References: <20141126163215.6289.51533.idtracker@ietfa.amsl.com>
To: rtcweb@ietf.org
X-Mailer: Apple Mail (2.1878.6)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold = On =
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/YFrztcyNEvmPVhvBc3GBPC6qiaM
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-usage-21.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 26 Nov 2014 16:47:40 -0000

The changes in this version are as follows:

- In Section 4.3, clarify reference to draft-ietf-rtcweb-audio and add reference draft-ietf-rtcweb-video for mandatory to implement codec and payload formats. Clarify that other codecs and payload formats MAY be implemented, and that all payload formats MUST be signalled before use.

- In Section 5.2.5, note that the CVO header extension MUST be implemented as described in Section 4 of draft-ietf-rtcweb-video.

- In Section 4.1, note that the RTCP SDES MID item MUST be implemented if the SDP bundle extension is used. In Section 5.2.4, note that the RTP MID header extension MUST be implemented if the SDP bundle extension is used.

- In Sections 5.2.1, 5.2.2, and 5.2.3, clarify that the header extension needs to be negotiated before it can be used.

- In Section 5.2.2, clarify that the RFC 6464 client-to-mixer audio level header extension MUST be implemented, based on discussion in IETF91.

- Update Section 6.2 on FEC to refer to draft-uberti-rtcweb-fec.

Colin



On 26 Nov 2014, at 16:32, 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
>        Authors         : Colin Perkins
>                          Magnus Westerlund
>                          Joerg Ott
> 	Filename        : draft-ietf-rtcweb-rtp-usage-21.txt
> 	Pages           : 45
> 	Date            : 2014-11-26
> 
> Abstract:
>   The Web Real-Time Communication (WebRTC) framework provides support
>   for direct interactive rich communication using audio, video, text,
>   collaboration, games, etc.  between two peers' 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.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-rtp-usage/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-rtcweb-rtp-usage-21
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-rtp-usage-21
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb



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