Re: [Dart] WGLC: draft-ietf-dart-dscp-rtp-02

<> Mon, 11 August 2014 10:21 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id B6E091A03FF; Mon, 11 Aug 2014 03:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.118
X-Spam-Status: No, score=-3.118 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NAHagK2RxI3P; Mon, 11 Aug 2014 03:21:47 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2D7031A03F7; Mon, 11 Aug 2014 03:21:46 -0700 (PDT)
Received: from ([]) by with ESMTP; 11 Aug 2014 12:21:39 +0200
X-IronPort-AV: E=Sophos;i="5.01,840,1400018400"; d="scan'208";a="118455659"
Received: from ([]) by with ESMTP/TLS/AES128-SHA; 11 Aug 2014 12:21:14 +0200
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([]) by ([::1]) with mapi; Mon, 11 Aug 2014 12:21:13 +0200
From: <>
To: <>
Date: Mon, 11 Aug 2014 12:21:12 +0200
Thread-Topic: [Dart] WGLC: draft-ietf-dart-dscp-rtp-02
Thread-Index: Ac+z+nRLTxiz6TcWSyWF7k9hB70xAwBPUAHQ
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F502DE409525@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <>
In-Reply-To: <>
Accept-Language: en-US, de-DE
Content-Language: de-DE
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Dart] WGLC: draft-ietf-dart-dscp-rtp-02
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"DiffServ Applied to RTP Transports discussion list\"" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 11 Aug 2014 10:21:51 -0000

Hi David,

new EF related text has been added in the -01 version. I've copied 
in some text of RFC3246 related to EF remarking and policing below. 
My take:

. remarking of entire flows is an option, but no remarking of 
  packets exceeding EF capacity limits.
- looking at the EF jitter and delay properties, I doubt that 
  shaping is desirable. RFC3246 doesn't mention shaping as part 
  of EF conditioning. I personally wouldn't expect EF shaping 
  in sections where policing is applied. 
- dropping of packets exceeding EF capacity is a MUST, if I 
  interpret RFC3246 correctly.

I suggest to adapt the section of draft-dart-dscp to be more 
precise regarding the optional remarking of EF traffic and to 
remove shaping as a conditioning option if traffic is beyond 
the EF forwarding capacity limit. A Proposal for the final 

...exceeds that capacity must be dropped. EF compliant flows may 
be remarked to a different DSCP.

All other new text indicated by the Diff version looks allright.




3. Expedited Forwarding (EF) [RFC3246] intended for inelastic	
   traffic. Beyond the basic EF PHB, the VOICE-ADMIT PHB [RFC5865]	
   is an admission controlled variant of the EF PHB. Both of these	
   PHBs are based on pre-configured limited forwarding capacity;	
   traffic that exceeds that capacity may be shaped, remarked to a	
   different DSCP, or dropped.


RFC3246 (three excerpts):

   Packets belonging to a single microflow within the EF aggregate
   passing through a device SHOULD NOT experience re-ordering in normal
   operation of the device.

   Packets marked for EF PHB MAY be remarked at a DS domain boundary
   only to other codepoints that satisfy the EF PHB.  Packets marked for
   EF PHBs SHOULD NOT be demoted or promoted to another PHB by a DS

   If the EF PHB is implemented by a mechanism that allows unlimited
   preemption of other traffic (e.g., a priority queue), the
   implementation MUST include some means to limit the damage EF traffic
   could inflict on other traffic (e.g., a token bucket rate limiter).
   Traffic that exceeds this limit MUST be discarded.

-----Ursprüngliche Nachricht-----
Von: Dart [] Im Auftrag von Ben Campbell
Gesendet: Samstag, 9. August 2014 19:50
Cc: Richard Barnes;;
Betreff: [Dart] WGLC: draft-ietf-dart-dscp-rtp-02

This is a DART Working Group Last Call of draft-ietf-dart-dscp-rtp-02. It's available on the data tracker at the following URL:

The WGLC will conclude on 22 August, 2014. Please send your comments to the authors and the DART mailing list. If you've reviewed it and think it's good to go, please say so.



Dart mailing list