IETF Logo Mail Archive

Re: [Int-area] Revving draft-intarea-shared-addressing-issues

Bernard Aboba <bernard_aboba@hotmail.com> Mon, 14 June 2010 20:04 UTC

Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: int-area@core3.amsl.com
Delivered-To: int-area@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4F8B73A6934 for <int-area@core3.amsl.com>; Mon, 14 Jun 2010 13:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.814
X-Spam-Level:
X-Spam-Status: No, score=-0.814 tagged_above=-999 required=5 tests=[AWL=1.784, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 wI6inx9iH2TN for <int-area@core3.amsl.com>; Mon, 14 Jun 2010 13:04:44 -0700 (PDT)
Received: from blu0-omc1-s16.blu0.hotmail.com (blu0-omc1-s16.blu0.hotmail.com [65.55.116.27]) by core3.amsl.com (Postfix) with ESMTP id 307CE3A6933 for <int-area@ietf.org>; Mon, 14 Jun 2010 13:04:44 -0700 (PDT)
Received: from BLU137-W30 ([65.55.116.8]) by blu0-omc1-s16.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 14 Jun 2010 13:04:48 -0700
Message-ID: <BLU137-W306A1BCDBB7C8182DAC35293DC0@phx.gbl>
Content-Type: multipart/alternative; boundary="_24598209-c69b-46f7-8a10-c8d0528d5cf7_"
X-Originating-IP: [75.164.156.18]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: dthaler@microsoft.com, dwing@cisco.com, ford@isoc.org
Date: Mon, 14 Jun 2010 13:04:47 -0700
Importance: Normal
In-Reply-To: <9B57C850BB53634CACEC56EF4853FF652C05FEC1@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
References: <1339FDB5-B518-4210-9D7E-6711E4E10DB0@isoc.org>, <020401cb08ec$97759280$b94c150a@cisco.com> <4C11EB81.9090407@gmail.com>, <01ee01cb0a4c$1d528290$7844150a@cisco.com>, <6A8F3173-1CC1-4A0A-A96D-EE5AF1D8B58D@isoc.org>, <04b601cb0be9$308d1930$7844150a@cisco.com>, <9B57C850BB53634CACEC56EF4853FF652C05FEC1@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 14 Jun 2010 20:04:48.0081 (UTC) FILETIME=[D73ACC10:01CB0BFC]
Cc: "int-area@ietf.org" <int-area@ietf.org>, brian.e.carpenter@gmail.com, draft-ford-shared-addressing-issues@tools.ietf.org, lorenzo@google.com
Subject: Re: [Int-area] Revving draft-intarea-shared-addressing-issues
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/int-area>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2010 20:04:45 -0000

The NAT box can use its public IPv4 address to enable 6to4, thereby providing IPv6 support for hosts "behind" it.  Why would this result in a disconnected IPv6 island?


> From: dthaler@microsoft.com
> To: dwing@cisco.com; ford@isoc.org
> Date: Mon, 14 Jun 2010 19:04:31 +0000
> CC: int-area@ietf.org; brian.e.carpenter@gmail.com; draft-ford-shared-addressing-issues@tools.ietf.org; lorenzo@google.com
> Subject: Re: [Int-area] Revving draft-intarea-shared-addressing-issues
> 
> > Some routers enable 6to4 [RFC3056] on their WAN link.  6to4 requires a
> > publicly-routable IPv4 address.  Enabling 6to4 behind a NAT causes a
> > disconnected IPv6 island."
> 
> The last sentence above is incorrect.  The second sentence is correct.
> So one cannot "enable" 6to4 behind a NAT since one has no 
> publically-routable IPv4 address.  Hence one does not get an IPv6
> island.  One gets no IPv6 at all (from 6to4 anyway).
> 
> -Dave
> 
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area

v2.23.0 | Report a Bug | By Email