<?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-10">
   <front>
      <title>Application-Layer Traffic Optimization (ALTO) Server Discovery</title>
      <author initials="H." surname="Song" fullname="Haibin Song">
         <organization>Huawei</organization>
      </author>
      <author initials="S." surname="Kiesel" fullname="Sebastian Kiesel">
         <organization>University of Stuttgart</organization>
      </author>
      <author initials="M." surname="Stiemerling" fullname="Martin Stiemerling">
         <organization>NEC Europe Ltd.</organization>
      </author>
      <author initials="N." surname="Schwan" fullname="Nico Schwan">
         <organization>Thales Deutschland</organization>
      </author>
      <author initials="M." surname="Scharf" fullname="Michael Scharf">
         <organization>Alcatel-Lucent Bell Labs</organization>
      </author>
      <date month="September" day="9" year="2013" />
      <abstract>
	 <t>The goal of Application-Layer Traffic Optimization (ALTO) is to provide guidance to applications that have to select one or several hosts from a set of candidates capable of providing a desired resource. ALTO is realized by a client-server protocol. Before an ALTO client can ask for guidance, it needs to discover one or more ALTO servers.

 This document specifies a procedure for resource-consumer-initiated ALTO server discovery, which can be used if the ALTO client is embedded in the resource consumer.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-alto-server-discovery-10" />
   
</reference>
