RFC 8686 on Application-Layer Traffic Optimization (ALTO) Cross‑Domain Server Discovery
rfc-editor@rfc-editor.org Thu, 06 February 2020 22:07 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D136912081C; Thu, 6 Feb 2020 14:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.201
X-Spam-Level:
X-Spam-Status: No, score=-3.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.999, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 rU7NLXwJPjiD; Thu, 6 Feb 2020 14:07:05 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D649812011B; Thu, 6 Feb 2020 14:07:05 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 74774F406F0; Thu, 6 Feb 2020 14:06:49 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8686 on Application-Layer Traffic Optimization (ALTO) Cross‑Domain Server Discovery
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, alto@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200206220649.74774F406F0@rfc-editor.org>
Date: Thu, 06 Feb 2020 14:06:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/EhsMxYPHrEtlCB4ZYPRPEbylMIY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2020 22:07:08 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8686
Title: Application-Layer Traffic Optimization (ALTO)
Cross‑Domain Server Discovery
Author: S. Kiesel,
M. Stiemerling
Status: Standards Track
Stream: IETF
Date: February 2020
Mailbox: ietf-alto@skiesel.de,
mls.ietf@gmail.com
Pages: 34
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-alto-xdom-disc-06.txt
URL: https://www.rfc-editor.org/info/rfc8686
DOI: 10.17487/RFC8686
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 necessary to discover an ALTO server outside of
the ALTO client's 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 (typically,
"ALTO:https") as parameters. It performs DNS lookups (for NAPTR
resource records in the "in-addr.arpa." or "ip6.arpa." trees) and
returns one or more URIs of information resources related to that IP
address or prefix.
This document is a product of the Application-Layer Traffic Optimization Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC