<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-alto-server-discovery" target="https://datatracker.ietf.org/doc/html/draft-ietf-alto-server-discovery-03">
   <front>
      <title>ALTO Server Discovery</title>
      <author initials="S." surname="Kiesel" fullname="Sebastian Kiesel">
         </author>
      <author initials="M." surname="Stiemerling" fullname="Martin Stiemerling">
         </author>
      <author initials="N." surname="Schwan" fullname="Nico Schwan">
         </author>
      <author initials="M." surname="Scharf" fullname="Michael Scharf">
         </author>
      <author initials="S." surname="Yongchao" fullname="Song Yongchao">
         </author>
      <date month="March" day="8" year="2012" />
      <abstract>
	 <t>   The goal of Application-Layer Traffic Optimization (ALTO) is to
   provide guidance to applications, which have to select one or several
   hosts from a set of candidates that are able to provide a desired
   resource.

   Entities seeking guidance need to discover and possibly select an
   ALTO server to ask.  This is called ALTO server discovery.  This memo
   describes an ALTO server discovery mechanism based on several
   alternative mechanisms that are applicable in a diverse set of ALTO
   deployment scenarios.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-alto-server-discovery-03" />
   
</reference>
