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

James Polk <jmpolk@cisco.com> Tue, 16 July 2013 21:10 UTC

Return-Path: <jmpolk@cisco.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CCD521F9F13 for <tsvwg@ietfa.amsl.com>; Tue, 16 Jul 2013 14:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.569
X-Spam-Level:
X-Spam-Status: No, score=-110.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 ftDxsx6ee3t9 for <tsvwg@ietfa.amsl.com>; Tue, 16 Jul 2013 14:10:13 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 3498C21F9E3C for <tsvwg@ietf.org>; Tue, 16 Jul 2013 14:10:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3446; q=dns/txt; s=iport; t=1374009013; x=1375218613; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=pL8BAHvUhS7egKUVOzKRwrBWXh0vHD+zbBT/gx5S9Cs=; b=dNL6wU2I1+8PxhQHStfRU76wu2bQjhFPbVntvRoNd1p/jziF7M+tGKSI Ze2ODJGXeSCM3O808T/XBkpCNEXGuJXRiuRcm3icyDBTcv0/Tp+WK+v5n UAQpEFOsG4X/psBR+WAtHsbbJ2Ddb4nZe50w+WgUqczxdXaQz3Vb/UUWJ c=;
X-IronPort-AV: E=Sophos;i="4.89,679,1367971200"; d="scan'208";a="235619756"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-2.cisco.com with ESMTP; 16 Jul 2013 21:10:13 +0000
Received: from jmpolk-WS.cisco.com ([10.89.8.39]) (authenticated bits=0) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r6GLAC3N019397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jul 2013 21:10:12 GMT
Message-Id: <201307162110.r6GLAC3N019397@rcdn-core2-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 16 Jul 2013 16:10:12 -0500
To: "Michael Ramalho (mramalho)" <mramalho@cisco.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <D21571530BF9644D9A443D6BD95B910315595D97@xmb-rcd-x12.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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Authenticated-User: jmpolk
Subject: Re: [tsvwg] FW: [rmcat] Fwd: Submitted ID on delay vs. loss-only rate-adaptive for DiffServ
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jul 2013 21:10:20 -0000

At 08:36 AM 7/16/2013, Michael Ramalho (mramalho) wrote:
>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.

Michael

Thank you for the quick review.

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


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