[alto] Fwd: I-D Action: draft-ietf-alto-xdom-disc-02.txt

Sebastian Kiesel <ietf-alto@skiesel.de> Mon, 05 March 2018 20:12 UTC

Return-Path: <sebi@gw01.ehlo.wurstkaes.de>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57DA412DA6D for <alto@ietfa.amsl.com>; Mon, 5 Mar 2018 12:12:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVrg7qey7rnv for <alto@ietfa.amsl.com>; Mon, 5 Mar 2018 12:12:31 -0800 (PST)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C198312DB71 for <alto@ietf.org>; Mon, 5 Mar 2018 12:12:30 -0800 (PST)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.89) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1eswTE-0001qZ-9x for alto@ietf.org; Mon, 05 Mar 2018 21:12:28 +0100
Date: Mon, 5 Mar 2018 21:12:28 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: alto@ietf.org
Message-ID: <20180305201228.l5jl76kyynu2jf57@gw01.ehlo.wurstkaes.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/23YTiUCeBb_rs11F3PhdGN-M78k>
Subject: [alto] Fwd: I-D Action: draft-ietf-alto-xdom-disc-02.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2018 20:12:32 -0000

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 internet-drafts@ietf.org -----

Date: Mon, 05 Mar 2018 11:56:18 -0800
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: alto@ietf.org
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
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

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