Re: [Architecture-discuss] 8+8 history (Re: Sources of architectural change)

Geoff Huston <gih@apnic.net> Wed, 02 November 2005 18:38 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EXNUy-0007xK-5q; Wed, 02 Nov 2005 13:38:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EXNUu-0007sn-JY for architecture-discuss@megatron.ietf.org; Wed, 02 Nov 2005 13:38:10 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29648 for <architecture-discuss@ietf.org>; Wed, 2 Nov 2005 13:37:46 -0500 (EST)
Received: from kahuna.telstra.net ([203.50.0.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EXNjX-0000it-ST for architecture-discuss@ietf.org; Wed, 02 Nov 2005 13:53:16 -0500
Received: from gihm3.apnic.net (dhcp18.potaroo.net [203.10.60.18]) by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id jA2IbUXt044894; Thu, 3 Nov 2005 05:37:32 +1100 (EST) (envelope-from gih@apnic.net)
Message-Id: <6.2.0.14.2.20051103052359.02c57828@kahuna.telstra.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Thu, 03 Nov 2005 05:37:26 +1100
To: Harald Tveit Alvestrand <harald@alvestrand.no>, Tony Li <tony.li@tony.li>, Leslie Daigle <leslie@thinkingcat.com>
From: Geoff Huston <gih@apnic.net>
Subject: Re: [Architecture-discuss] 8+8 history (Re: Sources of architectural change)
In-Reply-To: <6FD12FDCBB470881DF31DCEC@svartdal.hjemme.alvestrand.no>
References: <20051027122404.F31AA86AEE@mercury.lcs.mit.edu> <B0F996AD-8A42-43DF-874A-C6E67CB2F1DE@tony.li> <Pine.LNX.4.64.0510290935250.11815@netcore.fi> <AB9465E06F2E97C7E7F7E674@svartdal.hjemme.alvestrand.no> <CF6037C6-175B-4439-AECA-F5A7A5996356@tony.li> <4368482B.2020808@thinkingcat.com> <33C7305E-DCCB-4094-B8BD-1F3BDEFFBC63@tony.li> <4368580A.4040607@thinkingcat.com> <E3B3196D-23E1-4EC0-9979-C8AE75E57EC6@tony.li> <6FD12FDCBB470881DF31DCEC@svartdal.hjemme.alvestrand.no>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: architecture-discuss@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/architecture-discuss>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
Sender: architecture-discuss-bounces@ietf.org
Errors-To: architecture-discuss-bounces@ietf.org

>
>The first isn't even available from bgp.potaroo.net; the second is.


It is now - thanks for letting me know

http://draft-odell-8.potaroo.net/


>The IPNG WG seemed to achieve "rough consensus" that GSE was not a viable 
>approach; the arguments against GSE were summarized in the draft 
>draft-ietf-ipngwg-esd-analysis.
>
>At some later time, this draft was proposed for publication.
>
>This was in the Bad Days Before Tracker, so I'm operating strictly from 
>memory, both with dates and conclusions... my memory says that the IESG 
>questioned the justification for some of the claims in the draft regarding 
>the percieved security weaknesses of GSE and sent it back to the WG; it 
>never returned.
>
>Version -05 of that draft has a date of October 1999; version -00 had a 
>date of March 1997, and was written as *accepting* ESD, so while the end 
>result was probably a termination of discussion, the process did take 2.5 
>years to get that far.
>
>WRT what it would take to bring it back: At the current stage of IPv6, it 
>seems to me that it would take someone working through how to allow one 
>subnet in a classical IPv6 network to use 8+8 while the rest of the world 
>didn't..... apparently nobody's seriously suggested that in Multi6.... I 
>don't know if it's workable.....


To be best of my recollection this did not resurface in the multi6 effort - 
although its true to say that most forms of rewriting parts of the packet 
header by some form of foreign agent were reviewed in multi6. The issues of 
knowing (and being able to reliably detect)  the difference between a 
'friendly and helpful" rewrite and a "hostile effort at session hijack" 
remained significant issues with the foreign agent rewrite approaches. Like 
Harald my recollection of this in 1999 was that there was a similar concern 
over 8+8.

Certainly this is once more an active topic, in that the issues here appear 
to be a rather tough trade-off between control of the security issues in a 
host-based approach to this topic (such as shim6) and a site/ locale-based 
approach to this topic (such as gse approaches).

Among the detritus of unfinished work there was an effort by myself and 
Margaret Wasserman to write up the multi6 proposals - an early draft is in 
an appendix of 
http://smakd.potaroo.net/ietf/all-ids/draft-huston-multi6-architectures-00.txt-76090.txt. 
As I recall someone else volunteered at a multi6wg meeting to take on this 
as a separate draft - but no further progress was made


Geoff






_______________________________________________
Architecture-discuss mailing list
Architecture-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/architecture-discuss