RFC 5003: Attachment Individual Identifier (AII) Types for Aggregation
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC5003
- Published
- September 2007
- Authors
- C. Metz; L. Martini; F. Balus; J. Sugimoto
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5087Time Division Multiplexing over IP (TDMoIP)Current
December 2007
- RFC 5254Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)Current
October 2008
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
- RFC 5301Dynamic Hostname Exchange Mechanism for IS-ISUpdated
October 2008
- RFC 5308Routing IPv6 with IS-ISUpdated
October 2008
- RFC 4667Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)Current
September 2006
- RFC 4619Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) NetworksCurrent
September 2006
- RFC 4618Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS NetworksCurrent
September 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?