Re: [BEHAVE] [shara] Follow up on Layer2-Aware NAT (draft-miles-behave-l2nat-00)
"MILES DAVID" <David.Miles@alcatel-lucent.com.au> Sat, 28 March 2009 00:26 UTC
Return-Path: <David.Miles@alcatel-lucent.com.au>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D36B3A6859; Fri, 27 Mar 2009 17:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.634
X-Spam-Level:
X-Spam-Status: No, score=-2.634 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599]
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 AP+0mdrvRCgW; Fri, 27 Mar 2009 17:26:23 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 949283A67F8; Fri, 27 Mar 2009 17:26:23 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id n2S0RHFF010515; Fri, 27 Mar 2009 19:27:17 -0500 (CDT)
Received: from mail.apac.alcatel-lucent.com (h202-65-2-130.alcatel.com [202.65.2.130]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id n2S0RFtU024945; Fri, 27 Mar 2009 19:27:16 -0500 (CDT)
Received: from sgsinsbhs01.ad4.ad.alcatel.com (sgsinsbhs01.ap.lucent.com [135.254.109.34]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id n2S0QF3E025193; Sat, 28 Mar 2009 08:26:15 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.30]) by sgsinsbhs01.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 28 Mar 2009 08:27:14 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 28 Mar 2009 08:27:08 +0800
Message-ID: <986DCE2E44129444B6435ABE8C9E424D02F7E95D@SGSINSMBS02.ad4.ad.alcatel.com>
In-Reply-To: <D109C8C97C15294495117745780657AE0B7FD6FE@ftrdmel1>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [shara] Follow up on Layer2-Aware NAT (draft-miles-behave-l2nat-00)
Thread-Index: AcmgdlhcsqF9XOaRSFmUv5LfTG7d5QAAEU/wA2dPQ2AASTlpgA==
References: <986DCE2E44129444B6435ABE8C9E424D02D5CE0A@SGSINSMBS02.ad4.ad.alcatel.com> <D109C8C97C15294495117745780657AE0B7FD6FE@ftrdmel1>
From: MILES DAVID <David.Miles@alcatel-lucent.com.au>
To: pierre.levis@orange-ftgroup.com, behave@ietf.org, shara@ietf.org
X-OriginalArrivalTime: 28 Mar 2009 00:27:14.0285 (UTC) FILETIME=[F149D9D0:01C9AF3B]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
Subject: Re: [BEHAVE] [shara] Follow up on Layer2-Aware NAT (draft-miles-behave-l2nat-00)
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Mar 2009 00:26:24 -0000
Pierre, Thanks for the support. The presentation of draft-nishitani-cgn-01 outlined a good way forward - here the Network Model was separated from the core NAT Function. I think a L2-Aware NAT best belongs in a core document like this. In this way L2-Aware NAT could make up an optional component of the core NAT Function (in the way it describes a Virtual NAT [tables] facility). On top of this a variety of network models could be created and documented - these could even come from other working groups (such as Softwires).I believe a core NAT function (regardless of whether we describe IPv4 or IPv6) fits well in BEHAVE. Applying the mechanisms in L2-Aware NAT to PRR makes a lot of sense as well - I'm wondering if port-range solutions could be described (perhaps poorly) as similar to a NAPT mapping function (outside-ip/port to inside-ip/port) however in the case of PRR, the pairs are the same/common - in effect a address/port translation does not occur. What do you think of attempting to describe the PRR function like this? If agreeable I would like to invite the authors of PRR/A+P and CGN drafts to work within the bounds of a new draft that describes a core NAT function (without drawing reference to size or scale) - introducing elements of core NAT function (CGN/LSN) virtual NAPT tables (L2-Aware NAT), and mappings tables where translation is not applied (PRR). Best Regards, -David -----Original Message----- From: shara-bounces@ietf.org [mailto:shara-bounces@ietf.org] On Behalf Of pierre.levis@orange-ftgroup.com Sent: Thursday, March 26, 2009 6:17 AM To: behave@ietf.org; shara@ietf.org Subject: [shara] Follow up on Layer2-Aware NAT (draft-miles-behave-l2nat-00) The comment I had on the mike during behave session 2: This kind of work is very valuable, it is worth not only for CGN but also for Port Ranges solutions and for all IPv4 shortage solutions. As we presented it in the shara BoF all solutions basically: 1) Put a dedicated function in an ISP Box (CGN, PRR, whatever) 2) Use some sort of transport mechanism (tunneling, layer 2, whatever) between customers and ISPBox, 3) Are confronted with the same issues: how to force a route from customers to ISPBox, how to route back from ISPBox to relevant customer, how to identify the customer. This would advocate for seeing all work related to IPv4 shared addresses host in the same place, under the same ombrella. Regards Pierre _______________________________________________ shara mailing list shara@ietf.org https://www.ietf.org/mailman/listinfo/shara
- [BEHAVE] FW: Layer2-Aware NAT (draft-miles-behave… MILES DAVID
- Re: [BEHAVE] [shara] Layer2-Aware NAT (draft-mile… pierre.levis
- [BEHAVE] Follow up on Layer2-Aware NAT (draft-mil… pierre.levis
- Re: [BEHAVE] [shara] Follow up on Layer2-Aware NA… MILES DAVID
- Re: [BEHAVE] [shara] Follow up on Layer2-Aware NA… Randy Bush
- Re: [BEHAVE] [shara] Follow up on Layer2-Aware NA… Gabor Bajko
- Re: [BEHAVE] [shara] Follow up on Layer2-Aware NA… MILES DAVID
- Re: [BEHAVE] [shara] Follow up on Layer2-Aware NA… pierre.levis