Dear ALTO WG folks,

this new version of the Cross-Domain Server Discovery draft gives
a better specification of the discovery procedure (Ch. 2), without 
changing it.  We hope that it addresses all comments from the reviews
of last summer. Thanks again to all reviewers, and as allways: further
comments are most welcome!

cheers,
Sebastian

----- Forwarded message from [email protected] -----

Date: Mon, 05 Mar 2018 11:56:18 -0800
From: [email protected]
To: [email protected]
Cc: [email protected]
Subject: [alto] I-D Action: draft-ietf-alto-xdom-disc-02.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Application-Layer Traffic Optimization WG of 
the IETF.

        Title           : Application Layer Traffic Optimization (ALTO) 
Cross-Domain Server Discovery
        Authors         : Sebastian Kiesel
                          Martin Stiemerling
        Filename        : draft-ietf-alto-xdom-disc-02.txt
        Pages           : 31
        Date            : 2018-03-05

Abstract:
   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 that can provide suitable guidance.

   In some deployment scenarios, in particular if the information about
   the network topology is partitioned and distributed over several ALTO
   servers, it may be needed to discover an ALTO server outside of the
   own network domain, in order to get appropriate guidance.  This
   document details applicable scenarios, itemizes requirements, and
   specifies a procedure for ALTO cross-domain server discovery.

   Technically, the procedure specified in this document takes one
   IP address or prefix and a U-NAPTR Service Parameter (i.e., "ALTO:
   http" or "ALTO:https") as parameters.  It performs DNS lookups (for
   NAPTR resource records in the in-addr.arpa. or ip6.arpa. tree) and
   returns one or more URI(s) of information resources related to that
   IP address or prefix.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-xdom-disc/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-alto-xdom-disc-02
https://datatracker.ietf.org/doc/html/draft-ietf-alto-xdom-disc-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-alto-xdom-disc-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

----- End forwarded message -----

_______________________________________________
alto mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/alto

Reply via email to