Search RFCs
RFC 5003
Attachment Individual Identifier (AII) Types for Aggregation,September 2007
- File formats:
- Status:
- PROPOSED STANDARD
- Authors:
- C. Metz
L. Martini
F. Balus
J. Sugimoto - Stream:
- IETF
- Source:
- pwe3 (int)
Cite this RFC:TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC5003
Discuss this RFC: Send questions or comments to the mailing listpals@ietf.org
Other actions:View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 5003
Abstract
The signaling protocols used to establish point-to-point pseudowiresinclude type-length-value (TLV) fields that identify pseudowireendpoints called attachment individual identifiers (AIIs). Thisdocument defines AII structures in the form of new AII TLV fields thatsupport AII aggregation for improved scalability and Virtual PrivateNetwork (VPN) auto-discovery. It is envisioned that this would beuseful in large inter-domain virtual private wire service networkswhere pseudowires are established between selected local and remoteprovider edge (PE) nodes based on customer need. [STANDARDS-TRACK]
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.