<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bess-evpn-vpws-fxc" target="https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-vpws-fxc-12">
   <front>
      <title>EVPN VPWS Flexible Cross-Connect Service</title>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Brissette" fullname="Patrice Brissette">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="J." surname="Uttaro" fullname="Jim Uttaro">
         <organization>AT&amp;T</organization>
      </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="S." surname="Boutros" fullname="Sami Boutros">
         <organization>Ciena</organization>
      </author>
      <author initials="J." surname="Rabadan" fullname="Jorge Rabadan">
         <organization>Nokia</organization>
      </author>
      <date month="December" day="18" year="2024" />
      <abstract>
	 <t>   This document describes a new EVPN VPWS service type specifically for
   multiplexing multiple attachment circuits across different Ethernet
   Segments and physical interfaces into a single EVPN VPWS service
   tunnel and still providing Single-Active and All-Active multi-homing.
   This new service is referred to as EVPN VPWS flexible cross-connect
   service.  This document specifies a solution based on extensions to
   EVPN VPWS(RFC8214) which in turn is based on extensions to EVPN
   (RFC7432).  Therefore, a thorough understanding of RFC7432 and
   RFC8214 are prerequisites for this document.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bess-evpn-vpws-fxc-12" />
   
</reference>
