Re: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-usage-14.txt
"Hutton, Andrew" <andrew.hutton@unify.com> Mon, 19 May 2014 00:12 UTC
Return-Path: <andrew.hutton@unify.com>
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 263A81A021F for <rtcweb@ietfa.amsl.com>; Sun, 18 May 2014 17:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 oEN4qra0mV3f for <rtcweb@ietfa.amsl.com>; Sun, 18 May 2014 17:11:58 -0700 (PDT)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 564931A021D for <rtcweb@ietf.org>; Sun, 18 May 2014 17:11:58 -0700 (PDT)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx12.unify.com (Server) with ESMTP id 3B0AC23F0460; Mon, 19 May 2014 02:11:57 +0200 (CEST)
Received: from MCHP04MSX.global-ad.net ([169.254.1.60]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0174.001; Mon, 19 May 2014 02:11:57 +0200
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-usage-14.txt
Thread-Index: AQHPcPtboXhTXTBwKU+zGcTDoeUALptFD7ig
Date: Mon, 19 May 2014 00:11:55 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17D9A382@MCHP04MSX.global-ad.net>
References: <20140516113400.20381.24325.idtracker@ietfa.amsl.com> <5375F8A4.7040901@ericsson.com>
In-Reply-To: <5375F8A4.7040901@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/gFWNaDZyWhA7k3IRorhuq427VBE
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-usage-14.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: Mon, 19 May 2014 00:12:00 -0000
Looking through the updates and it is looking good I have a couple of minor comments. In sections 4.5 and 4.6 the text around the use of SDP has been cleaned up but now both sections state a MUST requirement against signaling if SDP is used. For example section 4.5 states "If SDP is used for signalling, this negotiation MUST use the attributes defined in [RFC5761]". Whilst it makes sense to implement it this way probably the RTP usage document should not contain "MUST" level requirements on how signaling is implemented. Maybe this is really something for the API considerations as if SDP is used at the API then we could say this is how it MUST be implemented. Type on section 6 "However, they generally some add overhead" -> "However,they generally add some overhead". Andy > -----Original Message----- > From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Magnus > Westerlund > Sent: 16 May 2014 12:38 > To: rtcweb@ietf.org > Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-usage-14.txt > > WG > > This version is intended to take care of the editorial comments we > received during the WG last call as well as any we authors directly > agreed with and have yet to see any disagreement with. > > At the interim next week we will take the opportunity to go through all > the changes to normative requirements as well as discuss the open > issues. I will attempt to summarize these to the mailing list also, > although start of them already are present in the review emails. > > Cheers > > Magnus > > On 2014-05-16 13:34, 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-14.txt > > Pages : 43 > > Date : 2014-05-16 > > > > 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-14 > > > > A diff from the previous version is available at: > > http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-rtp-usage-14 > > > > > > 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 > > > > > > > -- > > Magnus Westerlund > > ---------------------------------------------------------------------- > Services, Media and Network features, Ericsson Research EAB/TXM > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 10 7148287 > Färögatan 6 | Mobile +46 73 0949079 > SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com > ---------------------------------------------------------------------- > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-usage-… internet-drafts
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-us… Magnus Westerlund
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-us… Hutton, Andrew
- Re: [rtcweb] I-D Action: draft-ietf-rtcweb-rtp-us… Colin Perkins