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

"Dan Wing" <dwing@cisco.com> Mon, 14 June 2010 19:48 UTC

Return-Path: <dwing@cisco.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 69C753A6903 for <int-area@core3.amsl.com>; Mon, 14 Jun 2010 12:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.484
X-Spam-Level:
X-Spam-Status: No, score=-9.484 tagged_above=-999 required=5 tests=[AWL=1.115, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 RoipPZzM2Yig for <int-area@core3.amsl.com>; Mon, 14 Jun 2010 12:47:56 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 60F183A6934 for <int-area@ietf.org>; Mon, 14 Jun 2010 12:47:46 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtMJAMYkFkxAZnwN/2dsb2JhbACHY4EUlXVxpkCaFYUaBINNg0E
X-IronPort-AV: E=Sophos;i="4.53,415,1272844800"; d="scan'208";a="121631517"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 14 Jun 2010 19:47:40 +0000
Received: from dwingwxp01 (sjc-vpn2-998.cisco.com [10.21.115.230]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o5EJlb4g027860; Mon, 14 Jun 2010 19:47:37 GMT
From: Dan Wing <dwing@cisco.com>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Dave Thaler' <dthaler@microsoft.com>, 'Matthew Ford' <ford@isoc.org>
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> <056301cb0bf6$1fd9aa10$7844150a@cisco.com> <E1829B60731D1740BB7A0626B4FAF0A649E133B67F@XCH-NW-01V.nw.nos.boeing.com>
Date: Mon, 14 Jun 2010 12:47:37 -0700
Message-ID: <057901cb0bfa$72034ea0$7844150a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AQHLCJzpPlC2L8n+eEa0/YO9dB51gJJ8PUGAgACdQ4CAAiHRAIACrQsAgACNHQD//6BPQIAAAmtAgAAHmYCAAAJDMA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A649E133B67F@XCH-NW-01V.nw.nos.boeing.com>
Cc: int-area@ietf.org, 'Brian E Carpenter' <brian.e.carpenter@gmail.com>, draft-ford-shared-addressing-issues@tools.ietf.org, 'Lorenzo Colitti' <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 19:48:01 -0000

> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com] 
> Sent: Monday, June 14, 2010 12:40 PM
> To: Dan Wing; 'Dave Thaler'; 'Matthew Ford'
> Cc: int-area@ietf.org; 'Brian E Carpenter'; 
> draft-ford-shared-addressing-issues@tools.ietf.org; 'Lorenzo Colitti'
> Subject: RE: [Int-area] Revving draft-intarea-shared-addressing-issues
> 
> > Enabling 6to4 behind a NAT causes a disconnected IPv6 island.
> 
> s/NAT/proto-41 filtering firewall/

True.  However this document is discussing IP address sharing 
(not firewalls, nor all of other failures of IPv6-over-IPv4
tunneling.)

-d


> Fred
> fred.l.templin@boeing.com
> 
> > -----Original Message-----
> > From: int-area-bounces@ietf.org 
> [mailto:int-area-bounces@ietf.org] On Behalf Of Dan Wing
> > Sent: Monday, June 14, 2010 12:17 PM
> > To: 'Dave Thaler'; 'Matthew Ford'
> > Cc: int-area@ietf.org; 'Brian E Carpenter'; 
> draft-ford-shared-addressing-issues@tools.ietf.org;
> > 'Lorenzo Colitti'
> > Subject: Re: [Int-area] Revving 
> draft-intarea-shared-addressing-issues
> > 
> > > -----Original Message-----
> > > From: Dave Thaler [mailto:dthaler@microsoft.com]
> > > Sent: Monday, June 14, 2010 12:05 PM
> > > To: Dan Wing; 'Matthew Ford'
> > > Cc: int-area@ietf.org; 'Brian E Carpenter';
> > > draft-ford-shared-addressing-issues@tools.ietf.org; 
> 'Lorenzo Colitti'
> > > 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).
> > 
> > I was attempting to summarize the problem that has been 
> ascribed to Apple's
> > Airport Extreme routers turning on 6to4, which is mentioned 
> in many threads on
> > the Internet including
> > http://www.ops.ietf.org/lists/v6ops/v6ops.2008/msg00263.html
> > 
> > If there is more accurate wording, I'm all for it.  I would like
> > some discussion of CPE (and hosts) blindly enabling 6to4 causing
> > problems when the CPE's IPv4 WAN address is shared.
> > 
> > -d
> > 
> > _______________________________________________
> > Int-area mailing list
> > Int-area@ietf.org
> > https://www.ietf.org/mailman/listinfo/int-area