Type of Project: Amendment to IEEE Standard 802.1AX-2008 1.1 Project Number: P802.1AXb? 2.1 Title: Standard for Local and metropolitan area networks--Link Aggregation Amendment: Resilient Network-Network Interface 5.2 Scope: This standard enhances the Link Aggregation Control Protocol and its managed objects to support a resilient Network-Network Interface between a pair of Provider Bridged or Provider Backbone Bridged Networks. 5.3 Is the completion of this standard dependent upon the completion of another standard: No 5.4 Purpose: The purpose of this amendment is to add managed objects, information elements and procedures to the Link Aggregation Control Protocol (LACP) so that a set of physical and/or virtual bridge components provide a redundant connection between two separately administered provider networks that isolates the networks from each other as far as management, fault recovery and/or load balancing are concerned, while routing data frames belonging to any given customer service over the same physical path in both directions between the two networks. 5.5 Need for the Project: There is no current standard that permits separately managed provider Ethernet networks to exchange customer service data over robust, fault tolerant connections. That is, either changes to the active topology of one network, caused by component faults, fault recovery, or administrative changes can trigger consequent alterations in a neighboring network, or else the connection between the networks is subject to being severed by a single failure. The Link Aggregation Control Protocol (LACP) is widely supported and commonly employed in inter-provider connections, and is a suitable vehicle for the control information necessary for constructing a redundant network-network interface. 5.6 Stakeholders for the Standard: Developers, distributors, and users of provider networking equipment and services, especially switch vendors. 6.1.a. Is the Sponsor aware of any copyright permissions needed for this project?: No 6.1.b. Is the Sponsor aware of possible registration activity related to this project?: No 7.1 Are there other standards or projects with a similar scope?: No 7.2 International Activities. a. Adoption. Is there potential for this standard (in part or in whole) to be adopted by another national, regional or international organization?: No b. Joint Development. Is it the intent to develop this document jointly with another organization?: No c. Harmonization. Are you aware of another organization that may be interested in portions of this document in their standardization development efforts?: No