IP Library › Granted Patent US 12,255,976
Granted Patent B2
US 12,255,976 · App. 18/360,783 · Granted Mar 18, 2025

Ethernet virtual private network using segment routing

Inventors: Patrice Brissette (Gatineau, CA); Clarence Filsfils (Brussels, BE); Darren Dukes (Ottawa, CA); Gaurav Dawra (San Jose, CA); Francois Clad (Strasbourg, FR); Pablo Camarillo Garvia (Madrid, ES)
Assignee: Cisco Technology, Inc.
H04L69/22H04L12/4633H04L12/4641H04L45/04H04L45/14H04L45/34H04L45/50H04L45/74H04L45/741H04L49/35H04L61/5007H04L67/10H04L67/63H04L69/324H04L43/028H04L45/745H04L61/2503H04L63/0272H04L2101/00H04L2101/659H04L2212/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,255,976
App. No.
18/360,783
Granted
Mar 18, 2025
Kind
B2
Abstract

In one embodiment, Ethernet Virtual Private Network (EVPN) is implemented using Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) underlay network and SRv6-enhanced Border Gateway Protocol (BGP) signaling. A particular route associated with a particular Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) Segment Identifier (SID) is advertised in a particular route advertisement message of a routing protocol (e.g., BGP). The SID includes encoding representing a particular Ethernet Virtual Private Network (EVPN) Layer 2 (L2) flooding Segment Routing end function of the particular router and a particular Ethernet Segment Identifier (ESI), with the particular SID including a routable prefix to the particular router. The particular router receives a particular packet including the particular SID; and in response, the particular router performs the particular EVPN end function on the particular packet.

Claims (45)

1. A method of managing an Ethernet Virtual Private Network (EVPN) using Internet Protocol Version 6 (IPv6) Segment Routing (SRv6) connection comprising:

receiving a packet, the packet including an outer layer and an inner layer, wherein the outer layer includes an IPV6 header, the IPV6 header including a destination address,

wherein the inner layer includes a MAC source address and a MAC destination address,

wherein the outer layer destination address corresponds to a segment identifier (SID), and

wherein the SID corresponds to an EVPN endpoint and includes a Type-Length-Value (TLV) indicating that the SID has a corresponding end function;

removing the IPv6 header;

identifying the MAC source address and the MAC destination address in the inner layer;

look up the MAC destination address in a layer 2 lookup table to identify if a matching entry exists in the table; and

if a matching entry exists, forwarding the packet to the matched entry.

2. The method of claim 1 , wherein the method further comprises if no matching entry exists, forwarding the packet from an interface.

3. The method of claim 2 , wherein forwarding the packet includes forwarding to an associated L2 interface (OIF).

4. The method of claim 1 , further comprising:

if no matching entry exists, dropping the packet.

5. The method of claim 1 , wherein a routing protocol used to identify a route for the packet is Border Gateway Protocol (BGP).

6. The method of claim 1 , wherein the received IPV6 Packet includes a Segment Routing Header (SRH) including the SID as a currently active SID.

7. The method of claim 1 , wherein the end function is designated as Endpoint with decapsulation and specific unicast MAC L2 table lookup (END.DT2U).

8. An apparatus, comprising:

one or more hardware interfaces sending and receiving packets in a network; and one or more network processors with memory associated therewith, wherein the apparatus performs processing operations including:

receiving a packet over an Ethernet Virtual Private Network (EVPN) using Internet Protocol Version 6 (IPv6) segment routing (SRv6), the packet including an outer layer and an inner layer, wherein the outer layer includes an IPV6 header, the IPV6 header including a destination address, wherein the inner layer includes a MAC source address and a MAC destination address, wherein the outer layer destination address corresponds to a segment identifier (SID), and wherein the SID corresponds to an EVPN endpoint;

removing the IPV6 header;

identifying the MAC source address and the MAC destination address in the inner layer;

look up the MAC destination address in a layer 2 lookup table to identify if a matching entry exists in the table;

if a matching entry exists, forwarding the packet to the matched entry.

9. The apparatus of claim 8 , wherein if no matching entry exists in the layer 2 lookup table, the packet is dropped.

10. The apparatus of claim 8 , wherein if no matching entry exists in the layer 2 lookup table, the packet is forwarded via an interface of the one or more hardware interfaces.

11. The apparatus of claim 10 , wherein if no matching entry exists in the layer 2 lookup table, the packet is forwarded to an associated L2 interface (OIF).

12. The apparatus of claim 8 , wherein the packet includes a label, and the label is associated with an end function.

13. The apparatus of claim 12 , wherein the end function is designated as Endpoint with decapsulation and specific unicast MAC L2 table lookup (END.DT2U).

14. The apparatus of claim 8 , wherein the received IPv6 Packet includes a Segment Routing Header (SRH) including the SID as a currently active SID.

15. A non-transitory computer readable media containing logical instructions, which when interpreted by one or more processors in an apparatus having one or more hardware interfaces sending and receiving packets in a network, cause the apparatus to perform actions including:

receiving a packet over an Ethernet Virtual Private Network (EVPN) using Internet Protocol Version 6 (IPv6) segment routing (SRv6), the packet including an outer layer and an inner layer,

wherein the outer layer includes an IPV6 header, the IPV6 header including a destination address,

wherein the inner layer includes a MAC source address and a MAC destination address,

wherein the outer layer destination address corresponds to a segment identifier (SID), and

wherein the SID corresponds to an EVPN endpoint;

removing the IPV6 header;

identifying the MAC source address and the MAC destination address in the inner layer;

look up the MAC destination address in a layer 2 lookup table to identify if a matching entry exists in the table;

if a matching entry exists, forwarding the packet to the matched entry.

16. The instructions of claim 15 , further comprising instructions wherein if no matching entry exists in the layer 2 lookup table, the packet is dropped.

17. The instructions of claim 15 , further comprising instructions wherein if no matching entry exists in the layer 2 lookup table, the packet is forwarded via an interface of the one or more hardware interfaces.

18. The instructions of claim 17 , further comprising instructions wherein if no matching entry exists in the layer 2 lookup table, the packet is forwarded to an associated L2 interface (OIF).

19. The instructions of claim 15 , wherein the packet includes a label, and the label is associated with an end function.

20. The instructions of claim 19 , wherein the end function is designated as Endpoint with decapsulation and specific unicast MAC L2 table lookup (END.DT2U).

21. The instructions of claim 15 , wherein the received IPv6 Packet includes a Segment Routing Header (SRH) including the SID as a currently active SID.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 27, 2023
From: BRISSETTE, PATRICE; FILSFILS, CLARENCE; DUKES, DARREN; DAWRA, GAURAV; CLAD, FRANCOIS; CAMARILLO GARVIA, PABLO
To: CISCO TECHNOLOGY, INC.
Reel/Frame 064411/0718 →
Continuity (5)
Continuation 17671188 · Feb 14, 2022
Continuation 16697134 · Nov 26, 2019
Continuation 15783753 · Oct 13, 2017
Provisional Application 62525439 · Jun 27, 2017
Related Publication 20240098161A1 · Mar 21, 2024
References Cited (146)
US 8059661B2 · Patel et al. · 2011 [cited by applicant]
US 8151088B1 · Bao et al. · 2012 [cited by applicant]
US 8520672B2 · Guichard et al. · 2013 [cited by applicant]
US 9019814B1 · Mohanty et al. · 2015 [cited by applicant]
US 9112723B2 · Alexander, Jr. et al. · 2015 [cited by applicant]
US 9148290B2 · Salam et al. · 2015 [cited by applicant]
US 9178816B1 · Ojha et al. · 2015 [cited by applicant]
US 9258765B1 · Dacosta · 2016 [cited by applicant]
US 9397931B1 · Mohanty et al. · 2016 [cited by applicant]
US 9537769B2 · Bryant et al. · 2017 [cited by applicant]
US 9660897B1 · Gredler · 2017 [cited by applicant]
US 9742678B2 · Boutros et al. · 2017 [cited by applicant]
US 9762488B2 · Previdi et al. · 2017 [cited by applicant]
US 10063475B2 · Previdi et al. · 2018 [cited by applicant]
US 10135734B1 · Singh · 2018 [cited by examiner]
US 10382334B2 · Previdi et al. · 2019 [cited by applicant]
US 10469361B1 · Bayross et al. · 2019 [cited by applicant]
US 10491720B2 · Brissette et al. · 2019 [cited by applicant]
US 10506083B2 · Filsfils et al. · 2019 [cited by applicant]
US 10516610B2 · Filsfils et al. · 2019 [cited by applicant]
US 10530873B1 · Arya et al. · 2020 [cited by applicant]
US 10652366B2 · Bashandy et al. · 2020 [cited by applicant]
US 10778816B2 · Filsfils et al. · 2020 [cited by applicant]
US 11283906B2 · Brissette et al. · 2022 [cited by applicant]
US 20040111494A1 · Kostic et al. · 2004 [cited by applicant]
US 20040223497A1 · Sanderson et al. · 2004 [cited by applicant]
US 20110075667A1 · Li et al. · 2011 [cited by applicant]
US 20110110375A1 · Boucadair et al. · 2011 [cited by applicant]
US 20110286452A1 · Balus et al. · 2011 [cited by applicant]
US 20130227284A1 · Pfeffer et al. · 2013 [cited by applicant]
US 20140032782A1 · Jiang et al. · 2014 [cited by applicant]
US 20140098671A1 · Raleigh et al. · 2014 [cited by applicant]
US 20140098675A1 · Frost et al. · 2014 [cited by applicant]
US 20140269422A1 · Filsfils et al. · 2014 [cited by applicant]
US 20140269721A1 · Bashandy et al. · 2014 [cited by applicant]
US 20140369356A1 · Bryant et al. · 2014 [cited by applicant]
US 20150109902A1 · Kumar · 2015 [cited by examiner]
US 20150256456A1 · Previdi et al. · 2015 [cited by applicant]
US 20150304206A1 · Filsfils et al. · 2015 [cited by applicant]
US 20150326675A1 · Kini et al. · 2015 [cited by applicant]
US 20160014071A1 · Asati et al. · 2016 [cited by applicant]
US 20160021400A1 · Surcouf et al. · 2016 [cited by applicant]
US 20160099864A1 · Akiya et al. · 2016 [cited by applicant]
US 20160173366A1 · Saad et al. · 2016 [cited by applicant]
US 20160248860A1 · Dunbar et al. · 2016 [cited by applicant]
US 20160285780A1 · Strijkers et al. · 2016 [cited by applicant]
US 20160294644A1 · Pacella et al. · 2016 [cited by applicant]
US 20160359672A1 · Blair et al. · 2016 [cited by applicant]
US 20160380848A1 · Raney · 2016 [cited by applicant]
US 20170005922A1 · Tantsura et al. · 2017 [cited by applicant]
US 20170012873A1 · Berg · 2017 [cited by applicant]
US 20170012895A1 · Zhao et al. · 2017 [cited by applicant]
US 20170026286A1 · Surcouf et al. · 2017 [cited by applicant]
US 20170033939A1 · Bragg et al. · 2017 [cited by applicant]
US 20170063600A1 · Singh et al. · 2017 [cited by applicant]
US 20170134274A1 · Ara Jo · 2017 [cited by applicant]
US 20170141963A1 · Chalapathy et al. · 2017 [cited by applicant]
US 20170237656A1 · Gage · 2017 [cited by applicant]
US 20170250908A1 · Nainar et al. · 2017 [cited by applicant]
US 20170310594A1 · Kotha et al. · 2017 [cited by applicant]
US 20170339052A1 · Arora et al. · 2017 [cited by applicant]
US 20170346707A1 · Menon et al. · 2017 [cited by applicant]
US 20170346720A1 · Lazzeri et al. · 2017 [cited by applicant]
US 20180006948A1 · Torvi et al. · 2018 [cited by applicant]
US 20180006995A1 · Bickhart et al. · 2018 [cited by applicant]
US 20180034727A1 · Nainar et al. · 2018 [cited by applicant]
US 20180102965A1 · Hari et al. · 2018 [cited by applicant]
US 20180109444A1 · Sajassi et al. · 2018 [cited by applicant]
US 20180219783A1 · Pfister et al. · 2018 [cited by applicant]
US 20180241718A1 · Stair et al. · 2018 [cited by applicant]
US 20180295156A1 · Kolbe et al. · 2018 [cited by applicant]
US 20180324090A1 · Duncan · 2018 [cited by examiner]
US 20180357576A1 · Rachitsky et al. · 2018 [cited by applicant]
US 20180359176A1 · Nainar et al. · 2018 [cited by applicant]
US 20180373768A1 · Adams et al. · 2018 [cited by applicant]
US 20180375764A1 · Filsfils et al. · 2018 [cited by applicant]
US 20180375766A1 · Filsfils et al. · 2018 [cited by applicant]
US 20180375768A1 · Previdi et al. · 2018 [cited by applicant]
US 20180375968A1 · Bashandy et al. · 2018 [cited by applicant]
US 20190190818A1 · Ceccarelli · 2019 [cited by examiner]
US 20190215267A1 · Filsfils et al. · 2019 [cited by applicant]
US 20190288940A1 · Filsfils et al. · 2019 [cited by applicant]
US 20190394211A1 · Filsfils et al. · 2019 [cited by applicant]
Abdelsalam A., et al., “Implementation of Virtual Network Function Chaining through Segment Routing in a Linux-based NFV Infrastructure,” Apr. 20, 2017, 10 Pages, arXiv.org, doi:arXiv:1702.05157v4, (Sep. 7, 2018), XP055… [cited by applicant]
Aggarwal R., et al., “BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs,” Internet Engineering Task Force (IETF), Request for Comments: 6514, Category: Standards Track, Feb. 2012, ISSN: 2070-1721, pp. 1-59,… [cited by applicant]
Amendment A, U.S. Appl. No. 15/824,455, United States Patent and Trademark Office, Alexandria, VA, dated Sep. 27, 2019, 14 Pages. [cited by applicant]
Bates T., et al., “Multiprotocol Extensions for BGP-4,” Network Working Group, Request for Comments: 4760, Jan. 2007, pp. 1-12. [cited by applicant]
Bates T., et al., “Multiprotocol Extensions for BGP-4,” RFC 2283, Feb. 1998, the Internet Society, Reston, VA, USA, 9 pages. [cited by applicant]
Boutros S., et al., “Virtual Private Wire Service Support in Ethernet VPN (RFC8214),” IP.Com, Internet Engineering Task Force IETF, Aug. 2017, 18 Pages. [cited by applicant]
Boutros S., et al., “VXLAN DCI Using EVPN,” draft-boutros-bess-vxlan-evpn-02.txt, Oct. 21, 2016, the Internet Society, Reston, VA, USA, 15 pages. [cited by applicant]
Communication Pursuant to Article 94(3) EPC (EPO Office action) for EP Application No. 18742689.5, dated Feb. 2, 2021, 11 Pages. [cited by applicant]
Communication Pursuant to Rules 161(2) and 162 EPC (EPO Office action) for EP Application No. 18742689.5, dated Feb. 4, 2020, 3 Pages. [cited by applicant]
Dawra G., et al., “BGP Signaling of IPV6-Segment-Routing-based VPN Networks: draft-dawra-idr-srv6-vpn-01.txt,” The Internet Society, Reston, VA, USA, Sep. 11, 2017, 12 Pages. [cited by applicant]
Dawra G., et al., “BGP Signaling of IPv6-Segment-Routing-based VPN Networks: draft-dawra-idr-srv6-vpn-04,” The Internet Society, Reston, VA, USA, Jun. 25, 2018, 21 Pages. [cited by applicant]
Dawra G., et al., “BGP Signaling of IPV6-Segment-Routing-based VPN Networks; draft-dawra-idr-srv6-vpn-04.txt,” Internet-Draft: Inter-Domain Routin, Internet Engineering Task Force, IETF; Standard Working Draft, Internet… [cited by applicant]
Deering S., et al., “Internet Protocol, Version 6 (IPv6) Specification,” RFC 8200, Jul. 2017, the Internet Society, Reston, VA, USA, 42 pages. [cited by applicant]
Deering S., et al., “Internet Protocol, Version 6 (IPv6) Specification,” rfc2460.txt, Internet Protocol, Version 6 (IPV6) Specification, Internet Engineering Task Force, IETF, Standard, Internet Society (ISOC) 4, Rue De… [cited by applicant]
Filsfils C., et al., “Segment Routing Architecture draft-ietf-spring-segment-routing-11,” Network Working Group, the Internet Society, Internet-Draft, Reston, VA, USA, Feb. 16, 2017, pp. 1-28. [cited by applicant]
Filsfils C., et al., “Segment Routing Architecture draft-ietf-spring-segment-routing-12,” Network Working Group, the Internet Society, Reston, VA, USA, Jun. 20, 2017, pp. 1-28. [cited by applicant]
Filsfils C., et al., “Segment Routing Architecture: draft-ietf-spring-segment-routing-15,” The Internet Society, Reston, VA, USA, Jan. 25, 2018, 31 Pages. [cited by applicant]
Filsfils C., et al., “Segment Routing Policy for Traffic Engineering draft-filsfils-spring-segment-routing-policy-01.txt,” Network Working Group, the Internet Society, Reston, VA, USA, Jul. 3, 2017, pp. 1-30. [cited by applicant]
Filsfils C., et al., “SRv6 Network Programming draft-filsfils-spring-srv6-network-programming-00.txt,” Cisco Systems, Internet Engineering Task Force (IETF), Spring, Standard Working Draft, Internet Society (ISOC) 4, Ru… [cited by applicant]
Filsfils C., et al., “SRv6 Network Programming draft-filsfils-spring-srv6-network-programming-01,” Cisco Systems, Inc., Spring, the Internet Society, Reston, VA, USA, Jun. 28, 2017, pp. 1-42. [cited by applicant]
Filsfils C., et al., “SRv6 Network Programming: draft-filsfils-spring-srv6-network-programming-04,” Spring, Internet-Draft, Mar. 4, 2018, 58 Pages. [cited by applicant]
Filsfils D., et al., Inter-Domain Routing Internet-Draft, “BGP Signaling of IPv6-Segment-Routing-Based VPN Networks Draft-Dawra-idr-srv6-vpn-00.txt,” Mar. 13, 2017, Retrieved from URL: https://tools.ietf.org/pdf/draft-d… [cited by applicant]
Filsfls C., et al., “SRv6 Network Programming; draft-filsfils-spring-srv6-network-programming-00,” The Internet Society, Mar. 9, 2017, Reston, VA, USA, 41 Pages. [cited by applicant]
Halpern J., et al., “Service Function Chaining (SFC) Architecture,” RFC 7665, the Internet Society, Reston, VA, USA, Oct. 2015, 32 Pages. [cited by applicant]
International Preliminary Report on Patentability for International Application No. PCT/US2018/039714, mailed Jan. 9, 2020, 14 Pages. [cited by applicant]
International Preliminary Report on Patentability for International Application No. PCT/US2018/039722, mailed Jan. 9, 2020, 12 Pages. [cited by applicant]
International Preliminary Report on Patentability for International Application No. PCT/US2018/039731, mailed Jan. 9, 2020, 16 Pages. [cited by applicant]
International Preliminary Report on Patentability for International Application No. PCT/US2018/039739, mailed Jan. 9, 2020, 13 Pages. [cited by applicant]
International Search Report and Written Opinion for International Application No. PCT/US2018/039714, mailed Sep. 12, 2018, 19 Pages. [cited by applicant]
International Search Report and Written Opinion for International Application No. PCT/US2018/039722, mailed Sep. 12, 2018, 13 Pages. [cited by applicant]
International Search Report and Written Opinion for International Application No. PCT/US2018/039731, mailed Nov. 13, 2018, 20 Pages. [cited by applicant]
International Search Report and Written Opinion for International Application No. PCT/US2018/039739, mailed Sep. 18, 2018, 14 Pages. [cited by applicant]
International Standard, “Information Technology—Telecommunications and Information Exchange Between Systems—Intermediate System to Intermediate System Intra-domain Routeing Information Exchange Protocol for Use in Conju… [cited by applicant]
Kent S., et al., “Security Architecture for the Internet Protocol,” RFC 4301, the Internet Society, Reston, VA, USA, Dec. 2005, 101 Pages. [cited by applicant]
Kent S., “IP Authentication Header,” RFC 4302, the Internet Society, Reston, VA, USA, Dec. 2005, 34 Pages. [cited by applicant]
Kent S., “IP Encapsulating Security Payload (ESP),” RFC 4303, the Internet Society, Reston, VA, USA, Dec. 2005, 44 Pages. [cited by applicant]
Kompella K., Ed., et al., “Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling,” RFC 4761, Jan. 2007, the Internet Society, Reston, VA, USA, 28 pages. [cited by applicant]
Krawczyk H., et al., “HMAC: Keyed-Hashing for Message Authentication,” RFC 2104, the Internet Society, Reston, VA, USA, Feb. 1997, 11 Pages. [cited by applicant]
Lasserre M., et al., “Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling,” RFC 4762, the Internet Society, Reston, VA, USA, Jan. 2007, 31 Pages. [cited by applicant]
Lebrun D., “Leveraging IPv6 Segment Routing for Service Function Chaining,” Proceedings of ACM CoNEXT 2015 Student Workshop, Heidelberg, Germany, Dec. 2015, 2 Pages. [cited by applicant]
Mohapatra P., et al., “The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute,” RFC 5512, Apr. 2009, the Internet Society, Reston, VA, USA, 13 pages. [cited by applicant]
Office Action, U.S. Appl. No. 15/824,455, United States Patent and Trademark Office, Alexandria, VA, dated Dec. 18, 2019, 17 Pages. [cited by applicant]
Office Action, U.S. Appl. No. 15/824,455, United States Patent and Trademark Office, Alexandria, VA, dated Mar. 27, 2019, 20 Pages. [cited by applicant]
Office Action, U.S. Appl. No. 16/006,897, United States Patent and Trademark Office, Alexandria, VA, mailed Jun. 26, 2019, 29 Pages. [cited by applicant]
PCT Invitation to Pay Additional Fees, PCT Application PCT/US2018/039731, ISA/EP, European Patent Office, Netherlands, dated Sep. 20, 2018, 18 Pages. [cited by applicant]
Previdi S., et al., “IPv6 Segment Routing Header (SRH) draft-ietf-6man-segment-routing-header-06.txt,” Internet Engineering Task Force (IETF), Standard Working Draft, Internet Society (ISOC) 4, Rue Des Falaises CH-1205 … [cited by applicant]
Previdi S., et al., “IPv6 Segment Routing Header (SRH) draft-ietf-6man-segment-routing-header-07,” Jul. 20, 2017, Network Working Group, the Internet Society, Reston, VA, USA, pp. 1-34. [cited by applicant]
Previdi S., et al., “IPv6 Segment Routing Header (SRH) draft-ietf-6man-segment-routing-header-10,” The Internet Society, Reston, VA, USA, Mar. 17, 2018, 33 Pages. [cited by applicant]
Previdi S., et al., “IPv6 Segment Routing Header (SRH): draft-ietf-6man-segment-routing-header-13,” The Internet Society, Reston, VA, USA, May 23, 2018, 21 Pages. [cited by applicant]
Quinn P., et al., “Network Service Header (NSH) draft-ietf-sfc-nsh-20,” Service Function Chaining, Standards Track, the Internet Society, Reston, VA, USA, Sep. 1, 2017, 34 Pages. [cited by applicant]
Rabadan J., et al., “IP Prefix Advertisement in EVPN: draft-ietf-bess-evpn-prefix-advertisement-05,” The Internet Society, Reston, VA, USA, BESS Workgroup, Jul. 18, 2017, 33 Pages. [cited by applicant]
Rekhter Y., et al., “A Border Gateway Protocol 4 (BGP-4),” Network Working Group, RFC 4271, Reston, VA, USA, Jan. 2006, pp. 1-104, https://www.rfc-editor.org/rfc/rfc4271. [cited by applicant]
Response to Communication Pursuant to Rule 161 filed in EP Application No. 18742689.5, dated Apr. 15, 2020, Mathys Squire LLP, London, England, 32 Pages. [cited by applicant]
Rosen E., et al., “BGP/MPLS IP Virtual Private Networks (VPNs),” Network Working Group RFC 4364, Feb. 2006, 47 pages. [cited by applicant]
Rosen E., et al., “IANA Registries for BGP Extended Communities,” RFC 7153, Internet Engineering Task Force, the Internet Society, Reston, VA, USA, Mar. 2014, 16 Pages. [cited by applicant]
Rosen E., et al., “Multiprotocol Label Switching Architecture,” Network Working Group, Request for Comments: 3031, Jan. 2001, pp. 1-61. [cited by applicant]
Rosen E., et al., “The BGP Tunnel Encapsulation Attribute: draft-ietf-idr-tunnel-encaps-07,” The Internet Society, Reston, VA, USA, Jul. 17, 2017, 41 Pages. [cited by applicant]
Sajassi A., Ed., “A Network Virtualization Overlay Solution using EVPN; draft-ieff-bess-evpn-overlay-08,” The Internet Society, Reston, VA, USA, Mar. 27, 2017, 29 Pages. [cited by applicant]
Sajassi A., et al., “BGP MPLS-Based Ethernet VPN,” Internet Engineering Task Force (IETF), Request for Comments: 7432, Feb. 2015, pp. 1-56, Retrieved from URL: https://ietf.org. [cited by applicant]
Sajassi A., et al., “Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN),” RFC 7623, the Internet Society, Reston, VA, USA, Sep. 2015, 23 Pages. [cited by applicant]
Sajassi A., et al., “Requirements for Ethernet VPN (EVPN),” RFC 7209, the Internet Society, Reston, VA, USA, May 2014, 15 Pages. [cited by applicant]
Sangli S., et al., “BGP Extended Communities Attribute,” RFC 4360, the Internet Society, Reston, VA, USA, Feb. 2006, 12 Pages. [cited by applicant]
Seneviratfine T., et al., “MPLS Label Stack Authentication Methods and Algorithms: draft-tsenevir-mpls-lauth-01.txt,” The Internet Society, Reston, VA, USA, Jul. 2001, 7 Pages. [cited by applicant]