[Dart] Fwd: Document Action: 'Differentiated Services (DiffServ) and Real-time Communication' to Informational RFC (draft-ietf-dart-dscp-rtp-10.txt)
Ben Campbell <ben@nostrum.com> Thu, 13 November 2014 05:36 UTC
Return-Path: <ben@nostrum.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 2785E1A1B7A for <dart@ietfa.amsl.com>; Wed, 12 Nov 2014 21:36:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level:
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RP_MATCHES_RCVD=-0.594] 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 mI1cuiSuqgso for <dart@ietfa.amsl.com>; Wed, 12 Nov 2014 21:36:50 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB8831A1B81 for <dart@ietf.org>; Wed, 12 Nov 2014 21:36:50 -0800 (PST)
Received: from [192.168.9.231] (64-129-13-2.static.twtelecom.net [64.129.13.2] (may be forged)) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id sAD5amFo041665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Nov 2014 23:36:50 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 64-129-13-2.static.twtelecom.net [64.129.13.2] (may be forged) claimed to be [192.168.9.231]
From: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-95CDFC20-8FEB-4A1B-B355-B0045C81D2F8"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Message-Id: <11E29B6D-36C5-4A81-B176-1EC866F02C6C@nostrum.com>
Date: Wed, 12 Nov 2014 19:36:49 -1000
References: <20141113045136.23132.69855.idtracker@ietfa.amsl.com>
To: dart@ietf.org, draft-ietf-dart-dscp-rtp.all@tools.ietf.org
X-Mailer: iPad Mail (12B410)
Archived-At: http://mailarchive.ietf.org/arch/msg/dart/oLcN11XZBEyMQQM6Ybz6zPD7Jo0
Subject: [Dart] Fwd: 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:36:55 -0000
Yay! Many thanks to the authors, working group participants, and everyone else who played a part in this! Ben. Begin forwarded message: > Resent-From: wg-alias-bounces@tools.ietf.org > From: The IESG <iesg-secretary@ietf.org> > Date: November 12, 2014 at 6:51:36 PM HST > Resent-To: ben@nostrum.com > To: IETF-Announce <ietf-announce@ietf.org> > Cc: RFC Editor <rfc-editor@rfc-editor.org>, dart mailing list <dart@ietf.org>, dart chair <dart-chairs@tools.ietf.org> > 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: > http://datatracker.ietf.org/doc/draft-ietf-dart-dscp-rtp/ > > > > > > 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. > > > Personnel > > The Document Shepherd is Ben Campbell. The Responsible AD is Richard Barnes. > > >