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

"Dan Wing" <dwing@cisco.com> Sat, 12 June 2010 16:27 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 EEF213A68E7 for <int-area@core3.amsl.com>; Sat, 12 Jun 2010 09:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.277
X-Spam-Level:
X-Spam-Status: No, score=-8.277 tagged_above=-999 required=5 tests=[AWL=-0.278, BAYES_50=0.001, 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 vdK+Gl7JK93x for <int-area@core3.amsl.com>; Sat, 12 Jun 2010 09:27:16 -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 BC2873A6837 for <int-area@ietf.org>; Sat, 12 Jun 2010 09:27:15 -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: AoYKALpRE0xAZnwN/2dsb2JhbACHY4EUlgxxpQiZQoUaBINN
X-IronPort-AV: E=Sophos;i="4.53,408,1272844800"; d="scan'208";a="121020825"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 12 Jun 2010 16:27:18 +0000
Received: from dwingwxp01 ([10.32.240.194]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o5CGREOO012670; Sat, 12 Jun 2010 16:27:15 GMT
From: Dan Wing <dwing@cisco.com>
To: 'Brian E Carpenter' <brian.e.carpenter@gmail.com>
References: <1339FDB5-B518-4210-9D7E-6711E4E10DB0@isoc.org> <020401cb08ec$97759280$b94c150a@cisco.com> <4C11EB81.9090407@gmail.com>
Date: Sat, 12 Jun 2010 09:27:10 -0700
Message-ID: <01ee01cb0a4c$1d528290$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: AcsJOznwY1SR6xwwTK+jC8JOdu+eKABEF5rA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <4C11EB81.9090407@gmail.com>
Cc: int-area@ietf.org, 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: Sat, 12 Jun 2010 16:27:17 -0000

 

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] 
> Sent: Friday, June 11, 2010 12:54 AM
> To: Dan Wing
> Cc: 'Matthew Ford'; int-area@ietf.org; 
> draft-ford-shared-addressing-issues@tools.ietf.org; 'Lorenzo Colitti'
> Subject: Re: Revving draft-intarea-shared-addressing-issues
> 
> On 2010-06-11 10:30, Dan Wing wrote:
> ...
> >>  o Add some text to clarify that whether we're talking about 
> >> DS-LITE, NAT64 or NAT444 isn't especially important - it's 
> >> the view from the outside that matters, and given that, most 
> >> of the issues apply regardless of the specific address 
> >> sharing scenario in question.
> > 
> > That would be good.  Should be NAT44 (not "444"), though.  The
> > problem of IP address sharing is orthogonal to the subscriber
> > operating their own NAT in their house (which is one of the
> > 4's of NAT444).
> 
> Really, in every single case? I thought there were cases
> where single-NAT traversal works and double-NAT traversal doesn't.

Yes, there are such cases.  And those cases should be called 
out.

> Certainly the issues of subscriber identification and geolocation
> are significantly worse for NAT444 than for NAT44.

If we consider home routers with 802.11, geolocation works as well
with or without NAT -- the WiFi device could be in the living room
or maybe the back yard, but won't be much farther away.  Subscriber
ID works as well as telephone numbers (can't tell if it's me or
my wife or my kid using my telephone -- just know it is someone
at my house).

> Also, A+P should be in the list.

Agreed.

-d