<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-spring-segment-routing-msdc" target="https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-msdc-11">
   <front>
      <title>BGP Prefix Segment in Large-Scale Data Centers</title>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="G." surname="Dawra" fullname="Gaurav Dawra">
         <organization>LinkedIn</organization>
      </author>
      <author initials="E." surname="Aries" fullname="Ebben Aries">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="P." surname="Lapukhov" fullname="Petr Lapukhov">
         <organization>Facebook</organization>
      </author>
      <date month="November" day="29" year="2018" />
      <abstract>
	 <t>This document describes the motivation for, and benefits of, applying Segment Routing (SR) in BGP-based large-scale data centers.  It describes the design to deploy SR in those data centers for both the MPLS and IPv6 data planes.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-spring-segment-routing-msdc-11" />
   
</reference>
