[tram] A note from your (so far) friendly AD ...

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Tue, 25 February 2014 17:35 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 839FC1A01DD; Tue, 25 Feb 2014 09:35:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_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 jUih9hlrF80p; Tue, 25 Feb 2014 09:35:32 -0800 (PST)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8AB1A0105; Tue, 25 Feb 2014 09:35:29 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id wn1so3953516obc.28 for <multiple recipients>; Tue, 25 Feb 2014 09:35:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=3JRjT+Vb3HvFABdujYm/4X1/hE0zXBgGceva71Owqus=; b=Qyvj6bXkv9B26Tc3+Y49HpiuSvtVKV79txORdvKQNcfTDAfsmT+arre91e4UGFL2wp agrLLu03DhWm/5luUhyelpF1c3fbttOECmbwEj+InywK/hYGgTmNumoUXf4Texr71Zj9 wbcKOtl4qXCVKRoR/W0HxqKPQCBzsSpCNO6MBbrToHU7XVeax5q1aRk6pvjXEoiwcZGk hJJwnn+L2G5XCI2fYqFkvmEoRPNijmNclVZez245jnGJPCSY0whfOkR6UjlJTt9u5pfS ENefD2C+A+qiCU5GoOLN9kJFFAO2QLPRysiMy2DK69/R2C1BKODJ56v244WPbxAyLv1W T8/A==
X-Received: by 10.182.22.33 with SMTP id a1mr2447581obf.60.1393349728401; Tue, 25 Feb 2014 09:35:28 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id kn10sm137332740oeb.0.2014.02.25.09.35.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Feb 2014 09:35:27 -0800 (PST)
Message-ID: <530CD45E.5010306@gmail.com>
Date: Tue, 25 Feb 2014 11:35:26 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: tram@ietf.org
References: <20140214030712.30321.21888.idtracker@ietfa.amsl.com> <CAKhHsXGzA=ZTFGTK7ht9hQbfG70iqKrDtxrZCdQNNMzBYZCk8A@mail.gmail.com> <E721D8C6A2E1544DB2DEBC313AF54DE224412306@xmb-rcd-x02.cisco.com> <5303A4DE.8090500@viagenie.ca> <CALDtMrKN8hhDVLZQnPjPNkA=vBe0mznfxDpiAOx=uhkmw8PUHQ@mail.gmail.com> <5303D18C.5030705@viagenie.ca>
In-Reply-To: <5303D18C.5030705@viagenie.ca>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/tbXBO_t7_pAt2m8aO0gqAvswasc
Cc: rai-ads@ietf.org, "rtcweb-chairs@tools.ietf.org" <rtcweb-chairs@tools.ietf.org>, "tsv-ads@ietf.org" <tsv-ads@ietf.org>, "tsvwg-chairs@ietf.org" <tsvwg-chairs@ietf.org>
Subject: [tram] A note from your (so far) friendly AD ...
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2014 17:35:34 -0000

Dear TRAMsters,

If I might offer a couple of suggestions to a new working group ...

The TSV area diverts QoS discussions to the TSVWG working group, because 
that's where the QoS DSCP expertise lives.

RTCWeb and TSVWG are having a robust and so-far productive discussion 
about QoS for RTCWeb now (by "robust", I mean "involving chairs and ADs 
for both working groups"). That discussion is more likely to be 
productive if RTCWeb QoS topics don't start popping up on other working 
group mailing lists, like this one.

I'll let your working group chairs actually run the working group, but I 
note as more than an interested observer that the TRAM agenda at 
https://datatracker.ietf.org/meeting/89/agenda/tram/ is really tight, 
and I would really be happier if the working group focuses on the 
currently chartered milestones and demonstrates that you can deliver 
what you're already signed up to deliver, before adding more milestones. 
The rest of the IESG would be happier as well.

Thanks, and see you in London.

Spencer, as your responsible AD

On 02/18/2014 03:33 PM, Simon Perreault wrote:
> Le 2014-02-18 16:12, Oleg Moskalenko a écrit :
>> How to handle the DS and ECN fields is a part of TURN server RFC (see
>> the section 12):
>>
>> http://tools.ietf.org/search/rfc5766#section-12
>>
>> And a good TURN server is supposed to implement that.
> Well, the RFC just says that the TURN server should copy the DSCP from
> one side to the other when doing en/de-capsulation. It doesn't say that
> the server should actually do QoS based on the DSCP. My point is that
> there's nothing preventing the server from actually doing it.
>
> Anyway, I was expecting responses along the lines of "DiffServ doesn't
> work on the Internet in general." To which I would have replied: "then
> couldn't we define a STUN attribute for transporting the DSCP in the
> payload?" Instead of inventing a new taxonomy (audio, video, slides,
> etc.), why not reuse DSCP?
>
> Simon