[Dart] FW: Document Action: 'Differentiated Services (DiffServ) and Real-time Communication' to Informational RFC (draft-ietf-dart-dscp-rtp-10.txt)

"Black, David" <david.black@emc.com> Thu, 13 November 2014 05: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 []) by ietfa.amsl.com (Postfix) with ESMTP id 809C01A1B7F for <dart@ietfa.amsl.com>; Wed, 12 Nov 2014 21:07:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.895
X-Spam-Status: No, score=-4.895 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.594, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id cJumKapSHJzj for <dart@ietfa.amsl.com>; Wed, 12 Nov 2014 21:06:58 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3734D1A1B5E for <dart@ietf.org>; Wed, 12 Nov 2014 21:06:58 -0800 (PST)
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com []) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sAD56u8f027321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dart@ietf.org>; Thu, 13 Nov 2014 00:06:56 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com sAD56u8f027321
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1415855217; bh=gVVBOBVEFslkhMNynOA/toZc2j0=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=KCzrnAMed7JcKX8YlegRgYo1XblwxqjHS753i+IVgsXW52GWjyB2YK5S8NglRZiQd HU5qc0PUfPAByi0rAnhlwhRH2pagALIlG1hRQ/wpvZ2QeIgCU2uzYJ4mACjs2sCmdo SGvJGqc7GlEksuoaeIAKl9bLkJKudUp+4E+EaM18=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com sAD56u8f027321
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com []) by maildlpprd55.lss.emc.com (RSA Interceptor) for <dart@ietf.org>; Thu, 13 Nov 2014 00:06:35 -0500
Received: from mxhub10.corp.emc.com (mxhub10.corp.emc.com []) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id sAD56hr6017313 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dart@ietf.org>; Thu, 13 Nov 2014 00:06:44 -0500
Received: from MXHUB101.corp.emc.com ( by mxhub10.corp.emc.com ( with Microsoft SMTP Server (TLS) id 8.3.327.1; Thu, 13 Nov 2014 00:06:43 -0500
Received: from MX104CL02.corp.emc.com ([]) by MXHUB101.corp.emc.com ([::1]) with mapi id 14.03.0195.001; Thu, 13 Nov 2014 00:06:43 -0500
From: "Black, David" <david.black@emc.com>
To: "dart@ietf.org" <dart@ietf.org>
Thread-Topic: Document Action: 'Differentiated Services (DiffServ) and Real-time Communication' to Informational RFC (draft-ietf-dart-dscp-rtp-10.txt)
Thread-Index: AQHP/v2TmMzBA3EG/kCBSRhgOOJ035xd/x0A
Date: Thu, 13 Nov 2014 05:06:41 +0000
Message-ID: <CE03DB3D7B45C245BCA0D2432779493624B76C@MX104CL02.corp.emc.com>
References: <20141113045136.23132.69855.idtracker@ietfa.amsl.com>
In-Reply-To: <20141113045136.23132.69855.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public, GIS Solicitation
Archived-At: http://mailarchive.ietf.org/arch/msg/dart/ei0DBxs4EHXZxvNpCgEZqc2_f2w
Subject: [Dart] FW: Document Action: 'Differentiated Services (DiffServ) and Real-time Communication' to Informational RFC (draft-ietf-dart-dscp-rtp-10.txt)
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: Thu, 13 Nov 2014 05:07:03 -0000

> The DART working group was formed in April of 2014. The working group
> was chartered to focus on a constrained problem and conclude quickly.

And we did it - two IETF meeting cycles from start to IESG approval!

Many, many thanks to everyone who contributed - it's been a pleasure
to work on this draft.  Moreover, the one-and-only DART WG meeting in
Toronto was the most fun I've had at the front of the room in an IETF
WG meeting in a long time.  Thank you!


-----Original Message-----
From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG
Sent: Wednesday, November 12, 2014 11:52 PM
To: IETF-Announce
Cc: dart mailing list; dart chair; RFC Editor
Subject: Document Action: 'Differentiated Services (DiffServ) and Real-time Communication' to Informational RFC (draft-ietf-dart-dscp-rtp-10.txt)

The IESG has approved the following document:
- 'Differentiated Services (DiffServ) and Real-time Communication'
  (draft-ietf-dart-dscp-rtp-10.txt) as Informational RFC

This document is the product of the DiffServ Applied to Real-time
Transports Working Group.

The IESG contact persons are Richard Barnes and Alissa Cooper.

A URL of this Internet Draft is:

Technical Summary

This document describes the interaction between Differentiated Services
(DiffServ) network quality of service (QoS) functionality and real-time
network communication, including communication based on the Real-time
Transport Protocol (RTP).  DiffServ is based on network nodes applying
different forwarding treatments to packets whose IP headers are marked
with different DiffServ Code Points (DSCPs). WebRTC applications, as
well as some conferencing applications, have begun using the Session
Description Protocol (SDP) bundle negotiation mechanism to send multiple
traffic streams with different QoS requirements using the same network
5-tuple.  Use of different DSCPs to obtain different QoS treatments
within a single network 5-tuple, the results (e.g., reordering) may
cause transport protocol interactions, particularly with congestion
control functionality.  In addition, DSCP markings may be changed or
removed between the traffic source and destination.  This document
covers the implications of these DiffServ aspects for real-time network
communication, including WebRTC.

Working Group Summary

The DART working group was formed in April of 2014. The working group
was chartered to focus on a constrained problem and conclude quickly.
DART adopted this document with very little controversy.

While the working group is nominally in the RAI area, it has been
effectively a cross-area effort between RAI and TSV. This document
resulted in lively discussion among a core group of experts from both
areas. In general, the discussion converged quickly, and there were no
unresolved controversies.

In the shepherd's opinion, the only impediment to consensus was that
discussion kept overturning rocks, forcing participants to think about
new issues. One notable issue was whether this draft should offer
guidance on the interaction between having multiple DSCPs in a stream
and the multiple stream optimization work
(draft-ietf-avtcore-rtp-multi-stream-optimisation.) The working group
chose to avoid such guidance in this draft, and leave that for the
multi-stream draft to solve.

Document Quality

During the working group last call, we solicited comments from RTCWEB,
AVTCORE, MMUSIC, CLUE, TSVWG, and RMCAT. In the shepherd's opinion, it
has been well reviewed, and represents a strong consensus. The shepherd
does not think it needs any further specific reviews, other than the
usual reviews it would receive during the IETF last call process (for
example, Gen-ART and SecDir).

Since the document does not specify protocol, it will not be directly
implemented. However, we expect that at least the RTCWEB working group
will incorporate guidance from this document into it's output.


The Document Shepherd is Ben Campbell.  The Responsible AD is Richard Barnes.