[alto] RFC 8686 vs. RFC 6708
Sebastian Kiesel <ietf-alto@skiesel.de> Thu, 06 February 2020 22:23 UTC
Return-Path: <ietf-alto@skiesel.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 9AAC712082D for <alto@ietfa.amsl.com>; Thu, 6 Feb 2020 14:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 o1X1U2MpM8CM for <alto@ietfa.amsl.com>; Thu, 6 Feb 2020 14:23:01 -0800 (PST)
Received: from mx10.wurstkaes.de (mx10.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 A88341200B3 for <alto@ietf.org>; Thu, 6 Feb 2020 14:23:01 -0800 (PST)
Received: from l1.wurstkaes.de ([2a02:a00:e000:116::c1]:57494) by mx10.wurstkaes.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <ietf-alto@skiesel.de>) id 1izpY3-0000Zz-P4 for alto@ietf.org; Thu, 06 Feb 2020 23:22:59 +0100
Date: Thu, 06 Feb 2020 23:22:56 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: alto@ietf.org
Message-ID: <20200206222256.GE1044@l1.wurstkaes.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Organization: my personal mail account
Accept-Languages: en, de
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/OeTJtzlCue7Rrejg8S8HQLqXlOo>
Subject: [alto] RFC 8686 vs. RFC 6708
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Feb 2020 22:23:04 -0000
Dear ALTO WG, RFC 8686 "ALTO Cross-Domain Server Discovery" (was: draft-ietf-alto-xdom-disc-06) has just been published. Thanks to all contributors, reviewers, and all others who helped to make that happen! *looking in my closet for that old and dusty hat that I haven't worn in a long time, the one with the "ALTO requirements document editor" badge* Ladies and gentlemen, almost 12 years after the IETF P2PI workshop and the subsequent inception of the ALTO working group, the RFC editor has published RFC 8686 today. This specification, called "ALTO Cross-Domain Server Discovery" addresses requirements 33, 35, and 36 from RFC 6708, the ALTO Requirements document published in 2012. These were the last outstanding requirements, in other words: we have reached our initial goals (and of course various additional ones that emerged later). A big thank you to everyone who contributed! Looking forward to see many new ALTO use cases and protocol extensions. Thanks, Sebastian ----- Forwarded message from rfc-editor@rfc-editor.org ----- Date: Thu, 6 Feb 2020 14:06:49 -0800 (PST) From: rfc-editor@rfc-editor.org To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org Cc: drafts-update-ref@iana.org, alto@ietf.org, rfc-editor@rfc-editor.org Subject: [alto] RFC 8686 on Application-Layer Traffic Optimization (ALTO) Cross‑Domain Server Discovery 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 _______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto ----- End forwarded message -----
- [alto] RFC 8686 vs. RFC 6708 Sebastian Kiesel
- Re: [alto] RFC 8686 vs. RFC 6708 Vijay Gurbani
- Re: [alto] RFC 8686 vs. RFC 6708 Y. Richard Yang