IETF Logo Mail Archive

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

"Dan Wing" <dwing@cisco.com> Tue, 29 June 2010 20:00 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 B418F3A693A for <int-area@core3.amsl.com>; Tue, 29 Jun 2010 13:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.338
X-Spam-Level:
X-Spam-Status: No, score=-9.338 tagged_above=-999 required=5 tests=[AWL=0.261, BAYES_00=-2.599, J_BACKHAIR_11=1, 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 nvtJso2BiMHs for <int-area@core3.amsl.com>; Tue, 29 Jun 2010 13:00:13 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id A58383A67B4 for <int-area@ietf.org>; Tue, 29 Jun 2010 13:00:13 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EADHtKUyrR7Ht/2dsb2JhbACUK4sicaYomj+FJASDaQ
X-IronPort-AV: E=Sophos;i="4.53,506,1272844800"; d="scan'208";a="151578956"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 29 Jun 2010 20:00:24 +0000
Received: from dwingWS (sjc-vpn7-1923.cisco.com [10.21.151.131]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o5TK0LYl026960; Tue, 29 Jun 2010 20:00:21 GMT
From: Dan Wing <dwing@cisco.com>
To: '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> <66F07E5A-8FA7-4A7C-A56D-E3E13514F631@isoc.org>
In-Reply-To: <66F07E5A-8FA7-4A7C-A56D-E3E13514F631@isoc.org>
Date: Tue, 29 Jun 2010 13:00:20 -0700
Message-ID: <07be01cb17c5$b5e4fbb0$21aef310$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: en-us
Thread-Index: AcsXjzNhmiE9Q3pOQNeY09IzwpzvWwANllOg
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: Tue, 29 Jun 2010 20:00:14 -0000

> -----Original Message-----
> From: Matthew Ford [mailto:ford@isoc.org]
> Sent: Tuesday, June 29, 2010 6:30 AM
> To: Dan Wing
> Cc: 'Brian E Carpenter'; int-area@ietf.org; draft-ford-shared-
> addressing-issues@tools.ietf.org; 'Lorenzo Colitti'
> Subject: Re: Revving draft-intarea-shared-addressing-issues
> 
> Dan,
> 
> On 14 Jun 2010, at 18:44, Dan Wing wrote:
> 
> 8< snip >8
> 
> >
> > Here is a shot at some text:
> >
> >
> > "There are several commonly-deployed mechanisms that support
> > operating servers behind a NAT by forwarding a specific TCP
> > or UDP ports to a specific internal host ([UPnP-IGD],
> > [I-D.cheshire-nat-pmp], and manual HTML configuration).  All
> > of these mechanisms assume the NAT's WAN address is a
> > publicly-routable IP address, and fail to work normally
> > when that assumption is wrong.  There have been attempts to
> > avoid that problem by disabling the NAT function and merely
> > bridging traffic (is is required for [Windows-Logo]
> > certification), but this only works if the WAN address is
> > a specific address, and bridging (rather than NATting) has
> > other side effects (DHCP requests are served by an upstream
> > DHCP server which can increase complexity of in-home
> > networking).
> 
> Thanks for this. Can you clarify the the point about 'this only works
> if the WAN address is a specific address' - this isn't clear to me at
> least.

Reword to:

  ... and the bridging function is triggered when certain specific WAN
  addresses is assigned

better?

-d


>   - Mat=

v2.23.0 | Report a Bug | By Email