[TERNLI] Re: [Int-area] BOF: Transport-Enhancing Refinements to the Network Layer Interface (TERNLI)

Bernard Aboba <aboba@internaut.com> Tue, 13 June 2006 12:10 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fq7iy-00036M-KJ; Tue, 13 Jun 2006 08:10:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FplU2-00035I-2d; Mon, 12 Jun 2006 08:25:30 -0400
Received: from outbound.mailhop.org ([63.208.196.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FplTy-0000Im-RA; Mon, 12 Jun 2006 08:25:30 -0400
Received: from c-24-16-73-85.hsd1.wa.comcast.net ([24.16.73.85] helo=internaut.com) by outbound.mailhop.org with esmtpa (Exim 4.51) id 1FplTy-000GOR-2d; Mon, 12 Jun 2006 08:25:26 -0400
Received: by internaut.com (Postfix, from userid 1000) id D974B4F5E5; Mon, 12 Jun 2006 05:25:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by internaut.com (Postfix) with ESMTP id CCB5E4F5E4; Mon, 12 Jun 2006 05:25:24 -0700 (PDT)
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 24.16.73.85
X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information)
X-MHO-User: aboba
Date: Mon, 12 Jun 2006 05:25:24 -0700
From: Bernard Aboba <aboba@internaut.com>
To: ternli@ietf.org
In-Reply-To: <E4B0ECFD-3565-47C7-A970-CF245F91975C@netlab.nec.de>
Message-ID: <Pine.LNX.4.61.0606120513140.24393@internaut.com>
References: <E4B0ECFD-3565-47C7-A970-CF245F91975C@netlab.nec.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
X-Mailman-Approved-At: Tue, 13 Jun 2006 08:10:23 -0400
Cc: mobopts@irtf.org, int-area@ietf.org, ietf@ietf.org, tsvwg@ietf.org
Subject: [TERNLI] Re: [Int-area] BOF: Transport-Enhancing Refinements to the Network Layer Interface (TERNLI)
X-BeenThere: ternli@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport-Enhancing Refinements to the Network Layer Interface <ternli.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ternli>, <mailto:ternli-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ternli>
List-Post: <mailto:ternli@ietf.org>
List-Help: <mailto:ternli-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ternli>, <mailto:ternli-request@ietf.org?subject=subscribe>
Errors-To: ternli-bounces@ietf.org

> This isolation, however, comes at a cost, because the traditional
> communication abstraction maintained by these new network-layer extensions
> hides information that transport-layer protocols should act on. 

The information is hidden only for the purposes of connection management, 
not for parameter estimation. 

> Many common
> transport mechanisms, such as congestion window estimation, RTT measurements
> or path MTU discovery, are not agile enough to properly handle the significant
> instantaneous changes to path characteristics that these network-layer
> extensions introduce. 

I might say that "Many current transport algorithms for...", so that it 
is not implied that there are no algorithms that would work.