![]() |
[802 Architecture Group] . [Audio/Video Bridging Task Group] . [Data Center Bridging Task Group] [Email] . [Ancient Email] . [Meetings] . [802.1 MIBs] . [802.1 OIDs] . [802.1 Interpretations] . [IEEE 802] . [IEEE 802 PARs] [802] . [802a] . [802b] . [802.1D] . [802.1D-2004] . [802.1G] . [802.1H-REV] . [802.1Q] . [802.1Q-REV] . [802.1s] . [802.1v] . [802.1w] . [802.1AB-2005] . [802.1AB-2009] . [802.1AC] . [802.1ad] . [802.1ag] . [802.1ah] . [802.1aj] . [802.1ak] . [802.1ap] . [802.1aq] . [802.1Qaw] . [802.1Qay] . [802.1Qbc] . [802.1Qbe] . [802.1Qbf] Security: [802.1X-2001] . [802.1X-2004] . [802.1X-2010] . [802.1AE] . [802.1af] . [802.1AR] AVB: [802.1AS] . [802.1Qat] . [802.1Qav] . [802.1BA] . DCB: [802.1Qau] . [802.1Qaz] . [802.1Qbb] . [802.1Qbg] . [802.1Qbh] . [802.3bd] |
![]() |

The full title of this PAR is "IEEE Standard for Local and Metropolitan Area Networks---Virtual Bridged Local Area Networks - Amendment: Multiple Backbone Service Interface Identifier (I-SID) Registration Protocol (MIRP)".
This standard specifies protocols, procedures, and managed objects to support topology change signaling to alter the binding (held in an I-Component) of Customer addresses to Backbone addresses on a per-I-SID basis. This is accomplished by extending the use of the Multiple Registration Protocol (MRP).
MIRP provides the capabilities necessary when topology changes occur in networks attached to a Provider Backbone Bridged Network. A Backbone Edge Bridge (BEB) signals to other potentially affected BEBs the need to alter certain learned associations between Customer MAC Addresses and Backbone MAC Addresses. An access cloud that has an I-tagged connection to a Backbone network signals both its requirements for specific services, and topology change events in those services.
The deployment of IEEE Provider Backbone Bridged Networks, including I-tagged connections between these networks, has raised requirements for both signaling among Provider Edge Bridges the need to forget MAC address associations, and for extending the capabilities of MRP to backbone service identifiers. In the absence of MIRP, customer connections across a Provider Backbone Network can take several minutes to restore connectivity after a topology change in an access network.

| PAR | PAR approved Sep 11th, 2009 |
| Status | Task group ballot. |
| Document | 802.1Qbe draft 0.1 |
| Dispositions | Draft 0.1 proposed comment dispositions |
| Editor | Norm Finn |

| Date | Document |
|---|---|
| 10 Aug 2009 | 802.1Qbe, Draft 0.1 |
| 10 Aug 2009 | 802.1be, Draft 0.1 MIB |
| 09 Sep 2009 | 802.1be, Draft 0.1 proposed comment dispositions |
| 10 Sep 2009 | 802.1be, Draft 0.1 comment dispositions |
| 06 Oct 2009 | 802.1be, Draft 1.0 with changebars |
| 06 Oct 2009 | 802.1be, Draft 1.0 |
| 11 Nov 2009 | 802.1be, Draft 1.0 proposed comment dispositions |
| 14 Nov 2009 | 802.1be, Draft 1.0 proposed comment dispositions |
| 16 Nov 2009 | 802.1be, Draft 1.0 proposed comment dispositions |
| 19 Nov 2009 | 802.1be, Draft 1.0 comment dispositions |
| 17 Dec 2009 | 802.1be, Draft 1.1 with changebars |
| 17 Dec 2009 | 802.1be, Draft 1.1 |
| 17 Dec 2009 | 802.1be, Draft 1.1 |
| 19 Jan 2010 | 802.1be, Draft 1.1 proposed comment dispositions |
| 20 Jan 2010 | 802.1be, Draft 1.1 proposed comment dispositions |
| 04 Feb 2010 | 802.1be, Draft 1.2 with changebars |
| 04 Feb 2010 | 802.1be, Draft 1.2 MIB |
| 04 Feb 2010 | 802.1be, Draft 1.2 |

| Date | Document |
|---|
Pages copyright © Institute of Electrical and Electronics Engineers, Inc. Please read the rules on Confidentiality Statements and Copyright Notices on Communications. If you have any comments on these pages, please send them to me.