[alto] Some questions for alto-xdom-disc

xin wang <xinwang2014@hotmail.com> Fri, 01 December 2017 04:06 UTC

Return-Path: <xinwang2014@hotmail.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 6F0D81270B4; Thu, 30 Nov 2017 20:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.875
X-Spam-Level:
X-Spam-Status: No, score=-0.875 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.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 fxm9vdgvVGBe; Thu, 30 Nov 2017 20:06:12 -0800 (PST)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-sn1nam04olkn0822.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe4c::822]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A88631241F5; Thu, 30 Nov 2017 20:06:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=aDLtntE0QxTivkXAYqgfVPVazndRpbAPoXHTUS/QRHM=; b=K4wAZSLLSTqJR6UmAHjSiwqSr3bhkmo3OXEROBTBoiM4Q4lA+ahR/gza3rlixQYrOVAO6iFVQrJJFrv+2Cvryhy9HShhWz3Gv+5CGb360CSSQMx58jYMkUelTjtLBnqAysgeb0JzjLu9S+mdgUrWAGmMX9i8pehOWLZGlj6sAfrDrbsIv9Hfnx1EBnZ+T5vcIH5qQoAzbFpQIEdjOSb9+BEL6ocKRsfb8mvs64qN1Y0PG685B/2j8cIFbAUItyYctM3qTRcbvvUvg6i1vnZY0ntGLizpktv7u/LDYnjMnGZLsWADye6rr+dyQ/LBjm9RjJbY8Pza/kggbIJSpbAJWA==
Received: from CO1NAM04FT011.eop-NAM04.prod.protection.outlook.com (10.152.90.55) by CO1NAM04HT056.eop-NAM04.prod.protection.outlook.com (10.152.91.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.239.4; Fri, 1 Dec 2017 04:05:47 +0000
Received: from DM2PR08MB1337.namprd08.prod.outlook.com (10.152.90.52) by CO1NAM04FT011.mail.protection.outlook.com (10.152.90.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.239.4 via Frontend Transport; Fri, 1 Dec 2017 04:05:47 +0000
Received: from DM2PR08MB1337.namprd08.prod.outlook.com ([fe80::818c:4121:13c4:2fa7]) by DM2PR08MB1337.namprd08.prod.outlook.com ([fe80::818c:4121:13c4:2fa7%15]) with mapi id 15.20.0282.007; Fri, 1 Dec 2017 04:05:47 +0000
From: xin wang <xinwang2014@hotmail.com>
To: "draft-ietf-alto-xdom-disc@ietf.org" <draft-ietf-alto-xdom-disc@ietf.org>
CC: IETF ALTO <alto@ietf.org>
Thread-Topic: Some questions for alto-xdom-disc
Thread-Index: AQHTallX4KCqNlp+v0CCce0S3MxUOg==
Date: Fri, 1 Dec 2017 04:05:47 +0000
Message-ID: <DM2PR08MB1337AE2BC4D503AB8FDCC506A8390@DM2PR08MB1337.namprd08.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:039D0E3B3D15672395C81D5F1A04398D0422F6B5FBD0DFCF2F7D7A52DE60B5DF; UpperCasedChecksum:41A37ED8B6C0C55B4D5D106A954640D1850ED643352EBCB9A30D7FAF36400947; SizeAsReceived:6965; Count:45
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [Ugg1npo580w1Wf8GNCzHWzdCeDctERB1GT6ptjbN5hw=]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CO1NAM04HT056; 6:JQDkBC69Zd5FNoy7uFOdnc1BU63nZIMbCvmHOBwFy11ZYmdEdLXUj5WAvo5nkPgAp2UwQscqalJE2xJb6TQZkZRFh/LXnutVSGkRk86BU3k8B1+q9IEjEuUVa3S+XiYYVwtJ3VYGu2vK1ZMmiTjcYQjpN+vtVJGjF5OWAJ7fa/e6sT9SZRBTuBLV/NGazKg4NF2/DvN05u6FeTEIBbXsDujIdYaXIoUsU8YlUBSKqm5wdJG3w+E0eeVW33CUzePTBSrdNLesr5ftFMPdkf1DFvDO0xeZHYFw+FMfzgaMiSYlvIK1CAyXGaaaNMprnqTVEjxYt6xpvlWNJWzRPxkij5nJ5BCv0rEvTLZcWfnRBbs=; 5:uZL9rQwV5zlfj2ROUiof3iJXHViHJa8gHkiXah8xOSu/XJ/lqaIhVge6PWLce61IOnTrWOgbgqJXFB+JEdkfIgYNW+niM6JqVaKUymIqOfsG+syFvtZmAXNA8wKDWnweAy6Ia01TTNl2AVK0lhXHa7q2hbuq0SszP96TzCEdcUk=; 24:IsiafQk0tOhHaN+DceHqgGDhTbrAxwO5WJrbmKbkilXgirOeVJk0DyipT4hNUmQAJhCXEgYBnAmA8+hyksL1iNckW2OZsGrPXjhQ4s0SplI=; 7:bzbcDlI1tI9ff6mdYSEWCpBwtuy6wNuRUBENsUTCzHAu+VpjPhxWzZC5vI0MTe9GjmQpWEpOOiMhBd5S2hzrCyH4bHGNPNOz0071LMNWShFREKf3FTTjkftRtzC3tI7seXLLByouzr5DCSqOXWk60vH4p6b4Pv/gU4NnwB1+9TN5t+Oh4Qwf4MdMdqOSzmQcAPOo+gExPzgGSAxqeR5AY0eIuB78c06xyXhoGjul3WEqrZfo8Z5lhFelWkdJxYAB
x-incomingheadercount: 45
x-eopattributedmessage: 0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101448)(1601125374)(1701031045); SRVR:CO1NAM04HT056;
x-ms-traffictypediagnostic: CO1NAM04HT056:
x-ms-office365-filtering-correlation-id: d6a71e75-cad8-44ae-51f7-08d53870cd35
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:CO1NAM04HT056; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:CO1NAM04HT056;
x-forefront-prvs: 05087F0C24
x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:CO1NAM04HT056; H:DM2PR08MB1337.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM2PR08MB1337AE2BC4D503AB8FDCC506A8390DM2PR08MB1337namp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d6a71e75-cad8-44ae-51f7-08d53870cd35
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Dec 2017 04:05:47.1546 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1NAM04HT056
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/y-X3vWTFuZ-uKc5W0LLLloAlEiI>
Subject: [alto] Some questions for alto-xdom-disc
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: Fri, 01 Dec 2017 04:06:13 -0000

Dear authors of alto-xdom-disc and all,


Do you have any new updates on the draft of alto-xdom-disc? I know that the draft intends to address the IRD discovery issue in the cross-domain setting, but I find that the cross-domain itself arouse my great interest.


Considering that each domain has one ALTO server that can give a useful cost value (not default) between any two endpoints in the domain for the ECS. Then, the ALTO server discovery works when a client asks for the cost value between any two endpoints in the same domain, as it will direct to the right ALTO server which can give cost values for some endpoint-pairs. It might involve multiple ALTO servers to answer a single query of ECS service but the requirement of the client can be satisfied.


However, if a client asks for a cost value between two endpoints which locate in different domains, then who should be able to give the cost value? This should be a common case if we target to deploy ALTO across the public Internet as you listed as one of the requirements for ALTO cross-domain server discovery.


There are basically two approaches for the issue above: one is to depend each ALTO server itself to compute cost values across domains (e.g., recursive sending queries to other servers); the other is to set up a hierarchy structure to relay the query to an upper ALTO server which is able to support ECS across domains. In either way, there need substantial efforts to consider/design a protocol between two ALTO servers (which is discussed a little in the Sec. 1.1.2 in your draft).


Do you think there are potential solutions can resolve the issue without depending too much on the inter-ALTO-server information exchanging? Or design inter-ALTO-server protocol is the best direction?


Best,

X. Tony Wang