<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.yang-alto-multi-domain" target="https://datatracker.ietf.org/doc/html/draft-yang-alto-multi-domain-03">
   <front>
      <title>ALTO Multi-Domain Use Cases and Services</title>
      <author initials="D. A. L." surname="Perez" fullname="Danny Alex Lachos Perez">
         <organization>Benocs</organization>
      </author>
      <author initials="I." surname="Poese" fullname="Ingmar Poese">
         <organization>Benocs</organization>
      </author>
      <author initials="M." surname="Lassnig" fullname="Mario Lassnig">
         <organization>CERN</organization>
      </author>
      <author initials="A." surname="Gu" fullname="Annie Gu">
         <organization>Yale University</organization>
      </author>
      <author initials="Y. R." surname="Yang" fullname="Y. Richard Yang">
         <organization>Yale University</organization>
      </author>
      <author initials="J." surname="Ros-Giralt" fullname="Jordi Ros-Giralt">
         <organization>Qualcomm</organization>
      </author>
      <date month="July" day="10" year="2023" />
      <abstract>
	 <t>   Application-Layer Traffic Optimization (ALTO) provides means for
   network applications to obtain network information.  Although ALTO is
   inherently multi-domain, in that the ALTO server representing the
   network and the ALTO client requesting the network information belong
   to different trust domains, there are more general cases where the
   path from the source and the destination spans multiple autonomous
   networks, which we call multi-domain settings.  This document first
   gives three multi-domain use cases, and the challenges to address the
   challenges.  It then gives a brief update on the implementation
   solutions that we explored to address the challenges.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-yang-alto-multi-domain-03" />
   
</reference>
