[alto] Comments on draft-kiesel-alto-xdom-disc-02

Wendy Roome <wendy.roome@nokia-bell-labs.com> Tue, 19 July 2016 19:18 UTC

Return-Path: <wendy.roome@nokia-bell-labs.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 A7EFA12D0F4 for <alto@ietfa.amsl.com>; Tue, 19 Jul 2016 12:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 QGmtxTMy4723 for <alto@ietfa.amsl.com>; Tue, 19 Jul 2016 12:18:14 -0700 (PDT)
Received: from smtp-us.alcatel-lucent.com (us-hpswa-esg-02.alcatel-lucent.com [135.245.18.30]) (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 AF70812B016 for <alto@ietf.org>; Tue, 19 Jul 2016 12:18:14 -0700 (PDT)
Received: from us70uumx4.dmz.alcatel-lucent.com (unknown [135.245.18.16]) by Websense Email Security Gateway with ESMTPS id 83524BD9C06DF for <alto@ietf.org>; Tue, 19 Jul 2016 19:18:10 +0000 (GMT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (us70uusmtp4.zam.alcatel-lucent.com [135.5.2.66]) by us70uumx4.dmz.alcatel-lucent.com (GMO) with ESMTP id u6JJIDFI029025 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <alto@ietf.org>; Tue, 19 Jul 2016 19:18:13 GMT
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id u6JJICWe007404 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <alto@ietf.org>; Tue, 19 Jul 2016 19:18:12 GMT
Received: from [135.222.152.71] (wdr-i7mbp2.mh.lucent.com [135.222.152.71]) by umail.lucent.com (8.13.8/TPES) with ESMTP id u6JJIAoY025643 for <alto@ietf.org>; Tue, 19 Jul 2016 14:18:11 -0500 (CDT)
User-Agent: Microsoft-MacOutlook/14.6.6.160626
Date: Tue, 19 Jul 2016 15:18:24 -0400
From: Wendy Roome <wendy.roome@nokia-bell-labs.com>
To: IETF ALTO <alto@ietf.org>
Message-ID: <D3B3F540.7F90C2%w.roome@alcatel-lucent.com>
Thread-Topic: Comments on draft-kiesel-alto-xdom-disc-02
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/A2utAK1yAs5PTZf8k10O3Xqo9J0>
Subject: [alto] Comments on draft-kiesel-alto-xdom-disc-02
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 19 Jul 2016 19:18:17 -0000

draft-kiesel-alto-xdom-disc-02 has this (Sect 3.2, Endpoint Cost Service):

If an ALTO client wants to query the Endpoint Cost Service (see Section
11.5 of RFC 7285 [RFC7285]) for the costs from source address X to
destination address(es) Y (and Z), it has to invoke the crossdomain ALTO
server discovery procedure with parameter X. The result will be the IRD
URI of the ALTO server to query for the costs from X to Y (and Z).

My first comment was why do cross-domain ALTO server discover on X, rather
than Y or Z?

Then I realized there is a good reason. I believe most ECS queries will be
either 1->N or N->1. That is, costs from many sources to one destination
(client selecting server from which to download a file) or one source to
many dests (client selecting server for upload).

So if the query is 1->N or N->1, do cross-domain discovery on the one
address. That is probably the address of the real client - the one which
needs ALTO guidance. So use the ALTO server which has the best data for
that address.

	- Wendy Roome