Re: [Int-area] Revving draft-intarea-shared-addressing-issues
Matthew Ford <ford@isoc.org> Mon, 14 June 2010 09:19 UTC
Return-Path: <ford@isoc.org>
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 F23F13A6868 for <int-area@core3.amsl.com>; Mon, 14 Jun 2010 02:19:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.185
X-Spam-Level:
X-Spam-Status: No, score=-101.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 tx2sxRcfq+lH for <int-area@core3.amsl.com>; Mon, 14 Jun 2010 02:19:02 -0700 (PDT)
Received: from smtp211.iad.emailsrvr.com (smtp211.iad.emailsrvr.com [207.97.245.211]) by core3.amsl.com (Postfix) with ESMTP id 0C2A13A68A4 for <int-area@ietf.org>; Mon, 14 Jun 2010 02:19:02 -0700 (PDT)
Received: from relay11.relay.iad.mlsrvr.com (localhost [127.0.0.1]) by relay11.relay.iad.mlsrvr.com (SMTP Server) with ESMTP id 601E11B6E16; Mon, 14 Jun 2010 05:19:05 -0400 (EDT)
Received: by relay11.relay.iad.mlsrvr.com (Authenticated sender: ford-AT-isoc.org) with ESMTPSA id 8FE201B40BF; Mon, 14 Jun 2010 05:19:04 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: Matthew Ford <ford@isoc.org>
In-Reply-To: <01ee01cb0a4c$1d528290$7844150a@cisco.com>
Date: Mon, 14 Jun 2010 10:19:02 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <6A8F3173-1CC1-4A0A-A96D-EE5AF1D8B58D@isoc.org>
References: <1339FDB5-B518-4210-9D7E-6711E4E10DB0@isoc.org> <020401cb08ec$97759280$b94c150a@cisco.com> <4C11EB81.9090407@gmail.com> <01ee01cb0a4c$1d528290$7844150a@cisco.com>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1078)
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 09:19:03 -0000
Hi Dan, On 12 Jun 2010, at 17:27, Dan Wing wrote: > > >> -----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. > Care to offer (or point me to) some text on this point? Mat
- Re: [Int-area] Revving draft-intarea-shared-addre… Brian E Carpenter
- [Int-area] Revving draft-intarea-shared-addressin… Matthew Ford
- Re: [Int-area] Revving draft-intarea-shared-addre… Brian E Carpenter
- Re: [Int-area] Revving draft-intarea-shared-addre… Dan Wing
- Re: [Int-area] Revving draft-intarea-shared-addre… Dan Wing
- Re: [Int-area] Revving draft-intarea-shared-addre… Brian E Carpenter
- Re: [Int-area] Revving draft-intarea-shared-addre… Matthew Ford
- Re: [Int-area] Revving draft-intarea-shared-addre… Dan Wing
- Re: [Int-area] Revving draft-intarea-shared-addre… Dan Wing
- Re: [Int-area] Revving draft-intarea-shared-addre… Dave Thaler
- Re: [Int-area] Revving draft-intarea-shared-addre… Dan Wing
- Re: [Int-area] Revving draft-intarea-shared-addre… Templin, Fred L
- Re: [Int-area] Revving draft-intarea-shared-addre… Matthew Ford
- Re: [Int-area] Revving draft-intarea-shared-addre… Dan Wing
- Re: [Int-area] Revving draft-intarea-shared-addre… Dave Thaler
- Re: [Int-area] Revving draft-intarea-shared-addre… Dave Thaler
- Re: [Int-area] Revving draft-intarea-shared-addre… Bernard Aboba
- Re: [Int-area] Revving draft-intarea-shared-addre… Dan Wing
- Re: [Int-area] Revving draft-intarea-shared-addre… Dave Thaler
- Re: [Int-area] Revving draft-intarea-shared-addre… George, Wes E IV [NTK]
- Re: [Int-area] Revving draft-intarea-shared-addre… Dan Wing
- Re: [Int-area] Revving draft-intarea-shared-addre… Dave Thaler
- Re: [Int-area] Revving draft-intarea-shared-addre… Brian E Carpenter
- Re: [Int-area] Revving draft-intarea-shared-addre… Dave Thaler
- Re: [Int-area] Revving draft-intarea-shared-addre… Christian Vogt
- Re: [Int-area] Revving draft-intarea-shared-addre… pierre.levis
- Re: [Int-area] Revving draft-intarea-shared-addre… Lorenzo Colitti
- Re: [Int-area] Revving draft-intarea-shared-addre… Dan Wing
- Re: [Int-area] Revving draft-intarea-shared-addre… Joe Touch