RFC 5003

Attachment Individual Identifier (AII) Types for Aggregation, September 2007

Canonical URL:
https://www.rfc-editor.org/rfc/rfc5003.txt
File formats:
Plain TextPDF
Status:
PROPOSED STANDARD
Authors:
C. Metz
L. Martini
F. Balus
J. Sugimoto
Stream:
IETF
Source:
pwe3 (int)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC5003

Discuss this RFC: Send questions or comments to pwe3@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

The signaling protocols used to establish point-to-point pseudowires include type-length-value (TLV) fields that identify pseudowire endpoints called attachment individual identifiers (AIIs). This document defines AII structures in the form of new AII TLV fields that support AII aggregation for improved scalability and Virtual Private Network (VPN) auto-discovery. 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 provider edge (PE) nodes based on customer need. [STANDARDS-TRACK]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader



Search RFCs
Advanced Search
×