Subject: Re: [BEHAVE] [shara] Layer2-Aware NAT (draft-miles-behave-l2nat-00)

From: <[email-masked]>
Date: Mon, 9 Mar 2009 10:03:09 +0100

Hi,

Very interesting to cope with the IPv4 public AND private address exhaustion.

Actually what you propose can be used not only for CGN but also for port range solutions.
In port range solutions we have a PRR (Port Range Router) in the ISP network instead of a CGN, and we are also confronted with routing between CPEs and PRR.
As you mention, the best way would be IPv6 encap, but in case IPv6 is not deployed in the CPEs and access, Layer2-aware mechanisms are good alternatives.

I back the proposal of a larger CGN document.

Regards

Pierre

-----Message d'origine-----
De : [email-masked] [mailto:[email-masked]] De la part de MILES DAVID
Envoyé : lundi 9 mars 2009 06:18
À : [email-masked]; [email-masked]; Mark Townsley
Objet : [shara] Layer2-Aware NAT (draft-miles-behave-l2nat-00)

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.

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.
_______________________________________________
shara mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/shara