AII Types for Aggregation
draft-metz-aii-aggregate-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Chris Metz | ||
Last updated | 2005-10-21 | ||
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
[PWE3 Control] defines the signaling mechanisms for establishing point-to-point pseudowires between two provider edge (PE) nodes. The Generalized ID FEC element contained in PWE3 signaling protocols include TLV fields that identify pseudowire endpoints called attachment individual identifiers (AII). This document defines an AII structure in the form of new AII type-length-value fields that supports AII aggregation for improved scalability. It is envisioned that this would be useful in large inter-domain virtual private wire service networks where pseudowires are established between selected local and remote PE nodes based on customer need.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)