Re: [rmcat] [tsvwg] FW: Fwd: Submitted ID on delay vs. loss-only rate-adaptive for DiffServ

"Mo Zanaty (mzanaty)" <mzanaty@cisco.com> Wed, 17 July 2013 03:23 UTC

Return-Path: <mzanaty@cisco.com>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17C9521F9CA1; Tue, 16 Jul 2013 20:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.935
X-Spam-Level:
X-Spam-Status: No, score=-9.935 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L6nylqL3SaS2; Tue, 16 Jul 2013 20:23:14 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id AEB6E21F9AEE; Tue, 16 Jul 2013 20:23:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5490; q=dns/txt; s=iport; t=1374031393; x=1375240993; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=TXMzN7AE9tPnPsnArv5QIlGhzX43VyYZUtMH9BGTJv8=; b=bvTfunldjQKsWM/9y9XWT1nC9fvBUH51k8lOv1dq/JJxg8moI4a4HKcp uXnNWlehNiPnVFZk6rVIQoOOzGe+C/tFmtg8khx2zRs0H6HRH/LwZ3B1h wU+GyPY8wERs2LnmCRwWEx7dmygh5i61BGoO6RmkZepnJFBs1ru3S+I19 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAPoM5lGtJV2d/2dsb2JhbABagwY0T8IrgQ0WdIIjAQEBBDpLBAIBCBEDAQEBAQoUCQcyFAgBCAIEARIIAYgHDLVSjz04BoMGbgOpKYFZgTmCKA
X-IronPort-AV: E=Sophos;i="4.89,682,1367971200"; d="scan'208";a="235741391"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-8.cisco.com with ESMTP; 17 Jul 2013 03:23:13 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r6H3NC8W006020 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Jul 2013 03:23:12 GMT
Received: from xmb-rcd-x14.cisco.com ([169.254.4.194]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Tue, 16 Jul 2013 22:23:12 -0500
From: "Mo Zanaty (mzanaty)" <mzanaty@cisco.com>
To: "James Polk (jmpolk)" <jmpolk@cisco.com>, "Cheng-Jia Lai (chelai)" <chelai@cisco.com>, "Toerless Eckert (eckert)" <eckert@cisco.com>, "Michael Ramalho (mramalho)" <mramalho@cisco.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "rmcat@ietf.org" <rmcat@ietf.org>
Thread-Topic: [rmcat] [tsvwg] FW: Fwd: Submitted ID on delay vs. loss-only rate-adaptive for DiffServ
Thread-Index: AQHOgmkPCJii7CPYUk2ch+5QoO+R/JloLzYQ
Date: Wed, 17 Jul 2013 03:23:11 +0000
Message-ID: <3879D71E758A7E4AA99A35DD8D41D3D91D494900@xmb-rcd-x14.cisco.com>
References: <201307160608.r6G680RY026646@rcdn-core-4.cisco.com> <025A278C-55F2-4EB4-A12F-677F8F01A0D0@netapp.com> <D21571530BF9644D9A443D6BD95B910315595CC7@xmb-rcd-x12.cisco.com> <D21571530BF9644D9A443D6BD95B910315595D97@xmb-rcd-x12.cisco.com> <A860EC86B79FA646BF3F89165A88626415339C25@xmb-aln-x11.cisco.com> <201307162111.r6GLBSwF029514@rcdn-core-5.cisco.com>
In-Reply-To: <201307162111.r6GLBSwF029514@rcdn-core-5.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.251.178]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [rmcat] [tsvwg] FW: Fwd: Submitted ID on delay vs. loss-only rate-adaptive for DiffServ
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmcat>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jul 2013 03:23:19 -0000

I support something like what this draft proposes, to segregate RMCAT (and potentially other delay-adaptive traffic) from other traffic which does not adapt to delay trends (and therefore incurs maximum queue delay for all traffic in its queue). Of course, this only helps when such queue segregation is available in the network, but effective active queue management is not available (otherwise there would be no delay signals for delay-adaptive traffic to act on).

An open question in my mind, that I think this draft needs to address, is whether all delay-adaptive traffic should share the same queue/DSCP, or whether we need different queues/DSCPs for different delay-adaptive protocols/applications (for example, RMCAT vs. LEDBAT).

Mo

-----Original Message-----
From: rmcat-bounces@ietf.org [mailto:rmcat-bounces@ietf.org] On Behalf Of James Polk (jmpolk)
Sent: Tuesday, July 16, 2013 5:11 PM
To: Cheng-Jia Lai (chelai); James Polk (jmpolk); Toerless Eckert (eckert); Michael Ramalho (mramalho); tsvwg@ietf.org; rmcat@ietf.org
Subject: Re: [rmcat] [tsvwg] FW: Fwd: Submitted ID on delay vs. loss-only rate-adaptive for DiffServ

CJ

Thank you for the quick review.

I'll ask you the same question I just asked Michael, the draft isn't 
very long (under 8 pages currently), and it is a work in progress - 
but do you have text or just points that this draft needs to cover 
that it doesn't currently?

James

At 01:36 PM 7/16/2013, Cheng-Jia Lai (chelai) wrote:
>Same here... I feel it makes sense to create a new DSCP / CS4 for 
>transport of video flows that have rate adaptive behaviors and/or 
>intra-flow preferential drop priorities as indicated in the I-D. The 
>service provided by the network may thus be considered new, i.e. 
>different from what exists in AF4x, so IMHO, using a new or reusing 
>CS4 service class adds clarity for the user applications.
>
>Regards,
>CJ
>
>
>-----Original Message-----
>From: tsvwg-bounces@ietf.org [mailto:tsvwg-bounces@ietf.org] On 
>Behalf Of Michael Ramalho (mramalho)
>Sent: Tuesday, July 16, 2013 6:36 AM
>To: tsvwg@ietf.org
>Subject: [tsvwg] FW: [rmcat] Fwd: Submitted ID on delay vs. 
>loss-only rate-adaptive for DiffServ
>
>TSVWG Members,
>
>I should have copied you on my email to the RMCAT mailer below.
>
>I strongly support the creation of a new DSCP for transports in 
>which their congestion control can adapt based on delay.
>
>The current ID in support of this 
>(http://www.ietf.org/internet-drafts/draft-polk-tsvwg-delay-vs-loss-ds-service-classes-00.txt 
>) is a work in progress, but a step in the right direction.
>
>It is a given that the ability of the eventual RMCAT adaptation 
>mechanisms to achieve low delay will be function of the other 
>dominant traffic it is competing against. If the dominant competing 
>traffic DEPENDS on loss, the RMCAT packets are held hostage to being 
>delayed by the bottleneck queue delay maximum.
>
>Thus, whenever possible, it will be preferable for RMCAT flows to 
>compete with other congestion control transports that adapt on 
>delay. Even this may not get us to the desired low-delay goals when 
>a portion of the traffic has long RTTs (i.e., adaptation control 
>loops that are long in time), or for links that have a highly-time 
>varying capacity,  but it will help for a lot of common bottleneck 
>topologies (e.g., slowly time-varying access bufferbloat).
>
>It is my hope that this topic has some discussion time in the Berlin 
>Transport WG (not the specific codepoint to be chosen, but rather 
>the need for one).
>
>Off Soapbox,
>
>Michael Ramalho, Ph.D.
>
>-----Original Message-----
>From: Michael Ramalho (mramalho)
>Sent: Tuesday, July 16, 2013 9:06 AM
>To: rmcat@ietf.org
>Subject: RE: [rmcat] Fwd: [tsvwg] Submitted ID on delay vs. 
>loss-only rate-adaptive for DiffServ
>
>RMCAT Design Team,
>
>The draft Lars references below is a formal request for a DSCP 
>dedicated to "RMCAT-only (or other nice delay-based cc) traffic".
>
>It will take a while to become socialized ... and we can progress 
>our RMCAT work in the interim.
>
>Michael Ramalho
>
>-----Original Message-----
>From: rmcat-bounces@ietf.org [mailto:rmcat-bounces@ietf.org] On 
>Behalf Of Eggert, Lars
>Sent: Tuesday, July 16, 2013 5:26 AM
>To: WG WG
>Cc: draft-polk-tsvwg-delay-vs-loss-ds-service-classes@tools.ietf.org
>Subject: [rmcat] Fwd: [tsvwg] Submitted ID on delay vs. loss-only 
>rate-adaptive for DiffServ
>
>Possibly of interest to RMCAT.
>
>Begin forwarded message:
>
> > From: James Polk <jmpolk@cisco.com>
> > Subject: [tsvwg] Submitted ID on delay vs. loss-only 
> rate-adaptive for DiffServ
> > Date: July 16, 2013 8:07:59 GMT+02:00
> > To: <tsvwg@ietf.org>
> >
> > (as an author)
> >
> > Toerless and I put together a draft about legacy rate-adaptation 
> based only on loss vs. what RMCAT is looking to (for RTCWEB), which 
> is based on delay and loss.  Here's the URL.
> >
> > 
> http://www.ietf.org/internet-drafts/draft-polk-tsvwg-delay-vs-loss-ds-service-classes-00.txt
> >
> > It's more raw than we had in mind, but we believe this is 
> necessary, based on implementation experience and what users and 
> customers have in their networks, or are planning on having in 
> their networks soon.
> >
> > James & Toerless
> >