[BEHAVE] FW: Layer2-Aware NAT (draft-miles-behave-l2nat-00)

"MILES DAVID" <David.Miles@alcatel-lucent.com.au> Mon, 09 March 2009 05:19 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 83E763A6864 for <behave@core3.amsl.com>; Sun, 8 Mar 2009 22:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 APHN5DUhEHtn for <behave@core3.amsl.com>; Sun, 8 Mar 2009 22:19:45 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 9A1713A63EC for <behave@ietf.org>; Sun, 8 Mar 2009 22:19:45 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id n295KEjI013877 for <behave@ietf.org>; Mon, 9 Mar 2009 00:20:14 -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 n295KCwg022032 for <behave@ietf.org>; Mon, 9 Mar 2009 00:20:13 -0500 (CDT)
Received: from sgsinsbhs02.ad4.ad.alcatel.com (sgsinsbhs02.ap.lucent.com [135.254.109.35]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id n294nlFg010349 for <behave@ietf.org>; Mon, 9 Mar 2009 12:49:47 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.29]) by sgsinsbhs02.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 9 Mar 2009 13:20:11 +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: Mon, 09 Mar 2009 13:19:53 +0800
Message-ID: <986DCE2E44129444B6435ABE8C9E424D02D5CE0A@SGSINSMBS02.ad4.ad.alcatel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Layer2-Aware NAT (draft-miles-behave-l2nat-00)
Thread-Index: AcmgdlhcsqF9XOaRSFmUv5LfTG7d5QAAEU/w
From: MILES DAVID <David.Miles@alcatel-lucent.com.au>
To: behave@ietf.org
X-OriginalArrivalTime: 09 Mar 2009 05:20:11.0183 (UTC) FILETIME=[B81663F0:01C9A076]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
Subject: [BEHAVE] FW: 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: Mon, 09 Mar 2009 05:19:46 -0000

All,

A new method for NAT44 has been posted based on some of the work in the
Montreal v4/v6 coexistence meeting and methods described in Dual Stack
Lite.
L2-Aware NAT proposes a virtual NAT mapping table for each layer2
connection (be that VLAN, ATM, PPP or L2TP [similar to Dual Stack
Lite]).

We would see this work merging into a larger CGN document. The draft
will be presented in the BEHAVE session at IETF74.

Comments are most welcome!

Best Regards,

-David


http://tools.ietf.org/html/draft-miles-behave-l2nat-00


Filename:	 draft-miles-behave-l2nat
Revision:	 00
Title:		 Layer2-Aware NAT
Creation_date:	 2009-03-04
WG ID:		 Independent Submission
Number_of_pages: 16

Abstract:
This document describes a "Layer2-Aware" IPv4-to-IPv4 (NAT44) Service
Provider NAT function that identifies subscriber traffic based on IP-
independent methods such as a link-layer address, VLAN, PPP session,
tunnel, etc. in order to allow one to either avoid "double-NAT"
(NAT444) of subscriber IP traffic altogether, the need for additional
"Shared Service-Provider" IPv4 address space, or partitioning of RFC
1918 space between subscribers.  While the mechanisms described in this
document may be applicable to a variety of network architectures, the
primary focus is on residential "fixed-line"
Internet access.