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

Wesley Eddy <weddy@grc.nasa.gov> Wed, 12 July 2006 13:35 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0esH-0005F3-6O; Wed, 12 Jul 2006 09:35:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0esG-0005Ey-LZ for ternli@ietf.org; Wed, 12 Jul 2006 09:35:32 -0400
Received: from mx1.grc.nasa.gov ([128.156.11.68]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0esF-0004TL-BH for ternli@ietf.org; Wed, 12 Jul 2006 09:35:32 -0400
Received: from lombok-fi.grc.nasa.gov (seraph1.grc.nasa.gov [128.156.10.10]) by mx1.grc.nasa.gov (Postfix) with ESMTP id 80853C291 for <ternli@ietf.org>; Wed, 12 Jul 2006 09:35:30 -0400 (EDT)
Received: from apataki.grc.nasa.gov (apataki.grc.nasa.gov [139.88.112.35]) by lombok-fi.grc.nasa.gov (NASA GRC TCPD 8.13.7/8.13.7) with ESMTP id k6CDZU3O013789; Wed, 12 Jul 2006 09:35:30 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by apataki.grc.nasa.gov (NASA GRC TCPD 8.13.7/8.13.7) with ESMTP id k6CDZTor009873; Wed, 12 Jul 2006 09:35:29 -0400 (EDT)
Received: from apataki.grc.nasa.gov ([127.0.0.1])by localhost (apataki.grc.nasa.gov [127.0.0.1]) (amavisd-new, port 10024)with ESMTP id 06288-22; Wed, 12 Jul 2006 09:35:28 -0400 (EDT)
Received: from drpepper.grc.nasa.gov (gr2134391.grc.nasa.gov [139.88.44.123])by apataki.grc.nasa.gov (NASA GRC TCPD 8.13.7/8.13.7) with ESMTP id k6CDZNSB009804;Wed, 12 Jul 2006 09:35:23 -0400 (EDT)
Received: by drpepper.grc.nasa.gov (Postfix, from userid 501)id DB8C74FCA3; Wed, 12 Jul 2006 09:35:56 -0400 (EDT)
Date: Wed, 12 Jul 2006 09:35:56 -0400
From: Wesley Eddy <weddy@grc.nasa.gov>
To: Spencer Dawkins <spencer@mcsr-labs.org>
Subject: Re: [TERNLI] Notes from tonight's ad hoc
Message-ID: <20060712133556.GB11317@grc.nasa.gov>
References: <0b6401c6a545$01b89bc0$d31adb84@china.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0b6401c6a545$01b89bc0$d31adb84@china.huawei.com>
User-Agent: Mutt/1.5.5.1i
X-imss-version: 2.040
X-imss-result: Passed
X-imss-scores: Clean:98.02204 C:2 M:4 S:5 R:5
X-imss-settings: Baseline:2 C:1 M:1 S:1 R:1 (0.1500 0.1500)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ternli@ietf.org
X-BeenThere: ternli@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: weddy@grc.nasa.gov
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

On Tue, Jul 11, 2006 at 07:52:02PM -0400, Spencer Dawkins wrote:
> Were stuck into jabber log, at 
> http://www.ietf.org/meetings/ietf-logs/tsvwg/2006-07-11.html, at Lar's 
> suggestion.
> 

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.  In each table, we could have a row for each piece of data
and columns that describe the time-frame of relevence (per packet,
within an RTT, per-connection, etc), any existing "point" solutions, and
whether or not the solutions are deployed now, or still research.

There are a lot of starting points to feed this, including the IAB
link indications document and some of the mobopts work.

My thought is that once we have all the diverse things we're talking
about clearly listed, it might be easier to pick out commonalities or
visualize what an architected solution could look like, and also what
the current accidental architecture looks like.

Does this sound like a reasonable next step to take?

-- 
Wesley M. Eddy
Verizon Federal Network Systems