Simple Tunnel Endpoint Signaling in BGP
draft-xu-softwire-tunnel-endpoint-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Xiaohu Xu , Robert Raszuk | ||
| Last updated | 2011-03-08 | ||
| 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
The Softwire Mesh Framework provides a solution for intra-Autonomous System (AS) softwire, but not inter-AS softwire. The ability to provide inter-AS softwire extends the benefits of softwire to a larger scale. Indeed, the above Framework discusses the possibility of inter-AS softwire, but does not provide a solution. This document defines a specific BGP Extended Community attribute called the Tunnel Endpoint Extended Community, which allows for inter-AS softwire.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)