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

"Black, David" <david.black@emc.com> Tue, 26 August 2014 06:07 UTC

Return-Path: <david.black@emc.com>
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 124841A067D for <dart@ietfa.amsl.com>; Mon, 25 Aug 2014 23:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.969
X-Spam-Level:
X-Spam-Status: No, score=-4.969 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 LNPPQgUbqMg2 for <dart@ietfa.amsl.com>; Mon, 25 Aug 2014 23:07:26 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42D201A0653 for <dart@ietf.org>; Mon, 25 Aug 2014 23:07:26 -0700 (PDT)
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s7Q67MXt002153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Aug 2014 02:07:22 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s7Q67MXt002153
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1409033243; bh=CM9MNb2WjzwAI2+HQADkF77FsvU=; h=From:To:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=HzownwYEYCJKI2BV7+QfUtIpULhPp5McmlBWSoyZYjTWzIf39QGQ3q5eS2AO4GYfw gd/PfgYnP8bVHpakVPwfMXGpaSiHjKtB1lRowSoZFl7WveQZnqKfHXVbAVm88o+oaf anNVTo/dWDuFwhE6VbwjyEVZeyq8MX03NCWW4MMw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s7Q67MXt002153
Received: from mailusrhubprd03.lss.emc.com (mailusrhubprd03.lss.emc.com [10.253.24.21]) by maildlpprd05.lss.emc.com (RSA Interceptor); Tue, 26 Aug 2014 02:07:06 -0400
Received: from mxhub32.corp.emc.com (mxhub32.corp.emc.com [128.222.70.172]) by mailusrhubprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s7Q674W3021192 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 Aug 2014 02:07:06 -0400
Received: from mx15a.corp.emc.com ([169.254.1.175]) by mxhub32.corp.emc.com ([128.222.70.172]) with mapi; Tue, 26 Aug 2014 02:07:04 -0400
From: "Black, David" <david.black@emc.com>
To: Harald Alvestrand <harald@alvestrand.no>, "dart@ietf.org" <dart@ietf.org>
Date: Tue, 26 Aug 2014 02:07:02 -0400
Thread-Topic: draft-ietf-dart-dscp-rtp-02 - Section 4 data channel text
Thread-Index: Ac/A8/JUTzsBwNj8RPOI+dzvT/1H7Q==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712077BB42CEA@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd03.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/dart/sD9q9ghV4qPxg3VRRXJ1Ce9I8Kw
Subject: [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 06:07:29 -0000

> >>> -- 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.