RE: [Tsvwg] multiaddressing
"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Mon, 29 November 2004 19:59 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24897; Mon, 29 Nov 2004 14:59:13 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYrl0-0001kj-RZ; Mon, 29 Nov 2004 15:04:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYray-0001oY-2X; Mon, 29 Nov 2004 14:54:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYrW8-0000aI-51 for tsvwg@megatron.ietf.org; Mon, 29 Nov 2004 14:49:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24027 for <tsvwg@ietf.org>; Mon, 29 Nov 2004 14:48:58 -0500 (EST)
Received: from slb-smtpout-01.boeing.com ([130.76.64.48]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYrb2-0001WP-SF for tsvwg@ietf.org; Mon, 29 Nov 2004 14:54:08 -0500
Received: from slb-av-01.boeing.com ([129.172.13.4]) by slb-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id LAA10449; Mon, 29 Nov 2004 11:48:04 -0800 (PST)
Received: from XCH-NWBH-02.nw.nos.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id iATJm2i20308; Mon, 29 Nov 2004 11:48:02 -0800 (PST)
Received: from XCH-NW-27.nw.nos.boeing.com ([192.48.4.101]) by XCH-NWBH-02.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 29 Nov 2004 11:48:03 -0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Subject: RE: [Tsvwg] multiaddressing
Date: Mon, 29 Nov 2004 11:48:02 -0800
Message-ID: <6938661A6EDA8A4EA8D1419BCE46F24C04060929@xch-nw-27.nw.nos.boeing.com>
Thread-Topic: [Tsvwg] multiaddressing
Thread-Index: AcTSS/92cEakUxZNSzWLhdhMH1hr+wD/N95w
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: Randall Stewart <randall@stewart.chicago.il.us>, weddy@grc.nasa.gov
X-OriginalArrivalTime: 29 Nov 2004 19:48:03.0021 (UTC) FILETIME=[567E8FD0:01C4D64C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: quoted-printable
Cc: tsvwg@ietf.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Sender: tsvwg-bounces@ietf.org
Errors-To: tsvwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: quoted-printable
> -----Original Message----- > From: Randall Stewart [mailto:randall@stewart.chicago.il.us] > Sent: Wednesday, November 24, 2004 9:14 AM > To: weddy@grc.nasa.gov > Cc: tsvwg@ietf.org > Subject: Re: [Tsvwg] multiaddressing > > > Ok, I will finally comment a bit on this :-0 > > Wesley Eddy wrote: > > On Mon, Nov 15, 2004 at 01:40:47PM -0500, Wesley Eddy wrote: > > > >>In draft-crocker-mast-analysis-01 (now expired), the concept of > >>"multiaddressing" for solving multihoming and mobility problems is > >>explained. > >> > > The crocker draft was just an attempt to take the > SCTP add-ip draft and duplicate it into a lower level.. I never > thought it would work since the reason we have been holding > the add-ip draft is the fact that there are security issues > with it. These should be solved as soon as we finish the > work on the auth draft.. but you can't do that without state which > means a shim layer can't do it.. unless you want to mirror all > the transport state at a layer below transport.. ughly and far > from simple... I know that first hand.. I am working on NAT > and SCTP and let me tell you its tricky when restarts can > show up .. and thats not even the multi-homing .. just single > homed SCTP :-0 > <snip> > > I just don't see how you can have anything simple below transport > doing this.. It just gets more and more complicated.. IMO we should > leave it where per-connection state can be maintained so one can > do the necessary things... > When you say "all the transport state", what do you mean? I do not see it as being that daunting, perhaps because I don't assume that a wedge implementation completely virtualizes all of the possible network paths so that transport is unaware of path changes. The wedge layer proposals (multi6 and HIP) assume that the wedge works out the security issues in binding addresses to hosts. And probably the NAT issues in the future as well. That leaves the congestion control, which should be tied somehow to distinct paths (distinct address pairs?). SCTP implementations will support multiple paths, so they probably won't not need much change at all in such a scenario. TCP doesn't support mobility, failover, or load balancing. Depending on how ambitious one decided to be at the wedge layer, one might try to duplicate all of SCTP's capability there (probably not), but at least a simple cwnd/ssthresh reset upon path change detection at the wedge layer should not be that difficult, and would allow mobility and failover multihoming to work correctly. Tom _______________________________________________ tsvwg mailing list tsvwg@ietf.org https://www1.ietf.org/mailman/listinfo/tsvwg
- [Tsvwg] multiaddressing Wesley Eddy
- RE: [Tsvwg] multiaddressing Henderson, Thomas R
- Re: [Tsvwg] multiaddressing Wesley Eddy
- Re: [Tsvwg] multiaddressing Yogesh Prem Swami
- Re: [Tsvwg] multiaddressing Wesley Eddy
- Re: [Tsvwg] multiaddressing Mark Allman
- Re: [Tsvwg] multiaddressing Wesley Eddy
- Re: [Tsvwg] multiaddressing Randall Stewart
- Re: [Tsvwg] multiaddressing Ted Faber
- Re: [Tsvwg] multiaddressing Wesley Eddy
- Re: [Tsvwg] multiaddressing Mark Allman
- Re: [Tsvwg] multiaddressing Ted Faber
- Re: [Tsvwg] multiaddressing Randall Stewart
- Re: [Tsvwg] multiaddressing Randall Stewart
- Re: [Tsvwg] multiaddressing Janardhan Iyengar
- Re: [Tsvwg] multiaddressing Janardhan Iyengar
- Re: [Tsvwg] multiaddressing Ted Faber
- Re: [Tsvwg] multiaddressing Janardhan Iyengar
- RE: [Tsvwg] multiaddressing Henderson, Thomas R
- Re: [Tsvwg] multiaddressing (private) Janardhan Iyengar
- Re: [Tsvwg] multiaddressing (private) Ted Faber
- Re: [Tsvwg] multiaddressing Ted Faber
- RE: [Tsvwg] multiaddressing Henderson, Thomas R
- Re: [Tsvwg] multiaddressing Ted Faber
- RE: [Tsvwg] multiaddressing Henderson, Thomas R
- Re: [Tsvwg] multiaddressing (private) Joe Touch
- Re: [Tsvwg] multiaddressing Joe Touch
- Re: [Tsvwg] multiaddressing Joe Touch
- Re: [Tsvwg] multiaddressing Ted Faber
- RE: [Tsvwg] multiaddressing Fleischman, Eric
- Re: [Tsvwg] multiaddressing Ted Faber
- Re: [Tsvwg] multiaddressing Ted Faber
- RE: [Tsvwg] multiaddressing Fleischman, Eric
- RE: [Tsvwg] multiaddressing Fleischman, Eric
- Re: [Tsvwg] multiaddressing Wesley Eddy
- Re: [Tsvwg] multiaddressing Joe Touch
- Re: [Tsvwg] multiaddressing Joe Touch
- Re: [Tsvwg] multiaddressing Joe Touch
- Re: [Tsvwg] multiaddressing Ted Faber
- Re: [Tsvwg] multiaddressing Wesley Eddy
- Re: [Tsvwg] multiaddressing Joe Touch
- Re: [Tsvwg] multiaddressing Joe Touch
- Re: [Tsvwg] multiaddressing Randall Stewart
- RE: [Tsvwg] multiaddressing Henderson, Thomas R
- Re: [Tsvwg] multiaddressing Randall Stewart