Carrying PWE3 Pseudo Wires over Provider Backbone Transport
draft-allan-pw-o-pbt-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David Allan | ||
| Last updated | 2007-07-10 | ||
| 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
Provider Backbone Transport (PBT, known as well as PBB-TE and progressed in IEEE as 802.1Qay [802.1Qay]) provides a mechanism where native Ethernet point-to-point tunnels can be configured or signaled across a provider-based Ethernet network [FEDYK]. PWE3 architecture defines a mechanism, called pseudowires, that emulates the essential attributes of a layer-2 and layer-1 service over a Packet Switched Network (PSN). This draft describes the architecture and procedures where Pseudowires are carried across PBT tunnels. In this proposal PBT tunnels are used as the PSN.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)