<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.xu-lsvr-midr-use-cases" target="https://datatracker.ietf.org/doc/html/draft-xu-lsvr-midr-use-cases-00">
   <front>
      <title>Use Cases and Requirements for Multi-Domain and Hybrid Overlay/Underlay BGP-SPF (LSVR)</title>
      <author initials="M." surname="Xu" fullname="Mingwei Xu">
         <organization>Tsinghua University</organization>
      </author>
      <author initials="B." surname="Wang" fullname="Bo Wang">
         <organization>Tsinghua University</organization>
      </author>
      <author initials="Y." surname="Yang" fullname="Yuan Yang">
         <organization>Tsinghua University</organization>
      </author>
      <author initials="Y." surname="Liu" fullname="Yi Liu">
         <organization>Tsinghua University</organization>
      </author>
      <author initials="L." surname="Zhang" fullname="Leroy Zhang">
         <organization>ByteDance Inc.</organization>
      </author>
      <date month="July" day="6" year="2026" />
      <abstract>
	 <t>   This document presents use cases and the routing requirements they
   imply for operating the BGP Link State (BGP-LS) Shortest Path First
   (SPF) routing developed in the Link-State Vector Routing (LSVR)
   Working Group, across multiple administrative domains and over hybrid
   overlay/underlay topologies.  After motivating the work, it describes
   three scenarios of increasing complexity: a single overlay domain,
   the interconnection of multiple overlay domains, and hybrid overlay/
   underlay networks.  Each scenario gives the topology, its
   distinguishing challenges, and the requirements that follow.  The
   scenarios arise in globally distributed edge- and cloud-Point-of-
   Presence (PoP) deployments that serve performance-sensitive
   applications such as cross-region real-time communication,
   collaborative productivity, cloud gaming, and large-scale SaaS.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-xu-lsvr-midr-use-cases-00" />
   
</reference>
