Layer2-Aware NAT
draft-miles-behave-l2nat-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | David Miles , Mark Townsley | ||
| Last updated | 2009-03-04 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-miles-behave-l2nat-00.txt
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.
Authors
David Miles
(david.miles@alcatel-lucent.com)
Mark Townsley
(mark@townsley.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)