Re: [tsv-area] TANA BOF

Stanislav Shalunov <shalunov@shlang.com> Sat, 02 August 2008 19:29 UTC

Return-Path: <tsv-area-bounces@ietf.org>
X-Original-To: tsv-area-archive@optimus.ietf.org
Delivered-To: ietfarch-tsv-area-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB22C3A6AD6; Sat, 2 Aug 2008 12:29:08 -0700 (PDT)
X-Original-To: tsv-area@core3.amsl.com
Delivered-To: tsv-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CED043A6AD6 for <tsv-area@core3.amsl.com>; Sat, 2 Aug 2008 12:29:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.822
X-Spam-Level:
X-Spam-Status: No, score=-1.822 tagged_above=-999 required=5 tests=[AWL=0.462, BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uyL6RIxvVxsl for <tsv-area@core3.amsl.com>; Sat, 2 Aug 2008 12:29:06 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by core3.amsl.com (Postfix) with ESMTP id B9F573A6AC6 for <tsv-area@ietf.org>; Sat, 2 Aug 2008 12:29:06 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 27so1419478wfd.31 for <tsv-area@ietf.org>; Sat, 02 Aug 2008 12:29:30 -0700 (PDT)
Received: by 10.142.170.6 with SMTP id s6mr4278700wfe.228.1217705370006; Sat, 02 Aug 2008 12:29:30 -0700 (PDT)
Received: from ?192.168.1.103? ( [67.188.243.194]) by mx.google.com with ESMTPS id 30sm4195009wfa.10.2008.08.02.12.29.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 02 Aug 2008 12:29:29 -0700 (PDT)
Message-Id: <AB07836F-B38E-406E-B506-8AC86022D2E6@shlang.com>
From: Stanislav Shalunov <shalunov@shlang.com>
To: Roland Bless <bless@tm.uka.de>
In-Reply-To: <4892F2EC.3010902@tm.uka.de>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v926)
Date: Sat, 02 Aug 2008 12:29:28 -0700
References: <4892F2EC.3010902@tm.uka.de>
X-Mailer: Apple Mail (2.926)
Cc: TSV Area <tsv-area@ietf.org>
Subject: Re: [tsv-area] TANA BOF
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Transport Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tsv-area>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
Sender: tsv-area-bounces@ietf.org
Errors-To: tsv-area-bounces@ietf.org

On Aug 1, 2008, at 4:26 AM, Roland Bless wrote:
> It is not clear to me how "otherwise idle bandwidth"
> can be made available for pure end-to-end transport
> solutions, i.e., without differentiation in the
> network itself.

On a technical level, we can definitely design and implement end-to- 
end congestion control that yields to (New)Reno -- or, in fact, to any  
loss-based congestion control.  In fact, I happen to have done just  
that for a particular application that currently uses up a larger  
fraction of bits on the Internet than any other app with the possible  
exception of HTTP.  Delay-based congestion control schemes yield to  
loss-based control quite often regardless of whether they are designed  
to do this simply because delay needs to increase to buffer size  
before loss occurs.

> a) probably it is easier to start deploying
> RFC 3622 (http://tools.ietf.org/html/rfc3662)
> in ISP networks than to design new
> congestion control algorithms. All you need
> is a DSCP, a codepoint classifier, a separate
> queue and simple priority scheduling. CS(1)
> DSCP=001000 was proposed for LE traffic.

Yes, we tried that (http://qos.internet2.edu/wg/wg-documents/qbss-definition.txt 
  -- note dates on the documents: March 2001 for qbss, June 2002 for  
draft-bless-diffserv-pdb-le-00.txt).  We may like or not like it, but  
scavenger has not been deployed.

No, it is definitely not easier to upgrade the Internet than to design  
end-to-end algorithms that can be deployed by putting them into  
relevant applications.  This is a matter of deployment properties: to  
reach 80% deployment, one requires to change hundreds of millions of  
physical devices of thousands of different kinds, with virtually none  
of them on auto-update; the other requires to change a few pieces of  
software, all of them on auto-update.

The most congested links are uplinks of home connections.  We're not  
going to see the devices at their head ends changed any time soon.   
When they are changed, they will likely not support whatever scheme we  
like until there's a good reason to.  Whereas we can deploy end-to-end  
congestion control, and it'll work across these links.

Thank you for the comments,

-- Stas

--
Stanislav Shalunov