Re: [TERNLI] Notes from tonight's ad hoc

Mark Allman <mallman@icir.org> Thu, 20 July 2006 23:53 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3iKo-0008R0-42; Thu, 20 Jul 2006 19:53:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3iKf-0008HU-VC for ternli@ietf.org; Thu, 20 Jul 2006 19:53:29 -0400
Received: from wyvern.icir.org ([192.150.187.14]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3iFh-0005Ti-Bj for ternli@ietf.org; Thu, 20 Jul 2006 19:48:22 -0400
Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by wyvern.icir.org (8.12.11/8.12.11) with ESMTP id k6KNm2p0078968; Thu, 20 Jul 2006 16:48:02 -0700 (PDT) (envelope-from mallman@icir.org)
Received: from lawyers.icir.org (guns.icir.org [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id F1A6E77B6A2; Thu, 20 Jul 2006 19:47:59 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id 7BE1243F926; Thu, 20 Jul 2006 14:12:55 -0400 (EDT)
To: weddy@grc.nasa.gov
From: Mark Allman <mallman@icir.org>
Subject: Re: [TERNLI] Notes from tonight's ad hoc
In-Reply-To: <20060712133556.GB11317@grc.nasa.gov>
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: In the City
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_bOundary"; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 20 Jul 2006 14:12:55 -0400
Message-Id: <20060720181255.7BE1243F926@lawyers.icir.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: ternli@ietf.org
X-BeenThere: ternli@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mallman@icir.org
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

> One thing that I took away from yesterday was that it may be
> productive to build a pair of tables to describe the problem space;
> one table for "significant path changes" that might be passed up to
> the transport, and one table for "significant path desires" that the
> transport can pass down.  

This seems like a reasonable first step to me.  I would further winnow
the list of things to be passed up as "characteristics that impact
performance".  I.e., there is no use telling TCP that some random AP
switched from channel 6 to channel 11.  TCP does not care.  Now, if that
change results in more corruption or a lower bit rate then the TCP would
care about the latter.

From there then we can organize it and figure out where the lowest
hanging fruit really is.

My two cents.

allman