Re: [rtcweb] WGLC review of draft-ietf-rtcweb-rtp-usage-13

Cullen Jennings <fluffy@iii.ca> Sat, 17 May 2014 21:06 UTC

Return-Path: <fluffy@iii.ca>
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 504F41A015E for <rtcweb@ietfa.amsl.com>; Sat, 17 May 2014 14:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] 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 vA4-Wo7XHDH5 for <rtcweb@ietfa.amsl.com>; Sat, 17 May 2014 14:06:13 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C1531A0223 for <rtcweb@ietf.org>; Sat, 17 May 2014 14:06:13 -0700 (PDT)
Received: from sjc-vpn7-167.cisco.com (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 71CB822E256; Sat, 17 May 2014 17:06:07 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <53723549.1040200@ericsson.com>
Date: Sat, 17 May 2014 13:20:08 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <85A01677-A754-406A-A2B7-C40F50D33355@iii.ca>
References: <B01CF683-847B-43AF-AE91-7BE50D13C0D4@nostrum.com> <53723549.1040200@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/RI4AzaBkueRALZ3S6z7UMK07ahA
Cc: Ben Campbell <ben@nostrum.com>, rtcweb@ietf.org
Subject: Re: [rtcweb] WGLC review of draft-ietf-rtcweb-rtp-usage-13
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: Sat, 17 May 2014 21:06:15 -0000
X-List-Received-Date: Sat, 17 May 2014 21:06:15 -0000

On May 13, 2014, at 10:07 AM, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:

>> 
>> 
>> -- 12.1.3:
>> 
>> How does (or will) DART fit in here? Seems like it might have
>> something to say, but I'm not sure how the timing relates.
> 
> So this text is the high level teaser to DART work from my perspective.
> The Dart work will have to get into some of the more subtler issues. To
> my understanding the DART output will be part of the reference chain
> here. This document reference [I-D.ietf-tsvwg-rtcweb-qos]
> which in its turn will reference DART. You will also likely to be able
> to reach the DART document through draft-ietf-rtcweb-transports.
> 
> If the DART document becomes available and seen as ready prior to this
> having gone to far down the publication process we can reconsider if
> this should have a direct reference or not. For now I would leave it out.

+1 - that matches my understanding too