PWE3 Working Group Chris Metz Internet Draft Luca Martini Expires: August 2006 Cisco Systems Florin Balus Jeff Sugimoto Nortel Networks February 25, 2006 Pseudowire Attachment Identifiers for Aggregation and VPN Autodiscovery draft-ietf-pwe3-aii-aggregate-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. This document may only be posted in an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html This Internet-Draft will expire on August 25, 2006. Metz, et al. Expires May 2006 [Page 1] Internet-Draft AII Types for Aggregation September 2005 Copyright Notice Copyright (C) The Internet Society (2006). All Rights Reserved. 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 (AII). This document defines AII structures in the form of new AII type-length- value fields that support AII aggregation for improved scalability and VPN autodiscovery. 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. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 Error! Reference source not found.. Table of Contents 1. Introduction...................................................2 2. Structure for the New AII Type.................................4 2.1. AII Type 1................................................4 2.2. AII Type 2................................................4 3. IANA Considerations............................................6 4. Security Considerations........................................6 5. Acknowledgments................................................6 Author's Addresses................................................7 Intellectual Property Statement...................................8 Disclaimer of Validity............................................8 Copyright Statement...............................................8 Acknowledgment....................................................9 1. Introduction [PWE3-CONTROL] defines the signaling mechanisms for establishing point-to-point pseudowires (PWs) between two provider edge (PE) nodes. When a PW is set up, the LDP signaling messages include a forwarding equivalence class (FEC) element containing information about the PW type and an endpoint identifier used in the selection of Metz, et al. Expires August 2006 [Page 2] Internet-Draft AII Types for Aggregation September 2005 the PW forwarder that binds the PW to the attachment circuit at each end. There are two types of FEC elements defined for this purpose: PWid FEC (type 128) and the Generalized ID (GID) FEC (type 129). The PWid FEC element includes a fixed-length 32 bit value called the PWid that serves as an endpoint identifier. The same PWid value must be configured on the local and remote PE prior to PW setup. The GID FEC element includes TLV fields for attachment individual identifiers (AII) that, in conjunction with an attachment group identifier (AGI), serve as PW endpoint identifiers. The endpoint identifier on the local PE (denoted as