Re: [alto] RFC 8686 vs. RFC 6708
Vijay Gurbani <vijay.gurbani@gmail.com> Thu, 06 February 2020 23:19 UTC
Return-Path: <vijay.gurbani@gmail.com>
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 E6497120829 for <alto@ietfa.amsl.com>; Thu, 6 Feb 2020 15:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 DP2Upp5W6kul for <alto@ietfa.amsl.com>; Thu, 6 Feb 2020 15:19:20 -0800 (PST)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 241C712012E for <alto@ietf.org>; Thu, 6 Feb 2020 15:19:20 -0800 (PST)
Received: by mail-ed1-x533.google.com with SMTP id r21so362054edq.0 for <alto@ietf.org>; Thu, 06 Feb 2020 15:19:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Vky8dGTKz4UU2BpgA85QvCAzsNJ0NSZCerR4bvWwQj0=; b=Qo4GDPPjQMf8vHPKOv3ZOI1dSd3jx0Y0mDT57vHmyD4Yj7W4gqBTUPZtaDKZQkUPqJ UpuH+NZY6mu20G0T52b7SeEGrfsl4COXRXuol2TiG7VQOD7bvvThAWNvDGEJ7hpaH9Av Z91vGCTq6llX/jVvd9SLqRBYThvHV3jhQohfk19OUi6W4QOdTX9CMY4xzyfmicQYLaKL YgnjDLubv4v5u6yEbu+aGpcaQUgvUbgfwg4J2joNioAgJXCdJXYUfQecOjw9pdigUrfu wpoXF83vjPbGQjJC3KVshf56I//e9GrwZNWMIoDdCxyJD42oLPTNzkLTxuXlrLVSaR6o 7QQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Vky8dGTKz4UU2BpgA85QvCAzsNJ0NSZCerR4bvWwQj0=; b=nT9VXIlczXaFfU91rDNj4AVBOFk1lopmblfWp/uDG+UIrcDrhtFqMtfFX7t1cZHpOS MuLhajGfSkmcQBYhpY+csPDB8DuAh0gVBqI1FqmEmlCVBUH8lVawjyaCbkM9SYaHUE8J Po+CNnTp0eBznOquCRFW1UUqm6OzgP23DqnYB+yV1rcuEjecXSMUuWsJfoAktCoCt0lH 5SS5Pim+pPUHiatBmTV23ajNETq/rGMLbCzjsvk9NFMFXU3RE+U5hS1PPIiOJC04+JuX ww/uDYzOMbN4SgeYrfjpGGOS5KF+su8gg7xkAVrIJkoyuVcbQZ7pSxSuouSUXa/IvT9B 082Q==
X-Gm-Message-State: APjAAAXAzBgwWP+Mm7vtEfKVoOsq7S5KgdeS+6E9MhOScidhqMZXMkNL +j+H//XDN1Eojw4vzxt3dMyIYC9NMY4TnU9Z3a+Jjg==
X-Google-Smtp-Source: APXvYqzZNsotq4kdCDIJ6KgFHm7f2IyKUGeqvVEMQIt1JZjl+JRGviYTZ/qc9lEQXBEWgbYDv+ORsTe82q/V1MVJwSE=
X-Received: by 2002:a17:906:1904:: with SMTP id a4mr5333048eje.134.1581031158306; Thu, 06 Feb 2020 15:19:18 -0800 (PST)
MIME-Version: 1.0
References: <20200206222256.GE1044@l1.wurstkaes.de>
In-Reply-To: <20200206222256.GE1044@l1.wurstkaes.de>
From: Vijay Gurbani <vijay.gurbani@gmail.com>
Date: Thu, 06 Feb 2020 17:19:05 -0600
Message-ID: <CAMMTW_KdQENEtjdj_6NcSnFT+oXwW2LFfrYLg6MXHjZGyPO-YQ@mail.gmail.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>
Cc: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000091dc9e059df080fa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/24V6vbiG4B99to67561qdaPjsis>
Subject: Re: [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 23:19:24 -0000
Congratulations!! We should let Enrico know :-) On Thu, Feb 6, 2020, 4:23 PM Sebastian Kiesel <ietf-alto@skiesel.de> wrote: > 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 mailing list > alto@ietf.org > https://www.ietf.org/mailman/listinfo/alto >
- [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