Re: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers

Iljitsch van Beijnum <iljitsch@muada.com> Mon, 01 December 2008 21:15 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 069D23A698F; Mon, 1 Dec 2008 13:15:53 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C66F3A698F for <ietf@core3.amsl.com>; Mon, 1 Dec 2008 13:15:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.053
X-Spam-Level:
X-Spam-Status: No, score=-2.053 tagged_above=-999 required=5 tests=[AWL=-0.454, BAYES_00=-2.599, J_BACKHAIR_27=1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AN13fk6rULo4 for <ietf@core3.amsl.com>; Mon, 1 Dec 2008 13:15:51 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 3B0123A680E for <ietf@ietf.org>; Mon, 1 Dec 2008 13:15:51 -0800 (PST)
Received: from [192.168.0.192] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id mB1LEa1I008884 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 1 Dec 2008 22:14:42 +0100 (CET) (envelope-from iljitsch@muada.com)
Message-Id: <CE67747D-DE1F-47BB-982B-9080DBAE9CB5@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <FA256DDD-5C7B-4AD4-A8AA-ADC368F37162@cisco.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: [BEHAVE] Lack of need for 66nat : Long term impactto applicationdevelopers
Date: Mon, 01 Dec 2008 22:15:26 +0100
References: <200811262240.mAQMeC6Z045877@drugs.dv.isc.org><Pine.LNX.4.33.0811261455520.28290-100000@egate.xpasc.com> <075101c9501d$1344cf00$39ce6d00$@net> <2788466ED3E31C418E9ACC5C316615572FFBB6@mou1wnexmb09.vcorp.ad.vrsn.com> <FA256DDD-5C7B-4AD4-A8AA-ADC368F37162@cisco.com>
X-Mailer: Apple Mail (2.929.2)
Cc: IETF Discussion <ietf@ietf.org>, alh-ietf@tndh.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On 1 dec 2008, at 10:21, Fred Baker wrote:

> GSE/8+8 gives us the ability to manage the addresses we exchange in  
> routing down to a number of prefixes on the order of (eg equivalent  
> to a small multiple of) the number of autonomous systems.

Not really. Or rather, it will, at the following costs:

- all IPv6 implementations must be rewritten
- need an IPv6->GSE transition strategy but unlike v4->v6 addresses  
look the same
- still renumbering necessary when switching ISPs
- identity theft trivial unless we implement id<->locator security  
protocols
- no multihoming without extra protocols to detect and repair failures

See draft-ietf-ipngwg-esd-analysis-05.txt or
http://www.iab.org/about/workshops/routingandaddressing/routingws-gseproblems.pdf

As I've been saying for years: if you fix the problems with GSE, you  
end up with something that looks a lot like shim6.
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf