Re: [Dart] draft-ietf-dart-dscp-rtp-02 - Section 4 data channel text

Harald Alvestrand <harald@alvestrand.no> Tue, 26 August 2014 15:40 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: dart@ietfa.amsl.com
Delivered-To: dart@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E357D1A875A for <dart@ietfa.amsl.com>; Tue, 26 Aug 2014 08:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level:
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.668] 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 rRvggymW9S7P for <dart@ietfa.amsl.com>; Tue, 26 Aug 2014 08:40:01 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id BCB331A8753 for <dart@ietf.org>; Tue, 26 Aug 2014 08:40:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id A11F87C3FB9; Tue, 26 Aug 2014 17:39:59 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8NOZETApN568; Tue, 26 Aug 2014 17:39:57 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:58e1:effa:69ad:eb6f] (unknown [IPv6:2001:470:de0a:27:58e1:effa:69ad:eb6f]) by mork.alvestrand.no (Postfix) with ESMTPSA id 78E507C3FB8; Tue, 26 Aug 2014 17:39:57 +0200 (CEST)
Message-ID: <53FCAA4A.8040908@alvestrand.no>
Date: Tue, 26 Aug 2014 17:39:54 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>, "Black, David" <david.black@emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712077BB42CEA@MX15A.corp.emc.com> <289B2FA8-457F-4CF2-BA72-CF0DA947CE11@nostrum.com>
In-Reply-To: <289B2FA8-457F-4CF2-BA72-CF0DA947CE11@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dart/k-U0oVQ3kc9Vi_soaucKZhhfGqM
Cc: "dart@ietf.org" <dart@ietf.org>
Subject: Re: [Dart] draft-ietf-dart-dscp-rtp-02 - Section 4 data channel text
X-BeenThere: dart@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"DiffServ Applied to RTP Transports discussion list\"" <dart.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dart>, <mailto:dart-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dart/>
List-Post: <mailto:dart@ietf.org>
List-Help: <mailto:dart-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dart>, <mailto:dart-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Aug 2014 15:40:06 -0000

On 08/26/2014 04:38 PM, Ben Campbell wrote:
> On Aug 26, 2014, at 1:07 AM, Black, David <david.black@emc.com> wrote:
>
>>>>>> -- section 4:
>>>>>>
>>>>>> It might be nice to have a more WebRTC-ish example. For example an audio
>>>>>> stream, video stream, and a data channel carrying something like a shared
>>>>>> white board or game.
>>>>> Sure, please send text.
>>>>>
>>>> Okay, how about something like the following, added to the end of section 4:
>>>>
>>>> "A WebRTC application may carry one or more RTP streams, as discussed above.
>>> In addition, it might carry an SCTP data channel. The treatment of the data
>>> channel would depend on the nature of the application. For example, messaging
>>> applications, shared white board, or guided browsing applications might be
>>> best effort, while a latency-sensitive game application might require a higher
>>> priority PHB."
>>>
>>> I would prefer to say "A WebRTC application may use...." - an
>>> application is something that lives in a browser at one end of a
>>> connection, talking to something at the other end of the connection
>>> (might be an instance of the same application, might be something
>>> completely different).
>>>
>>> I would also prefer "might desire" to "might require" - games are
>>> unlikely to refuse to operate if they don't get a higher priority PHB,
>>> they'll just work with degraded performance. That's nits.
>> Done, plus some more editing, here's the result in my working draft:
>>
>>   A WebRTC application may use one or more RTP streams, as discussed
>>   above.  In addition, it may include an SCTP-based data channel
>>   [I-D.ietf-rtcweb-data-channel] whose QoS treatment depends on the
>>   nature of the application.  For example, best effort treatment of
>>   data channels is likely to suffice for messaging, shared white board,
>>   and guided browsing applications, whereas latency-sensitive games
>>   might desire better QoS for their data channels.
>>
> WFM.

Works for me too.
If I was nitpicking, I would change "it may include" to "it may use" in
sentence 2 too, but I can live with this just fine.

>


-- 
Surveillance is pervasive. Go Dark.