| < draft-ietf-l2vpn-spbm-evpn-01.txt | draft-ietf-l2vpn-spbm-evpn-02.txt > | |||
|---|---|---|---|---|
| L2VPN Working Group Dave Allan, Jeff Tantsura | L2VPN Working Group Dave Allan, Jeff Tantsura | |||
| Internet Draft Ericsson | Internet Draft Ericsson | |||
| Intended status: Standards Track Don Fedyk | Intended status: Standards Track Don Fedyk | |||
| Expires: October 2014 HP | Expires: April 2015 HP | |||
| Ali Sajassi | Ali Sajassi | |||
| Cisco | Cisco | |||
| April 2014 | October 2014 | |||
| Shortest Path Bridging, MAC mode Support over EVPN | Shortest Path Bridging, MAC mode Support over EVPN | |||
| draft-ietf-l2vpn-spbm-evpn-01 | draft-ietf-l2vpn-spbm-evpn-02 | |||
| Abstract | Abstract | |||
| This document describes how Ethernet Shortest Path Bridging MAC mode | This document describes how Ethernet Shortest Path Bridging MAC mode | |||
| (802.1aq) can be combined with EVPN in a way that interworks with | (802.1aq) can be combined with EVPN in a way that interworks with | |||
| PBB-PEs as described in the PBB-EVPN solution. This is achieved via | PBB-PEs as described in the PBB-EVPN solution. This is achieved via | |||
| operational isolation of each Ethernet network subtending an EVPN | operational isolation of each Ethernet network subtending an EVPN | |||
| core while supporting full interworking between the different | core while supporting full interworking between the different | |||
| variations of Ethernet networks. | variations of Ethernet networks. | |||
| skipping to change at page 2, line 32 ¶ | skipping to change at page 2, line 32 ¶ | |||
| 2. Conventions used in this document..............................3 | 2. Conventions used in this document..............................3 | |||
| 2.1. Terminology..................................................3 | 2.1. Terminology..................................................3 | |||
| 3. Changes since previous version.................................4 | 3. Changes since previous version.................................4 | |||
| 4. Solution Overview..............................................4 | 4. Solution Overview..............................................4 | |||
| 5. Elements of Procedure..........................................5 | 5. Elements of Procedure..........................................5 | |||
| 5.1. PE Configuration.............................................5 | 5.1. PE Configuration.............................................5 | |||
| 5.2. DF Election..................................................6 | 5.2. DF Election..................................................6 | |||
| 5.3. Control plane interworking ISIS-SPB to EVPN..................6 | 5.3. Control plane interworking ISIS-SPB to EVPN..................6 | |||
| 5.4. Control plane interworking EVPN to ISIS-SPB..................7 | 5.4. Control plane interworking EVPN to ISIS-SPB..................7 | |||
| 5.5. Data plane Interworking 802.1aq SPBM island or PBB-PE to | 5.5. Data plane Interworking 802.1aq SPBM island or PBB-PE to | |||
| EVPN..............................................................7 | EVPN..............................................................8 | |||
| 5.6. Data plane Interworking EVPN to 802.1aq SPBM island..........8 | 5.6. Data plane Interworking EVPN to 802.1aq SPBM island..........8 | |||
| 5.7. Data plane interworking EVPN to 802.1ah PBB-PE...............8 | 5.7. Data plane interworking EVPN to 802.1ah PBB-PE...............8 | |||
| 5.8. Multicast Support............................................8 | 5.8. Multicast Support............................................8 | |||
| 6. Other Aspects..................................................8 | 6. Other Aspects..................................................8 | |||
| 6.1. Flow Ordering................................................8 | 6.1. Flow Ordering................................................8 | |||
| 6.2. Transit......................................................8 | 6.2. Transit......................................................8 | |||
| 7. Acknowledgements...............................................8 | 7. Acknowledgements...............................................9 | |||
| 8. Security Considerations........................................9 | 8. Security Considerations........................................9 | |||
| 9. IANA Considerations............................................9 | 9. IANA Considerations............................................9 | |||
| 10. References....................................................9 | 10. References....................................................9 | |||
| 10.1. Normative References........................................9 | 10.1. Normative References........................................9 | |||
| 10.2. Informative References......................................9 | 10.2. Informative References......................................9 | |||
| 11. Authors' Addresses...........................................10 | 11. Authors' Addresses...........................................10 | |||
| 1. Introduction | 1. Introduction | |||
| This document describes how Ethernet Shortest Path Bridging MAC mode | This document describes how Ethernet Shortest Path Bridging MAC mode | |||
| skipping to change at page 4, line 13 ¶ | skipping to change at page 4, line 13 ¶ | |||
| PBBN: Provider Backbone Bridged Network | PBBN: Provider Backbone Bridged Network | |||
| PBB-PE: Co located 802.1ah BEB and EVPN PE | PBB-PE: Co located 802.1ah BEB and EVPN PE | |||
| PE: provider edge | PE: provider edge | |||
| SPB: Shortest path bridging | SPB: Shortest path bridging | |||
| SPBM: Shortest path bridging MAC mode | SPBM: Shortest path bridging MAC mode | |||
| SPBM-PE: Co-located 802.1aq SPBM<->EVPN interworking function and | SPBM-PE: Co-located 802.1aq SPBM<->EVPN interworking function and | |||
| EVPN PE | EVPN PE | |||
| 3. Changes since previous version | 3. Changes since previous version | |||
| 1) Comments received during call for WG adoption resolved. | 1) References corrected/updated. | |||
| 2) Reference to draft-allan-mldp-evpn removed. | ||||
| 4. Solution Overview | 4. Solution Overview | |||
| The EVPN solution for 802.1aq SPBM incorporates control plane | The EVPN solution for 802.1aq SPBM incorporates control plane | |||
| interworking in the PE to map ISIS-SPB [RFC6329] information elements | interworking in the PE to map ISIS-SPB [RFC6329] information elements | |||
| into the EVPN NLRI information and vice versa. This requires each PE to | into the EVPN NLRI information and vice versa. This requires each PE to | |||
| act both as an EVPN BGP speaker and as an ISIS-SPB edge node. Associated | act both as an EVPN BGP speaker and as an ISIS-SPB edge node. Associated | |||
| with this are procedures for configuring the forwarding operations of | with this are procedures for configuring the forwarding operations of | |||
| the PE such that an arbitrary number of EVPN subtending SPBM islands may | the PE such that an arbitrary number of EVPN subtending SPBM islands may | |||
| be interconnected without any topological or multipathing dependencies. | be interconnected without any topological or multipathing dependencies. | |||
| skipping to change at page 4, line 40 ¶ | skipping to change at page 5, line 4 ¶ | |||
| +-----+ +----+ | | +----+ +---+ | +-----+ +----+ | | +----+ +---+ | |||
| | |-----|SPBM| | | |PBB |---|CE2| | | |-----|SPBM| | | |PBB |---|CE2| | |||
| |SPBM | |PE1 | | IP/MPLS | |PE1 | +---+ | |SPBM | |PE1 | | IP/MPLS | |PE1 | +---+ | |||
| +---+ |NTWK1| +----+ | Network | +----+ | +---+ |NTWK1| +----+ | Network | +----+ | |||
| |CE1|-| | | | | |CE1|-| | | | | |||
| +---+ | | +----+ | | | +---+ | | +----+ | | | |||
| | |-----|SPBM| | | +----+ +-----+ | | |-----|SPBM| | | +----+ +-----+ | |||
| +-----+ |PE2 | | | |SPBM| |SPBM | +---+ | +-----+ |PE2 | | | |SPBM| |SPBM | +---+ | |||
| +----+ | | |PE3 |---|NTWK2|-|CE3| | +----+ | | |PE3 |---|NTWK2|-|CE3| | |||
| +--------------+ +----+ +-----+ +---+ | +--------------+ +----+ +-----+ +---+ | |||
| Figure 1: PBB and SPBM EVPN Network | Figure 1: PBB and SPBM EVPN Network | |||
| Each EVPN is identified by a route target. The route target identifies | Each EVPN is identified by a route target. The route target identifies | |||
| the set of SPBM islands and PBB-PEs that are allowed to communicate. | the set of SPBM islands and PBB-PEs that are allowed to communicate. | |||
| Each SPBM island is administered to have an associated Ethernet Segment | Each SPBM island is administered to have an associated Ethernet Segment | |||
| ID (ESI) associated with it. This manifests itself as a set of Ethernet | ID (ESI) associated with it. This manifests itself as a set of Ethernet | |||
| segments, where each ESI is unique within the route target. | segments, where each ESI is unique within the route target. | |||
| BGP acts as a common repository of the I-SID attachment points for the | BGP acts as a common repository of the I-SID attachment points for the | |||
| set of subtending PEs/SPBM islands. This is in the form of B-MAC | set of subtending PEs/SPBM islands. This is in the form of B-MAC | |||
| address/I-SID/Tx-Rx-attribute tuples. BGP filters leaking I-SID | address/I-SID/Tx-Rx-attribute tuples. BGP filters leaking I-SID | |||
| information into each SPBM island on the basis of locally registered | information into each SPBM island on the basis of locally registered | |||
| interest. If an SPBM island has no BEBs registering interest in an I- | interest. If an SPBM island has no BEBs registering interest in an I- | |||
| SID, information about that I-SID from other SPBM islands, PBB-PEs or | SID, information about that I-SID from other SPBM islands, PBB-PEs or | |||
| PBBNs will not be leaked into the local ISIS-SPB routing system. | PBBNs will not be leaked into the local ISIS-SPB routing system. | |||
| For each B-VID in an SPBM island, a single SPBM-PE is elected the | For each B-VID in an SPBM island, a single SPBM-PE is elected the | |||
| designated forwarder for the B-VID. An SPBM-PE may be a DF for more than | designated forwarder for the B-VID. An SPBM-PE may be a DF for more than | |||
| one B-VID. This is described further in section 4.2. The SPBM-PE | one B-VID. This is described further in section 5.2. The SPBM-PE | |||
| originates IS-IS advertisements as if it were an IB-BEB that proxies for | originates IS-IS advertisements as if it were an IB-BEB that proxies for | |||
| the other SPBM islands and PBB PEs in the EVPN defined by the route | the other SPBM islands and PBB PEs in the EVPN defined by the route | |||
| target, but the PE typically will not actually host any I-components. | target, but the PE typically will not actually host any I-components. | |||
| An SPBM-PE that is a DF for a B-VID strips the B-VID tag information | An SPBM-PE that is a DF for a B-VID strips the B-VID tag information | |||
| from frames relayed towards the EVPN. The DF also inserts the | from frames relayed towards the EVPN. The DF also inserts the | |||
| appropriate B-VID tag information into frames relayed towards the SPBM | appropriate B-VID tag information into frames relayed towards the SPBM | |||
| island on the basis of the local I-SID/B-VID bindings advertised in | island on the basis of the local I-SID/B-VID bindings advertised in | |||
| ISIS-SPB. | ISIS-SPB. | |||
| 5. Elements of Procedure | 5. Elements of Procedure | |||
| skipping to change at page 6, line 17 ¶ | skipping to change at page 6, line 21 ¶ | |||
| multi-pathing algorithms used may be different in different | multi-pathing algorithms used may be different in different | |||
| domains and the B-VID itself is removed for frames carried over | domains and the B-VID itself is removed for frames carried over | |||
| the IP/MPLS network. | the IP/MPLS network. | |||
| A type-1 Route Distinguisher for the node can be auto-derived. This | A type-1 Route Distinguisher for the node can be auto-derived. This | |||
| will be described in a future version of the document. | will be described in a future version of the document. | |||
| 5.2. DF Election | 5.2. DF Election | |||
| PEs self appoint in the role of DF for a B-VID for a given SPBM | PEs self appoint in the role of DF for a B-VID for a given SPBM | |||
| island. The procedure used is as per section 9.5 of [EVPN] | island. The procedure used is as per section 8.5 of [EVPN] | |||
| "Designated Forwarder election". | "Designated Forwarder election". | |||
| A PE that assumes the role of DF for a given DF is responsible for | A PE that assumes the role of DF for a given DF is responsible for | |||
| originating specific information into BGP from ISIS-SPB and vice | originating specific information into BGP from ISIS-SPB and vice | |||
| versa. A PE that ceases to perform the role of DF for a given B-VID | versa. A PE that ceases to perform the role of DF for a given B-VID | |||
| is responsible for withdrawing the associated information from BGP | is responsible for withdrawing the associated information from BGP | |||
| and ISIS-SPB respectively. The actual information exchanged is | and ISIS-SPB respectively. The actual information exchanged is | |||
| outlined in the following sections. | outlined in the following sections. | |||
| 5.3. Control plane interworking ISIS-SPB to EVPN | 5.3. Control plane interworking ISIS-SPB to EVPN | |||
| skipping to change at page 8, line 28 ¶ | skipping to change at page 8, line 34 ¶ | |||
| A PBB-PE actually has no subtending PBBN nor concept of B-VID so no | A PBB-PE actually has no subtending PBBN nor concept of B-VID so no | |||
| frame processing is required. | frame processing is required. | |||
| A PBB-PE is required to accept SPBM encoded multicast DAs as if they | A PBB-PE is required to accept SPBM encoded multicast DAs as if they | |||
| were 802.1ah encoded multicast DAs. The only information of interest | were 802.1ah encoded multicast DAs. The only information of interest | |||
| being that it is a multicast frame, and the I-SID encoded in the | being that it is a multicast frame, and the I-SID encoded in the | |||
| lower 24 bits. | lower 24 bits. | |||
| 5.8. Multicast Support | 5.8. Multicast Support | |||
| Refer to "mLDP extensions for integrating EVPN and multicast"[mLDP]. | Not addressed by this memo. | |||
| 6. Other Aspects | 6. Other Aspects | |||
| 6.1. Flow Ordering | 6.1. Flow Ordering | |||
| When per I-SID multicast is implemented via PE replication, a stable | When per I-SID multicast is implemented via PE replication, a stable | |||
| network will preserve frame ordering between known unicast and | network will preserve frame ordering between known unicast and | |||
| broadcast/unknown/multicast traffic (e.g. race conditions will not | broadcast/unknown/multicast traffic (e.g. race conditions will not | |||
| exist). This cannot be guaranteed when multicast is used in the EVPN. | exist). This cannot be guaranteed when multicast is used in the EVPN. | |||
| skipping to change at page 9, line 24 ¶ | skipping to change at page 9, line 29 ¶ | |||
| 10.1. Normative References | 10.1. Normative References | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
| [RFC6329] Fedyk et.al. "IS-IS Extensions Supporting IEEE 802.1aq | [RFC6329] Fedyk et.al. "IS-IS Extensions Supporting IEEE 802.1aq | |||
| Shortest Path Bridging", IETF RFC 6329, April 2012 | Shortest Path Bridging", IETF RFC 6329, April 2012 | |||
| [EVPN] Aggarwal et.al. "BGP MPLS Based Ethernet VPN", IETF work | [EVPN] Aggarwal et.al. "BGP MPLS Based Ethernet VPN", IETF work | |||
| in progress, draft-ietf-l2vpn-evpn-04, July 2013 | in progress, draft-ietf-l2vpn-evpn-11, October 2014 | |||
| [mLDP] Allan et.al. "mLDP extensions for integrating EVPN and | ||||
| multicast", IETF work in progress draft-allan-l2vpn-mldp- | ||||
| evpn-01, May 2013 | ||||
| 10.2. Informative References | 10.2. Informative References | |||
| [802.1aq] | [802.1aq] | |||
| 802.1aq(2012) IEEE Standard for Local and Metropolitan | 802.1aq(2012) IEEE Standard for Local and Metropolitan | |||
| Area Networks: Bridges and Virtual Bridged Local Area | Area Networks: Bridges and Virtual Bridged Local Area | |||
| Networks - Amendment 9: Shortest Path Bridging | Networks - Amendment 9: Shortest Path Bridging | |||
| [PBB-EVPN] Sajassi et.al. "PBB E-VPN", IETF work in progress, | [PBB-EVPN] Sajassi et.al. "PBB E-VPN", IETF work in progress, | |||
| draft-ietf-l2vpn-pbb-evpn-06, October 2013 | draft-ietf-l2vpn-pbb-evpn-08, October 2014 | |||
| [802.1Q] | [802.1Q] | |||
| 802.1Q (2011) IEEE Standard for Local and metropolitan | 802.1Q (2011) IEEE Standard for Local and metropolitan | |||
| area networks--Media Access Control (MAC) Bridges and | area networks--Media Access Control (MAC) Bridges and | |||
| Virtual Bridged Local Area Networks | Virtual Bridged Local Area Networks | |||
| 11. Authors' Addresses | 11. Authors' Addresses | |||
| Dave Allan (editor) | Dave Allan (editor) | |||
| Ericsson | Ericsson | |||
| End of changes. 12 change blocks. | ||||
| 15 lines changed or deleted | 14 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||