Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE charter

Rémi Després <remi.despres@free.fr> Tue, 21 October 2008 06:29 UTC

Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 368C53A6AF9; Mon, 20 Oct 2008 23:29:53 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 785D53A69CF; Mon, 20 Oct 2008 23:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.761
X-Spam-Level:
X-Spam-Status: No, score=-1.761 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
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 SsqAsSD-JrAZ; Mon, 20 Oct 2008 23:29:50 -0700 (PDT)
Received: from smtp6-g19.free.fr (smtp6-g19.free.fr [212.27.42.36]) by core3.amsl.com (Postfix) with ESMTP id ADBB73A6869; Mon, 20 Oct 2008 23:29:50 -0700 (PDT)
Received: from smtp6-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp6-g19.free.fr (Postfix) with ESMTP id E85AC17258; Tue, 21 Oct 2008 08:31:03 +0200 (CEST)
Received: from ordinateur-de-remi-despres.local (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by smtp6-g19.free.fr (Postfix) with ESMTP id 1067E19740; Tue, 21 Oct 2008 08:31:02 +0200 (CEST)
Message-ID: <48FD76D0.9050509@free.fr>
Date: Tue, 21 Oct 2008 08:29:36 +0200
From: Rémi Després <remi.despres@free.fr>
User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914)
MIME-Version: 1.0
To: Margaret Wasserman <mrw@lilacglade.org>
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com> <3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com> <200810201358.29295.remi.denis-courmont@nokia.com> <930B8AEC-9FA5-4FCF-AA6C-EC5064FA3AB7@lilacglade.org>
In-Reply-To: <930B8AEC-9FA5-4FCF-AA6C-EC5064FA3AB7@lilacglade.org>
Cc: 'Behave WG' <behave@ietf.org>, v4v6interim@ietf.org, 46translation@employees.org
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6 coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

Margaret Wasserman   (m/j/a) 10/20/08 4:50 PM:
> I don't _want_ NAT66 to be deployed any more than the rest of you, but 
> I believe it is inevitable. 
Although I also believe that IPv6 NATs will be deployed, there is IMO a 
competitive alternative, say SAM66, to implement purely local routing 
plans  in private sites.

It is an IPv6-IPv6 application of the Static Address Mapping approach 
(SAM) I presented in Montreal:
-  E2E IPv6 packets, where they  traverse private routing networks, are 
locally encapsulated (somewhat like for ISATAP, but IPv6 in IPv6).
-  Border routers of customer sites derive intra-site addresses from 
global addresses by substituting an intra-site header to an ISP site prefix.

Its advantages include:
- No interference with the DNS (global addresses are the only needed ones ).
- No interference with transport checksums.
- Stateless operation of border routers (scalability and resilience)
- Openness to site multi-homing with a unique intra-site routing plan 
(yet to be documented ).

Its main drawback is clearly that hosts have to be upgraded (very simple 
addition, yet a real one).  Also,  participation of DHCPv6 (or router 
advertisements?) is needed  to automate configuration. A possible 
consequence that  SAM66 and NAT66 will have to coexist.


Best regards,

RD

_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim