Stateless Address Mapping (SAM) - Mesh Softwires without e-BGP
draft-despres-softwire-mesh-sam-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Rémi Després | ||
| Last updated | 2009-10-26 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
SAM is a generic and simple mechanism for packets having addresses in a family IPvX to traverse routing domains where this address family is not directly routed. SAM topological scenarios are those of Mesh Softwire, i.e. with point to multipoint tunnels between border nodes of interior routing domains. In the mesh-softwire context, SAM differs from RFC 5565 in that SAM uses no protocol between border nodes of the domain, and in that customer border nodes don't need to maintain states for all other border nodes. (RFC 5565 is based on an Exterior Border-Gateway Protocol e-BGP between border nodes, with dynamic routing tables to be maintained in all of them). SAM's address mappings are stateless, based on only a few domain parameters. SAM is thus suitable to small to medium enterprises, and small to medium ISPs, that cannot afford e-BGP in all their border nodes. All combinations of IPv4 and IPv6, global or private, are supported. Also, to mitigate consequences of the IPv4 address shortage, SAM supports port-extended IPv4 addresses (A+P).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)