
From nobody Mon Jun  5 05:38:56 2017
Return-Path: <session-request@ietf.org>
X-Original-To: alto@ietf.org
Delivered-To: alto@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD54128959; Mon,  5 Jun 2017 05:38:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: alto-chairs@ietf.org, ietf@kuehlewind.net, alto@ietf.org, vijay.gurbani@nokia.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149666633501.3119.7288087959180155724.idtracker@ietfa.amsl.com>
Date: Mon, 05 Jun 2017 05:38:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/hKGaa8PiAU-J2z5LTQAXFz3Fn0Q>
Subject: [alto] alto - New Meeting Session Request for IETF 99
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 05 Jun 2017 12:38:55 -0000

A new meeting session request has just been submitted by Vijay K. Gurbani, a Chair of the alto working group.


---------------------------------------------------------
Working Group Name: Application-Layer Traffic Optimization
Area Name: Transport Area
Session Requester: Vijay Gurbani

Number of Sessions: 1
Length of Session(s):  2.5 Hours
Number of Attendees: 20
Conflicts to Avoid: 
 First Priority: tsvarea tsvwg tcpm i2rs nvo3 supa netmod netconf cdni ippm nfvrg
 Second Priority: dispatch rtcweb sipcore lmap



People who must be present:
  Vijay K. Gurbani
  Jan Seedorf
  Mirja Kuehlewind

Resources Requested:

Special Requests:
  
---------------------------------------------------------


From nobody Wed Jun  7 01:53:01 2017
Return-Path: <jingxuan.n.zhang@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 8772F12EB17; Wed,  7 Jun 2017 01:52:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 tKRhJkGv0OFi; Wed,  7 Jun 2017 01:52:58 -0700 (PDT)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (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 CEEB412EB09; Wed,  7 Jun 2017 01:52:54 -0700 (PDT)
Received: by mail-vk0-x22f.google.com with SMTP id p85so2517536vkd.3; Wed, 07 Jun 2017 01:52:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=IH60gwq0nTf+SDrb7ZO+eU4+eX6wo+c4tuFEsTpEXrE=; b=sNfkL6X3eMeq34XOavUJHoDqci8DXwuw9XBSvJW95vZeFXBxfh1xEiHGlDP00/ZKhH ryHCXKAoC4nkr0mALnPveM0H21MnwibTZ+qo5QarzMtm1sMg+Bz8xOzsogikzHc7WM1o nGsifDZK3L68d1tXg38xQKnJTumIeyhVwJ5y6AaWryNg1G1sNjqPo9gid0/mSk9X9fnt 3z1fGsgo/6upyhrBZhqz1t9DdZbD5hjiXMbhAA2voTwXqJJ1FlxK/xpQro5sJgxeGaKc nCJ1Xbw4agbHpAEIgdEUNSG3LS5DuSeMph6rgJmNgndc1pUxuV7lwn1x3jn89N5gjO71 3y3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=IH60gwq0nTf+SDrb7ZO+eU4+eX6wo+c4tuFEsTpEXrE=; b=s3FKdmUDu0ayBht2Hj1lEy6TbQge5JfWXCeVaIG7myOQz1E+CaPxyU9ldPfus0HqG4 qkfFH0OO9iKWopOy4NZwozrCcOhd7TmOAtKKGAP521gGO+yTW05pG0dyh6H+F7MCj+sc f1l+Xck1gtct/wNWSMJ/FJckWzf5P0lRmvC/H/ZUukeAfgO7VcXm+0ZUP/xJ5aDQpnrh Ma+k+1i8M/7pi8Nfoy3D0zThOu4hpVnfa9MVMsg0hjuHe7QFNBslRg9E2SrfgKxrpRrJ gLyPl3VDYoGRFwPVtZlv63JJABFk3gUnJQ42J9Sco+PddScoSMukeFBkKJBAunlKqNVO r/BQ==
X-Gm-Message-State: AODbwcBHqPCSa0dqt3IJm+MC9s31olDQgwDJnU/b1UuLwGfbUEvIkulL UWZ/RoDhOiBbUS+2X7KIDu460gp+Sw==
X-Received: by 10.31.41.76 with SMTP id p73mr9941178vkp.94.1496825573611; Wed, 07 Jun 2017 01:52:53 -0700 (PDT)
MIME-Version: 1.0
From: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Date: Wed, 07 Jun 2017 08:52:42 +0000
Message-ID: <CAAbpuyomorgNdjm3MAAgUTwawis1g8s9ANF2RVhZMXruwohXbw@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>,  "draft-yang-alto-path-vector@ietf.org" <draft-yang-alto-path-vector@ietf.org>
Content-Type: multipart/alternative; boundary="001a113ef44a9b1be405515adc75"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/SWxZyXHI1l_-0PwMZTYtAukfXVI>
Subject: [alto] Some considerations about path vector design
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: Wed, 07 Jun 2017 08:52:59 -0000

--001a113ef44a9b1be405515adc75
Content-Type: text/plain; charset="UTF-8"

Hi all,

I am going to resume the discussion about graph representation and path
vector. After some attempts to adopt the path-vector extension, I have the
following considerations:

1. The current design is inefficient. Since IETF 98, we have agreed on the
design of a two-stage protocol extension (path-vector cost map + unified
property map) for graph representation. It is extensible enough because we
can customize the element (ane) properties. But the two-stage protocol will
conduct the long delay and increase the complexity of state maintenance.

2. The resource dependencies are not clear. The "Dependent Resources"
attribute in ALTO protocol is defined to claim the one-way resource
dependencies. But many resource dependencies should be bidirectional. e.g.
In path vector design, the cost map and the corresponding property map are
bound to the same query.

For 1, my personal idea is to deliver a service to accept a sequence of
queries. In this way, the client can query both cost map and property map
in a single request. And the server will handle the two-stage protocol
efficiently.

Here is a rough example:

request:
- resource: /alto/pv-costmap
  pids:
  - srcs: [xxx]
  - dsts: [yyy]
- resource: /alto/ane-prop-map
  query-id: $resource[0].$response.meta.queryId
  entities: $resource[0].$response.costmap.values.reduce(
            (x,y) => x.values.concat(y.values))

For 2, I have not found a good solution to handle the generic case.

Looking forward to any feedback.

Best regards,
Jensen

--001a113ef44a9b1be405515adc75
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<div><br></div><div>I am going to resume the discus=
sion about graph representation and path vector. After some attempts to ado=
pt the path-vector extension, I have the following considerations:</div><di=
v><br></div><div>1. The current design is inefficient. Since IETF 98, we ha=
ve agreed on the design of a two-stage protocol extension (path-vector cost=
 map + unified property map) for graph representation. It is extensible eno=
ugh because we can customize the element (ane) properties. But the two-stag=
e protocol will conduct the long delay and increase the complexity of state=
 maintenance.</div><div><br></div><div>2. The resource dependencies are not=
 clear. The &quot;Dependent Resources&quot; attribute in ALTO protocol is d=
efined to claim the one-way resource dependencies. But many resource depend=
encies should be bidirectional. e.g. In path vector design, the cost map an=
d the corresponding property map are bound to the same query.</div><div><br=
></div><div>For 1, my personal idea is to deliver a service to accept a seq=
uence of queries. In this way, the client can query both cost map and prope=
rty map in a single request. And the server will handle the two-stage proto=
col efficiently.</div><div><br></div><div>Here is a rough example:</div><di=
v><br></div><div><font face=3D"monospace">request:</font></div><div><font f=
ace=3D"monospace">- resource: /alto/pv-costmap</font></div><div><font face=
=3D"monospace">=C2=A0 pids:</font></div><div><font face=3D"monospace">=C2=
=A0 - srcs: [xxx]</font></div><div><font face=3D"monospace">=C2=A0 - dsts: =
[yyy]</font></div><div><font face=3D"monospace">- resource: /alto/ane-prop-=
map</font></div><div><font face=3D"monospace">=C2=A0 query-id: $resource[0]=
.$response.meta.queryId</font></div><div><font face=3D"monospace">=C2=A0 en=
tities: $resource[0].$response.costmap.values.reduce(</font></div><div><fon=
t face=3D"monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (x,y) =3D&gt=
; x.values.concat(y.values))</font></div><div><br></div><div>For 2, I have =
not found a good solution to handle the generic case.</div><div><br></div><=
div>Looking forward to any feedback.</div><div><br></div><div>Best regards,=
</div><div>Jensen</div></div>

--001a113ef44a9b1be405515adc75--


From nobody Tue Jun 20 20:58:03 2017
Return-Path: <dawn_chen_f@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 286A8126D05; Tue, 20 Jun 2017 20:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.126
X-Spam-Level: 
X-Spam-Status: No, score=-1.126 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_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 CWnh73PGxkBn; Tue, 20 Jun 2017 20:57:59 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-oln040092253045.outbound.protection.outlook.com [40.92.253.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F878126DCA; Tue, 20 Jun 2017 20:57:55 -0700 (PDT)
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=Ly6xRRKX/0luAo/vI2QdOHgR+Ea/qV+Oh6K3fv0N280=; b=KORhImHuRY3BKgtBrM6fmLtncbdrjrmz0wrVDOfRvTtTQ8bUVj+mb2jbXEkvIG4gIk05udAxa0c/IWG4N02v4X2vOyqgOXwNqBvrDCtqZx4X7MDMBzev5117Ugi8ynaOcoWdGm4/fMQ40HLIMCSLbgweMEL7s2xaCmZZY4EbbCfyGBBM47k83XIcjR8yXvIqCyYQ+BIcuQCAwH1vStpY57queRWMuL2gR5IgXcusnZQZtIJQIyLqhYvf41Gh/7OgtYoC3sajLdeIxibgUyQxt+5ItHcAQSBUEZvJBIzV+W2nSs1NEoGLjCEE4yAaAAIuBBT4OCB8ySILWLe7wg7rcQ==
Received: from HK2APC01FT115.eop-APC01.prod.protection.outlook.com (10.152.248.55) by HK2APC01HT077.eop-APC01.prod.protection.outlook.com (10.152.249.122) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1157.12; Wed, 21 Jun 2017 03:57:52 +0000
Received: from HK2PR0401MB1588.apcprd04.prod.outlook.com (10.152.248.53) by HK2APC01FT115.mail.protection.outlook.com (10.152.248.194) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1157.12 via Frontend Transport; Wed, 21 Jun 2017 03:57:52 +0000
Received: from HK2PR0401MB1588.apcprd04.prod.outlook.com ([fe80::55b9:5e68:5795:5198]) by HK2PR0401MB1588.apcprd04.prod.outlook.com ([fe80::55b9:5e68:5795:5198%14]) with mapi id 15.01.1178.018; Wed, 21 Jun 2017 03:57:52 +0000
From: Dawn Chan <dawn_chen_f@hotmail.com>
To: "draft-ietf-alto-cost-calendar@ietf.org" <draft-ietf-alto-cost-calendar@ietf.org>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: Some opinions about cost calendar
Thread-Index: AQHS6kKO/F96ShC+eESr7CeYtldFgA==
Date: Wed, 21 Jun 2017 03:57:52 +0000
Message-ID: <HK2PR0401MB1588F6C5286616118F67FA48B5DA0@HK2PR0401MB1588.apcprd04.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:EE45E4993C1B9C2A0EF8A74C67FE8ED6FD436B2E70E7E3A98406C60D152484C3; UpperCasedChecksum:9EE34CE9A811F0A8567570C6812F206ADD377FB78930E15E62984AEF4A2334EE; SizeAsReceived:7183; Count:43
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [iM5XaC3bxofYf+m2Jcmw7N5IRMHMIGGe]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HK2APC01HT077; 7:q5QOhUzlbe9Nb/Hb8rgbsJf3CJ1aq6H1QDp9w+mHhf5Rdp4McTshk6W2LI2X09c5Cpny2lmR41cdprLN3kYaCk5Qec54Ay74FienPAiO8PBnsD4j2PcsmR5ZhVqsnPOK7xGTwhpUmO/3uc/iHhuXuVeTtpjD6zb9J8OUF+amPh2H79pzcHs/rsmAPuqz6U9Tbi7h1ABdydHJVMY6Zlh366pJtaC+/in2u9lJfhrNLLvlPgL8DwKn/2A50DaWtC/WFXy4Xdk1rGYyqoI7a5A1jX/PW0eNBLoxhMnqnZNq9CDQoZoKU7lTE7dN+pRIWA2RYk6J29JI+HfrGv2FsxjslCE7W+TzfqepRSdRZ6nts53e7RpnB7YFC2v5napE8LRadn5OdiAnHsk52aEW6xNsEUYqEO+3A1RmURqYecOJDzR9nqXV4Gw4NWfO88gi706U+2g39IXGz2ma3pco63NAKcANl0gF77ThSVi+4EXZp5bPkbBwHYVhylY1vB0xIO+x32S+9iTiSg8drVPoVCci3PZTlcejYbaLeh7RFOlwmG0rz6cyd+c3meEn53fNTJLwYbEYz5umMfp3QNaxc6JjKA1rAJq+8+af54lHVRfC/2N7fp+JC1/zNOJvPUucmmaAKm4ALeM450GimXWWLcXj04NMPy9/2klDV0NUyjdDCCNk30P+o9tT7kcYqNDuDnjJAGR0PJRY+hxouqrKQvaK3E3Uh53tZh7l4yUfH+22CU72cnZvpwHLO/EVIJqiZ73UE6LYXUrOc0+rp/D5yETyww==
x-incomingheadercount: 43
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HK2APC01HT077; H:HK2PR0401MB1588.apcprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-traffictypediagnostic: HK2APC01HT077:
x-ms-office365-filtering-correlation-id: 255086d5-2093-4d10-9675-08d4b859b048
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045); SRVR:HK2APC01HT077; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:HK2APC01HT077; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:HK2APC01HT077; 
x-forefront-prvs: 0345CFD558
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HK2PR0401MB1588F6C5286616118F67FA48B5DA0HK2PR0401MB1588_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jun 2017 03:57:52.5073 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT077
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/Ef2W97m-sO-rVxOIQ8TY0eouNHU>
Subject: [alto] Some opinions about cost calendar
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: Wed, 21 Jun 2017 03:58:01 -0000

--_000_HK2PR0401MB1588F6C5286616118F67FA48B5DA0HK2PR0401MB1588_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgYXV0aG9ycyBvZiBhbHRvLWNvc3QtY2FsZW5kYXIgYW5kIGFsbCwNCkFmdGVyIHJldmlld2lu
ZyB0aGUgZHJhZnQgY29zdCBjYWxlbmRhciwgSSB0aGluayB0aGVyZSBhcmUgdHdvIHBvaW50cyB0
aGF0IGNvdWxkIGJlIHNwZWNpZmllZCBtb3JlIGNsZWFybHkgaW4gdGhlIGNvc3QgY2FsZW5kYXIg
ZGVzaWduLg0KRmlyc3QsIGluIFNlY3Rpb24gNC4xLjEsIGZvciBhIG11bHRpLWNvc3QgYXdhcmUg
Y2xpZW50LCBpZiB0aGUgbnVtYmVyIG9mIHZhbHVlcyBvZiBmaWVsZCDigJxjYWxlbmRhcmVk4oCd
IGlzIGxlc3MgdGhhbiB0aGUg4oCcY29zdC10eXBlLW5hbWVz4oCdIHF1ZXJpZWQsIHRoZSBBTFRP
IHNlcnZlciBtYXkgcmV0dXJuIGFuIEVSUk9SLiBBbm90aGVyIHByb2JsZW0gcmVsYXRlZCB0byB0
aGUgZmllbGQg4oCcY2FsZW5kYXJlZOKAnSBpcyB0aGF0LCBpZiB0aGVyZSBpcyBhIOKAnGZhbHNl
4oCdIGluIGZpZWxkIOKAnGNhbGVuZGFyZWTigJ1mb3IgYSBjZXJ0YWluIGNvc3QgdHlwZSB3aGls
ZSBjb3N0IHR5cGVzIGFyZSDigJx0cnVl4oCdKGZvciBleGFtcGxlLCB0aGUgY2xpZW50IHdhbnRz
IOKAnG51bS1yb3V0aW5nY29zdOKAnSB0byBiZSBjYWxlbmRhcmVkIHdoaWxlIGRvIG5vdCB3YW50
IOKAnG51bS1sYXRlbmN54oCdIHRvIGJlIGNhbGVuZGFyZWQpLCB3aGVuIHdpbGwgdGhlIGNvc3Qg
dmFsdWUgb2Yg4oCcbnVtLWxhdGVuY3nigJ0gYmUgcmV0dXJuZWQ/IFdpbGwgaXQgYmUgcmV0dXJu
ZWQgdG9nZXRoZXIgd2l0aCDigJxudW0tcm91dGluZ2Nvc3TigJ0gYWZ0ZXIgc29tZSB0aW1lIGlu
dGVydmFscz8NCg0KU2Vjb25kLCB0aGUgZm9sbG93aW5nIGlzIHRoZSBleGFtcGxlIG9mIGhlIGNh
cGFiaWxpdHkgb2YgRmlsdGVyZWQgQ29zdCBNYXAgaW4gU2VjdGlvbiAzLjMuIEFzIHdlIGNhbiBz
ZWUsIHRoZSBjb3N0LXR5cGUg4oCcbnVtLXJvdXRpbmctY29zdOKAnSBhbmQg4oCcbnVtLXBhdGhi
YW5kd2lkdGjigJ0gc2hhcmUgdGhlIHNhbWUg4oCcdGltZS1pbnRlcnZhbC1zaXpl4oCdIGFuZCDi
gJxudW1iZXItb2YtaW50ZXJ2YWxz4oCdLCBzbyB0aGV5IGFyZSBsaXN0ZWQgaW4gb25lIOKAnGNh
bGVuZGFyLWF0dHJpYnV0ZXPigJ0uDQoiY2FwYWJpbGl0aWVzIiA6IHsNCiAgICAgICAgICAgICAg
ImNvc3QtY29uc3RyYWludHMiIDogdHJ1ZSwNCiAgICAgICAgICAgICAgImNvc3QtdHlwZS1uYW1l
cyIgIDogWyAibnVtLXJvdXRpbmdjb3N0IiwgIm51bS1wYXRoYmFuZHdpZHRoIiwNCiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAic3RyaW5nLXNlcnZpY2Utc3RhdHVzIiBdLA0K
ICAgICAgICAgICAgICAiY2FsZW5kYXItYXR0cmlidXRlcyIgOiBbDQogICAgICAgICAgICAgICAg
IHsiY29zdC10eXBlLW5hbWVzIiA6IFsgIm51bS1yb3V0aW5nY29zdCIsICJudW0tcGF0aGJhbmR3
aWR0aCIgXSwNCiAgICAgICAgICAgICAgICAgICJ0aW1lLWludGVydmFsLXNpemUiIDogIjEgaG91
ciIsDQogICAgICAgICAgICAgICAgICAibnVtYmVyLW9mLWludGVydmFscyIgOiAyNA0KICAgICAg
ICAgICAgICAgICB9LA0KICAgICAgICAgICAgICAgICB7ImNvc3QtdHlwZS1uYW1lcyIgOiAic3Ry
aW5nLXNlcnZpY2Utc3RhdHVzIiwNCiAgICAgICAgICAgICAgICAgICJ0aW1lLWludGVydmFsLXNp
emUiIDogIjMwIG1pbnV0ZSIsDQogICAgICAgICAgICAgICAgICAibnVtYmVyLW9mLWludGVydmFs
cyIgOiA0OA0KICAgICAgICAgICAgICAgICB9DQogICAgICAgICAgICAgICBdIC8vIGVuZCBjYWxl
bmRhci1hdHRyaWJ1dGVzDQogICAgICAgICAgICAgICJ1c2VzIjogWyAibXktZGVmYXVsdC1uZXR3
b3JrLW1hcCIgXQ0KICAgICAgICAgICAgICB9DQp9DQoNCkhvd2V2ZXIsIHRoZSBvYmplY3QgIENh
bGVuZGFyQXR0cmlidXRlcyBkZWZpbmVkIGluIFNlY3Rpb24gMy4xIGlzIGZvbGxvd2luZywgaXQg
ZG9lcyBub3Qgc3VwcG9ydCBtdWx0aXBsZSBjb3N0LXR5cGUtbmFtZXMgaW4gYSBzaW5nbGUgQ2Fs
ZW5kYXJBdHRyaWJ1dGVzIGN1cnJlbnRseQ0Kb2JqZWN0ew0KICAgICBbSlNPTlN0cmluZyAgIGNv
c3QtdHlwZS1uYW1lO10NCiAgICAgSlNPTlN0cmluZyAgICB0aW1lLWludGVydmFsLXNpemU7DQog
ICAgIEpTT05OdW1iZXIgICAgbnVtYmVyLW9mLWludGVydmFsczsNCiB9IENhbGVuZGFyQXR0cmli
dXRlczsNCg0KQW5vdGhlciBwb2ludCBpcyB0aGF0IGluIFNlY3Rpb24gNC4yLjEsIHRoZSBvYmpl
Y3QgUmVxRW5kcG9pbnRDb3N0TWFwIGlzIGV4dGVuZGVkIGFzIGZvbGxvd3MgKGEgbmV3IGZpZWxk
IGNhbGVuZGFyZWQgaXMgYWRkZWQpLiBJdCBleHRlbmRzIHRoZSBxdWVyeSBmb3JtYXQgb2YgbGVn
YWN5IGVuZHBvaW50IGNvc3QgcXVlcnksIHdlIG1heSBhbHNvIG5lZWQgdG8gZXh0ZW5kIHRoZSBx
dWVyeSBmb3JtYXQgb2YgbXVsdGktY29zdCBhd2FyZSBxdWVyeShhIG5ldyBmaWVsZCDigJxjYWxl
bmRhcmVk4oCdIGFkZCB0byB0aGUgcXVlcnkpLg0Kb2JqZWN0IHsNCiAgICAgQ29zdFR5cGUgICAg
ICAgY29zdC10eXBlOw0KICAgICBbSlNPTkJvb2xlYW4gICAgY2FsZW5kYXJlZDwxLi4qPjtdDQog
ICAgIEVuZHBvaW50RmlsdGVyIGVuZHBvaW50czsNCiAgIH0gUmVxRW5kcG9pbnRDb3N0TWFwOw0K
ICAgb2JqZWN0IHsNCiAgICAgW1R5cGVkRW5kcG9pbnRBZGRyIHNyY3M8MC4uKj47XQ0KICAgICBb
VHlwZWRFbmRwb2ludEFkZHIgZHN0czwwLi4qPjtdDQogICB9IEVuZHBvaW50RmlsdGVyOw0KDQpU
aGF04oCZcyBteSBvcGluaW9ucyBhYm91dCB0aGUgZHJhZnQgY29zdC1jYWxlbmRhci4gV2lzaCB0
byBoZWFyIHlvdXIgaWRlYXMsIHRoYW5rcy4NCg0KQmVzdCBSZWdhcmRzLA0KRGF3bg0K

--_000_HK2PR0401MB1588F6C5286616118F67FA48B5DA0HK2PR0401MB1588_
Content-Type: text/html; charset="utf-8"
Content-ID: <D0BCC628554EE041B177C0F8EE146F95@apcprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAw
cHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBj
b2xvcjogcmdiKDY5LCA2OSwgNjkpOyIgY2xhc3M9IiI+DQpIaSBhdXRob3JzIG9mIGFsdG8tY29z
dC1jYWxlbmRhciBhbmQgYWxsLDwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7IGxpbmUt
aGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBjb2xvcjogcmdi
KDY5LCA2OSwgNjkpOyIgY2xhc3M9IiI+DQpBZnRlciByZXZpZXdpbmcgdGhlIGRyYWZ0IGNvc3Qg
Y2FsZW5kYXIsIEkgdGhpbmsgdGhlcmUgYXJlIHR3byBwb2ludHMgdGhhdCBjb3VsZCBiZSBzcGVj
aWZpZWQgbW9yZSBjbGVhcmx5IGluIHRoZSBjb3N0IGNhbGVuZGFyIGRlc2lnbi48L2Rpdj4NCjxk
aXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250LWZhbWlseTog
J0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsiIGNsYXNzPSIiPg0KRmly
c3QsIGluIFNlY3Rpb24gNC4xLjEsIGZvciBhIG11bHRpLWNvc3QgYXdhcmUgY2xpZW50LCBpZiB0
aGUgbnVtYmVyIG9mIHZhbHVlcyBvZiBmaWVsZCDigJxjYWxlbmRhcmVk4oCdIGlzIGxlc3MgdGhh
biB0aGUg4oCcY29zdC10eXBlLW5hbWVz4oCdIHF1ZXJpZWQsIHRoZSBBTFRPIHNlcnZlciBtYXkg
cmV0dXJuIGFuIEVSUk9SLiBBbm90aGVyIHByb2JsZW0gcmVsYXRlZCB0byB0aGUgZmllbGQg4oCc
Y2FsZW5kYXJlZOKAnSBpcyB0aGF0LCBpZiB0aGVyZSBpcyBhIOKAnGZhbHNl4oCdDQogaW4gZmll
bGQg4oCcY2FsZW5kYXJlZOKAnWZvciBhIGNlcnRhaW4gY29zdCB0eXBlIHdoaWxlIGNvc3QgdHlw
ZXMgYXJlIOKAnHRydWXigJ0oZm9yIGV4YW1wbGUsIHRoZSBjbGllbnQgd2FudHMg4oCcbnVtLXJv
dXRpbmdjb3N04oCdIHRvIGJlIGNhbGVuZGFyZWQgd2hpbGUgZG8gbm90IHdhbnQg4oCcbnVtLWxh
dGVuY3nigJ0gdG8gYmUgY2FsZW5kYXJlZCksIHdoZW4gd2lsbCB0aGUgY29zdCB2YWx1ZSBvZiDi
gJxudW0tbGF0ZW5jeeKAnSBiZSByZXR1cm5lZD8gV2lsbCBpdCBiZSByZXR1cm5lZA0KIHRvZ2V0
aGVyIHdpdGgg4oCcbnVtLXJvdXRpbmdjb3N04oCdIGFmdGVyIHNvbWUgdGltZSBpbnRlcnZhbHM/
PC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9u
dC1mYW1pbHk6ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9yOiByZ2IoNjksIDY5LCA2OSk7IG1pbi1o
ZWlnaHQ6IDE0cHg7IiBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBzdHls
ZT0ibWFyZ2luOiAwcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0
aWNhIE5ldWUnOyBjb2xvcjogcmdiKDY5LCA2OSwgNjkpOyIgY2xhc3M9IiI+DQpTZWNvbmQsIHRo
ZSBmb2xsb3dpbmcgaXMgdGhlIGV4YW1wbGUgb2YgaGUgY2FwYWJpbGl0eSBvZiBGaWx0ZXJlZCBD
b3N0IE1hcCBpbiBTZWN0aW9uIDMuMy4gQXMgd2UgY2FuIHNlZSwgdGhlIGNvc3QtdHlwZSDigJxu
dW0tcm91dGluZy1jb3N04oCdIGFuZCDigJxudW0tcGF0aGJhbmR3aWR0aOKAnSBzaGFyZSB0aGUg
c2FtZSDigJx0aW1lLWludGVydmFsLXNpemXigJ0gYW5kIOKAnG51bWJlci1vZi1pbnRlcnZhbHPi
gJ0sIHNvIHRoZXkgYXJlIGxpc3RlZCBpbiBvbmUg4oCcY2FsZW5kYXItYXR0cmlidXRlc+KAnS48
L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250
LWZhbWlseTogJ0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsiIGNsYXNz
PSIiPg0KJnF1b3Q7Y2FwYWJpbGl0aWVzJnF1b3Q7IDogezwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFy
Z2luOiAwcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5l
dWUnOyBjb2xvcjogcmdiKDY5LCA2OSwgNjkpOyIgY2xhc3M9IiI+DQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJnF1b3Q7Y29zdC1jb25zdHJhaW50cyZx
dW90OyA6IHRydWUsPC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgbGluZS1oZWlnaHQ6
IG5vcm1hbDsgZm9udC1mYW1pbHk6ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9yOiByZ2IoNjksIDY5
LCA2OSk7IiBjbGFzcz0iIj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmcXVvdDtjb3N0LXR5cGUtbmFtZXMmcXVvdDsmbmJzcDsgOiBbICZxdW90O251
bS1yb3V0aW5nY29zdCZxdW90OywgJnF1b3Q7bnVtLXBhdGhiYW5kd2lkdGgmcXVvdDssPC9kaXY+
DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1p
bHk6ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9yOiByZ2IoNjksIDY5LCA2OSk7IiBjbGFzcz0iIj4N
CiZuYnNwOyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZxdW90O3N0cmluZy1zZXJ2aWNlLXN0YXR1cyZxdW90OyBdLDwv
ZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZvbnQt
ZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBjb2xvcjogcmdiKDY5LCA2OSwgNjkpOyIgY2xhc3M9
IiI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJnF1
b3Q7Y2FsZW5kYXItYXR0cmlidXRlcyZxdW90OyA6IFs8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdp
bjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250LWZhbWlseTogJ0hlbHZldGljYSBOZXVl
JzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsiIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB7JnF1b3Q7Y29zdC10
eXBlLW5hbWVzJnF1b3Q7IDogWyAmcXVvdDtudW0tcm91dGluZ2Nvc3QmcXVvdDssICZxdW90O251
bS1wYXRoYmFuZHdpZHRoJnF1b3Q7IF0sPC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsg
bGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1pbHk6ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9y
OiByZ2IoNjksIDY5LCA2OSk7IiBjbGFzcz0iIj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZxdW90O3RpbWUtaW50ZXJ2YWwt
c2l6ZSZxdW90OyA6ICZxdW90OzEgaG91ciZxdW90Oyw8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdp
bjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250LWZhbWlseTogJ0hlbHZldGljYSBOZXVl
JzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsiIGNsYXNzPSIiPg0KJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJnF1b3Q7bnVtYmVy
LW9mLWludGVydmFscyZxdW90OyA6IDI0PC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsg
bGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1pbHk6ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9y
OiByZ2IoNjksIDY5LCA2OSk7IiBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfSw8L2Rpdj4NCjxkaXYgc3R5bGU9
Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250LWZhbWlseTogJ0hlbHZldGlj
YSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsiIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB7JnF1b3Q7
Y29zdC10eXBlLW5hbWVzJnF1b3Q7IDogJnF1b3Q7c3RyaW5nLXNlcnZpY2Utc3RhdHVzJnF1b3Q7
LDwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZv
bnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBjb2xvcjogcmdiKDY5LCA2OSwgNjkpOyIgY2xh
c3M9IiI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmcXVvdDt0aW1lLWludGVydmFsLXNpemUmcXVvdDsgOiAmcXVvdDszMCBt
aW51dGUmcXVvdDssPC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgbGluZS1oZWlnaHQ6
IG5vcm1hbDsgZm9udC1mYW1pbHk6ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9yOiByZ2IoNjksIDY5
LCA2OSk7IiBjbGFzcz0iIj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZxdW90O251bWJlci1vZi1pbnRlcnZhbHMmcXVvdDsg
OiA0ODwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7
IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBjb2xvcjogcmdiKDY5LCA2OSwgNjkpOyIg
Y2xhc3M9IiI+DQombmJzcDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7IH08L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhl
aWdodDogbm9ybWFsOyBmb250LWZhbWlseTogJ0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2
OSwgNjksIDY5KTsiIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7IF0gLy8gZW5kIGNhbGVuZGFyLWF0dHJpYnV0ZXM8L2Rpdj4N
CjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250LWZhbWls
eTogJ0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsiIGNsYXNzPSIiPg0K
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZxdW90O3Vz
ZXMmcXVvdDs6IFsgJnF1b3Q7bXktZGVmYXVsdC1uZXR3b3JrLW1hcCZxdW90OyBdPC9kaXY+DQo8
ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1pbHk6
ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9yOiByZ2IoNjksIDY5LCA2OSk7IiBjbGFzcz0iIj4NCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB9PC9kaXY+DQo8
ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1pbHk6
ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9yOiByZ2IoNjksIDY5LCA2OSk7IiBjbGFzcz0iIj4NCn08
L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250
LWZhbWlseTogJ0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsgbWluLWhl
aWdodDogMTRweDsiIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IHN0eWxl
PSJtYXJnaW46IDBweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1pbHk6ICdIZWx2ZXRp
Y2EgTmV1ZSc7IGNvbG9yOiByZ2IoNjksIDY5LCA2OSk7IiBjbGFzcz0iIj4NCkhvd2V2ZXIsIHRo
ZSBvYmplY3QmbmJzcDsgQ2FsZW5kYXJBdHRyaWJ1dGVzIGRlZmluZWQgaW4gU2VjdGlvbiAzLjEg
aXMgZm9sbG93aW5nLCBpdCBkb2VzIG5vdCBzdXBwb3J0IG11bHRpcGxlIGNvc3QtdHlwZS1uYW1l
cyBpbiBhIHNpbmdsZSBDYWxlbmRhckF0dHJpYnV0ZXMgY3VycmVudGx5PC9kaXY+DQo8ZGl2IHN0
eWxlPSJtYXJnaW46IDBweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1pbHk6ICdIZWx2
ZXRpY2EgTmV1ZSc7IGNvbG9yOiByZ2IoNjksIDY5LCA2OSk7IiBjbGFzcz0iIj4NCm9iamVjdHs8
L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250
LWZhbWlseTogJ0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsiIGNsYXNz
PSIiPg0KJm5ic3A7Jm5ic3A7ICZuYnNwOyBbSlNPTlN0cmluZyAmbmJzcDsgY29zdC10eXBlLW5h
bWU7XTwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7
IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBjb2xvcjogcmdiKDY5LCA2OSwgNjkpOyIg
Y2xhc3M9IiI+DQombmJzcDsmbmJzcDsgJm5ic3A7IEpTT05TdHJpbmcmbmJzcDsgJm5ic3A7IHRp
bWUtaW50ZXJ2YWwtc2l6ZTs8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhl
aWdodDogbm9ybWFsOyBmb250LWZhbWlseTogJ0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2
OSwgNjksIDY5KTsiIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7ICZuYnNwOyBKU09OTnVtYmVyJm5i
c3A7ICZuYnNwOyBudW1iZXItb2YtaW50ZXJ2YWxzOzwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2lu
OiAwcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUn
OyBjb2xvcjogcmdiKDY5LCA2OSwgNjkpOyIgY2xhc3M9IiI+DQombmJzcDt9IENhbGVuZGFyQXR0
cmlidXRlczs8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9y
bWFsOyBmb250LWZhbWlseTogJ0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5
KTsgbWluLWhlaWdodDogMTRweDsiIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8
ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1pbHk6
ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9yOiByZ2IoNjksIDY5LCA2OSk7IiBjbGFzcz0iIj4NCkFu
b3RoZXIgcG9pbnQgaXMgdGhhdCBpbiBTZWN0aW9uIDQuMi4xLCB0aGUgb2JqZWN0IFJlcUVuZHBv
aW50Q29zdE1hcCBpcyBleHRlbmRlZCBhcyBmb2xsb3dzIChhIG5ldyBmaWVsZCBjYWxlbmRhcmVk
IGlzIGFkZGVkKS4gSXQgZXh0ZW5kcyB0aGUgcXVlcnkgZm9ybWF0IG9mIGxlZ2FjeSBlbmRwb2lu
dCBjb3N0IHF1ZXJ5LCB3ZSBtYXkgYWxzbyBuZWVkIHRvIGV4dGVuZCB0aGUgcXVlcnkgZm9ybWF0
IG9mIG11bHRpLWNvc3QgYXdhcmUgcXVlcnkoYQ0KIG5ldyBmaWVsZCDigJxjYWxlbmRhcmVk4oCd
IGFkZCB0byB0aGUgcXVlcnkpLjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7IGxpbmUt
aGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBjb2xvcjogcmdi
KDY5LCA2OSwgNjkpOyIgY2xhc3M9IiI+DQpvYmplY3QgezwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFy
Z2luOiAwcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5l
dWUnOyBjb2xvcjogcmdiKDY5LCA2OSwgNjkpOyIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsgJm5i
c3A7IENvc3RUeXBlICZuYnNwOyAmbmJzcDsgJm5ic3A7IGNvc3QtdHlwZTs8L2Rpdj4NCjxkaXYg
c3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250LWZhbWlseTogJ0hl
bHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsiIGNsYXNzPSIiPg0KJm5ic3A7
Jm5ic3A7ICZuYnNwOyBbSlNPTkJvb2xlYW4mbmJzcDsgJm5ic3A7IGNhbGVuZGFyZWQmbHQ7MS4u
KiZndDs7XTwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7IGxpbmUtaGVpZ2h0OiBub3Jt
YWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBjb2xvcjogcmdiKDY5LCA2OSwgNjkp
OyIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsgJm5ic3A7IEVuZHBvaW50RmlsdGVyIGVuZHBvaW50
czs8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBm
b250LWZhbWlseTogJ0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsiIGNs
YXNzPSIiPg0KJm5ic3A7Jm5ic3A7IH0gUmVxRW5kcG9pbnRDb3N0TWFwOzwvZGl2Pg0KPGRpdiBz
dHlsZT0ibWFyZ2luOiAwcHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVs
dmV0aWNhIE5ldWUnOyBjb2xvcjogcmdiKDY5LCA2OSwgNjkpOyIgY2xhc3M9IiI+DQombmJzcDsm
bmJzcDsgb2JqZWN0IHs8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdo
dDogbm9ybWFsOyBmb250LWZhbWlseTogJ0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwg
NjksIDY5KTsiIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7ICZuYnNwOyBbVHlwZWRFbmRwb2ludEFk
ZHIgc3JjcyZsdDswLi4qJmd0OztdPC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgbGlu
ZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1pbHk6ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9yOiBy
Z2IoNjksIDY5LCA2OSk7IiBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyAmbmJzcDsgW1R5cGVkRW5k
cG9pbnRBZGRyIGRzdHMmbHQ7MC4uKiZndDs7XTwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAw
cHg7IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBj
b2xvcjogcmdiKDY5LCA2OSwgNjkpOyIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsgfSBFbmRwb2lu
dEZpbHRlcjs8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9y
bWFsOyBmb250LWZhbWlseTogJ0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5
KTsgbWluLWhlaWdodDogMTRweDsiIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8
ZGl2IHN0eWxlPSJtYXJnaW46IDBweDsgbGluZS1oZWlnaHQ6IG5vcm1hbDsgZm9udC1mYW1pbHk6
ICdIZWx2ZXRpY2EgTmV1ZSc7IGNvbG9yOiByZ2IoNjksIDY5LCA2OSk7IiBjbGFzcz0iIj4NClRo
YXTigJlzIG15IG9waW5pb25zIGFib3V0IHRoZSBkcmFmdCBjb3N0LWNhbGVuZGFyLiBXaXNoIHRv
IGhlYXIgeW91ciBpZGVhcywgdGhhbmtzLjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7
IGxpbmUtaGVpZ2h0OiBub3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBjb2xv
cjogcmdiKDY5LCA2OSwgNjkpOyIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxk
aXYgc3R5bGU9Im1hcmdpbjogMHB4OyBsaW5lLWhlaWdodDogbm9ybWFsOyBmb250LWZhbWlseTog
J0hlbHZldGljYSBOZXVlJzsgY29sb3I6IHJnYig2OSwgNjksIDY5KTsiIGNsYXNzPSIiPg0KQmVz
dCBSZWdhcmRzLDwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwcHg7IGxpbmUtaGVpZ2h0OiBu
b3JtYWw7IGZvbnQtZmFtaWx5OiAnSGVsdmV0aWNhIE5ldWUnOyBjb2xvcjogcmdiKDY5LCA2OSwg
NjkpOyIgY2xhc3M9IiI+DQpEYXduPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_HK2PR0401MB1588F6C5286616118F67FA48B5DA0HK2PR0401MB1588_--


From nobody Fri Jun 23 17:11:39 2017
Return-Path: <agenda@ietf.org>
X-Original-To: alto@ietf.org
Delivered-To: alto@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DE13712EB00; Fri, 23 Jun 2017 17:07:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <alto-chairs@ietf.org>, <vijay.gurbani@nokia.com>
Cc: ietf@kuehlewind.net, alto@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149826282690.7840.14744246469975094068.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jun 2017 17:07:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/Ywgj3gObbJ0U4ZGzO9NYSI85dTg>
Subject: [alto] alto - Requested session has been scheduled for IETF 99
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 24 Jun 2017 00:07:10 -0000

Dear Vijay Gurbani,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

alto Session 1 (2:30:00)
    Thursday, Afternoon Session I 1330-1530
    Room Name: Karlin III size: 60
    ---------------------------------------------
    


Request Information:


---------------------------------------------------------
Working Group Name: Application-Layer Traffic Optimization
Area Name: Transport Area
Session Requester: Vijay Gurbani

Number of Sessions: 1
Length of Session(s):  2.5 Hours
Number of Attendees: 20
Conflicts to Avoid: 
 First Priority: tsvarea tsvwg tcpm i2rs nvo3 supa netmod netconf cdni ippm nfvrg
 Second Priority: dispatch rtcweb sipcore lmap



People who must be present:
  Vijay K. Gurbani
  Jan Seedorf
  Mirja Kuehlewind

Resources Requested:

Special Requests:
  
---------------------------------------------------------


From nobody Sun Jun 25 11:01:50 2017
Return-Path: <ietf@j-f-s.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 BA50112441E for <alto@ietfa.amsl.com>; Sun, 25 Jun 2017 11:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.699
X-Spam-Level: 
X-Spam-Status: No, score=-4.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, 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 vuXJ9H4fwbjV for <alto@ietfa.amsl.com>; Sun, 25 Jun 2017 11:01:46 -0700 (PDT)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (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 3A6F61201F2 for <alto@ietf.org>; Sun, 25 Jun 2017 11:01:46 -0700 (PDT)
Received: from Jans-MacBook-Air.local ([2.246.97.212]) by mrelayeu.kundenserver.de (mreue001 [212.227.15.167]) with ESMTPSA (Nemesis) id 0Lcsbo-1e70zw1WTY-00iBiv for <alto@ietf.org>; Sun, 25 Jun 2017 20:01:44 +0200
To: alto@ietf.org
References: <149826282690.7840.14744246469975094068.idtracker@ietfa.amsl.com>
From: Jan Seedorf <ietf@j-f-s.de>
Message-ID: <f9e0cc15-7abd-8e64-ba31-c81e5a64d769@j-f-s.de>
Date: Sun, 25 Jun 2017 20:01:43 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <149826282690.7840.14744246469975094068.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:KfXRVS6fzdp4nyI2+nrwrvQ3rA9qVlQd2Ig2d+ETMwRhSW+bJfW ZkDqVrvgCzpabvxpU0Bth1Hps8GEPh5A7Bd0cWKjCPOSMMKWn3INIxYNfpXq10n59qdyjep 7IKDEVmzok6sB5idYdwcdqbFXE9ZHkjv+OXhwvrIwKNhVNFAzcaRw7QmTcaG7XEc/aHmfnf KoCBOUjkMhS83y2HRGIgA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:+2HHNWPn6j4=:gfBEgYYmsWjaz3FdCVkwEu Zj5siO+2qxCACyXY/bYwCzhKzaDqhFabWsx/hZd2DTcsenooQv/YZd0+ea1reI+k9FjSjk9Gc 6jbdV2uE2FtcbyY9vGVKS8SxZC1T0hIuIQlTewwil2XWyPa3zT3WTt+CpVs+aVBwik8auHa9c 8wyluvpL2XqZxVgEjgeK1KcEHh8yWO5gXjFvB09ZMOsUrjTuf9XbLXmFV8pJPLY/7ZhZ6FWF0 xnWDOH39OcCjoyLV7z1+UZl5dtXac7+VoEgRHTy0jwzt8ethN91Qsbz01oxeMvzYeB00gmeLT bumNJTeiU8LxMmHY82BsJSyObWkAoKf7LZb7ESqHHXVrcjgrFOZxLIwz2eBuBZ43vsBpyOVCr TQLAUyRDbvQnCP3kpUOfdmQxQQrUwmbYpPn81hiSIfv21fTdnIZjdRv8eqdvK/s6WvTinvXZU oQe8gvIXR0Ygl5hCJ811rnsn/7U8hVO4cQ0tLVN674eItqhNr/QD9I0ImbUgyKTI603rk4TcD tqBLbfuz9JRI/ufbplJ9GSdqBpxND84naf5OceRnmMYCtofbE52/oR4n4m6b75gdbNZKBrHou CQB6+agi6WTVvLx61cQzS0r2VwndxXIDKKQtrtwCnASO2QaS58h5pL14EaXQsgg5dmHuMNAkp oM74zB/DFrFxoaVz63l5/IfOFNcH2sbvL0VDzMPT+j5D2EUTr2SxznJIzOYzJKLSweI0BqX++ m91Ge9az50Uesw5V
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/-3yuzS913RN-b2v3AX0R3E45kyo>
Subject: [alto] ALTO Session Requests for IETF 99
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: Sun, 25 Jun 2017 18:01:49 -0000

Dear all,

please let Vijay and myself know if you intend to present during the 
ALTO session at IETF-99 (details see below). Please let us know title, 
presenter, time needed, and respective draft name.

Hope to see all of you in Prague,

  - Jan


On 24.06.17 02:07, "IETF Secretariat" wrote:
> Dear Vijay Gurbani,
>
> The session(s) that you have requested have been scheduled.
> Below is the scheduled session information followed by
> the original request.
>
> alto Session 1 (2:30:00)
>      Thursday, Afternoon Session I 1330-1530
>      Room Name: Karlin III size: 60
>      ---------------------------------------------
>      
>
>
> Request Information:
>
>
> ---------------------------------------------------------
> Working Group Name: Application-Layer Traffic Optimization
> Area Name: Transport Area
> Session Requester: Vijay Gurbani
>
> Number of Sessions: 1
> Length of Session(s):  2.5 Hours
> Number of Attendees: 20
> Conflicts to Avoid:
>   First Priority: tsvarea tsvwg tcpm i2rs nvo3 supa netmod netconf cdni ippm nfvrg
>   Second Priority: dispatch rtcweb sipcore lmap
>
>
>
> People who must be present:
>    Vijay K. Gurbani
>    Jan Seedorf
>    Mirja Kuehlewind
>
> Resources Requested:
>
> Special Requests:
>    
> ---------------------------------------------------------
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From nobody Mon Jun 26 02:08:33 2017
Return-Path: <dawn_chen_f@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 E70D1129562; Mon, 26 Jun 2017 02:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.126
X-Spam-Level: 
X-Spam-Status: No, score=-0.126 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_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 sRrXKOYWM2nv; Mon, 26 Jun 2017 02:08:30 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-oln040092253087.outbound.protection.outlook.com [40.92.253.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2A041270A0; Mon, 26 Jun 2017 02:08:26 -0700 (PDT)
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=2Mzec++346Py4NKbiaR8tR9RkdMnfYFPsmKQPED4kK8=; b=IEnMXpnXCvann10DecZu4YDXPts5ztpIsq2zSzDL9nUaIuzAaLhTP2aCwQKuhVz+89WtpD+4gtUx8jwMjKKZrrew6BOxiLMYDG1Ll8H8R4fIZW894EUwgFWmBWKyu47Y8Eikj8ln/rYBlDIDHXFv0txw3iji4FvJBtiFuNWyBsu0jGZ72sOQ0t8AYvqv6BEc0gjPg0vtgwhZ/fyF0KvPRJy6D7q2i+HqNp/wNfAImQByfPNkndvo8914t4WQKefxTlpnGuXSa1cGMzwItjBH4JudeIJH9FdLss4NDcnLKcQINl3o3dspLaZ5onA6dScmmArKcbtKmhlGOrUwCBQmGg==
Received: from SG2APC01FT025.eop-APC01.prod.protection.outlook.com (10.152.250.51) by SG2APC01HT102.eop-APC01.prod.protection.outlook.com (10.152.250.253) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1199.9; Mon, 26 Jun 2017 09:08:23 +0000
Received: from HK2PR0401MB1588.apcprd04.prod.outlook.com (10.152.250.56) by SG2APC01FT025.mail.protection.outlook.com (10.152.250.187) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.9 via Frontend Transport; Mon, 26 Jun 2017 09:08:23 +0000
Received: from HK2PR0401MB1588.apcprd04.prod.outlook.com ([fe80::9c4:7e35:e642:38db]) by HK2PR0401MB1588.apcprd04.prod.outlook.com ([fe80::9c4:7e35:e642:38db%14]) with mapi id 15.01.1199.017; Mon, 26 Jun 2017 09:08:22 +0000
From: Dawn Chan <dawn_chen_f@hotmail.com>
To: Jensen Zhang <jingxuan.n.zhang@gmail.com>
CC: "alto@ietf.org" <alto@ietf.org>, "draft-ietf-alto-path-vector@ietf.org" <draft-ietf-alto-path-vector@ietf.org>
Thread-Topic: Some considerations about path vector design
Thread-Index: AQHS32t6H605ElohBU+N4OZpXQL526I2+KkA
Date: Mon, 26 Jun 2017 09:08:22 +0000
Message-ID: <HK2PR0401MB1588257A93D04368D9CC18EAB5DF0@HK2PR0401MB1588.apcprd04.prod.outlook.com>
References: <CAAbpuyomorgNdjm3MAAgUTwawis1g8s9ANF2RVhZMXruwohXbw@mail.gmail.com>
In-Reply-To: <CAAbpuyomorgNdjm3MAAgUTwawis1g8s9ANF2RVhZMXruwohXbw@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:10218A5766CBBCA8A62D470A6C5A03884C7FE404486A8D9FB37FF5E1714FD10D; UpperCasedChecksum:CFA4037CFAC80DE897FBE0D734F6317DCAD1DA2AA43E8AF1A847BBCE822223C1; SizeAsReceived:7419; Count:46
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [aJFqpqegE5CtQ1SsGfse0FVaJtQ++6T3]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SG2APC01HT102; 7:UI9scR/a7wgEvmXDUbjRfCD2TepPXak1kcNqOAZTMFeWvi8dQXL4O7E6BD6caZJWySk5Z14EoS+pAJ7GqnXYRaBZ3c8kKwccvqiHRhH5oWk6EUbigtEzKzWu21SZKAQTE5n2k0O9lJcPZ7VAUL82zU3dy3JbSV7zQ+2dICbNAOJvn8OItGBV0fiIayaN63joctQI/W9eEHb7TtK69gbIXxqCsdIECn4bFt8JcfIUmn/3MnkppBhsz9UOkeaxrPcRn2w4K9rbT1gH7wyrra0Ni6T4bw37jNJ2WvYDA4BZ2H84hBhelXdfaHqm2VWw8RYx4bTnsANGXK0MQMnzSo1HNKzLOiPponAM6fsmHhylF5UEUS51RJTSBx5oiuo2e3A/4Gvpqsk89S9QXjZIDSuhjzT6EzFjvxx4cKExKctlUZJkP1sCnh8eC6yPNOp/2Pddu7xZNMteyAE17XMGf2kcaB5XF/nQzWMfvx2sVb2iyi3nxgSqPRhXTw7fjcMRf0T8VWrWs0sYTAjIvq6kc9tV5PQg/ieeszVXEKwHHknyG+/cIjx6uxNCHfCAfaNfFx1vlVjtNLfJEFxjbwDy7WoS8WVxMDV8+wcuDuW9AyEonEn7GtGKjI0Y3YRe81rFPXWT7I68VWvqE2U/hbs4bntm6n+8p+jhF3eqcOz4bzF9qGBGfDMPvXFLHGBJaGlQxShTW0PlmeL8cqzn09B+9rIT6BP+OUgtZjIMnvCAYLtYgbplE62GFD1YWu8zTfl25llQRMyqD/tlIHTldmRGa+XgPA==
x-incomingheadercount: 46
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:SG2APC01HT102; H:HK2PR0401MB1588.apcprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: afdcac07-69cf-4e99-ca36-08d4bc72e52a
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095); SRVR:SG2APC01HT102; 
x-ms-traffictypediagnostic: SG2APC01HT102:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:SG2APC01HT102; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SG2APC01HT102; 
x-forefront-prvs: 0350D7A55D
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HK2PR0401MB1588257A93D04368D9CC18EAB5DF0HK2PR0401MB1588_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jun 2017 09:08:22.8788 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT102
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/VscJ17tBwkxiVGPbaN8JYJgDcbI>
Subject: Re: [alto] Some considerations about path vector design
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: Mon, 26 Jun 2017 09:08:32 -0000

--_000_HK2PR0401MB1588257A93D04368D9CC18EAB5DF0HK2PR0401MB1588_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Jensen and all,
Sorry for the late reply. Please see my comments inline.
On 7 Jun 2017, at 4:52 PM, Jensen Zhang <jingxuan.n.zhang@gmail.com<mailto:=
jingxuan.n.zhang@gmail.com>> wrote:

Hi all,

I am going to resume the discussion about graph representation and path vec=
tor. After some attempts to adopt the path-vector extension, I have the fol=
lowing considerations:

1. The current design is inefficient. Since IETF 98, we have agreed on the =
design of a two-stage protocol extension (path-vector cost map + unified pr=
operty map) for graph representation. It is extensible enough because we ca=
n customize the element (ane) properties. But the two-stage protocol will c=
onduct the long delay and increase the complexity of state maintenance.

2. The resource dependencies are not clear. The "Dependent Resources" attri=
bute in ALTO protocol is defined to claim the one-way resource dependencies=
. But many resource dependencies should be bidirectional. e.g. In path vect=
or design, the cost map and the corresponding property map are bound to the=
 same query.

For 1, my personal idea is to deliver a service to accept a sequence of que=
ries. In this way, the client can query both cost map and property map in a=
 single request. And the server will handle the two-stage protocol efficien=
tly.

Here is a rough example:

request:
- resource: /alto/pv-costmap
  pids:
  - srcs: [xxx]
  - dsts: [yyy]
- resource: /alto/ane-prop-map
  query-id: $resource[0].$response.meta.queryId
  entities: $resource[0].$response.costmap.values.reduce(
            (x,y) =3D> x.values.concat(y.values))
This design idea is a one-step service to get the cost map response and the=
 property map response together in one request, which means it will return =
all the abstract network elements generated by one query. The effect of thi=
s design is probably same as the inline-mode that will directly return the =
properties of anes in the cost map, right?

For 2, I have not found a good solution to handle the generic case.

Looking forward to any feedback.

Best regards,
Jensen


--_000_HK2PR0401MB1588257A93D04368D9CC18EAB5DF0HK2PR0401MB1588_
Content-Type: text/html; charset="us-ascii"
Content-ID: <814E59544888154C84EDBC3FA6D622E7@apcprd04.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;" class=3D"">
Hi Jensen and all,
<div class=3D"">Sorry for the late reply. Please see my comments inline.<br=
 class=3D"">
<div>
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On 7 Jun 2017, at 4:52 PM, Jensen Zhang &lt;<a href=3D"mail=
to:jingxuan.n.zhang@gmail.com" class=3D"">jingxuan.n.zhang@gmail.com</a>&gt=
; wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div dir=3D"ltr" class=3D"">Hi all,
<div class=3D""><br class=3D"">
</div>
<div class=3D"">I am going to resume the discussion about graph representat=
ion and path vector. After some attempts to adopt the path-vector extension=
, I have the following considerations:</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">1. The current design is inefficient. Since IETF 98, we hav=
e agreed on the design of a two-stage protocol extension (path-vector cost =
map &#43; unified property map) for graph representation. It is extensible =
enough because we can customize the element
 (ane) properties. But the two-stage protocol will conduct the long delay a=
nd increase the complexity of state maintenance.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">2. The resource dependencies are not clear. The &quot;Depen=
dent Resources&quot; attribute in ALTO protocol is defined to claim the one=
-way resource dependencies. But many resource dependencies should be bidire=
ctional. e.g. In path vector design, the cost
 map and the corresponding property map are bound to the same query.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">For 1, my personal idea is to deliver a service to accept a=
 sequence of queries. In this way, the client can query both cost map and p=
roperty map in a single request. And the server will handle the two-stage p=
rotocol efficiently.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Here is a rough example:</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D""><font face=3D"monospace" class=3D"">request:</font></div>
<div class=3D""><font face=3D"monospace" class=3D"">- resource: /alto/pv-co=
stmap</font></div>
<div class=3D""><font face=3D"monospace" class=3D"">&nbsp; pids:</font></di=
v>
<div class=3D""><font face=3D"monospace" class=3D"">&nbsp; - srcs: [xxx]</f=
ont></div>
<div class=3D""><font face=3D"monospace" class=3D"">&nbsp; - dsts: [yyy]</f=
ont></div>
<div class=3D""><font face=3D"monospace" class=3D"">- resource: /alto/ane-p=
rop-map</font></div>
<div class=3D""><font face=3D"monospace" class=3D"">&nbsp; query-id: $resou=
rce[0].$response.meta.queryId</font></div>
<div class=3D""><font face=3D"monospace" class=3D"">&nbsp; entities: $resou=
rce[0].$response.costmap.values.reduce(</font></div>
<div class=3D""><font face=3D"monospace" class=3D"">&nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; (x,y) =3D&gt; x.values.concat(y.values))</font></div>
</div>
</div>
</blockquote>
This design idea is a one-step service to get the cost map response and the=
 property map response together in one request, which means it will return =
all the abstract network elements generated by one query. The effect of thi=
s design is probably same as the
 inline-mode that will directly return the properties of anes in the cost m=
ap, right?<br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">
<div dir=3D"ltr" class=3D"">
<div class=3D""><br class=3D"">
</div>
<div class=3D"">For 2, I have not found a good solution to handle the gener=
ic case.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Looking forward to any feedback.</div>
<div class=3D""><br class=3D"">
</div>
<div class=3D"">Best regards,</div>
<div class=3D"">Jensen</div>
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
</body>
</html>

--_000_HK2PR0401MB1588257A93D04368D9CC18EAB5DF0HK2PR0401MB1588_--


From nobody Mon Jun 26 07:05:16 2017
Return-Path: <jingxuan.n.zhang@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 7027E129C2F; Mon, 26 Jun 2017 07:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-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 zvpfJa2-raDV; Mon, 26 Jun 2017 07:05:12 -0700 (PDT)
Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::22d]) (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 72D02129BF3; Mon, 26 Jun 2017 07:05:12 -0700 (PDT)
Received: by mail-ua0-x22d.google.com with SMTP id z22so1445110uah.1; Mon, 26 Jun 2017 07:05:12 -0700 (PDT)
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=LI6t6/HJeEYg3Wyuowc69cwerbfmT+k2MtY3Hw/lVYY=; b=VEycXqKYGC1gx47EtEe+JH/w4J4v1G6KZwTuH0TgQEd0dMmPYzEc/9/AXCap0pBUcb zhKfZnnBYoTkGWRxhgrK0m91jrCZXrz1OuHx8Ss/0qQqFYOE8EJx8M7FFJ4raObiq0Id VvclDeapQjbjwTZSMa+Zy6rC0EUvwvUWRkXrE3avZsYgqc4byfWvdC0tdnyuMm+jmkOK qrUikq+LPIBIiLRQrMW/RYA92Y5EOPHoFH6cIYNSRWCG3XpW7a+Uiy1B7v/KdNUXCWEg T64WaK7KIkk47oTQ8oau7zX7gLmrt/iUxr71RY+acakPg5eMNLGAPBQBmUKiLH5Hv8mg 9UYw==
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=LI6t6/HJeEYg3Wyuowc69cwerbfmT+k2MtY3Hw/lVYY=; b=WhXADXAIDj6gem0NIwboF9sItahm3SoGG1u+0kKTsDeTbul3Kqxr2mtCaphRZ0mSH2 URIVIOF78HEqMBsG+zUytwXJUa/Lm8IppUKnUG45XuC2uZMQeh3gARz1YJ1prbQBt4m2 94EHodVuXa1by3PW8o/73UzUbKN+KiJumtASKYTJWTmbJYMz8O/FiwRDwheH+K+I6YMx B69pr5tSFicK5u7JYiA4FUvN4qQHDVcqltv3nx8QavdBTeeQ305yCoBG8l5lX0ULVdj8 DOsBtp8Yi8ylJVJ3J+tJPtI+YS00YEArVmHvn3fQuuiHjQtzzKhymq4HXnQ+yp+jl4ei jT2A==
X-Gm-Message-State: AKS2vOyJwACOH2QVkUEvYgIfptNQc8AQ9CMP3ojGW/At53yHSj6pAi3K u8voAXo28hkAaHESTjh+zRb8C2oA3Q==
X-Received: by 10.176.16.11 with SMTP id f11mr217369uab.146.1498485911517; Mon, 26 Jun 2017 07:05:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAAbpuyomorgNdjm3MAAgUTwawis1g8s9ANF2RVhZMXruwohXbw@mail.gmail.com> <HK2PR0401MB1588257A93D04368D9CC18EAB5DF0@HK2PR0401MB1588.apcprd04.prod.outlook.com>
In-Reply-To: <HK2PR0401MB1588257A93D04368D9CC18EAB5DF0@HK2PR0401MB1588.apcprd04.prod.outlook.com>
From: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Date: Mon, 26 Jun 2017 14:05:00 +0000
Message-ID: <CAAbpuyqbZYOHbg+FO9z13nv-ieatUOtMWGxGTNrRzAUjWuF6TA@mail.gmail.com>
To: Dawn Chan <dawn_chen_f@hotmail.com>
Cc: "alto@ietf.org" <alto@ietf.org>,  "draft-ietf-alto-path-vector@ietf.org" <draft-ietf-alto-path-vector@ietf.org>
Content-Type: multipart/alternative; boundary="f403045e1d6c7524000552dd7032"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/tRE5eyfVWsM9IZ0XKwhfA183FtE>
Subject: Re: [alto] Some considerations about path vector design
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: Mon, 26 Jun 2017 14:05:14 -0000

--f403045e1d6c7524000552dd7032
Content-Type: text/plain; charset="UTF-8"

Hi Dawn,

Thanks for your reply. Comment inline.

Thanks,
Jensen

On Mon, Jun 26, 2017 at 5:08 PM Dawn Chan <dawn_chen_f@hotmail.com> wrote:

> Hi Jensen and all,
> Sorry for the late reply. Please see my comments inline.
>
> On 7 Jun 2017, at 4:52 PM, Jensen Zhang <jingxuan.n.zhang@gmail.com>
> wrote:
>
> Hi all,
>
> I am going to resume the discussion about graph representation and path
> vector. After some attempts to adopt the path-vector extension, I have the
> following considerations:
>
> 1. The current design is inefficient. Since IETF 98, we have agreed on the
> design of a two-stage protocol extension (path-vector cost map + unified
> property map) for graph representation. It is extensible enough because we
> can customize the element (ane) properties. But the two-stage protocol will
> conduct the long delay and increase the complexity of state maintenance.
>
> 2. The resource dependencies are not clear. The "Dependent Resources"
> attribute in ALTO protocol is defined to claim the one-way resource
> dependencies. But many resource dependencies should be bidirectional. e.g.
> In path vector design, the cost map and the corresponding property map are
> bound to the same query.
>
> For 1, my personal idea is to deliver a service to accept a sequence of
> queries. In this way, the client can query both cost map and property map
> in a single request. And the server will handle the two-stage protocol
> efficiently.
>
> Here is a rough example:
>
> request:
> - resource: /alto/pv-costmap
>   pids:
>   - srcs: [xxx]
>   - dsts: [yyy]
> - resource: /alto/ane-prop-map
>   query-id: $resource[0].$response.meta.queryId
>   entities: $resource[0].$response.costmap.values.reduce(
>             (x,y) => x.values.concat(y.values))
>
> This design idea is a one-step service to get the cost map response and
> the property map response together in one request, which means it will
> return all the abstract network elements generated by one query. The effect
> of this design is probably same as the inline-mode that will directly
> return the properties of anes in the cost map, right?
>
>
Not exact. The inline-mode pv design just provides one resource. This idea
proposes a complete grammar of a query language. The response contains
multiple resources. The PV query is just a special example. The design can
also be used in other query combinition, e.g. Network Map + Cost Map. And
the client can offload some computation on the server part.


>
> For 2, I have not found a good solution to handle the generic case.
>
> Looking forward to any feedback.
>
> Best regards,
> Jensen
>
>

--f403045e1d6c7524000552dd7032
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Dawn,<div><br></div><div>Thanks for your reply. Comment=
 inline.</div><div><br></div><div>Thanks,</div><div>Jensen</div><div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr">On Mon, Jun 26, 2017 at 5:08 PM D=
awn Chan &lt;<a href=3D"mailto:dawn_chen_f@hotmail.com">dawn_chen_f@hotmail=
.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
Hi Jensen and all,
<div>Sorry for the late reply. Please see my comments inline.<br>
<div></div></div></div><div style=3D"word-wrap:break-word"><div><div>
<blockquote type=3D"cite">
<div>On 7 Jun 2017, at 4:52 PM, Jensen Zhang &lt;<a href=3D"mailto:jingxuan=
.n.zhang@gmail.com" target=3D"_blank">jingxuan.n.zhang@gmail.com</a>&gt; wr=
ote:</div>
<br class=3D"m_8328545563280957355Apple-interchange-newline">
<div>
<div dir=3D"ltr">Hi all,
<div><br>
</div>
<div>I am going to resume the discussion about graph representation and pat=
h vector. After some attempts to adopt the path-vector extension, I have th=
e following considerations:</div>
<div><br>
</div>
<div>1. The current design is inefficient. Since IETF 98, we have agreed on=
 the design of a two-stage protocol extension (path-vector cost map + unifi=
ed property map) for graph representation. It is extensible enough because =
we can customize the element
 (ane) properties. But the two-stage protocol will conduct the long delay a=
nd increase the complexity of state maintenance.</div>
<div><br>
</div>
<div>2. The resource dependencies are not clear. The &quot;Dependent Resour=
ces&quot; attribute in ALTO protocol is defined to claim the one-way resour=
ce dependencies. But many resource dependencies should be bidirectional. e.=
g. In path vector design, the cost
 map and the corresponding property map are bound to the same query.</div>
<div><br>
</div>
<div>For 1, my personal idea is to deliver a service to accept a sequence o=
f queries. In this way, the client can query both cost map and property map=
 in a single request. And the server will handle the two-stage protocol eff=
iciently.</div>
<div><br>
</div>
<div>Here is a rough example:</div>
<div><br>
</div>
<div><font face=3D"monospace">request:</font></div>
<div><font face=3D"monospace">- resource: /alto/pv-costmap</font></div>
<div><font face=3D"monospace">=C2=A0 pids:</font></div>
<div><font face=3D"monospace">=C2=A0 - srcs: [xxx]</font></div>
<div><font face=3D"monospace">=C2=A0 - dsts: [yyy]</font></div>
<div><font face=3D"monospace">- resource: /alto/ane-prop-map</font></div>
<div><font face=3D"monospace">=C2=A0 query-id: $resource[0].$response.meta.=
queryId</font></div>
<div><font face=3D"monospace">=C2=A0 entities: $resource[0].$response.costm=
ap.values.reduce(</font></div>
<div><font face=3D"monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (x,=
y) =3D&gt; x.values.concat(y.values))</font></div>
</div>
</div>
</blockquote></div></div></div><div style=3D"word-wrap:break-word"><div><di=
v>
This design idea is a one-step service to get the cost map response and the=
 property map response together in one request, which means it will return =
all the abstract network elements generated by one query. The effect of thi=
s design is probably same as the
 inline-mode that will directly return the properties of anes in the cost m=
ap, right?</div></div></div><div style=3D"word-wrap:break-word"><div><div><=
br></div></div></div></blockquote><div><br></div><div>Not exact. The inline=
-mode pv design just provides one resource. This idea proposes a complete g=
rammar of a query language. The response contains multiple resources. The P=
V query is just a special example. The design can also be used in other que=
ry combinition, e.g. Network Map=C2=A0+ Cost Map. And the client can offloa=
d some computation on the server part.</div><div>=C2=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><div style=3D"word-wrap:break-word"><div><div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">
<div><br>
</div>
<div>For 2, I have not found a good solution to handle the generic case.</d=
iv>
<div><br>
</div>
<div>Looking forward to any feedback.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Jensen</div>
</div>
</div>
</blockquote>
</div></div></div></blockquote></div></div></div>

--f403045e1d6c7524000552dd7032--


From nobody Mon Jun 26 08:59:34 2017
Return-Path: <cs90911@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 5D95E129B70; Mon, 26 Jun 2017 08:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 IvT0CrBdOZ2V; Mon, 26 Jun 2017 08:59:31 -0700 (PDT)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (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 B9BF812EAA9; Mon, 26 Jun 2017 08:59:24 -0700 (PDT)
Received: by mail-ua0-x233.google.com with SMTP id j53so3456167uaa.2; Mon, 26 Jun 2017 08:59:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=CNMkhc9G6cALOXrh19M/bgkqNcJXfzPTYoDH3LBTphw=; b=PSqN1lQEnYV8LElLirQ9XkO5CfldJkpKzoPyfqpCSqzB58oe1en1IJwg17TfgMYjHR 9yMh42iCkQ4akjtBuo0ZB59ZZwv/9oYgaTlnn8AjJE9angWWV/yrvX2S14Ylhk0QUl5B Fgsuz+lgo+tiQizk7uUw/NOM/IaYugGHuB8nfvLwYLoENKfQ5y0GpST1z77AzvmnECxY Tu6BVuhwG/yS6igoSFgd4SeUcodm/jj9Mafa6vGlovNk9ia1cAisOIWmNtAUssJriaSO Bqw/gPyiS0t9xEZqvBJOuvtR6IdlU7gRwtkrsu6YR2dGHrI4bzLw1xkGrg3Uq9TgEAuY rP8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=CNMkhc9G6cALOXrh19M/bgkqNcJXfzPTYoDH3LBTphw=; b=DL6yZ5ZVzJCHakdwVVFXYriP4EpFOxVk9ioMCAFUCFw7WAl0zBVEUjGpKdV64PFmQL TtfPRHekDkZKWjQJEZlvkI123W7/n+Uc3j3OxSAGDHV3V7D48SzThQJ4A28u9fLQ0MDT fiwend4XiQkj9QH1xZug8HjZayoYEKGbHQQOSViSNlJLrpE8XlogfZ96LXc6X53S9UIw YQvgsa8QYqfjJMlBJx1TuGO2XnbfMlKwwDpL3qvPlik/U/Tu1NQ/Col/63Nk4MVh2EbW pJuifmqE2wRk/PYEwIakGUsq+3MOJk7YRfCXzDkLa6vyJrJ2YAx0pOSMRheX1LFcm7Zs yzyQ==
X-Gm-Message-State: AKS2vOwgDWZjvhMgekA8gKh6NML7env9NO/2mG/mMUrnleb7WvbeEq4D 6jdkeIIS5IrY6fTIyVdk59b0ECTHA2fAgDw=
X-Received: by 10.176.1.52 with SMTP id 49mr537435uak.82.1498492763680; Mon, 26 Jun 2017 08:59:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.236.199 with HTTP; Mon, 26 Jun 2017 08:58:43 -0700 (PDT)
From: Shenshen Chen <cs90911@gmail.com>
Date: Mon, 26 Jun 2017 23:58:43 +0800
Message-ID: <CAKRjQSDOPoiWW_HCyawv34bkiN4H2y749i3vTCOc=3ngyyhaow@mail.gmail.com>
To: draft-roome-alto-unified-props-new@ietf.org, alto@ietf.org
Content-Type: multipart/alternative; boundary="001a113d0e2ae0b65e0552df08a9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/rTXt1dXX48Jwi7NIAIfdInCrOAw>
Subject: [alto]  Review of draft-roome-alto-unified-props-new-00
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: Mon, 26 Jun 2017 15:59:33 -0000

--001a113d0e2ae0b65e0552df08a9
Content-Type: text/plain; charset="UTF-8"

Dear authors of alto-unified-props and all,

In section 2.5, I feel "property type" could be better (because RFC7285
names
sections using "property type", but not "property name") and "property
value"
should be mentioned (includes the "null" value mentioned in section 4.6).
I also suggest showing the "null" value can be inherited explicitly
in the section 3.1.3 or emphasizing it as a normal property value.

Here is a list of typos (comments are marked with ">>>"):

[Page 2]
       3.1.3.  Heirarchy And Inheritance . . . . . . . . . . . . . .   7
       3.1.4.  Relationship To Network Maps  . . . . . . . . . . . .   8
     3.2.  PID Domain  . . . . . . . . . . . . . . . . . . . . . . .   9
       3.2.1.  Domain Name . . . . . . . . . . . . . . . . . . . . .   9
       3.2.2.  Domain-Specific Entity Addresses  . . . . . . . . . .   9
       3.2.3.  Heirarchy And Inheritance . . . . . . . . . . . . . .   9
       3.2.4.  Relationship To Internet Addresses Domains  . . . . .   9

>>> "To" => "to", "And" => "and", "Heirarchy" => "Hierarchy"


[Page 3]
   Second, the EPS is only defined as a POST-mode service.  Clients must
   request the properties for an explicit set of addresses.  By
   contrast, [RFC7285] defines a GET-mode Cost Map resource which
   returns all available costs, so a client can get the full set of
   costs once, and then lookup costs without querying the ALTO server.
   RFC7285 does not define an equivalent service for endpoint
   properties.  Granted, it is not be practical to enumerate the

>>> "is not be" => "is not"


[Page 4]
   This document proposes a new approach to ALTO properties.
   Specifically, it defines two new resource types, namely Property Maps
   and Filtered Property Maps.  The former are GET-mode resources which
   return the property values for all entities in a domain, and are
   analogous the ALTO's Network Map and Cost Map resources.  The latter

>>> "Network Map and Cost Map resources" => "Network Maps and Cost Maps"
    I think it should keep the same format with "Filtered Network Maps
    and Filtered Cost Maps" in the last sentence of this paragraph.

   are POST-mode resources which return the values for a set of
   properties and entities requested by the client, and are analogous to
   ALTO's Filtered Network Maps and Filtered Cost Maps.

[Page 7]
3.1.3.  Heirarchy And Inheritance

[Page 9]
3.2.3.  Heirarchy And Inheritance

>>> "Heirarchy" => "Hierarchy"

[Page 19]
   Note that the value of "pid" for the prefix "ipv4:10.0.0.0/15" is
   "pid1", even though all addresses in that block are in "pid2",
   because "ipv4:10.0.0.0/8" is the longest prefix in the network map
   which prefix-matches "ipv4:10.0.0.0/15", and that prefix is in
   "pid1".

   POST /propmap/lookup/pid HTTP/1.1
   Host: alto.example.com
   Accept: application/alto-propmap+json,application/alto-error+json
   Content-Length: ###
   Content-Type: application/alto-propmapparams+json

   {
     "entities" : [
                   "ipv4:192.0.2.0  10.0.0.0",
                   "ipv4:192.0.2.16 10.1.0.0",
                   "ipv4:192.0.2.64  10.3.0.0",
                   "ipv4:192.0.2.128  11.0.0.0",
                   "ipv4:192.0.2.0/26 10.0.0.0/15",
                   "ipv4:192.0.2.0/30 10.0.0.0/17" ],
     "properties" : [ "pid" ]
   }

>>> This part should be modified into:

   Note that the value of "pid" for the prefix "ipv4:192.0.2.0/26" is
   "pid1", even though all addresses in that block are in "pid2",
   because "ipv4:192.0.2.0/25" is the longest prefix in the network map
   which prefix-matches "ipv4:192.0.2.0/26", and that prefix is in
   "pid1".

   POST /propmap/lookup/pid HTTP/1.1
   Host: alto.example.com
   Accept: application/alto-propmap+json,application/alto-error+json
   Content-Length: ###
   Content-Type: application/alto-propmapparams+json

   {
     "entities" : [
                   "ipv4:192.0.2.0",
                   "ipv4:192.0.2.16",
                   "ipv4:192.0.2.64",
                   "ipv4:192.0.2.128",
                   "ipv4:192.0.2.0/26",
                   "ipv4:192.0.2.0/30" ],
     "properties" : [ "pid" ]
   }

[Page 23]
   New ALTO entity domains are assigned after IETF Review [RFC5226] to
   ensure that proper documentation regarding the new ALTO entity
   domains and their security considerations has been provided.  RFCs

>>> "has been" => "have been"

   defining new entity domains should indicate how an entity in a
   registered domain is encoded as an EntityName, and, if applicable,
   the rules defining the entity hierarchy and property inheritance.
   Updates and deletions of ALTO entity domains follow the same
   procedure.


Best Regards,
Shenshen

--001a113d0e2ae0b65e0552df08a9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear authors of alto-unified-props and all,</div><div=
><br></div><div>In section 2.5, I feel &quot;property type&quot; could be b=
etter (because RFC7285 names</div><div>sections using &quot;property type&q=
uot;, but not &quot;property name&quot;) and &quot;property value&quot;=C2=
=A0</div><div>should be mentioned (includes the &quot;null&quot; value ment=
ioned in section 4.6).</div><div>I also suggest showing=C2=A0the &quot;null=
&quot; value can be inherited explicitly</div><div>in the section 3.1.3 or =
emphasizing it as a normal property value.</div><div><br></div><div>Here is=
 a list of typos (comments are marked with &quot;&gt;&gt;&gt;&quot;):</div>=
<div><br></div><div>[Page 2]</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.1.3.=C2=
=A0 Heirarchy And Inheritance . . . . . . . . . . . . . . =C2=A0 7</div><di=
v>=C2=A0 =C2=A0 =C2=A0 =C2=A03.1.4.=C2=A0 Relationship To Network Maps =C2=
=A0. . . . . . . . . . . . =C2=A0 8</div><div>=C2=A0 =C2=A0 =C2=A03.2.=C2=
=A0 PID Domain =C2=A0. . . . . . . . . . . . . . . . . . . . . . . =C2=A0 9=
</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.2.1.=C2=A0 Domain Name . . . . . . =
. . . . . . . . . . . . . . . =C2=A0 9</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A03.2.2.=C2=A0 Domain-Specific Entity Addresses =C2=A0. . . . . . . . . . =
=C2=A0 9</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.2.3.=C2=A0 Heirarchy And In=
heritance . . . . . . . . . . . . . . =C2=A0 9</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A03.2.4.=C2=A0 Relationship To Internet Addresses Domains =C2=A0. .=
 . . . =C2=A0 9</div><div><br></div><div>&gt;&gt;&gt; &quot;To&quot; =3D&gt=
; &quot;to&quot;, &quot;And&quot; =3D&gt; &quot;and&quot;, &quot;Heirarchy&=
quot; =3D&gt; &quot;Hierarchy&quot;</div><div><br></div><div><br></div><div=
>[Page 3]</div><div>=C2=A0 =C2=A0Second, the EPS is only defined as a POST-=
mode service.=C2=A0 Clients must</div><div>=C2=A0 =C2=A0request the propert=
ies for an explicit set of addresses.=C2=A0 By</div><div>=C2=A0 =C2=A0contr=
ast, [RFC7285] defines a GET-mode Cost Map resource which</div><div>=C2=A0 =
=C2=A0returns all available costs, so a client can get the full set of</div=
><div>=C2=A0 =C2=A0costs once, and then lookup costs without querying the A=
LTO server.</div><div>=C2=A0 =C2=A0RFC7285 does not define an equivalent se=
rvice for endpoint</div><div>=C2=A0 =C2=A0properties.=C2=A0 Granted, it is =
not be practical to enumerate the</div><div><br></div><div>&gt;&gt;&gt; &qu=
ot;is not be&quot; =3D&gt; &quot;is not&quot;</div><div><br></div><div><br>=
</div><div>[Page 4]</div><div>=C2=A0 =C2=A0This document proposes a new app=
roach to ALTO properties.</div><div>=C2=A0 =C2=A0Specifically, it defines t=
wo new resource types, namely Property Maps</div><div>=C2=A0 =C2=A0and Filt=
ered Property Maps.=C2=A0 The former are GET-mode resources which</div><div=
>=C2=A0 =C2=A0return the property values for all entities in a domain, and =
are</div><div>=C2=A0 =C2=A0analogous the ALTO&#39;s Network Map and Cost Ma=
p resources.=C2=A0 The latter</div><div><br></div><div>&gt;&gt;&gt; &quot;N=
etwork Map and Cost Map resources&quot; =3D&gt; &quot;Network Maps and Cost=
 Maps&quot;</div><div>=C2=A0 =C2=A0 I think it should keep the same format =
with &quot;Filtered Network Maps=C2=A0</div><div>=C2=A0 =C2=A0 and Filtered=
 Cost Maps&quot; in the last sentence of this paragraph.</div><div><br></di=
v><div>=C2=A0 =C2=A0are POST-mode resources which return the values for a s=
et of</div><div>=C2=A0 =C2=A0properties and entities requested by the clien=
t, and are analogous to</div><div>=C2=A0 =C2=A0ALTO&#39;s Filtered Network =
Maps and Filtered Cost Maps.</div><div><br></div><div>[Page 7]</div><div>3.=
1.3.=C2=A0 Heirarchy And Inheritance</div><div><br></div><div>[Page 9]</div=
><div>3.2.3.=C2=A0 Heirarchy And Inheritance</div><div><br></div><div>&gt;&=
gt;&gt; &quot;Heirarchy&quot; =3D&gt; &quot;Hierarchy&quot;</div><div><br><=
/div><div>[Page 19]</div><div>=C2=A0 =C2=A0Note that the value of &quot;pid=
&quot; for the prefix &quot;ipv4:<a href=3D"http://10.0.0.0/15">10.0.0.0/15=
</a>&quot; is</div><div>=C2=A0 =C2=A0&quot;pid1&quot;, even though all addr=
esses in that block are in &quot;pid2&quot;,</div><div>=C2=A0 =C2=A0because=
 &quot;ipv4:<a href=3D"http://10.0.0.0/8">10.0.0.0/8</a>&quot; is the longe=
st prefix in the network map</div><div>=C2=A0 =C2=A0which prefix-matches &q=
uot;ipv4:<a href=3D"http://10.0.0.0/15">10.0.0.0/15</a>&quot;, and that pre=
fix is in</div><div>=C2=A0 =C2=A0&quot;pid1&quot;.</div><div><br></div><div=
>=C2=A0 =C2=A0POST /propmap/lookup/pid HTTP/1.1</div><div>=C2=A0 =C2=A0Host=
: <a href=3D"http://alto.example.com">alto.example.com</a></div><div>=C2=A0=
 =C2=A0Accept: application/alto-propmap+json,application/alto-error+json</d=
iv><div>=C2=A0 =C2=A0Content-Length: ###</div><div>=C2=A0 =C2=A0Content-Typ=
e: application/alto-propmapparams+json</div><div><br></div><div>=C2=A0 =C2=
=A0{</div><div>=C2=A0 =C2=A0 =C2=A0&quot;entities&quot; : [</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv=
4:192.0.2.0 =C2=A010.0.0.0&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.16 10.1.0.0&quot;,=
</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&quot;ipv4:192.0.2.64 =C2=A010.3.0.0&quot;,</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.1=
28 =C2=A011.0.0.0&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:<a href=3D"http://192.0.2.0/26">1=
92.0.2.0/26</a> <a href=3D"http://10.0.0.0/15">10.0.0.0/15</a>&quot;,</div>=
<div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&=
quot;ipv4:<a href=3D"http://192.0.2.0/30">192.0.2.0/30</a> <a href=3D"http:=
//10.0.0.0/17">10.0.0.0/17</a>&quot; ],</div><div>=C2=A0 =C2=A0 =C2=A0&quot=
;properties&quot; : [ &quot;pid&quot; ]</div><div>=C2=A0 =C2=A0}</div><div>=
<br></div><div>&gt;&gt;&gt; This part should be modified into:</div><div><b=
r></div><div>=C2=A0 =C2=A0Note that the value of &quot;pid&quot; for the pr=
efix &quot;ipv4:<a href=3D"http://192.0.2.0/26">192.0.2.0/26</a>&quot; is</=
div><div>=C2=A0 =C2=A0&quot;pid1&quot;, even though all addresses in that b=
lock are in &quot;pid2&quot;,</div><div>=C2=A0 =C2=A0because &quot;ipv4:<a =
href=3D"http://192.0.2.0/25">192.0.2.0/25</a>&quot; is the longest prefix i=
n the network map</div><div>=C2=A0 =C2=A0which prefix-matches &quot;ipv4:<a=
 href=3D"http://192.0.2.0/26">192.0.2.0/26</a>&quot;, and that prefix is in=
</div><div>=C2=A0 =C2=A0&quot;pid1&quot;.</div><div><br></div><div>=C2=A0 =
=C2=A0POST /propmap/lookup/pid HTTP/1.1</div><div>=C2=A0 =C2=A0Host: <a hre=
f=3D"http://alto.example.com">alto.example.com</a></div><div>=C2=A0 =C2=A0A=
ccept: application/alto-propmap+json,application/alto-error+json</div><div>=
=C2=A0 =C2=A0Content-Length: ###</div><div>=C2=A0 =C2=A0Content-Type: appli=
cation/alto-propmapparams+json</div><div><br></div><div>=C2=A0 =C2=A0{</div=
><div>=C2=A0 =C2=A0 =C2=A0&quot;entities&quot; : [</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.0=
&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&quot;ipv4:192.0.2.16&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.64&quot;=
,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&quot;ipv4:192.0.2.128&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:<a href=3D"http://192.0=
.2.0/26">192.0.2.0/26</a>&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:<a href=3D"http://192.0.2.=
0/30">192.0.2.0/30</a>&quot; ],</div><div>=C2=A0 =C2=A0 =C2=A0&quot;propert=
ies&quot; : [ &quot;pid&quot; ]</div><div>=C2=A0 =C2=A0}</div><div><br></di=
v><div>[Page 23]</div><div>=C2=A0 =C2=A0New ALTO entity domains are assigne=
d after IETF Review [RFC5226] to</div><div>=C2=A0 =C2=A0ensure that proper =
documentation regarding the new ALTO entity</div><div>=C2=A0 =C2=A0domains =
and their security considerations has been provided.=C2=A0 RFCs</div><div><=
br></div><div>&gt;&gt;&gt; &quot;has been&quot; =3D&gt; &quot;have been&quo=
t;</div><div><br></div><div>=C2=A0 =C2=A0defining new entity domains should=
 indicate how an entity in a</div><div>=C2=A0 =C2=A0registered domain is en=
coded as an EntityName, and, if applicable,</div><div>=C2=A0 =C2=A0the rule=
s defining the entity hierarchy and property inheritance.</div><div>=C2=A0 =
=C2=A0Updates and deletions of ALTO entity domains follow the same</div><di=
v>=C2=A0 =C2=A0procedure.</div><div><br></div><div><br></div><div>Best Rega=
rds,</div><div>Shenshen</div><div><br></div></div>

--001a113d0e2ae0b65e0552df08a9--


From nobody Mon Jun 26 17:58:06 2017
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 4D4F012741D; Mon, 26 Jun 2017 17:58:05 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 qlcOOrt1AtOL; Mon, 26 Jun 2017 17:58:03 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255058.outbound.protection.outlook.com [40.92.255.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49FA3126CC4; Mon, 26 Jun 2017 17:57:59 -0700 (PDT)
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=6wPeSmXgMSKLxPUuSj8KdEgMx3nz+7PsHO4P133b1Rk=; b=Lga4fR0eB13XVQ1JP9u5RjDQ+/no/dpo/ufLafOxiIrVjjKJWy7es4CiuE2qwsyuenxhpTFKx4eilmeaMFBQl8dh0PNeuZe4udYCu/AukJYIKZgczQ2fVXfhC9kL6R4ordbz3ehZ849IS1SvfXLMgPIKuyPxGDz80kS1egKpNgfAsDaSVP3jdmWnlOIN7XXHPrWBJ3z9mDCH1d4IyL7VQLM64sa620eQloRntJPw+W7q1ely/sOQxJWKD0DT86V4KG2wSIz/2sui15eLPtIMVfUtD1JSClV7boMT23g658qxBa6s8KzvjRUsXXEN2CPOGj+nI/HKwEs5wLNZ6XKDKw==
Received: from PU1APC01FT043.eop-APC01.prod.protection.outlook.com (10.152.252.55) by PU1APC01HT144.eop-APC01.prod.protection.outlook.com (10.152.253.254) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1157.12; Tue, 27 Jun 2017 00:57:56 +0000
Received: from PS1PR0302MB2457.apcprd03.prod.outlook.com (10.152.252.53) by PU1APC01FT043.mail.protection.outlook.com (10.152.253.6) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.9 via Frontend Transport; Tue, 27 Jun 2017 00:57:56 +0000
Received: from PS1PR0302MB2457.apcprd03.prod.outlook.com ([fe80::290a:8d10:d903:ff49]) by PS1PR0302MB2457.apcprd03.prod.outlook.com ([fe80::290a:8d10:d903:ff49%18]) with mapi id 15.01.1220.010; Tue, 27 Jun 2017 00:57:56 +0000
From: xin wang <xinwang2014@hotmail.com>
To: "draft-hommes-alto-blockchain@ietf.org" <draft-hommes-alto-blockchain@ietf.org>, IETF ALTO <alto@ietf.org>
Thread-Topic: Reviews of draft-hommes-alto-blockchain-02
Thread-Index: AQHS7t/7n3mw2eKah0eGdsf8ZfLn8A==
Date: Tue, 27 Jun 2017 00:57:56 +0000
Message-ID: <PS1PR0302MB2457B4B4982453997C6E13FDA8DC0@PS1PR0302MB2457.apcprd03.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:D904A9863F386670199B6B4AF54CCED8632357B1C49861F70BF4A10C08EBE301; UpperCasedChecksum:F517283CE4298FED328FE950868B0763525E5B4668C1938F7FA91F422299350E; SizeAsReceived:7183; Count:43
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [RvgbN9NF6AXh4aRoTXL3OhMyorO7ngYnHToz3Gtewdk=]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; PU1APC01HT144; 7:DB+wSrIqWqpqtDLzVL6dqJYCYTvDXKsa0fcTpRbFH4RsKjGAo3Tp0NuEob0XlzxDKXSlVuDuufLFEBr92uivF+5Tb4VX3VqQC0XtCry5Dz6EC0VphDiplgwHGARR/XppZDmHtZJjMClur+taULD25ix1WU7QWzAG2MioxP1jJiW1MpE98i/nIoaAM406H1JDOR1ript5gRwdM8fXU50vrRVmoJvy+RZwZJ++PJvs+CCG5B5NZlNP5Tror/HrQtE7ZZ8dFxtPe8fSIbeCas2wabFuO/DkTIYEl7YCmu/zE1E9DLWQyy/BfLGjfYVw/WHq/Iq4UlmBRGIv1hfHTtJMGlvWQKrWg50lCG0M/R7jy7vKg02ez0tk7pgKyM+rD+E4Q13DmiVHVyikLARI16oFpHBvFPhinWW2/xRrLpIw+EWbOjxolGHNiuOYYewUmvvm5BxItuIuXlIj4pRDlXSzHkxsBF9KRyujK8dVNiznQLST0hJmrSknyrC0XG5sb122SRmJ37GNxvv6cLLqiiD7Qzpvr77l/4ACynuOjDhYJXwIDjaLosLkI7vgKXfrD/jwxK9tfOU5LG3ercAebpD12FckCLVCuysVHhdm4tJc5L7iZpcAT6pH7h5aMqvHgR4yxre2u3OKg/a8u71FUOmJ3P8DWVvARCQFjcOa7mDKgqhbOv7vuv5lSeF0nxPu0rNUy5XGYtVWg16FwULPHCyeCRqOm6x4hyPTjOWZP42zMf+Xg9bqKfj5g55d87TfWf8ZKmYGgD/2CWSL1IKLrpv6Uw==
x-incomingheadercount: 43
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:PU1APC01HT144; H:PS1PR0302MB2457.apcprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-traffictypediagnostic: PU1APC01HT144:
x-ms-office365-filtering-correlation-id: 845839bd-6d3a-488b-e39a-08d4bcf78c62
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1603101448)(1601125374)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095); SRVR:PU1APC01HT144; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:PU1APC01HT144; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:PU1APC01HT144; 
x-forefront-prvs: 0351D213B3
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_PS1PR0302MB2457B4B4982453997C6E13FDA8DC0PS1PR0302MB2457_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Jun 2017 00:57:56.3366 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT144
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/asDIZ89w7ksxjcHoZLUP8XNx-ec>
Subject: [alto] Reviews of draft-hommes-alto-blockchain-02
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: Tue, 27 Jun 2017 00:58:05 -0000

--_000_PS1PR0302MB2457B4B4982453997C6E13FDA8DC0PS1PR0302MB2457_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear authors of "ALTO for the blockchain",


Your draft about using ALTO to improve the communication in a blockchain ne=
twork looks very practical and interesting. It would be grateful to deploy =
ALTO in a blockchain network. The following is a review of the draft:


a. Fixed peer relationship or not?


The broadcasting mechanism in a blockchain network needs a node to broadcas=
t transactions/blocks in the network, and the goal is to minimize the infor=
mation propagation time. The broadcast mechanism depends on peer relationsh=
ip between nodes to transfer information. Then, ALTO can help with the peer=
 selection process which decides peer relationship based on communication p=
erformance obtained from an ALTO server. From the section 3, I assume the p=
eer selection happens at the very beginning when a node joins a blockchain =
network. Therefore, the peer relationship should be fixed if there is no fa=
ilure. Then, one question would be that is it possible to change the peer r=
elationship as the system running to get a better communication performance=
? Here is a draft about ALTO incremental updating (https://datatracker.ietf=
.org/doc/draft-ietf-alto-incr-update-sse/

draft-ietf-alto-incr-update-sse-05 - ALTO Incremental ...<https://datatrack=
er.ietf.org/doc/draft-ietf-alto-incr-update-sse/>
datatracker.ietf.org
ALTO Incremental Updates Using Server-Sent Events (SSE) (Internet-Draft, 20=
17)



) which can be used to get updated values from ALTO server.


b. Centralized peer selection or not?


The draft describes two frameworks where an ALTO client can be embedded int=
o: the Resource Directory and a blockchain node. From my thinking, the reso=
urce directory framework really provides a centralized view of a blockchain=
 network, which is able to get the optimal solution for the peer selection.=
 However, if an ALTO client is embedded into a blockchain node, then each n=
ode can only make a selection based on information of the neighboring of th=
e node, which may not be able to be optimal.


c. Cost map service and ECS in two frameworks


Another comment about the two frameworks is that you are trying to apply th=
e cost map service for the Resource Directory and Endpoint Cost Service (EC=
S) for public blockchains respectively. It might be true that requesting a =
cost map could reduce the information exposure about the topology, but I re=
commend you for another draft about Routing State Abstraction (https://data=
tracker.ietf.org/doc/draft-gao-alto-routing-state-abstraction/

draft-gao-alto-routing-state-abstraction-03 - ALTO ...<https://datatracker.=
ietf.org/doc/draft-gao-alto-routing-state-abstraction/>
datatracker.ietf.org
ALTO Extension: A Routing State Abstraction Service Using Declarative Equiv=
alence (Internet-Draft, 2017)



) which aims to provide an abstract topology against a raw topology. For pu=
blic blockchains, I am not sure your choice to use ECS instead of a cost ma=
p is better for the large number of peers in the network.


And here are some typos you may fix:


Page 5: e.i. -> i.e.


Page 6: occur -> occurs, send -> sent



Best,

Xin


--_000_PS1PR0302MB2457B4B4982453997C6E13FDA8DC0PS1PR0302MB2457_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Dear authors of &quot;<span style=3D"-w=
ebkit-text-stroke-width: initial;">ALTO for the blockchain</span>&quot;,</s=
pan></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;"><br>
</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Your draft about using ALTO to improve =
the communication in a blockchain network looks very practical and interest=
ing. It would be grateful to deploy ALTO in a blockchain network. The follo=
wing is a review of the draft:</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">a. Fixed peer relationship or not?</spa=
n></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">The broadcasting mechanism in a blockch=
ain network needs a node to broadcast transactions/blocks in the network, a=
nd the goal is to minimize the information propagation time. The broadcast =
mechanism depends on peer relationship
 between nodes to transfer information. Then, ALTO can help with the peer s=
election process which decides peer relationship based on communication per=
formance obtained from an ALTO server. From the section 3, I assume the pee=
r selection happens at the very
 beginning when a node joins a blockchain network. Therefore, the peer rela=
tionship should be fixed if there is no failure. Then, one question would b=
e that is it possible to change the peer relationship as the system running=
 to get a better communication performance?
 Here is a draft about ALTO incremental updating (<a href=3D"https://datatr=
acker.ietf.org/doc/draft-ietf-alto-incr-update-sse/" id=3D"LPlnk950427" pre=
viewremoved=3D"true"><span style=3D"text-decoration: underline; font-kernin=
g: none; color: rgb(158, 74, 47); -webkit-text-stroke: 0px rgb(158, 74, 47)=
;">https://datatracker.ietf.org/doc/draft-ietf-alto-incr-update-sse/</span>=
</a></span></p>
<div id=3D"LPBorder_GT_14985248924190.8065317345916079" style=3D"margin-bot=
tom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id=3D"LPContainer_14985248924160.9367384319836247" role=3D"presentat=
ion" cellspacing=3D"0" style=3D"width: 90%; background-color: rgb(255, 255,=
 255); position: relative; overflow: auto; padding-top: 20px; padding-botto=
m: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); borde=
r-bottom: 1px dotted rgb(200, 200, 200);">
<tbody>
<tr valign=3D"top" style=3D"border-spacing: 0px;">
<td id=3D"TextCell_14985248924170.13869542089656894" colspan=3D"2" style=3D=
"vertical-align: top; position: relative; padding: 0px; display: table-cell=
;">
<div id=3D"LPRemovePreviewContainer_14985248924170.5181410851598642"></div>
<div id=3D"LPTitle_14985248924170.49508164862149595" style=3D"top: 0px; col=
or: rgb(0, 120, 215); font-weight: normal; font-size: 21px; font-family: wf=
_segoe-ui_light, &quot;Segoe UI Light&quot;, &quot;Segoe WP Light&quot;, &q=
uot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial, sans-serif; line-h=
eight: 21px;">
<a id=3D"LPUrlAnchor_14985248924180.6522449612915198" href=3D"https://datat=
racker.ietf.org/doc/draft-ietf-alto-incr-update-sse/" target=3D"_blank" sty=
le=3D"text-decoration: none;">draft-ietf-alto-incr-update-sse-05 - ALTO Inc=
remental ...</a></div>
<div id=3D"LPMetadata_14985248924180.039963467273284925" style=3D"margin: 1=
0px 0px 16px; color: rgb(102, 102, 102); font-weight: normal; font-family: =
wf_segoe-ui_normal, &quot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Ari=
al, sans-serif; font-size: 14px; line-height: 14px;">
datatracker.ietf.org</div>
<div id=3D"LPDescription_14985248924180.29419936481318953" style=3D"display=
: block; color: rgb(102, 102, 102); font-weight: normal; font-family: wf_se=
goe-ui_normal, &quot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial, s=
ans-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow:=
 hidden;">
ALTO Incremental Updates Using Server-Sent Events (SSE) (Internet-Draft, 20=
17)</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<p></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">) which can be used to get updated valu=
es from ALTO server.</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">b. Centralized peer selection or not?</=
span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">The draft describes two frameworks wher=
e an ALTO client can be embedded into: the Resource Directory and a blockch=
ain node. From my thinking, the resource directory framework really provide=
s a centralized view of a blockchain
 network, which is able to get the optimal solution for the peer selection.=
 However, if an ALTO client is embedded into a blockchain node, then each n=
ode can only make a&nbsp;selection based on information of the neighboring =
of the node, which may not be able to
 be optimal.&nbsp;</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">c. Cost map service and ECS in two fram=
eworks</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Another comment about the two framework=
s is that you are trying to apply the cost map service for the Resource Dir=
ectory and Endpoint Cost Service (ECS) for public blockchains respectively.=
 It might be true that requesting
 a cost map could reduce the information exposure about the topology, but I=
 recommend you for another draft about Routing State Abstraction (<a href=
=3D"https://datatracker.ietf.org/doc/draft-gao-alto-routing-state-abstracti=
on/" id=3D"LPlnk430837" previewremoved=3D"true"><span style=3D"text-decorat=
ion: underline; font-kerning: none; color: rgb(158, 74, 47); -webkit-text-s=
troke: 0px rgb(158, 74, 47);">https://datatracker.ietf.org/doc/draft-gao-al=
to-routing-state-abstraction/</span></a></span></p>
<div id=3D"LPBorder_GT_14985248923970.27341278741890473" style=3D"margin-bo=
ttom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id=3D"LPContainer_14985248923920.9205874734523827" role=3D"presentat=
ion" cellspacing=3D"0" style=3D"width: 90%; background-color: rgb(255, 255,=
 255); position: relative; overflow: auto; padding-top: 20px; padding-botto=
m: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); borde=
r-bottom: 1px dotted rgb(200, 200, 200);">
<tbody>
<tr valign=3D"top" style=3D"border-spacing: 0px;">
<td id=3D"TextCell_14985248923940.5011733788961381" colspan=3D"2" style=3D"=
vertical-align: top; position: relative; padding: 0px; display: table-cell;=
">
<div id=3D"LPRemovePreviewContainer_14985248923940.3255058821091652"></div>
<div id=3D"LPTitle_14985248923940.7572866574065305" style=3D"top: 0px; colo=
r: rgb(0, 120, 215); font-weight: normal; font-size: 21px; font-family: wf_=
segoe-ui_light, &quot;Segoe UI Light&quot;, &quot;Segoe WP Light&quot;, &qu=
ot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial, sans-serif; line-he=
ight: 21px;">
<a id=3D"LPUrlAnchor_14985248923950.5467384915220079" href=3D"https://datat=
racker.ietf.org/doc/draft-gao-alto-routing-state-abstraction/" target=3D"_b=
lank" style=3D"text-decoration: none;">draft-gao-alto-routing-state-abstrac=
tion-03 - ALTO ...</a></div>
<div id=3D"LPMetadata_14985248923950.14014024723270468" style=3D"margin: 10=
px 0px 16px; color: rgb(102, 102, 102); font-weight: normal; font-family: w=
f_segoe-ui_normal, &quot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Aria=
l, sans-serif; font-size: 14px; line-height: 14px;">
datatracker.ietf.org</div>
<div id=3D"LPDescription_14985248923960.8364332651552635" style=3D"display:=
 block; color: rgb(102, 102, 102); font-weight: normal; font-family: wf_seg=
oe-ui_normal, &quot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial, sa=
ns-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: =
hidden;">
ALTO Extension: A Routing State Abstraction Service Using Declarative Equiv=
alence (Internet-Draft, 2017)</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<p></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">) which aims to provide an abstract top=
ology against a raw topology. For public blockchains, I am not sure your ch=
oice to use ECS instead of a cost map is better for the large number of pee=
rs in the network.</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">And here are some typos you may fix:</s=
pan></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 5: e.i. -&gt; i.e.</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 6: occur -&gt; occurs, send -&gt; =
sent</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;"><br>
</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;"><br>
</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Best,</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Xin</span></p>
<br>
<p></p>
</div>
</body>
</html>

--_000_PS1PR0302MB2457B4B4982453997C6E13FDA8DC0PS1PR0302MB2457_--


From nobody Tue Jun 27 01:13:55 2017
Return-Path: <92yichenqian@tongji.edu.cn>
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 8B4FD129417 for <alto@ietfa.amsl.com>; Tue, 27 Jun 2017 01:13:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 rujddsSPRLpa for <alto@ietfa.amsl.com>; Tue, 27 Jun 2017 01:13:51 -0700 (PDT)
Received: from tongji.edu.cn (mailusrsvr2.tongji.edu.cn [202.120.164.62]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08EE612009C for <alto@ietf.org>; Tue, 27 Jun 2017 01:13:49 -0700 (PDT)
Received: from [192.168.1.161] (unknown [10.60.139.182]) by mailusersvr2 (Coremail) with SMTP id PqR4ygA3ubC3E1JZ7+OLAA--.3808S2; Tue, 27 Jun 2017 16:13:46 +0800 (CST)
From: Yichen Qian <92yichenqian@tongji.edu.cn>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Jun 2017 16:13:42 +0800
Message-Id: <17A28926-71DD-449D-A808-FBC275C6064A@tongji.edu.cn>
Cc: IETF ALTO <alto@ietf.org>
To: Qiao Xiang <xiangq27@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-CM-TRANSID: PqR4ygA3ubC3E1JZ7+OLAA--.3808S2
X-Coremail-Antispam: 1UD129KBjvJXoWxZF4kKr17tFW5Xr15Ary7Wrg_yoWruF4xpF WfCa1Dtws7Xr1UCan7Zw4xXr1ru3sYyF43G343KryUZwsxCrWDtF12yF1YvFZrCryfXw1Y v390vr15uwn0vaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUkjb7Iv0xC_Kw4lb4IE77IF4wAFc2x0x2IEx4CE42xK8VAvwI8I cIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2 AK021l84ACjcxK6xIIjxv20xvE14v26w1j6s0DM28EF7xvwVC0I7IYx2IY6xkF7I0E14v2 6F4UJVW0owA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwVC2z280aVCY1x0267AKxV W0oVCq3wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40EFcxC0VAKzVAqx4xG6I80ewAv 7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r 1j6r4UM4x0Y48IcxkI7VAKI48JMxAIw28IcxkI7VAKI48JMxAIw28IcVCjz48v1sIEY20_ Cr1UJr1UMxC20s026xCaFVCjc4AY6r1j6r4UMI8I3I0E5I8CrVAFwI0_Jr0_Jr4lx2IqxV Cjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUXVWUAwCIc40Y0x0EwIxGrwCI42IY 6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxVWUJVW8JwCI42IY6x AIw20EY4v20xvaj40_WFyUJVCq3wCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv 6xkF7I0E14v26r1j6r4UYxBIdaVFxhVjvjDU0xZFpf9x07beAp5UUUUU=
X-CM-SenderInfo: qrqrmmmu6w00xjmlhvlgxou0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/aK-DhNZLDLWB124VMeyDtnDIJGo>
Subject: [alto] Review of draft-xiang-alto-exascale-network-optimization-01
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: Tue, 27 Jun 2017 08:13:53 -0000

Hi Qiao, all,

It=E2=80=99s interesting to introduce I/O and computation resources into =
ALTO to get not only the network resources for more accurate query. Here =
is my review of the draft:

>>> It is mentioned in chapter 4.2 (=E2=80=9CSharing raw site/cluster =
information would violate sites' privacy constraints.=E2=80=9D) and 6 =
(=E2=80=9CHow much privacy, including=E2=80=A6 will be exposed?=E2=80=9D) =
that the privacy is a problem in providing the information, but it seems =
that it is not addressed in this draft.

Abstract
"In this document, we propose that it is feasible to use existing ALTO =
services to provides not only network information, but also information =
about other resources in science networks including computing and =
storage."

>>> to provides -> to provide

"ExaO provides simple APIs for users to submit and manage dataset =
transfer and analytic requests and to monitor the status of each =
request, along with fine-grained local and global network and site state =
information in real-time. "

>>> Too many =E2=80=9Cand=E2=80=9D to read and understand.
=20
1.  Introduction
"Applications such as the Production ANd Distributed Analysis system =
(PanDA) in ATLAS and the Physics Experiment Data Export system (PhEDEX) =
in CMS have been developed to manage the data transfers among different =
cluster sites."
  =20
>>> have been -> has been

"Section 6 lists several key issues to address in order to realize the =
proposal of providng multi-resource information by ALTO topology =
services."

>>> providng -> providing

5.2.  Example: encode storage bandwidth into path vector
"Other than network resource, assume in this topology eh1 and eh3 are =
equipped with commodity hard drive disk (HDD) while eh2 and eh4 are =
equipped with SSD."

>>> There is the full name of HDD but no full name for SSD.
  =20
"In this example, if we see the end hosts as network elements, the =
storage I/O bandwidth of each host can also be encoded as an abstract =
element into the path-vector."

>>> It=E2=80=99s better to have a new figure with the storage I/O =
bandwidth as an abstract element in the topology.

6.  Key Issues
"a large dataset transfer or analytic application always involve many =
network elements in multiple clusters/sites and the absolute number of =
involved network elements keep increasing as the scale of clusters =
increase."

>>> involve -> involves

"There still lacks of an analytics or experimental understanding on the =
scalability of path-vector and RSA services."

>>> lacks of -> lacks

7.1.  Architecture
"including replica selection, routing path computation and bandwidth =
allocation, and request parallelization decisions, such as which cluster =
each sub-request should be placed at the multi-resource orchestrator."

>>> missing a preposition before =E2=80=9Cthe multi-resource =
orchestrator=E2=80=9D -> in the multi-resource=E2=80=A6

7.2.1.  User API

>>> Another API that allows a user to query all the requests that the =
user has submitted can be considered in case of missing the requestID.

7.4.  ALTO Server
"Each ALTO server must provide basic information services as specified =
in [RFC7285] such as network map, cost map, endpoint cost service (ECS), =
etc.  To support the fine-grained multi-resource allocation in ExaO, =
each ALTO server should also provide more fine-grained information about =
different resources in clusters through ALTO extension services such as =
the routing state abstraction [DRAFT-RSA], path vector [DRAFT-PV], =
network graph [DRAFT-NETGRAPH],multi-cost [DRAFT-MC] and cost-calendar =
[DRAFT-CC] services."
			=09
>>> Providing basic information along with fine-grained information may =
has some overlap or redundant information such as information provided =
by cost map and RSA. It may increase the burden of data transfer. Some =
ways to reduce the redundant or send part of the information can be =
considered.

7.7.1.  Orchestration Algorithms
"The modular design of ExaO allows the adoption of different =
orchestration algorithms and methodologies, depending on the specific =
performance requirements."
>>> If using a specific algorithm, what interface (inputs/outputs=E2=80=A6=
) should users specify?

7.7.3.  Example: A Max-Min Fairness Resource Allocation Algorithm

>>> As an example, I think there is too much introduction and =
description for MFRA. May be it can be seen as a default algorithm in =
the system?

8.3.  Constraints of the MFRA Algorithm
"Simply denoting the replica selection as a set of binary constraint =
will significantly increases the computation complexity of the =
scheduling process."

>>> increases -> increase



From nobody Tue Jun 27 02:11:01 2017
Return-Path: <jingxuan.n.zhang@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 D182E12EC03; Tue, 27 Jun 2017 02:10:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-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 yUI91zN6XCtD; Tue, 27 Jun 2017 02:10:58 -0700 (PDT)
Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::22e]) (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 E2D72127275; Tue, 27 Jun 2017 02:10:57 -0700 (PDT)
Received: by mail-ua0-x22e.google.com with SMTP id j53so14779628uaa.2; Tue, 27 Jun 2017 02:10:57 -0700 (PDT)
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=RxKIJj3LevfjrMRN/wHrnXu/BSvPUGTXyCZoAx6AIPQ=; b=HGaOP6kkuhbQ+RUhwARhb3+xtNIvSXhXOYGiCKnSgdEjC+/MyB2Kh94iZhRAJpGWpP MkZoyd6xHA6poujW9JoOJxVT55qoea+ZBgZ3ZSZBbL9jN529/wz+tzQvZVBYglyu/gfI vwyEKr0Z1gtZgGyMRwtEhyokB73SD36qk947lH/t8GHVANCJE8AzgtCcfHGmLjyy4ZUG 70UOhmqpFHyLlfklF+pXDzZP0hZzqKgoFdma99s1DRMBMvY/fW+0bqb+TLvhT3DPo43I NGlEbbg9mRKF/ptaVqN9mQV1N18M8W7S7Yv3UNOa67M+VUJZA3DMGsMwztd0BdcCPq+p xJgQ==
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=RxKIJj3LevfjrMRN/wHrnXu/BSvPUGTXyCZoAx6AIPQ=; b=TQog8UKUF5NXjdj5//9rD9Ekq+FmwgLL6D7bHFFP5dCX0J1rjUgOw3BkShGLb5Mk/n NLl/+aYD1UYC4GqjnKMsHH4kJEIP5CBc0njQg4ymQre7HThWcdLjgaZBf6qJ8cZGoLRP W3o96xuZCm2FUwYC3kuHRPeoYuJ2DDMy2KtPbhp4NZJG7a2rrl+ebAqRLJ8AgAH72SN2 uhMAsI0SBKLCYZpMrA7pL+478aN+80C9tkoKJHBaTy0fD1+La125GMI9xEzmYTGSisZD KeDCvR1vCUVPCBl4G3Y2FSaV+2PerMfrwgLMTlsCFhE0Th4Fd46zHm3nOFxmOfwtOKtu 7DrA==
X-Gm-Message-State: AKS2vOwiMuq5VoyxynGV3C2unEIKR4zkqu1bmq/STGKlLrIaWV6bnW4Y +AOaE/T/AspxVGkXwCh3oiAEm+Ieiw==
X-Received: by 10.176.6.104 with SMTP id f95mr2582916uaf.15.1498554657097; Tue, 27 Jun 2017 02:10:57 -0700 (PDT)
MIME-Version: 1.0
References: <CAAbpuyomorgNdjm3MAAgUTwawis1g8s9ANF2RVhZMXruwohXbw@mail.gmail.com> <HK2PR0401MB1588257A93D04368D9CC18EAB5DF0@HK2PR0401MB1588.apcprd04.prod.outlook.com> <CAAbpuyqbZYOHbg+FO9z13nv-ieatUOtMWGxGTNrRzAUjWuF6TA@mail.gmail.com>
In-Reply-To: <CAAbpuyqbZYOHbg+FO9z13nv-ieatUOtMWGxGTNrRzAUjWuF6TA@mail.gmail.com>
From: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Date: Tue, 27 Jun 2017 09:10:46 +0000
Message-ID: <CAAbpuyqyYdwha12Vp8XcS5EDJCc8z2n8tVqjg-DbmvYieQzs_Q@mail.gmail.com>
To: Dawn Chan <dawn_chen_f@hotmail.com>
Cc: "alto@ietf.org" <alto@ietf.org>,  "draft-ietf-alto-path-vector@ietf.org" <draft-ietf-alto-path-vector@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c122e3a034e5f0552ed72ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/LE7I-FROSfOvs2dcboG4qsyJV2g>
Subject: Re: [alto] Some considerations about path vector design
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: Tue, 27 Jun 2017 09:11:00 -0000

--94eb2c122e3a034e5f0552ed72ed
Content-Type: text/plain; charset="UTF-8"

I just realized that the example I took to explain how to
query pv-cost-map + ane-prop-map may make people confused.

Ideally, I hope to provide a general query service to handle some batch
query or some resource combination query. I want to know how many people
are interested in this idea or think it is useful. To make the discussion
more efficiently, I will post an initial draft to define the formal grammar
asap.

Best,
Jensen

On Mon, Jun 26, 2017 at 10:04 PM Jensen Zhang <jingxuan.n.zhang@gmail.com>
wrote:

> Hi Dawn,
>
> Thanks for your reply. Comment inline.
>
> Thanks,
> Jensen
>
> On Mon, Jun 26, 2017 at 5:08 PM Dawn Chan <dawn_chen_f@hotmail.com> wrote:
>
>> Hi Jensen and all,
>> Sorry for the late reply. Please see my comments inline.
>>
>> On 7 Jun 2017, at 4:52 PM, Jensen Zhang <jingxuan.n.zhang@gmail.com>
>> wrote:
>>
>> Hi all,
>>
>> I am going to resume the discussion about graph representation and path
>> vector. After some attempts to adopt the path-vector extension, I have the
>> following considerations:
>>
>> 1. The current design is inefficient. Since IETF 98, we have agreed on
>> the design of a two-stage protocol extension (path-vector cost map +
>> unified property map) for graph representation. It is extensible enough
>> because we can customize the element (ane) properties. But the two-stage
>> protocol will conduct the long delay and increase the complexity of state
>> maintenance.
>>
>> 2. The resource dependencies are not clear. The "Dependent Resources"
>> attribute in ALTO protocol is defined to claim the one-way resource
>> dependencies. But many resource dependencies should be bidirectional. e.g.
>> In path vector design, the cost map and the corresponding property map are
>> bound to the same query.
>>
>> For 1, my personal idea is to deliver a service to accept a sequence of
>> queries. In this way, the client can query both cost map and property map
>> in a single request. And the server will handle the two-stage protocol
>> efficiently.
>>
>> Here is a rough example:
>>
>> request:
>> - resource: /alto/pv-costmap
>>   pids:
>>   - srcs: [xxx]
>>   - dsts: [yyy]
>> - resource: /alto/ane-prop-map
>>   query-id: $resource[0].$response.meta.queryId
>>   entities: $resource[0].$response.costmap.values.reduce(
>>             (x,y) => x.values.concat(y.values))
>>
>> This design idea is a one-step service to get the cost map response and
>> the property map response together in one request, which means it will
>> return all the abstract network elements generated by one query. The effect
>> of this design is probably same as the inline-mode that will directly
>> return the properties of anes in the cost map, right?
>>
>>
> Not exact. The inline-mode pv design just provides one resource. This idea
> proposes a complete grammar of a query language. The response contains
> multiple resources. The PV query is just a special example. The design can
> also be used in other query combinition, e.g. Network Map + Cost Map. And
> the client can offload some computation on the server part.
>
>
>>
>> For 2, I have not found a good solution to handle the generic case.
>>
>> Looking forward to any feedback.
>>
>> Best regards,
>> Jensen
>>
>>

--94eb2c122e3a034e5f0552ed72ed
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I just realized that the example I took to explain how to =
query=C2=A0pv-cost-map=C2=A0+ ane-prop-map may make people confused.<div><b=
r></div><div>Ideally, I hope to provide a general query service to handle s=
ome batch query or some resource combination query. I want to know how many=
 people are interested in this idea or think it is useful. To make the disc=
ussion more efficiently, I will post an initial draft to define the formal =
grammar asap.</div><div><br></div><div>Best,</div><div>Jensen<br><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr">On Mon, Jun 26, 2017 at 10:04 PM Jens=
en Zhang &lt;<a href=3D"mailto:jingxuan.n.zhang@gmail.com">jingxuan.n.zhang=
@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr">Hi Dawn,<div><br></div><div>Thanks for your reply. Comment inline.=
</div><div><br></div><div>Thanks,</div><div>Jensen</div><div><br><div class=
=3D"gmail_quote"></div></div></div><div dir=3D"ltr"><div><div class=3D"gmai=
l_quote"><div dir=3D"ltr">On Mon, Jun 26, 2017 at 5:08 PM Dawn Chan &lt;<a =
href=3D"mailto:dawn_chen_f@hotmail.com" target=3D"_blank">dawn_chen_f@hotma=
il.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
Hi Jensen and all,
<div>Sorry for the late reply. Please see my comments inline.<br>
<div></div></div></div><div style=3D"word-wrap:break-word"><div><div>
<blockquote type=3D"cite">
<div>On 7 Jun 2017, at 4:52 PM, Jensen Zhang &lt;<a href=3D"mailto:jingxuan=
.n.zhang@gmail.com" target=3D"_blank">jingxuan.n.zhang@gmail.com</a>&gt; wr=
ote:</div>
<br class=3D"m_-8525774956040444482m_8328545563280957355Apple-interchange-n=
ewline">
<div>
<div dir=3D"ltr">Hi all,
<div><br>
</div>
<div>I am going to resume the discussion about graph representation and pat=
h vector. After some attempts to adopt the path-vector extension, I have th=
e following considerations:</div>
<div><br>
</div>
<div>1. The current design is inefficient. Since IETF 98, we have agreed on=
 the design of a two-stage protocol extension (path-vector cost map + unifi=
ed property map) for graph representation. It is extensible enough because =
we can customize the element
 (ane) properties. But the two-stage protocol will conduct the long delay a=
nd increase the complexity of state maintenance.</div>
<div><br>
</div>
<div>2. The resource dependencies are not clear. The &quot;Dependent Resour=
ces&quot; attribute in ALTO protocol is defined to claim the one-way resour=
ce dependencies. But many resource dependencies should be bidirectional. e.=
g. In path vector design, the cost
 map and the corresponding property map are bound to the same query.</div>
<div><br>
</div>
<div>For 1, my personal idea is to deliver a service to accept a sequence o=
f queries. In this way, the client can query both cost map and property map=
 in a single request. And the server will handle the two-stage protocol eff=
iciently.</div>
<div><br>
</div>
<div>Here is a rough example:</div>
<div><br>
</div>
<div><font face=3D"monospace">request:</font></div>
<div><font face=3D"monospace">- resource: /alto/pv-costmap</font></div>
<div><font face=3D"monospace">=C2=A0 pids:</font></div>
<div><font face=3D"monospace">=C2=A0 - srcs: [xxx]</font></div>
<div><font face=3D"monospace">=C2=A0 - dsts: [yyy]</font></div>
<div><font face=3D"monospace">- resource: /alto/ane-prop-map</font></div>
<div><font face=3D"monospace">=C2=A0 query-id: $resource[0].$response.meta.=
queryId</font></div>
<div><font face=3D"monospace">=C2=A0 entities: $resource[0].$response.costm=
ap.values.reduce(</font></div>
<div><font face=3D"monospace">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (x,=
y) =3D&gt; x.values.concat(y.values))</font></div>
</div>
</div>
</blockquote></div></div></div><div style=3D"word-wrap:break-word"><div><di=
v>
This design idea is a one-step service to get the cost map response and the=
 property map response together in one request, which means it will return =
all the abstract network elements generated by one query. The effect of thi=
s design is probably same as the
 inline-mode that will directly return the properties of anes in the cost m=
ap, right?</div></div></div><div style=3D"word-wrap:break-word"><div><div><=
br></div></div></div></blockquote><div><br></div></div></div></div><div dir=
=3D"ltr"><div><div class=3D"gmail_quote"><div>Not exact. The inline-mode pv=
 design just provides one resource. This idea proposes a complete grammar o=
f a query language. The response contains multiple resources. The PV query =
is just a special example. The design can also be used in other query combi=
nition, e.g. Network Map=C2=A0+ Cost Map. And the client can offload some c=
omputation on the server part.</div></div></div></div><div dir=3D"ltr"><div=
><div class=3D"gmail_quote"><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div style=3D"word-wrap:break-word"><div><div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">
<div><br>
</div>
<div>For 2, I have not found a good solution to handle the generic case.</d=
iv>
<div><br>
</div>
<div>Looking forward to any feedback.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Jensen</div>
</div>
</div>
</blockquote>
</div></div></div></blockquote></div></div></div></blockquote></div></div><=
/div>

--94eb2c122e3a034e5f0552ed72ed--


From nobody Tue Jun 27 06:09:50 2017
Return-Path: <gaok12@mails.tsinghua.edu.cn>
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 D75CE129B0D for <alto@ietfa.amsl.com>; Tue, 27 Jun 2017 06:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 R_RORGC3cc1x for <alto@ietfa.amsl.com>; Tue, 27 Jun 2017 06:09:46 -0700 (PDT)
Received: from tsinghua.edu.cn (smtp29.tsinghua.edu.cn [166.111.204.53]) by ietfa.amsl.com (Postfix) with ESMTP id BF60B129B07 for <alto@ietf.org>; Tue, 27 Jun 2017 06:09:45 -0700 (PDT)
Received: from [192.168.11.215] (unknown [106.187.89.196]) by app5 (Coremail) with SMTP id DsxvpgD3NHISWVJZsuBWAA--.8621S2; Tue, 27 Jun 2017 21:09:42 +0800 (CST)
To: IETF ALTO <alto@ietf.org>
From: Kai Gao <gaok12@mails.tsinghua.edu.cn>
Message-ID: <07e102bd-999a-c6b3-de5c-e5f01bc5b924@mails.tsinghua.edu.cn>
Date: Tue, 27 Jun 2017 21:09:38 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-CM-TRANSID: DsxvpgD3NHISWVJZsuBWAA--.8621S2
X-Coremail-Antispam: 1UD129KBjvJXoW7Ar48urWxuryrAw1kWF48Zwb_yoW8WrW8pr WfXFZ8CrZ8WFy5Jw1fAan5KF95uan5Gan0qrWrZr4DCanFgryvv3WfKrZ0gayDJryqvrsa gr45X397A3WrAr7anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUyFb7Iv0xC_Cr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2z4x0Y4vE2Ix0cI8IcVAFwI0_tr0E3s1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr1j 6F4UJwA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwVC2z280aVCY1x0267AKxVW0oV Cq3wAac4AC62xK8xCEY4vEwIxC4wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40EFcxC 0VAKzVAqx4xG6I80ewAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr 1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y48IcVAKI48JMxk0xIA0c2IEe2xFo4CEbIxvr21l 42xK82IYc2Ij64vIr41lx2IqxVAqx4xG67AKxVWUJVWUGwC20s026x8GjcxK67AKxVWUGV WUWwC2zVAF1VAY17CE14v26r1j6r15MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_ Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rV WrZr1j6s0DMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_ GrUvcSsGvfC2KfnxnUUI43ZEXa7xUUe_AUUUUUU==
X-CM-SenderInfo: 5jdryi2s6ptxtovo32xlqjx3vdohv3gofq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/AeDc7i3zQ63t9_FCkFYa1yWI8us>
Subject: [alto] Reviews on draft-gao-alto-fcs-02
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: Tue, 27 Jun 2017 13:09:49 -0000

Dear authors of draft-gao-alto-fcs,

I have roughly reviewed the latest FCS draft. Please see the comments below.


Regards,
Kai

Terminology:

sX: section X
ppX: page X
pX: paragraph X
lX: line X

pp3, s1, p1
l2: scenario -> scenarios
l3-4: "... the P2P application ..." -> "... P2P applications ..."

pp3, s1
p2, l2: central -> centralized
p2 & p3: I think these two paragraphs can benefit from some restructuring to
make the motivations for flow-based query more explicit and also easier 
to read.

pp3, s1, p5
l1: consider -> describe
l3: schema -> schemas


pp4, s1, p1
l2: "... 5-tuples of ..." -> Use the explicit form of the 5-tuple: "... 
5-tuple <ip-protocol, ...>"
l6: "SHOULD support" -> "supports"
l7: "to satisfy" -> "and satisfies"

pp5, s3.1.2, p5
l4: "appeared" -> "appear"

pp6, s3.2
title: "Extend" -> "Extended"
p2, l2: "... to measure the cost" -> "... to specify the request"
p2, l3: "SHOULD" -> "MUST"
p2, l4: "be" -> "have"
p2, l5: "format" -> "formats"
p4, l2: Extra space after "TypedEndpointAddr"

pp6, s3.2.1, p1
l1: "contain" -> "can be"
l4: "specified" -> remove it.
l5: "be conflict" -> "conflict"
l6: "is conflict" -> "conflicts"

pp7, s3.2.3, p1: Use "Protocol" instead of "protocol" to make it 
explicit that
it represents the value contained in the query.

pp8
s3.3.1, p1, l1: Remove "then"
s3.3.2, p6, l4: "appeared" -> "appear"
s3.3.3, p1, l2: "exactly" -> "exactly the same"
s4, title: Example -> Examples

pp14, s4.2.3, p4, l3: "value types" -> "value type"

pp15, s4.2.5.1, p1, l5: ", the servers" -> ". The servers"

pp16, s4.2.5, p3, l3: "TypedHeadreField" -> "TypedHeaderField"



From nobody Tue Jun 27 09:24:47 2017
Return-Path: <dennis.yht@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 418F51271DF for <alto@ietfa.amsl.com>; Tue, 27 Jun 2017 09:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, 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 JS-aYOTDwC6E for <alto@ietfa.amsl.com>; Tue, 27 Jun 2017 09:24:43 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 686D8129B9C for <alto@ietf.org>; Tue, 27 Jun 2017 09:24:43 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id v202so3135648itb.1 for <alto@ietf.org>; Tue, 27 Jun 2017 09:24:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GsUfSKz94XOtAbpfBGKGzKvoGwqgt+wIIMTbqcol5Gk=; b=mFDcVmMqvJLCsd4KG2Fe3hiVeq5mIgYBBdtfvxidSVVjGLo1HNCrKtVXlPT3Wt59IG w37WiJ/Fx5Ts+1BYSuWCos3TQzbCgVSo95uLD9ziqr0eGwQ6C/2zD5Lefi/5YEmuEqGW Y+m78Q7n78ECHH+SmceJbVIbkEithZYn2lwfHziasNKBINl7A5LIvrnxNTsQH97lAta7 JP9sgjVKuzuClHsClpO5zwDhP7FPB1u4XMJuuiYtLVZ/FOFMGzLCeh6hp5vGrT2NXrhw ac0FUEh5icKK3bDUlrfaO/YeqZEyq9OGzfyVTZsOUEgXbuf0eRzN7lCZ6X435lZ3+2Cc gw2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GsUfSKz94XOtAbpfBGKGzKvoGwqgt+wIIMTbqcol5Gk=; b=sHbXlYYABz0kV0QB96gyZjXHqPrdr9QOgHLrETd2mkIYEX76QiVeIVkSImXjPZVmi5 CGd9n/Yj+a/NO8ZKSTDnUPCznBF2eblOJI463GzTlb/aQ/KLKZtvf0p2zEa99mxzIcHR PleOhaeGHPxXOlP6Jk84UOLoOTXz6vmAJsWQ3506aHaB8uxDkxGIv86YhO4NHq/Ps8am OH137xq04E/F0lSgwEQ6zSkns7XVbJY7j/4G25cdiP5JVB3csvdRyJChS2gXHaeTywC1 6VuMffls9VgRk5wdrax8Rg6iIOQt+BtONBHxlfUm1B9hxuRo0YG+IdTZCVSCmLUVEHZf etOg==
X-Gm-Message-State: AKS2vOx0X9J+0++0oVWJ1ItBjuUwNHI0mV4vwKxzxbzMDx0g/LMCZB5q gZSduEeQ/RNBa3WJ3zfehs20NuxaQfvg
X-Received: by 10.36.23.146 with SMTP id 140mr4025599ith.88.1498580682716; Tue, 27 Jun 2017 09:24:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.159.132 with HTTP; Tue, 27 Jun 2017 09:24:42 -0700 (PDT)
In-Reply-To: <07e102bd-999a-c6b3-de5c-e5f01bc5b924@mails.tsinghua.edu.cn>
References: <07e102bd-999a-c6b3-de5c-e5f01bc5b924@mails.tsinghua.edu.cn>
From: Dennis Yu <dennis.yht@gmail.com>
Date: Wed, 28 Jun 2017 00:24:42 +0800
Message-ID: <CAN-YqX2=qFJOyHAVKSGgzJJjGpuJpca2Kht6w0+bPKNQi2cW5g@mail.gmail.com>
To: Kai Gao <gaok12@mails.tsinghua.edu.cn>
Cc: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="001a1143776442be7b0552f3819b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/8deIrpVcGnwytJKZxblZebr4sw0>
Subject: Re: [alto] Reviews on draft-gao-alto-fcs-02
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: Tue, 27 Jun 2017 16:24:46 -0000

--001a1143776442be7b0552f3819b
Content-Type: text/plain; charset="UTF-8"

Dear authors of draft-gao-alto-fcs-02,

Yet another review of draft-gao-alto-fcs-02 :)
Here are some opinions that maybe have some help,

1.
Some inconsistency with draft-ietf-alto-multi-cost-10,

the definition of ReqFilteredCostMap in "multi-cost" section 4.1.2 is as
follows,
(the comments are appended)

    object {
        [CostType cost-type;]
        [CostType multi-cost-types<1..*>;]
        [CostType testable-cost-types<1..*>;]
        [JSONString constraints<0..*>;]
        [JSONString or-constraints<1..*><1..*>;]
        [PIDFilter pids];   //<---- likely a typo
    } ReqFilteredCostMap;

and the extended definition in "fcs" section 3.1.2 is,

    object {
        [CostType cost-type;]
        [CostType multi-cost-types<1..*>;]
        [CostType testable-cost-types<1..*>;]
        [JSONString constraints<0..*>;]
        [JSONString or-constraints<0..*><0..*>;]  //  1 --> 0
        [PIDFilter  pids;]
        [PIDFilter  pid-flows<1..*>;]
    } ReqFilteredCostMap;

also see the definition of ReqEndpointCostMap. Although the difference
between "1" and "0" is tiny, but I think it's better to agree on one
definition.

2.
the definition of FlowCostResponse in section 4.2.5 is as follows,

    object {
        FlowCostMap     flow-cost-map;
        [FlowCostMap    flow-cost-confidences;]
    } FlowCostResponse : ResponseEntityBase;

    object-map {
        FlowId -> JSONValue;
    } FlowCostMap;

Firstly, I'm not sure the "JSONValue" is well-defined. According to RFC7159
section 3, "A JSON value MUST be an object, array, number, or string, or
one of the following three literal names: false null true"

Secondly, I think the "flow-cost-confidences" could have its clear type
definition, maybe

    object-map {
        FlowId -> JSONValue;
    } FlowCostConfidence

Thirdly, I personally think that the cost confidence should better be
defined as a JSON fractional number between 0 to 1.

3.
A missing comma in the example of page 19 (l3-flow-aggr)
Two redundant commas in the example of page 19 (cost-type) and page 10
(dependent-vtags)

4.
The change log of section 2 can be composed as an appendix.

5.
Section 8.2, "Openflow" and "openflow" -> "OpenFlow"

Sincerely,
Dennis Yu

On Tue, Jun 27, 2017 at 9:09 PM, Kai Gao <gaok12@mails.tsinghua.edu.cn>
wrote:

> Dear authors of draft-gao-alto-fcs,
>
> I have roughly reviewed the latest FCS draft. Please see the comments
> below.
>
>
> Regards,
> Kai
>
> Terminology:
>
> sX: section X
> ppX: page X
> pX: paragraph X
> lX: line X
>
> pp3, s1, p1
> l2: scenario -> scenarios
> l3-4: "... the P2P application ..." -> "... P2P applications ..."
>
> pp3, s1
> p2, l2: central -> centralized
> p2 & p3: I think these two paragraphs can benefit from some restructuring
> to
> make the motivations for flow-based query more explicit and also easier to
> read.
>
> pp3, s1, p5
> l1: consider -> describe
> l3: schema -> schemas
>
>
> pp4, s1, p1
> l2: "... 5-tuples of ..." -> Use the explicit form of the 5-tuple: "...
> 5-tuple <ip-protocol, ...>"
> l6: "SHOULD support" -> "supports"
> l7: "to satisfy" -> "and satisfies"
>
> pp5, s3.1.2, p5
> l4: "appeared" -> "appear"
>
> pp6, s3.2
> title: "Extend" -> "Extended"
> p2, l2: "... to measure the cost" -> "... to specify the request"
> p2, l3: "SHOULD" -> "MUST"
> p2, l4: "be" -> "have"
> p2, l5: "format" -> "formats"
> p4, l2: Extra space after "TypedEndpointAddr"
>
> pp6, s3.2.1, p1
> l1: "contain" -> "can be"
> l4: "specified" -> remove it.
> l5: "be conflict" -> "conflict"
> l6: "is conflict" -> "conflicts"
>
> pp7, s3.2.3, p1: Use "Protocol" instead of "protocol" to make it explicit
> that
> it represents the value contained in the query.
>
> pp8
> s3.3.1, p1, l1: Remove "then"
> s3.3.2, p6, l4: "appeared" -> "appear"
> s3.3.3, p1, l2: "exactly" -> "exactly the same"
> s4, title: Example -> Examples
>
> pp14, s4.2.3, p4, l3: "value types" -> "value type"
>
> pp15, s4.2.5.1, p1, l5: ", the servers" -> ". The servers"
>
> pp16, s4.2.5, p3, l3: "TypedHeadreField" -> "TypedHeaderField"
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

--001a1143776442be7b0552f3819b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style=3D"font-size:12.8px">Dear authors of draft-gao-=
alto-fcs-02,</div><div style=3D"font-size:12.8px"><br></div><div style=3D"f=
ont-size:12.8px">Yet another review of draft-gao-alto-fcs-02 :)</div><div s=
tyle=3D"font-size:12.8px">Here are some opinions that maybe have some help,=
</div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.=
8px">1.</div><div style=3D"font-size:12.8px">Some inconsistency with draft-=
ietf-alto-multi-cost-10,</div><div style=3D"font-size:12.8px"><br></div><di=
v style=3D"font-size:12.8px">the definition of ReqFilteredCostMap in &quot;=
multi-cost&quot; section 4.1.2 is as follows,</div><div style=3D"font-size:=
12.8px">(the comments are appended)</div><div style=3D"font-size:12.8px"><b=
r></div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 object {</div><div st=
yle=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [CostType cost-type;]<=
/div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [CostType =
multi-cost-types&lt;1..*&gt;;]</div><div style=3D"font-size:12.8px">=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 [CostType testable-cost-types&lt;1..*&gt;;]</div><div =
style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [JSONString constrai=
nts&lt;0..*&gt;;]</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 [JSONString or-constraints&lt;1..*&gt;&lt;1..*&gt;;]</div><div styl=
e=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [PIDFilter pids]; =C2=A0=
 //&lt;---- likely a typo</div><div style=3D"font-size:12.8px">=C2=A0 =C2=
=A0 } ReqFilteredCostMap;</div><div style=3D"font-size:12.8px"><br></div><d=
iv style=3D"font-size:12.8px">and the extended definition in &quot;fcs&quot=
; section 3.1.2 is,</div><div style=3D"font-size:12.8px"><br></div><div sty=
le=3D"font-size:12.8px">=C2=A0 =C2=A0 object {</div><div style=3D"font-size=
:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [CostType cost-type;]</div><div style=
=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [CostType multi-cost-type=
s&lt;1..*&gt;;]</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 [CostType testable-cost-types&lt;1..*&gt;;]</div><div style=3D"font-=
size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [JSONString constraints&lt;0..*&gt=
;;]</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [JSONS=
tring or-constraints&lt;0..*&gt;&lt;0..*&gt;;] =C2=A0// =C2=A01 --&gt; 0</d=
iv><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [PIDFilter =
=C2=A0pids;]</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 [PIDFilter =C2=A0pid-flows&lt;1..*&gt;;]</div><div style=3D"font-size:1=
2.8px">=C2=A0 =C2=A0 } ReqFilteredCostMap;</div><div style=3D"font-size:12.=
8px"><br></div><div style=3D"font-size:12.8px">also see the definition of R=
eqEndpointCostMap. Although the difference between &quot;1&quot; and &quot;=
0&quot; is tiny, but I think it&#39;s better to agree on one definition.</d=
iv><div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px=
">2.</div><div style=3D"font-size:12.8px">the definition of FlowCostRespons=
e in section 4.2.5 is as follows,</div><div style=3D"font-size:12.8px"><br>=
</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 object {</div><div styl=
e=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 FlowCostMap =C2=A0 =C2=
=A0 flow-cost-map;</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 [FlowCostMap =C2=A0 =C2=A0flow-cost-confidences;]</div><div styl=
e=3D"font-size:12.8px">=C2=A0 =C2=A0 } FlowCostResponse : ResponseEntityBas=
e;</div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:1=
2.8px">=C2=A0 =C2=A0 object-map {</div><div style=3D"font-size:12.8px">=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 FlowId -&gt; JSONValue;</div><div style=3D"font-si=
ze:12.8px">=C2=A0 =C2=A0 } FlowCostMap;</div><div style=3D"font-size:12.8px=
"><br></div><div style=3D"font-size:12.8px">Firstly, I&#39;m not sure the &=
quot;JSONValue&quot; is well-defined. According to RFC7159 section 3, &quot=
;A JSON value MUST be an object, array, number, or string, or one of the fo=
llowing three literal names: false null true&quot;</div><div style=3D"font-=
size:12.8px"><br></div><div style=3D"font-size:12.8px">Secondly, I think th=
e &quot;flow-cost-confidences&quot; could have its clear type definition, m=
aybe</div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-size=
:12.8px">=C2=A0 =C2=A0 object-map {</div><div style=3D"font-size:12.8px">=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 FlowId -&gt; JSONValue;</div><div style=3D"font=
-size:12.8px">=C2=A0 =C2=A0 } FlowCostConfidence</div><div style=3D"font-si=
ze:12.8px"><br></div><div style=3D"font-size:12.8px">Thirdly, I personally =
think that the cost confidence should better be defined as a JSON fractiona=
l number between 0 to 1.</div><div style=3D"font-size:12.8px"><br></div><di=
v style=3D"font-size:12.8px">3.</div><div style=3D"font-size:12.8px">A miss=
ing comma in the example of page 19 (l3-flow-aggr)</div><div style=3D"font-=
size:12.8px">Two redundant commas in the example of page 19 (cost-type) and=
 page 10 (dependent-vtags)</div><div style=3D"font-size:12.8px"><br></div><=
div style=3D"font-size:12.8px">4.</div><div style=3D"font-size:12.8px">The =
change log of section 2 can be composed as an appendix.</div><div style=3D"=
font-size:12.8px"><br></div><div style=3D"font-size:12.8px">5.</div><div st=
yle=3D"font-size:12.8px">Section 8.2, &quot;Openflow&quot; and &quot;openfl=
ow&quot; -&gt; &quot;OpenFlow&quot;=C2=A0</div><div style=3D"font-size:12.8=
px"><br></div><div style=3D"font-size:12.8px">Sincerely,</div><div style=3D=
"font-size:12.8px">Dennis Yu</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Jun 27, 2017 at 9:09 PM, Kai Gao <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:gaok12@mails.tsinghua.edu.cn" target=3D"_blank">gaok=
12@mails.tsinghua.edu.cn</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">Dear authors of draft-gao-alto-fcs,<br>
<br>
I have roughly reviewed the latest FCS draft. Please see the comments below=
.<br>
<br>
<br>
Regards,<br>
Kai<br>
<br>
Terminology:<br>
<br>
sX: section X<br>
ppX: page X<br>
pX: paragraph X<br>
lX: line X<br>
<br>
pp3, s1, p1<br>
l2: scenario -&gt; scenarios<br>
l3-4: &quot;... the P2P application ...&quot; -&gt; &quot;... P2P applicati=
ons ...&quot;<br>
<br>
pp3, s1<br>
p2, l2: central -&gt; centralized<br>
p2 &amp; p3: I think these two paragraphs can benefit from some restructuri=
ng to<br>
make the motivations for flow-based query more explicit and also easier to =
read.<br>
<br>
pp3, s1, p5<br>
l1: consider -&gt; describe<br>
l3: schema -&gt; schemas<br>
<br>
<br>
pp4, s1, p1<br>
l2: &quot;... 5-tuples of ...&quot; -&gt; Use the explicit form of the 5-tu=
ple: &quot;... 5-tuple &lt;ip-protocol, ...&gt;&quot;<br>
l6: &quot;SHOULD support&quot; -&gt; &quot;supports&quot;<br>
l7: &quot;to satisfy&quot; -&gt; &quot;and satisfies&quot;<br>
<br>
pp5, s3.1.2, p5<br>
l4: &quot;appeared&quot; -&gt; &quot;appear&quot;<br>
<br>
pp6, s3.2<br>
title: &quot;Extend&quot; -&gt; &quot;Extended&quot;<br>
p2, l2: &quot;... to measure the cost&quot; -&gt; &quot;... to specify the =
request&quot;<br>
p2, l3: &quot;SHOULD&quot; -&gt; &quot;MUST&quot;<br>
p2, l4: &quot;be&quot; -&gt; &quot;have&quot;<br>
p2, l5: &quot;format&quot; -&gt; &quot;formats&quot;<br>
p4, l2: Extra space after &quot;TypedEndpointAddr&quot;<br>
<br>
pp6, s3.2.1, p1<br>
l1: &quot;contain&quot; -&gt; &quot;can be&quot;<br>
l4: &quot;specified&quot; -&gt; remove it.<br>
l5: &quot;be conflict&quot; -&gt; &quot;conflict&quot;<br>
l6: &quot;is conflict&quot; -&gt; &quot;conflicts&quot;<br>
<br>
pp7, s3.2.3, p1: Use &quot;Protocol&quot; instead of &quot;protocol&quot; t=
o make it explicit that<br>
it represents the value contained in the query.<br>
<br>
pp8<br>
s3.3.1, p1, l1: Remove &quot;then&quot;<br>
s3.3.2, p6, l4: &quot;appeared&quot; -&gt; &quot;appear&quot;<br>
s3.3.3, p1, l2: &quot;exactly&quot; -&gt; &quot;exactly the same&quot;<br>
s4, title: Example -&gt; Examples<br>
<br>
pp14, s4.2.3, p4, l3: &quot;value types&quot; -&gt; &quot;value type&quot;<=
br>
<br>
pp15, s4.2.5.1, p1, l5: &quot;, the servers&quot; -&gt; &quot;. The servers=
&quot;<br>
<br>
pp16, s4.2.5, p3, l3: &quot;TypedHeadreField&quot; -&gt; &quot;TypedHeaderF=
ield&quot;<br>
<br>
<br>
______________________________<wbr>_________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/alto</a><br>
</blockquote></div><br></div></div>

--001a1143776442be7b0552f3819b--


From nobody Tue Jun 27 19:05:52 2017
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 A962012762F; Tue, 27 Jun 2017 19:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.876
X-Spam-Level: 
X-Spam-Status: No, score=-0.876 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 0UBb8Kgx1Doi; Tue, 27 Jun 2017 19:05:49 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255056.outbound.protection.outlook.com [40.92.255.56]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80C53127871; Tue, 27 Jun 2017 19:05:45 -0700 (PDT)
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=QV7ZeYcAp4slJdt4wa0QMg4pTO245KrR/qxuunaPHls=; b=XKYlC7Hn/vJz5wQrMTDvJo6Jo/U4CEsDqNG6OYLHkxMBL2At0BOcd+zKmpU37b2C99z9hSR/brKJT3f1Xc672dXHl3aewJ3kcdICUIhao2KpEWhKZ+Ed/4RT4guYMgd/frdkiqdubN881F4/GsT8NB2RRkYhbQciDJF24YMwWyA7m9hYHG+YoAcCGaLozSPLusnbm3BUrdkBpRfUQIuSLCpuFDxMqWZIIp/67fZnTFYT00wFEvgJYL6A85c4VidY2ds1i8ymVgUWOPX17c3B6tkl4lDkyp6I6ksicYZCoN0tZye6k7D924i/ZtNkPu+3w3B+UVsq7pZLJoq+Sw3K4Q==
Received: from HK2APC01FT114.eop-APC01.prod.protection.outlook.com (10.152.248.59) by HK2APC01HT110.eop-APC01.prod.protection.outlook.com (10.152.249.201) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1199.9; Wed, 28 Jun 2017 02:05:42 +0000
Received: from PS1PR0302MB2457.apcprd03.prod.outlook.com (10.152.248.52) by HK2APC01FT114.mail.protection.outlook.com (10.152.248.192) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.9 via Frontend Transport; Wed, 28 Jun 2017 02:05:42 +0000
Received: from PS1PR0302MB2457.apcprd03.prod.outlook.com ([fe80::290a:8d10:d903:ff49]) by PS1PR0302MB2457.apcprd03.prod.outlook.com ([fe80::290a:8d10:d903:ff49%18]) with mapi id 15.01.1220.011; Wed, 28 Jun 2017 02:05:42 +0000
From: xin wang <xinwang2014@hotmail.com>
To: "draft-ietf-alto-performance-metrics@ietf.org" <draft-ietf-alto-performance-metrics@ietf.org>
CC: IETF ALTO <alto@ietf.org>
Thread-Topic: Here is a review of draft-ietf-alto-performance-metrics-01
Thread-Index: AQHS77KHjlFF1/I4VEOSeLJnKnux4Q==
Date: Wed, 28 Jun 2017 02:05:42 +0000
Message-ID: <PS1PR0302MB24575EB8EFEB9023D40F4530A8DD0@PS1PR0302MB2457.apcprd03.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:A965E7A7402916E170FA641314CF39A2577B41DE1B5375450D0CE8937B0139DF; UpperCasedChecksum:58C2F97C6129A8B91A4AB52E2BE0D25F3B807A66BFD42F70A400B2F447E50335; SizeAsReceived:7206; Count:44
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [m3ohLlDLxPXmul1hFij3lonSE9Oq1uyK]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HK2APC01HT110; 7:t3zxBwCSxVVONdxDJ1WhKwq0oqgXTfGwhVktfswFc1xEXMt0uemlPBtYJMCO0/eBGCRxQFkwTDTAGt6c+BTdEIFb8RCS2JfCvXIjtv6fGz6ATpCEounrpYvj4vgEfGHvbaLxW2GjJYekWiHjUMx/UfksMEIEMDviZkqJyz20aU1BjFqsViEv95xspzBh5/jjAtXRVGSdktzQhAOOaafM+Qf2FpN4DnQM5vTAS43dLIMA6LMxEPF73qQwkps1XHw47u41NUtUAifwWfFxvnzn5GqR/hg6dLwc+munU1su67XmS29b9Qv6AVQ6PKwN+av6ZqNvlCTpU68q47071mHX/s/NeYbvWr3dlUaSx1m6WUFkdVCT80IQ1/XLdLIRIBcxbh0mV5tFjy/mf/OigkHxCz+K3i+zmfOfE1H/c+umfA7W+ZK5kgfhUWaoRj/2vmyQ0Yn0rgXFR0p6NPMW4oAN+GnFDgoYxy1ZffDXJK27HRDefkTw9IKbm7m6r16ZH0DMLNCThulRYTkbFnFMDJApA354YF0Y7lwC4fJsoIgEoTwDWZk37XkRybfbnC2vkoOLjicMWqMAGwFtX5J5T1Iesmge8XblftoMrnwaM+qpUCMyAWPM+5BrTNWsGYo0O6ezh4jGIlROwk75Ykv4iqTxdoYWl6I+yYCkzGigSsrzRc/sZMEY+JsDVuMfiaraSjW3IkRRuTb0gBwuEjCIuPlvMt+cyVk3aWiwwG1G08EOO+/AVfiodiw8HsoVEfVCHkiUy3m5hKmWnY/ZS92S8TY+4Q==
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:HK2APC01HT110; H:PS1PR0302MB2457.apcprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 7b04da7e-e142-45fe-9bd5-08d4bdca2e80
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095)(300000506073)(300135500095); SRVR:HK2APC01HT110; 
x-ms-traffictypediagnostic: HK2APC01HT110:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:HK2APC01HT110; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:HK2APC01HT110; 
x-forefront-prvs: 03524FBD26
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_PS1PR0302MB24575EB8EFEB9023D40F4530A8DD0PS1PR0302MB2457_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jun 2017 02:05:42.6993 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT110
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/KwqRl-ii7N0jnvrgJaqKuFP_GXU>
Subject: [alto] Here is a review of draft-ietf-alto-performance-metrics-01
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: Wed, 28 Jun 2017 02:05:51 -0000

--_000_PS1PR0302MB24575EB8EFEB9023D40F4530A8DD0PS1PR0302MB2457_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Dear authors of "ALTO Performance Cost Metrics=94,


Your draft about extending cost metrics of ALTO looks very useful, especial=
ly for varieties of applications with different criteria to make decisions =
for traffic engineering. The following is a review of your draft:


a. Link Maximum Reservable Bandwidth and Link Residue Bandwidth


These three cost metrics look very similar but have different meanings acco=
rding to your draft. In my understanding, based on the concept of bandwidth=
 oversubscription, a reserved bandwidth could be larger than current remain=
ing bandwidth (equals to max bandwidth subtract the sum of all reserved ban=
dwidth). Then, Link Maximum Reservable Bandwidth should be slightly larger =
than Link Residue Bandwidth. Is this right?


b. Unitless performance scores


In section 2.1, the draft suggests providing unitless performance scores fo=
r privacy issues. In ALTO cost mode, it defines =93ordinal=94 which indicat=
es the ranking of the cost values instead of actual costs. Do you suggest t=
o add more intelligent abstraction of cost values besides of ranking?


c. Packet Delay Variation


The draft uses the minimum delay observed as the definition of packet delay=
 variation. I am not sure it is a good solution. There are some other appro=
aches you may consider, such as standard deviation.


d. The unit of Periodic One Way Delay


The draft uses seconds as the unit of Periodic One Way Delay. I am not sure=
 it is typos or not since the example shows the powdelay cost values are 10=
, 20, and 30.


Also there are some typos you may fix:


Abstraction: add space between "BGP-LS,OSPF-TE";

Page 2: =93delay sensitive=94 -> =93delay-sensitive=94;

Page 2: =93a set new=94 -> =93a set of new=94;

Page 2: =93 explicitely=94 -> =93 explicitly=94

Page 4: =93 invlove=94 -> =93 involve"


Best,

Xin


--_000_PS1PR0302MB24575EB8EFEB9023D40F4530A8DD0PS1PR0302MB2457_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Dear authors of &quot;ALTO Performance =
Cost Metrics=94,</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Your draft about extending cost metrics=
 of ALTO looks very useful, especially for varieties of applications with d=
ifferent criteria to make decisions for traffic engineering. The following =
is a review of your draft:</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">a. Link Maximum Reservable Bandwidth an=
d Link Residue Bandwidth</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">These three cost metrics look&nbsp;very=
 similar but have different meanings according to your draft. In my underst=
anding, based on the concept of bandwidth oversubscription, a reserved band=
width could be larger than current remaining
 bandwidth (equals to max bandwidth subtract the sum of all reserved bandwi=
dth). Then, Link Maximum Reservable Bandwidth should be slightly larger tha=
n Link Residue Bandwidth. Is this right?</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">b. Unitless performance scores</span></=
p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">In section 2.1, the draft suggests prov=
iding unitless performance scores for privacy issues. In ALTO cost mode, it=
 defines =93ordinal=94 which indicates the&nbsp;ranking of the cost values =
instead of actual costs. Do you suggest to
 add more intelligent abstraction of cost values besides of ranking?</span>=
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">c. Packet Delay Variation</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">The draft uses the minimum delay observ=
ed as the definition of packet delay variation. I am not sure it is a good =
solution. There are some other approaches you may consider, such as standar=
d deviation.</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">d. The unit of Periodic One Way Delay</=
span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">The draft uses seconds as the unit of P=
eriodic One Way Delay. I am not sure it is typos or not since the example s=
hows the powdelay cost values are 10, 20, and 30.</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Also there are some typos you may fix:<=
/span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Abstraction: add space between &quot;BG=
P-LS,OSPF-TE&quot;;</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 2: =93delay sensitive=94 -&gt; =93=
delay-sensitive=94;</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 2: =93a set new=94 -&gt; =93a set =
of new=94;</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 2: =93 explicitely=94 -&gt; =93 ex=
plicitly=94</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 4: =93 invlove=94 -&gt; =93 involv=
e&quot;</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;"><br>
</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Best,</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Xin</span></p>
<br>
<p></p>
</div>
</body>
</html>

--_000_PS1PR0302MB24575EB8EFEB9023D40F4530A8DD0PS1PR0302MB2457_--


From geng.li@yale.edu  Tue Jun 27 19:52:33 2017
Return-Path: <geng.li@yale.edu>
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 38806129AD7; Tue, 27 Jun 2017 19:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yale.edu
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 a6_6v7abboaC; Tue, 27 Jun 2017 19:52:30 -0700 (PDT)
Received: from mx0b-00135301.pphosted.com (mx0b-00135301.pphosted.com [148.163.159.240]) (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 94AC6126CBF; Tue, 27 Jun 2017 19:52:27 -0700 (PDT)
Received: from pps.filterd (m0109492.ppops.net [127.0.0.1]) by mx0b-00135301.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v5S2oNct020908; Tue, 27 Jun 2017 22:52:25 -0400
Authentication-Results: ppops.net; spf=pass smtp.mailfrom=geng.li@yale.edu
Received: from nam02-sn1-obe.outbound.protection.outlook.com (mail-sn1nam02lp0015.outbound.protection.outlook.com [216.32.180.15]) by mx0b-00135301.pphosted.com with ESMTP id 2bbqnk24mh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 27 Jun 2017 22:52:25 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8H8neMbx1tkDIHoji1JAUgXQGZJJXljWzq6+5GdI8og=; b=uzegkxUJsWyO7VfvfnkzvCsZPU4U8ibNKHH8FN7zcehb5ZsSQNIt9BgCwgEFPhcG7Gkv2LyEXehYTxsmn5X7wyUhlDV8TNf8yABh9fj2k1IXetdLW/MKwlbCJre3mbLTKr4cox/idnvByGVNgQxnZlcNeSoXFPqgB/Sy83MVFMk=
Received: from CY4PR08MB3526.namprd08.prod.outlook.com (10.171.254.13) by CY4PR08MB3528.namprd08.prod.outlook.com (10.171.254.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.11; Wed, 28 Jun 2017 02:52:23 +0000
Received: from CY4PR08MB3526.namprd08.prod.outlook.com ([10.171.254.13]) by CY4PR08MB3526.namprd08.prod.outlook.com ([10.171.254.13]) with mapi id 15.01.1199.019; Wed, 28 Jun 2017 02:52:23 +0000
From: "Li, Geng" <geng.li@yale.edu>
To: "alto@ietf.org" <alto@ietf.org>, "draft-ietf-alto-xdom-disc@ietf.org" <draft-ietf-alto-xdom-disc@ietf.org>
Thread-Topic: Review on draft-ietf-alto-xdom-disc-00 by Geng
Thread-Index: AQHS77fDBZjF8eIItUe+KIo37MP0vg==
Date: Wed, 28 Jun 2017 02:52:23 +0000
Message-ID: <CY4PR08MB352648AA55E5F4CCB1DF666491DD0@CY4PR08MB3526.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=yale.edu;
x-originating-ip: [130.132.173.199]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR08MB3528; 7:gY1IYdOjUF5sz7BdHm15H5XBmpdf9ts3Wbz9mamyvSgb+EaRfI+TmGr+CSDQah6W8X/zYFgSnwUhj6sd/WZGbewdWyKSUOcS4W31nh6NkbijPnbao4PwqFEuMSOfjL1G7Q5Dtp10j2Vce3FWvP34D6BdFaY6plThG/HSF8jJGo2bkBc68KF3RO/NAxQUwO5OE0zZGyeXf07YhRZhBrphGOjp7hIQ+pi4k1Gl7foRgb7TuV//qbMJjNai/oqosENrsEZWXVD6jUpkr9RbDnMDGuMhD9UXlqdDrRdSuTDhbzvq7WQnnYA+7GnsbgtLJeWCUvMA2msvPkKg9ziovT2EGDY8Q8AD7wsVW6gEG6bZtEZ8+qeKkv89wVvNy61MW0uPmRENPfIzXJGpISWElVFtkq+JOHxiPoYaHTqk6vgVpsQHpnqp3HxqUpnfgfpjMGorDCyVZ+nf0+F+MZdKNLIzXN6HYA32d/xoCHAlCUrMUBubt0ZQFjVCnBx4Hgm712cQikHob3tSBtJ2uFGKuecjJ+/JaUaMenXbXmw8KhRlVbAKCbmkIYrhOO9eUx+2etb7eodbtq8jGSUllHjX1kz1Q0CBJXd+p5vcHKU5yHWddbHerlRnw+UUvNIm/8Vx66UCQOLd0QMpj8gPI6p0Vbyb649LwueOc8Je1NzuLAA8W96zzfSVzgk82JcrORqKb0BckHAvFjT9+2z/UoJMcCLxFu9j7ePpanITaH3vc4GhZnTis8KAsdoDMinW+Y2Ed8yrMbZuybYBjTJyRsQL1+5/4saNPQpPI1OEequQI4D6Tyo=
x-ms-office365-filtering-correlation-id: 99242a18-01c7-42b7-6f73-08d4bdd0b415
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(300000502095)(300135100095)(22001)(2017030254075)(300000503095)(300135400095)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506074)(300135500095); SRVR:CY4PR08MB3528; 
x-ms-traffictypediagnostic: CY4PR08MB3528:
x-microsoft-antispam-prvs: <CY4PR08MB35280832BDADDA890AFD40EF91DD0@CY4PR08MB3528.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(133145235818549)(236129657087228)(192374486261705)(48057245064654)(148574349560750)(92977632026198);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(100000703101)(100105400095)(93006095)(93001095)(6041248)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123558100)(20161123562025)(20161123564025)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY4PR08MB3528; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY4PR08MB3528; 
x-forefront-prvs: 03524FBD26
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39400400002)(39450400003)(39850400002)(39840400002)(2906002)(33656002)(413944005)(7696004)(25786009)(3660700001)(6606003)(88552002)(189998001)(19627405001)(2900100001)(478600001)(5660300001)(74316002)(3280700002)(54896002)(77096006)(55016002)(6436002)(6506006)(38730400002)(99286003)(230783001)(9686003)(2501003)(450100002)(7736002)(50986999)(86362001)(54356999)(66066001)(53936002)(8676002)(8936002)(102836003)(6116002)(81166006)(3846002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR08MB3528; H:CY4PR08MB3526.namprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY4PR08MB352648AA55E5F4CCB1DF666491DD0CY4PR08MB3526namp_"
MIME-Version: 1.0
X-OriginatorOrg: yale.edu
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jun 2017 02:52:23.6827 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: dd8cbebb-2139-4df8-b411-4e3e87abeb5c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR08MB3528
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-27_16:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706280045
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/KPgl9PjU7PTHxv9ZHzYGOUQmFjE>
Subject: [alto] Review on draft-ietf-alto-xdom-disc-00 by Geng
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: Wed, 28 Jun 2017 02:53:43 -0000

--_000_CY4PR08MB352648AA55E5F4CCB1DF666491DD0CY4PR08MB3526namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Dear authors,


Your work is impressive, and here are some comments I have.


1. In 2nd paragraph of the abstract, =93it may be needed to discover an ALT=
O server outside=85=94, who is the =93it=94? Who is the initiator of the di=
scovery? It can be by the server or the client, corresponding to approach 2=
.1, 2.2 (by servers) and 2.4 (by clients) in section 1.1.1. What is the dif=
ference in protocol between these two initiators of the discovery?

2. What is the detailed algorithm for the reverse DNS lookup? Only the roug=
h procedure is given in the draft. However, considering that the searching =
space will be large, an optimized algorithm for speeding up is needed.

3. With regard to implementation, how to deploy the database and where to s=
tore the DNS information?

4. Suggestion. Some of the security issues can be solved by allocating diff=
erent DNS servers with different policies to the queries. In a result, for =
instance, operator =93A=94 can discover and get the information from the se=
rver of =93B=94, whereas =93B=94 can not discover =93A=94.

5. Does the protocol support successive discovery? For example, operator =
=93A=94 need the information from the server of =93C=94, but it can only di=
scover =93B=94, then =93B=94 will help =93A=94 to discover =93C=94, and rel=
ays the information to =93A=94.

6. In 2nd paragraph of the section 1.1.2, besides the legal liability, the =
synchronization between different servers is also an inevitable challenge. =
Non-ideal synchronization will lead to conflicts and other issues.

7. In the 1st paragraph of the section 1.3, =93a new registration administr=
ation authority would have to be established=94, but why is it a problem? T=
he reason is not well interpreted here.

8. With regard to the endpoint service (section 3.2), as for the destinatio=
n IP addresses, (D1, D2, D3, ...), what if the destinations are in differen=
t domains? Then will the server start another discovery for such new domain=
s?

  9. Language typos. The 1st sentence in the 1st paragraph of the section 2=
.3. The 2st sentence in the 1st paragraph of the section 3.3, =93ressources=
=94 =3D=3D> =93resources=94.



Hope these are helpful.


Best, Geng

Computer Science, Yale

--_000_CY4PR08MB352648AA55E5F4CCB1DF666491DD0CY4PR08MB3526namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" dir=3D"ltr" style=3D"font-size: 12pt; colo=
r: rgb(0, 0, 0); font-family: Calibri,Helvetica,sans-serif,&quot;EmojiFont&=
quot;,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;,NotoColorEmo=
ji,&quot;Segoe UI Symbol&quot;,&quot;Android Emoji&quot;,EmojiSymbols;">
<p>Dear authors,</p>
<p><br>
</p>
<p>Your work is impressive, and here are some comments I have.</p>
<p><br>
</p>
<p><span style=3D"font-size:10.5pt;mso-bidi-font-size:11.0pt;font-family:=
=0A=
&quot;Calibri&quot;,sans-serif;mso-ascii-theme-font:minor-latin;mso-fareast=
-font-family:=0A=
&#23435;&#20307;;mso-fareast-theme-font:minor-fareast;mso-hansi-theme-font:=
minor-latin;=0A=
mso-bidi-font-family:&quot;Times New Roman&quot;;mso-bidi-theme-font:minor-=
bidi;=0A=
mso-ansi-language:EN-US;mso-fareast-language:ZH-CN;mso-bidi-language:AR-SA"=
 lang=3D"EN-US"></p>
<div>1. In 2nd paragraph of the abstract, =93it may be needed to discover a=
n ALTO server outside=85=94, who is the =93it=94? Who is the initiator of t=
he discovery? It can be by the server or the client, corresponding to appro=
ach 2.1, 2.2 (by servers) and 2.4 (by clients)
 in section 1.1.1. What is the difference in protocol between these two ini=
tiators of the discovery?<br>
&nbsp;<br>
2. What is the detailed algorithm for the reverse DNS lookup? Only the roug=
h procedure is given in the draft. However, considering that the searching =
space will be large, an optimized algorithm for speeding up is needed.<br>
&nbsp;<br>
3. With regard to implementation, how to deploy the database and where to s=
tore the DNS information?<br>
&nbsp;<br>
4. Suggestion. Some of the security issues can be solved by allocating diff=
erent DNS servers with different policies to the queries. In a result, for =
instance, operator =93A=94 can discover and get the information from the se=
rver of =93B=94, whereas =93B=94 can not discover
 =93A=94.<br>
&nbsp;<br>
5. Does the protocol support successive discovery? For example, operator =
=93A=94 need the information from the server of =93C=94, but it can only di=
scover =93B=94, then =93B=94 will help =93A=94 to discover =93C=94, and rel=
ays the information to =93A=94.<br>
&nbsp;<br>
6. In 2nd paragraph of the section 1.1.2, besides the legal liability, the =
synchronization between different servers is also an inevitable challenge. =
Non-ideal synchronization will lead to conflicts and other issues.<br>
&nbsp;<br>
7. In the 1st paragraph of the section 1.3, =93a new registration administr=
ation authority would have to be established=94, but why is it a problem? T=
he reason is not well interpreted here.<br>
&nbsp;<br>
8. With regard to the endpoint service (section 3.2), as for the destinatio=
n IP addresses, (D1, D2, D3, ...), what if the destinations are in differen=
t domains? Then will the server start another discovery for such new domain=
s?<br>
&nbsp;<br>
&nbsp; 9. Language typos. The 1st sentence in the 1st paragraph of the sect=
ion 2.3. The 2st sentence in the 1st paragraph of the section 3.3, =93resso=
urces=94 =3D=3D&gt; =93resources=94.</div>
<br>
</span>
<p></p>
<p><br>
</p>
<p>Hope these are helpful.<br>
</p>
<p><br>
</p>
<p>Best, Geng</p>
<p>Computer Science, Yale <br>
</p>
</div>
</body>
</html>

--_000_CY4PR08MB352648AA55E5F4CCB1DF666491DD0CY4PR08MB3526namp_--


From nobody Tue Jun 27 22:02:24 2017
Return-Path: <geng.li@yale.edu>
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 D37AE12009C; Tue, 27 Jun 2017 22:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yale.edu
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 9xyCrjcMyAwA; Tue, 27 Jun 2017 22:02:20 -0700 (PDT)
Received: from mx0a-00135301.pphosted.com (mx0a-00135301.pphosted.com [67.231.145.237]) (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 3F83E1275C5; Tue, 27 Jun 2017 22:02:17 -0700 (PDT)
Received: from pps.filterd (m0109485.ppops.net [127.0.0.1]) by mx0b-00135301.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v5S4x0V9011544; Wed, 28 Jun 2017 01:02:15 -0400
Authentication-Results: ppops.net; spf=pass smtp.mailfrom=geng.li@yale.edu
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0052.outbound.protection.outlook.com [216.32.180.52]) by mx0b-00135301.pphosted.com with ESMTP id 2bbsqd1e17-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 28 Jun 2017 01:02:15 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=B/cLGO1XQItJvFILtcpGCq2GS9z5RUJHkt8hxjXTd6c=; b=F4UKqR5wK78qAcf9UJhkX1r6HyIYOn1Kl9NKhkgMnj0anHx+ZVhcjjAwG2qv95XLaQyxnvm/gU/x/CVQNbYU4Pw4Esnd9lQ3zuGectN/AUmU7hyOouRjPcAVfH9TncYXb8LbhNw2o/SQKhs275jd7x+CKluHTBZx/N2UumG2jjc=
Received: from DM5PR08MB3531.namprd08.prod.outlook.com (10.164.154.153) by DM5PR08MB3532.namprd08.prod.outlook.com (10.164.154.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.15; Wed, 28 Jun 2017 05:02:13 +0000
Received: from DM5PR08MB3531.namprd08.prod.outlook.com ([10.164.154.153]) by DM5PR08MB3531.namprd08.prod.outlook.com ([10.164.154.153]) with mapi id 15.01.1199.019; Wed, 28 Jun 2017 05:02:13 +0000
From: "Li, Geng" <geng.li@yale.edu>
To: "alto@ietf.org" <alto@ietf.org>, "draft-randriamasy-alto-cost-context@ietf.org" <draft-randriamasy-alto-cost-context@ietf.org>
Thread-Topic: Review on draft-randriamasy-alto-cost-context-01 by Geng
Thread-Index: AQHS78u03Vx/E/AmE0+5Ta1bITuj2g==
Date: Wed, 28 Jun 2017 05:02:13 +0000
Message-ID: <DM5PR08MB3531C6687BF468CD9F16939F91DD0@DM5PR08MB3531.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=yale.edu;
x-originating-ip: [130.132.173.199]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR08MB3532; 7:PsgxGUSZBC+AqcvSbk5RfJ4JccWVOwl3/q3wAlkYMAMt99X2iOa+Z1gasIdAONWZoWJAdPVJrdzwEE1hVWzVfd3TfYJMu0DlDdRXKpguzsHajbdpT0XINYI3F03DxRbGMmtID3B9p7yIOdFrKYhWz3hzulrzZk16tTyHNGww7IpQirBPykJ5zYQs4+1l78+i5+4Seb0figdbPl/o+0P2VfuEr37osFkWOrBfSOlX30zyqdH2E1Psmnu9CILia/mT96zyz7B15YAyw8j5MaXHk5406qdBwxR2oWxnP6jQmk/Ql1STc1fM5M8xlpZ3HUS5GCkH3yUBiJuclFBqgtsh7EPuDldzs1Um+/qflZzEdQogO5sA9m8nbIFCVqGeDsPHYBPddp9kt/7dqhsAWzumTSgRUFaygJgE7jpNNPMGnVJci/KOlgXNxP8VdbvGaZwFoyY6V82E6VRkSKUna/HgkJ3U+UnzV75DEgCwmSqE+gpXzPT1X/eUgr++et5GJXMmor8yucdhcoPMsekhnYiqdC05TNIy96xdoZzu8VWq/IAiPDfrQ8hp5BUHS22X8h7D8nYqYvEyf7gG3kJIdLRcpS54aCb7LmeSZzNYvFI1mrC08G8omn3xFRZmTbOWfGw65TH9k7+YYEa7Pos4TNjYdNT12SzITMczc+SnyyHbbnfkcRrAfl7OM4Cu/dvqlT+uNwZedga9fx/JcuNKSRp60cb7MVOPUt8SH3O7nmtXuHRG3ENVBvYtYvLeQJw9IQfdoWqDbjZ4hDiT19/+7UQD3se/vqdLejZhUwEHmwX9T44=
x-ms-office365-filtering-correlation-id: 07230546-17eb-4c0c-325d-08d4bde2d740
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095); SRVR:DM5PR08MB3532; 
x-ms-traffictypediagnostic: DM5PR08MB3532:
x-microsoft-antispam-prvs: <DM5PR08MB35320658890BC4071F8F00C391DD0@DM5PR08MB3532.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(133145235818549)(236129657087228)(48057245064654)(92977632026198)(158140799945019)(247924648384137);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(3002001)(6041248)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123564025)(20161123555025)(20161123562025)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM5PR08MB3532; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM5PR08MB3532; 
x-forefront-prvs: 03524FBD26
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39830400002)(39450400003)(39400400002)(8676002)(6606003)(81166006)(54356999)(5660300001)(189998001)(478600001)(7736002)(74316002)(3280700002)(3660700001)(230783001)(8936002)(88552002)(86362001)(2906002)(33656002)(413944005)(7696004)(6116002)(102836003)(54896002)(55016002)(6506006)(9686003)(99286003)(2501003)(450100002)(38730400002)(66066001)(6436002)(3846002)(25786009)(50986999)(77096006)(19627405001)(2900100001)(53936002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR08MB3532; H:DM5PR08MB3531.namprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR08MB3531C6687BF468CD9F16939F91DD0DM5PR08MB3531namp_"
MIME-Version: 1.0
X-OriginatorOrg: yale.edu
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jun 2017 05:02:13.6712 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: dd8cbebb-2139-4df8-b411-4e3e87abeb5c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR08MB3532
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-28_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706280081
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/jUyt3dC-yPyLGJGyeR20P7oAhHc>
Subject: [alto] Review on draft-randriamasy-alto-cost-context-01 by Geng
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: Wed, 28 Jun 2017 05:02:23 -0000

--_000_DM5PR08MB3531C6687BF468CD9F16939F91DD0DM5PR08MB3531namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Dear authors,


Your work is excellent, and here are some comments I have.

In the draft, to extend ALTO in cellular networks to support context based =
service is innovative and significant. In my view, Use Case 1 may face seve=
ral challenges before being applied, but Use Case 2 makes a lot of sense fo=
r the future mobile network.

In Use Case 1, the challenges to bring ALTO into wireless world can be conc=
luded as following.
1. The RF cost is hard to be measured for real-time services because only c=
onsidering the load is not enough. The wireless channel consists of larger =
scale fading and small scale fading, where the small scale fading (also cal=
led frequency-selective fading) is caused by multi-path effects and Doppler=
 effects. The transmission performance at different frequency points varies=
, which is why cellular networks adopt per-RB scheduling. To transmit the d=
elay sensitive data, the decisions for selecting cells by using the cost ma=
p may be not effective.
2. With regard to the =93unattended data=94 (UD), my understanding is that =
they are tailed for the =93context-aware=94 transmission, which is an impor=
tant topic for the next generation of mobile network to realize =93user cen=
tric=94 network. It is good, but I doubt that the amount of UD may be not a=
s much as you think. And the data is not mandatory and is delay tolerant, t=
herefore using another cell to transmit seems to be not that necessary.
3. The overhead of signaling to apply ALTO seems to be considerable. Such d=
ata should belong to the control plane and transmitted by the RRC (Radio Re=
source Control) container. Only the RRC establishment and re-configuration =
will trigger this transmission, and the control plane signals are designed =
to be as short and reliable as possible. But considering the data size for =
network map request/response and the interval for updating, the overhead ma=
y be relatively high.

In Use Case 2, the access-aware endpoint selection is more reasonable. The =
transportation (backbone) network and the Core Network (CN) are more stable=
 compared with the Radio Access Network (RAN), and they are more likely to =
be the bottleneck in today=92s mobile network. For example, for WiFi and LT=
E, when the conditions in RAN are similar, then the QoE is largely dependen=
t on the selection of accessed gateway to PDN, especially for some video st=
ream downloading service. The only challenge lies here is the technique for=
 =93Multi-RAT=94 coordination, which is also a big direction in 5G.

Issues:
1. In the 1st paragraph of section 2.1, when describing LAOC can be associa=
ted to several cells, it is needed to state that the control plane of LAOC =
is anchored at the serving cells, and all the signals are transmitted with =
the serving cells.
2. In the 1st paragraph of section 2.1, one can easily think of the =93Duel=
 Connectivity=94, which is supported in 3GPP and described as a UE can tran=
smit data with two cells at the same time, specifically with a macro cell a=
nd a small cell. But in this draft, it seems to be multi-connectivity, that=
 I don=92t think 3GPP supports.
3. In the 2nd paragraph of section 2.2, the words =93serving PGW=94 may con=
fuse the audience by another entity SGW. SGW (Serving Gateway) is the gatew=
ay which terminates the interface towards E-UTARN. For each UE associated w=
ith the EPS, at given point of time, there is a single Serving GW. The PGW =
is the gateway which terminates the SGi interface towards PDN. If UE is acc=
essing multiple PDNs, there may be more than one PGW for that UE. I assume =
the authors wanted to say PGW, but the words =93serving PGW=94 may bring mi=
sunderstanding.
4. In section 2.2, a UE can dynamically choose Wifi or LTE for transmission=
 according to the endpoint cost. One important element that the author need=
 to announce is the handover, i.e., how to execute the handover and how to =
make sure the data is not dropped when doing handover.
5. In the example of Use Case 1, I=92m curious about the data size for the =
cost map, say how many bits it will be roughly.
6. In the example of Use Case 2, I=92m curious about how to calculate the c=
ost value of WiFi and LTE. They are two RATs, and they all include both RAN=
 and backbone networks.

*Suggestion:
The concept of cost map continues to be used. However, according to the map=
, the decision is made by the base station or ALTO server instead of the UE=
.
In the draft, the procedure can be described as:
UE-->base station (query for the map)
base station-->UE (return the map)
UE-->base station (make the association decision)
base station-->UE (resource allocation signal for scheduling in PDCCH/PUCCH=
)
UE<-->base station (transmit data, both uplink or downlink)
My suggestion is to move the decider from UE to base station, and the stati=
on (or ALTO server) just return the final association result, then they can=
 start to transmit data. The procedure becomes:
UE-->base station (query for the map)
base station-->UE (make decision according to the map, then resource alloca=
tion signal for scheduling in PDCCH/PUCCH)
UE<-->base station (transmit data, both uplink or downlink)
In that case, there are two advantages. First, it can reduce the overhead a=
nd signal transmitting to realize ALTO; second, it can reduce the processin=
g load of UE.

Hope these are helpful.

Best, Geng
Computer Science, Yale



--_000_DM5PR08MB3531C6687BF468CD9F16939F91DD0DM5PR08MB3531namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" dir=3D"ltr" style=3D"font-size: 12pt; colo=
r: rgb(0, 0, 0); font-family: Calibri,Helvetica,sans-serif,&quot;EmojiFont&=
quot;,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;,NotoColorEmo=
ji,&quot;Segoe UI Symbol&quot;,&quot;Android Emoji&quot;,EmojiSymbols;">
<p></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Dear authors,</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Your work is excellent, and her=
e are some comments I have.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In the draft, to extend ALTO in=
 cellular networks to support context based service is innovative and signi=
ficant. In my view, Use Case 1 may face several challenges before being app=
lied, but Use Case 2 makes a lot of
 sense for the future mobile network.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In Use Case 1, the challenges t=
o bring ALTO into wireless world can be concluded as following.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">1. The RF cost is hard to be me=
asured for real-time services because only considering the load is not enou=
gh. The wireless channel consists of larger scale fading and small scale fa=
ding, where the small scale fading (also
 called frequency-selective fading) is caused by multi-path effects and Dop=
pler effects. The transmission performance at different frequency points va=
ries, which is why cellular networks adopt per-RB scheduling. To transmit t=
he delay sensitive data, the decisions
 for selecting cells by using the cost map may be not effective.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">2. With regard to the =93unatte=
nded data=94 (UD), my understanding is that they are tailed for the =93cont=
ext-aware=94 transmission, which is an important topic for the next generat=
ion of mobile network to realize =93user centric=94
 network. It is good, but I doubt that the amount of UD may be not as much =
as you think. And the data is not mandatory and is delay tolerant, therefor=
e using another cell to transmit seems to be not that necessary.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">3. The overhead of signaling to=
 apply ALTO seems to be considerable. Such data should belong to the contro=
l plane and transmitted by the RRC (Radio Resource Control) container. Only=
 the RRC establishment and re-configuration
 will trigger this transmission, and the control plane signals are designed=
 to be as short and reliable as possible. But considering the data size for=
 network map request/response and the interval for updating, the overhead m=
ay be relatively high.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In Use Case 2, the access-aware=
 endpoint selection is more reasonable. The transportation (backbone) netwo=
rk and the Core Network (CN) are more stable compared with the Radio Access=
 Network (RAN), and they are more likely
 to be the bottleneck in today=92s mobile network. For example, for WiFi an=
d LTE, when the conditions in RAN are similar, then the QoE is largely depe=
ndent on the selection of accessed gateway to PDN, especially for some vide=
o stream downloading service. The
 only challenge lies here is the technique for =93Multi-RAT=94 coordination=
, which is also a big direction in 5G.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Issues:</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">1. In the 1st paragraph of sect=
ion 2.1, when describing LAOC can be associated to several cells, it is nee=
ded to state that the control plane of LAOC is anchored at the serving cell=
s, and all the signals are transmitted
 with the serving cells.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">2. In the 1st paragraph of sect=
ion 2.1, one can easily think of the =93Duel Connectivity=94, which is supp=
orted in 3GPP and described as a UE can transmit data with two cells at the=
 same time, specifically with a macro cell
 and a small cell. But in this draft, it seems to be multi-connectivity, th=
at I don=92t think 3GPP supports.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">3. In the 2nd paragraph of sect=
ion 2.2, the words =93serving PGW=94 may confuse the audience by another en=
tity SGW. SGW (Serving&nbsp;Gateway)&nbsp;is the gateway which terminates t=
he interface towards E-UTARN. For each&nbsp;UE&nbsp;associated
 with the&nbsp;EPS, at given point of time, there is a single Serving&nbsp;=
GW.&nbsp;The PGW is the gateway which terminates the SGi interface towards =
PDN. If UE is accessing multiple PDNs, there may be more than one PGW for t=
hat UE. I assume the authors wanted to say PGW,
 but the words =93serving PGW=94 may bring misunderstanding.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">4. In section 2.2, a UE can dyn=
amically choose Wifi or LTE for transmission according to the endpoint cost=
. One important element that the author need to announce is the handover, i=
.e., how to execute the handover and
 how to make sure the data is not dropped when doing handover.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">5. In the example of Use Case 1=
, I=92m curious about the data size for the cost map, say how many bits it =
will be roughly.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">6. In the example of Use Case 2=
, I=92m curious about how to calculate the cost value of WiFi and LTE. They=
 are two RATs, and they all include both RAN and backbone networks.</span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><b>*Suggestion:</b></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The concept of cost map continu=
es to be used. However, according to the map, the decision is made by the b=
ase station or ALTO server instead of the UE.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In the draft, the procedure can=
 be described as:</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:10.5pt"><span lang=3D"EN-US">UE=
--&gt;base station (query for the map)</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:10.5pt"><span lang=3D"EN-US">ba=
se station--&gt;UE (return the map)</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:10.5pt"><span lang=3D"EN-US">UE=
--&gt;base station (make the association decision)</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:10.5pt"><span lang=3D"EN-US">ba=
se station--&gt;UE (resource allocation signal for scheduling in PDCCH/PUCC=
H)</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:10.5pt"><span lang=3D"EN-US">UE=
&lt;--&gt;base station (transmit data, both uplink or downlink)</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">My suggestion is to move the de=
cider from UE to base station, and the station (or ALTO server) just return=
 the final association result, then they can start to transmit data. The pr=
ocedure becomes:</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:10.5pt"><span lang=3D"EN-US">UE=
--&gt;base station (query for the map)</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:10.5pt"><span lang=3D"EN-US">ba=
se station--&gt;UE (make decision according to the map, then resource alloc=
ation signal for scheduling in PDCCH/PUCCH)</span></p>
<p class=3D"MsoNormal" style=3D"margin-left:10.5pt"><span lang=3D"EN-US">UE=
&lt;--&gt;base station (transmit data, both uplink or downlink)</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In that case, there are two adv=
antages. First, it can reduce the overhead and signal transmitting to reali=
ze ALTO; second, it can reduce the processing load of UE.</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hope these are helpful.</span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best, Geng</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Computer Science, Yale </span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;</span></p>
</div>
<br>
<p></p>
</div>
</body>
</html>

--_000_DM5PR08MB3531C6687BF468CD9F16939F91DD0DM5PR08MB3531namp_--


From nobody Wed Jun 28 06:09:10 2017
Return-Path: <xiangq27@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 29CFB126CD8; Wed, 28 Jun 2017 06:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 e3-wP5ciFAZa; Wed, 28 Jun 2017 06:09:02 -0700 (PDT)
Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (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 BBD7E127868; Wed, 28 Jun 2017 06:09:01 -0700 (PDT)
Received: by mail-yw0-x232.google.com with SMTP id l21so15530018ywb.1; Wed, 28 Jun 2017 06:09:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=X4P+NW0GL1zoiECzGJIVcqFANzGkc2Pxdq384MIJwr4=; b=VvxMTwpFmGZghzosPwk+t4Op4U4JGIqDNAa46+GDRHf+JL4JDOXfz27JOwDDS5o8zU jdbaUKEkPw6juSmJPQ8JIUt7OaEMbCAYtofmpjVLqvDWOd0SQQiT98WiJ/fimNAL5YH3 zV9wV+rxVcIgoRXogs5OIAnAyPEGtY1+rUkZwF6LyeQcjybfGXx3CwTdzFbd3W5DlXS2 SFeEbNjOAAKeJKMTuw9cjYnEbTfOY13A8WVgally3TCaS3z6JnOscjWph+0hGpf7pvHa graRoGcUCiEvf13+WCBy7gNMFhytmtEr5Hi/DOpmBusdn8UuP/S3Gee2wB2kwpUhDoxe kpSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=X4P+NW0GL1zoiECzGJIVcqFANzGkc2Pxdq384MIJwr4=; b=Lnz+OgINzgEv3L/kyuRZTSjDDMJ3IMbPfusGU3htG0JTIoEkx9ATo18vI45RQQgWw0 LBR0IffQOd9ye5mfq2xLi+kCfGkB0QBtCNBFKrAMIPHYW5Mco/oPfMi2lKOeC6fVVBXF vseH6DXvPrF8BLlDV3p828n2sfHKZv5LenExS8tUGaNIKc/IuFsyoy6gdnfxufmagzVw QFfsnmqD+8xrbqwrQl1Qrjnl1/R0WstE339uolRwOylXB+AmmOw28qiDrXHGJ+iW0qtZ e+ok2kbPKQWud4uPq4buxf0NW1vjNw2x6m6GJFpAEuygqImA5LKgrNTiVjk6ugEmZkRi TJCA==
X-Gm-Message-State: AKS2vOwyw4kEpi5P3UX6wmBgoNu1VHsT2GKbdVcnscd10uVF3mh2coho oBsGPmEGfZWmgy/FHQxyz7Zum2WLmueX
X-Received: by 10.129.91.85 with SMTP id p82mr8230552ywb.201.1498655340444; Wed, 28 Jun 2017 06:09:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.50.137 with HTTP; Wed, 28 Jun 2017 06:08:39 -0700 (PDT)
In-Reply-To: <CAKRjQSDOPoiWW_HCyawv34bkiN4H2y749i3vTCOc=3ngyyhaow@mail.gmail.com>
References: <CAKRjQSDOPoiWW_HCyawv34bkiN4H2y749i3vTCOc=3ngyyhaow@mail.gmail.com>
From: Qiao Xiang <xiangq27@gmail.com>
Date: Wed, 28 Jun 2017 21:08:39 +0800
Message-ID: <CAOB1xS_3GD1p7_qkEfwBGQ131xLNQB+Njg6=4tZx_sMNo_52Hg@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>, draft-roome-alto-unified-props-new@ietf.org
Content-Type: multipart/alternative; boundary="001a114c887a3546e4055304e3b1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/7242smnRjMSbpAzBAZVmEgY0v7E>
Subject: Re: [alto] Review of draft-roome-alto-unified-props-new-00
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: Wed, 28 Jun 2017 13:09:07 -0000

--001a114c887a3546e4055304e3b1
Content-Type: text/plain; charset="UTF-8"

Hi Wendy, Richard and all,

I reviewed the unified property map draft. I agree with
all Shenshen's comments. In addition, please see my other comments in the
following.

In addition to the review, the key design questions I want to raise
discussions are (1) how does property map handle dynamic entity, e.g., ane
defined in the path-vector draft? (2) is the inheritance design in the
property map draft too rigid? (see my comments marked with <QX??>) and (3)
in the current path vector draft the ane is defined with no inheritance or
hierarchy, but aggregating/compressing multiple ane's is an important
process for the path vector service to reduce overhead and provide privacy
of networks. how should we modify/improve the designs of both path vector
and property map to make the whole solution a unified one. I will work on
these three questions in the next few days and share my thoughts.
Menawhile, would you please also share any comments/thoughts you may have?
Thank you very much.


*Reviews:*
*Page 4*

   This document proposes a new approach to ALTO properties.
*<QX> "approach to ALTO properties" -> "approach to retrieve ALTO
properties"*

   Specifically, it defines two new resource types, namely Property Maps
   and Filtered Property Maps.  The former are GET-mode resources which
   return the property values for all entities in a domain, and are
   analogous the ALTO's Network Map and Cost Map resources.  The latter
*<QX> "analogous the ALTO's " -> "analogous to the ALTO's "*

   are POST-mode resources which return the values for a set of
   properties and entities requested by the client, and are analogous to
*<QX> "the values for a set of properties and entities" -> "the values of a
set of properties for a set of entities"*

   ALTO's Filtered Network Maps and Filtered Cost Maps.

*Page 5*

   The format of the second part of an entity address depends on the
   domain, and must be specified when registering a new domain.
*<QX> "must" -> "MUST"*

   Addresses may be hierarchical, and properties may be inherited based
   on that hierarchy.  Again, the rules defining any hierarchy or
   inheritance must be defined when the domain is registered.
*<QX> "must" -> "MUST"*

   Note that entity addresses do NOT have a unique textual
   representation.  For example, the strings "ipv6:2001:db8::1" and
   "ipv6:2001:db8:0:0:0:0:0:1" refer to the same entity.
*<QX> "NOT" is not defined in RFC2119. "do NOT have a unique" -> "MAY have
different"*

   ...

   Domain names must be registered with the IANA, and the format of the
   entity addresses in that domain, as well as any hierarchical or
   inheritance rules for those entities, must be specified at the same
   time.
*<QX> "must"->"MUST"*

   ...

   Property names are not specific to a domain, although some properties
   may only be applicable for particular domains, and the interpretation
   of the value may depend on the domain.  For example, suppose the
   "geo-location" property is defined as the coordinates of a point,
   encoded as (say) "latitude longitude [altitude]."  When applied to an
*<QX> "as (say)" -> "as"*

*Page 6*

   ...

   [RFC7285] recognizes that some properties may be specific to another
   ALTO resource, such as a network map.  Accordingly [RFC7285] defines
   the concept of "resource-specific endpoint properties"
   (Section 10.8.1), and indicates that dependency by prefixing the
   property name with the ID of the resource on which it depends.  That
   document defines one resource-specific property, namely the "pid"
   property, whose value is the name of the name of the PID containing
*<QX> "the name of the name of the PID" -> "the name of the PID"*

   that endpoint in the associated network map.

   ...
   According to [RFC7285], an ALTO server with two network maps, with
*<QX> "an ALTO server" -> "a legacy ALTO server"*

*Page 7*

3.1.  Internet Address Domains

   The domain of internet addresses consists of two domains (IPv4 and
   IPv6).  Both domains include individual addresses and blocks of
   addresses.
*<QX> After reading the beginning of Sec 3.2, I feel that Section 3.1
should add a sentence like "this domain does not have to depend on an ALTO
network map resource." in the beginning.*

3.1.1.  IPV4 Domain
*<QX> "IPV4" -> "IPv4"*

   ...
   For the purpose of defining properties, an individual internet
   address and the corresponding full-length prefix are considered
   aliases for the same entity.  Thus "ipv4:192.0.2.0" and
   "ipv4:192.0.2.0/32" are equivalent, and have the same set of
   properties, as are "ipv6:2001:db8::" and "ipv6:2001:db8::/128".
*<QX> remove ", as are "ipv6:2001:db8::" and "ipv6:2001:db8::/128" because
this section is about IPv4 domain.*

3.1.2.  IPV6 Domain
*<QX> "IPV6" -> "IPv6"*

    ...
3.1.2.2.  Domain-Specific Entity Addresses

   ...
   For the purpose of defining properties, an individual internet
   address and the corresponding 128-bit prefix are considered aliases
   for the same entity.  That is, "ipv6:2001:db8::1" and
   "ipv:2001:db8::1/128" are equivalent, and have the same set of
   properties.
*<QX> "ipv:2001:db8::1/128" -> "ipv6:2001:db8::1/128"*

*Page 8*

   ...
   Then the following entities have the indicated values:

          ipv4:192.0.2.0:    P=v4
          ipv4:192.0.2.1:    P=v3
          ipv4:192.0.2.16:   P=v2
*<QX> "ipv4:192.0.2.16 <http://192.0.2.16>:   P=v2" -> "ipv4:192.0.2.16
<http://192.0.2.16>:   P=v1", if we want an example of P=v2, we can use
"ipv4:192.0.2.8 <http://192.0.2.8>:   P=v2"*

          ipv4:192.0.2.32:   P=v1
          ipv4:192.0.2.64:   (not defined)
          ipv4:192.0.2.0/32: P=v4
          ipv4:192.0.2.0/31: P=v3
          ipv4:192.0.2.0/29: P=v2
          ipv4:192.0.2.0/27: P=v1
          ipv4:192.0.2.0/25: (not defined)

                         Inherited Property Values
    ...
3.3.  Internet Address Properties vs. PID Properties

   ...

   For example, because internet addresses are allocated to server
*<QX> "server" -> "service"*

*Page 10*

4.  Property Map Resource

   A Property Map returns the properties defined for all entities in one
   of more domains.
*<QX> "of more" -> "or more"*

   ...

*Page 11*

   For each entity in the Property Map, the ALTO Server returns the
   value defined for each of the properties specified in this resource's
   "capabilities" list.  For efficiency, the ALTO Server SHOULD omit
   property values that are inherited rather than explicitly defined; if
   a client needs inherited values, the client SHOULD use the domain's
   inheritance rules to deduce those values.
*<QX??> in the current draft, inheritance is defined in an all-or-nothing
form. Either a domain allows inheritance or it does not. Since the
computation of a property is up to the implementation, shouldn't we let the
implementation decide how properties are inherited from a larger block to a
smaller block of entities? Consider the example in Section 7.6, the current
draft seems to tell the admin: either you come up with a better property
map stored in the ALTO server to avoid failed/inaccurate query, or there is
zero flexibility for you to compute or update property map on demand. My
feeling is this may not be the right way... *

*Page 12*

    ...
5.2.  HTTP Method

   An ALTO Property Map resource is requested using the HTTP POST
   method.
*<QX> "an ALTO Property Map" -> "an ALTO Filtered Property Map"*


*Page 13*

5.6.  Response

   The response is the same as for the property map (Section 4.6),
*<QX> "property map" -> "Property Map"*

   except that it only includes the entities and properties requested by
   the client.

   Also, the Filtered Property Map response MUST include all inherited
   property values for the specified entities (unlike the Full Property
*<QX> "Full" -> "full", since Full Property Map is not a term defined in
this document.*

   Map, the Filtered Property Map response does not include enough
   information for the client to calculate the inherited values).

6.  Impact On Legacy Servers And Clients
*<QX> "Legacy Servers And Clients" -> "Legacy ALTO Servers And ALTO
Clients"*

6.1.  Impact on Endpoint Property Service

   The property maps defined in this document provide the same
*<QX> "property maps" -> "Property Map"*

   functionality as the Endpoint Property Service (EPS) defined in
   Section 11.4 of [RFC7285].  Accordingly, it is RECOMMENDED that the
   EPS be deprecated in favor of property maps.  However, ALTO servers
*<QX> "property maps" -> "Property Map"*

   MAY provide an EPS for the benefit of legacy clients.

*Page 14*

   ...
   However, when used with property maps, this document amends the
*<QX> "property maps" -> "Property Map"*

   definition of the "pid" property as follows.

   First, the name of the property is simply "pid"; the name is not
   prefixed with the resource ID of a network map.  The "uses"
   capability of the property map resource indicates the associated
   network map.  This implies that a property map can only return the
   "pid" property for one network map; if an ALTO server provides
   several network maps, it must provide a property map resource for
   each one.
*<QX> "must provide" -> "MUST provide"*


*Page 15*

    ...
    7.3.  Information Resource Directory (IRD)

   ...
   The Property Maps for the "ISP", "ASN", "country" and "state"
*<QX> "Property Maps" -> "Filtered Property Map"*

   properties do not depend on the default network map (they do not have
*<QX> "do not depend on the default network map (they do not have" ->*
*     "does not depend on the default network map (it does not have"*

*Page 18*

    ...
7.6.  Filtered Property Map Example #2

   ...
   Also note the "ASN" property has the value "12345" for both the
   blocks "ipv4:192.0.2.0/28" and "ipv4:192.0.2.16/28", so every address
   in the block "ipv4:192.0.2.0/27" has that property value.  However
   the block "ipv4:192.0.2.0/27" itself does not have a value for "ASN":
   address blocks cannot inherit properties from blocks with longer
   prefixes, even if every such block has the same value.
*<QX> This is a very good example. Please see my comments makred in <QX??>
for page 11. And if we eventually insist the all-or-nothing inheritance
design, it would make the inheritance of properties much clearer to readers
if we use it in Section 3.1.3, instead of explaining the reasons here.*

*Page 19*

7.7.  Filtered Property Map Example #3

   ...
   Note that the value of "pid" for the prefix "ipv4:10.0.0.0/15" is
   "pid1", even though all addresses in that block are in "pid2",
   because "ipv4:10.0.0.0/8" is the longest prefix in the network map
   which prefix-matches "ipv4:10.0.0.0/15", and that prefix is in
   "pid1".
*<QX> I agree with Shenzhen's comments. 10.0.0.0/XX <http://10.0.0.0/XX> is
inconsistent with the settings in Section 7.1. It should be fixed in the
next version.*

*Page 21*

   Also, while technically this document does not introduce any security
   risks not inherent in the Endpoint Property Service defined by
   [RFC7285], the GET-mode property map resource defined in this
   document does make it easier for a client to download large numbers
   of property values.  Accordingly, an ALTO Server should limit GET-
   mode property maps for to properties which do not contain sensitive
   data.
*<QX> "for to properties" -> "to properties"*

9.1.  application/alto-* Media Types
   ...
   Security considerations:  Security considerations relating to the
*<QX> "relating" -> "related"*

      generation and consumption of ALTO Protocol messages are discussed
      in Section 15 of [RFC7285].

   Interoperability considerations:  This document specifies format of
*<QX> "format" -> "formats"*


On Mon, Jun 26, 2017 at 11:58 PM, Shenshen Chen <cs90911@gmail.com> wrote:

> Dear authors of alto-unified-props and all,
>
> In section 2.5, I feel "property type" could be better (because RFC7285
> names
> sections using "property type", but not "property name") and "property
> value"
> should be mentioned (includes the "null" value mentioned in section 4.6).
> I also suggest showing the "null" value can be inherited explicitly
> in the section 3.1.3 or emphasizing it as a normal property value.
>
> Here is a list of typos (comments are marked with ">>>"):
>
> [Page 2]
>        3.1.3.  Heirarchy And Inheritance . . . . . . . . . . . . . .   7
>        3.1.4.  Relationship To Network Maps  . . . . . . . . . . . .   8
>      3.2.  PID Domain  . . . . . . . . . . . . . . . . . . . . . . .   9
>        3.2.1.  Domain Name . . . . . . . . . . . . . . . . . . . . .   9
>        3.2.2.  Domain-Specific Entity Addresses  . . . . . . . . . .   9
>        3.2.3.  Heirarchy And Inheritance . . . . . . . . . . . . . .   9
>        3.2.4.  Relationship To Internet Addresses Domains  . . . . .   9
>
> >>> "To" => "to", "And" => "and", "Heirarchy" => "Hierarchy"
>
>
> [Page 3]
>    Second, the EPS is only defined as a POST-mode service.  Clients must
>    request the properties for an explicit set of addresses.  By
>    contrast, [RFC7285] defines a GET-mode Cost Map resource which
>    returns all available costs, so a client can get the full set of
>    costs once, and then lookup costs without querying the ALTO server.
>    RFC7285 does not define an equivalent service for endpoint
>    properties.  Granted, it is not be practical to enumerate the
>
> >>> "is not be" => "is not"
>
>
> [Page 4]
>    This document proposes a new approach to ALTO properties.
>    Specifically, it defines two new resource types, namely Property Maps
>    and Filtered Property Maps.  The former are GET-mode resources which
>    return the property values for all entities in a domain, and are
>    analogous the ALTO's Network Map and Cost Map resources.  The latter
>
> >>> "Network Map and Cost Map resources" => "Network Maps and Cost Maps"
>     I think it should keep the same format with "Filtered Network Maps
>     and Filtered Cost Maps" in the last sentence of this paragraph.
>
>    are POST-mode resources which return the values for a set of
>    properties and entities requested by the client, and are analogous to
>    ALTO's Filtered Network Maps and Filtered Cost Maps.
>
> [Page 7]
> 3.1.3.  Heirarchy And Inheritance
>
> [Page 9]
> 3.2.3.  Heirarchy And Inheritance
>
> >>> "Heirarchy" => "Hierarchy"
>
> [Page 19]
>    Note that the value of "pid" for the prefix "ipv4:10.0.0.0/15" is
>    "pid1", even though all addresses in that block are in "pid2",
>    because "ipv4:10.0.0.0/8" is the longest prefix in the network map
>    which prefix-matches "ipv4:10.0.0.0/15", and that prefix is in
>    "pid1".
>
>    POST /propmap/lookup/pid HTTP/1.1
>    Host: alto.example.com
>    Accept: application/alto-propmap+json,application/alto-error+json
>    Content-Length: ###
>    Content-Type: application/alto-propmapparams+json
>
>    {
>      "entities" : [
>                    "ipv4:192.0.2.0  10.0.0.0",
>                    "ipv4:192.0.2.16 10.1.0.0",
>                    "ipv4:192.0.2.64  10.3.0.0",
>                    "ipv4:192.0.2.128  11.0.0.0",
>                    "ipv4:192.0.2.0/26 10.0.0.0/15",
>                    "ipv4:192.0.2.0/30 10.0.0.0/17" ],
>      "properties" : [ "pid" ]
>    }
>
> >>> This part should be modified into:
>
>    Note that the value of "pid" for the prefix "ipv4:192.0.2.0/26" is
>    "pid1", even though all addresses in that block are in "pid2",
>    because "ipv4:192.0.2.0/25" is the longest prefix in the network map
>    which prefix-matches "ipv4:192.0.2.0/26", and that prefix is in
>    "pid1".
>
>    POST /propmap/lookup/pid HTTP/1.1
>    Host: alto.example.com
>    Accept: application/alto-propmap+json,application/alto-error+json
>    Content-Length: ###
>    Content-Type: application/alto-propmapparams+json
>
>    {
>      "entities" : [
>                    "ipv4:192.0.2.0",
>                    "ipv4:192.0.2.16",
>                    "ipv4:192.0.2.64",
>                    "ipv4:192.0.2.128",
>                    "ipv4:192.0.2.0/26",
>                    "ipv4:192.0.2.0/30" ],
>      "properties" : [ "pid" ]
>    }
>
> [Page 23]
>    New ALTO entity domains are assigned after IETF Review [RFC5226] to
>    ensure that proper documentation regarding the new ALTO entity
>    domains and their security considerations has been provided.  RFCs
>
> >>> "has been" => "have been"
>
>    defining new entity domains should indicate how an entity in a
>    registered domain is encoded as an EntityName, and, if applicable,
>    the rules defining the entity hierarchy and property inheritance.
>    Updates and deletions of ALTO entity domains follow the same
>    procedure.
>
>
> Best Regards,
> Shenshen
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>


-- 
Qiao Xiang
Postdoctoral Fellow,
Department of Computer Science,
Yale University

--001a114c887a3546e4055304e3b1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Wendy, Richard and all,<div><br></div><div>I reviewed t=
he unified property map draft. I agree with all=C2=A0Shenshen&#39;s=C2=A0co=
mments. In addition, please see my other comments in the following.</div><d=
iv><br></div><div>In addition to the review, the key design=C2=A0questions =
I want to raise discussions are (1) how does property map handle dynamic en=
tity, e.g., ane defined in the path-vector draft? (2) is the inheritance de=
sign in the property map draft too rigid? (see my comments marked with &lt;=
QX??&gt;) and (3) in the current path vector draft the ane is defined with =
no inheritance or hierarchy, but aggregating/compressing multiple ane&#39;s=
 is an important process for the path vector service to reduce overhead and=
 provide privacy of networks. how should we modify/improve the designs of b=
oth path vector and property map to make the whole solution a unified one. =
I will work on these three questions in the next few days and share my thou=
ghts. Menawhile, would you please also share any comments/thoughts you may =
have? Thank you very much.</div><div><br></div><div><br></div><div><b>Revie=
ws:</b></div><div><div><b>Page 4</b></div><div><br></div><div>=C2=A0 =C2=A0=
This document proposes a new approach to ALTO properties.</div><div><b>&lt;=
QX&gt; &quot;approach to ALTO properties&quot; -&gt; &quot;approach to retr=
ieve ALTO properties&quot;</b></div><div><br></div><div>=C2=A0 =C2=A0Specif=
ically, it defines two new resource types, namely Property Maps</div><div>=
=C2=A0 =C2=A0and Filtered Property Maps.=C2=A0 The former are GET-mode reso=
urces which</div><div>=C2=A0 =C2=A0return the property values for all entit=
ies in a domain, and are</div><div>=C2=A0 =C2=A0analogous the ALTO&#39;s Ne=
twork Map and Cost Map resources.=C2=A0 The latter</div><div><b>&lt;QX&gt; =
&quot;analogous the ALTO&#39;s &quot; -&gt; &quot;analogous to the ALTO&#39=
;s &quot;</b></div><div><br></div><div>=C2=A0 =C2=A0are POST-mode resources=
 which return the values for a set of</div><div>=C2=A0 =C2=A0properties and=
 entities requested by the client, and are analogous to</div><div><b>&lt;QX=
&gt; &quot;the values for a set of properties and entities&quot; -&gt; &quo=
t;the values of a set of properties for a set of entities&quot;</b></div><d=
iv><br></div><div>=C2=A0 =C2=A0ALTO&#39;s Filtered Network Maps and Filtere=
d Cost Maps.</div><div><br></div><div><b>Page 5</b></div><div>=C2=A0 =C2=A0=
</div><div>=C2=A0 =C2=A0The format of the second part of an entity address =
depends on the</div><div>=C2=A0 =C2=A0domain, and must be specified when re=
gistering a new domain.</div><div><b>&lt;QX&gt; &quot;must&quot; -&gt; &quo=
t;MUST&quot;</b></div><div><br></div><div>=C2=A0 =C2=A0Addresses may be hie=
rarchical, and properties may be inherited based</div><div>=C2=A0 =C2=A0on =
that hierarchy.=C2=A0 Again, the rules defining any hierarchy or</div><div>=
=C2=A0 =C2=A0inheritance must be defined when the domain is registered.</di=
v><div><b>&lt;QX&gt; &quot;must&quot; -&gt; &quot;MUST&quot;</b></div><div>=
<br></div><div>=C2=A0 =C2=A0Note that entity addresses do NOT have a unique=
 textual</div><div>=C2=A0 =C2=A0representation.=C2=A0 For example, the stri=
ngs &quot;ipv6:2001:db8::1&quot; and</div><div>=C2=A0 =C2=A0&quot;ipv6:2001=
:db8:0:0:0:0:0:1&quot; refer to the same entity.</div><div><b>&lt;QX&gt; &q=
uot;NOT&quot; is not defined in RFC2119. &quot;do NOT have a unique&quot; -=
&gt; &quot;MAY have different&quot;</b></div><div><br></div><div>=C2=A0 =C2=
=A0...</div><div><br></div><div>=C2=A0 =C2=A0Domain names must be registere=
d with the IANA, and the format of the</div><div>=C2=A0 =C2=A0entity addres=
ses in that domain, as well as any hierarchical or</div><div>=C2=A0 =C2=A0i=
nheritance rules for those entities, must be specified at the same</div><di=
v>=C2=A0 =C2=A0time.</div><div><b>&lt;QX&gt; &quot;must&quot;-&gt;&quot;MUS=
T&quot;</b></div><div><br></div><div>=C2=A0 =C2=A0...</div><div><br></div><=
div>=C2=A0 =C2=A0Property names are not specific to a domain, although some=
 properties</div><div>=C2=A0 =C2=A0may only be applicable for particular do=
mains, and the interpretation</div><div>=C2=A0 =C2=A0of the value may depen=
d on the domain.=C2=A0 For example, suppose the</div><div>=C2=A0 =C2=A0&quo=
t;geo-location&quot; property is defined as the coordinates of a point,</di=
v><div>=C2=A0 =C2=A0encoded as (say) &quot;latitude longitude [altitude].&q=
uot; =C2=A0When applied to an</div><div><b>&lt;QX&gt; &quot;as (say)&quot; =
-&gt; &quot;as&quot;</b></div><div><br></div><div><b>Page 6</b></div><div>=
=C2=A0 =C2=A0</div><div>=C2=A0 =C2=A0...</div><div><br></div><div>=C2=A0 =
=C2=A0[RFC7285] recognizes that some properties may be specific to another<=
/div><div>=C2=A0 =C2=A0ALTO resource, such as a network map.=C2=A0 Accordin=
gly [RFC7285] defines</div><div>=C2=A0 =C2=A0the concept of &quot;resource-=
specific endpoint properties&quot;</div><div>=C2=A0 =C2=A0(Section 10.8.1),=
 and indicates that dependency by prefixing the</div><div>=C2=A0 =C2=A0prop=
erty name with the ID of the resource on which it depends.=C2=A0 That</div>=
<div>=C2=A0 =C2=A0document defines one resource-specific property, namely t=
he &quot;pid&quot;</div><div>=C2=A0 =C2=A0property, whose value is the name=
 of the name of the PID containing</div><div><b>&lt;QX&gt; &quot;the name o=
f the name of the PID&quot; -&gt; &quot;the name of the PID&quot;</b></div>=
<div><br></div><div>=C2=A0 =C2=A0that endpoint in the associated network ma=
p.</div><div><br></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0 =C2=A0Accordi=
ng to [RFC7285], an ALTO server with two network maps, with</div><div><b>&l=
t;QX&gt; &quot;an ALTO server&quot; -&gt; &quot;a legacy ALTO server&quot;<=
/b></div><div><br></div><div><b>Page 7</b></div><div>=C2=A0 =C2=A0</div><di=
v>3.1.=C2=A0 Internet Address Domains</div><div><br></div><div>=C2=A0 =C2=
=A0The domain of internet addresses consists of two domains (IPv4 and</div>=
<div>=C2=A0 =C2=A0IPv6).=C2=A0 Both domains include individual addresses an=
d blocks of</div><div>=C2=A0 =C2=A0addresses.</div><div><b>&lt;QX&gt; After=
 reading the beginning of Sec 3.2, I feel that Section 3.1 should add a sen=
tence like &quot;this domain does not have to depend on an ALTO network map=
 resource.&quot; in the beginning.</b></div><div><br></div><div>3.1.1.=C2=
=A0 IPV4 Domain</div><div><b>&lt;QX&gt; &quot;IPV4&quot; -&gt; &quot;IPv4&q=
uot;</b></div><div><br></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0 =C2=A0F=
or the purpose of defining properties, an individual internet</div><div>=C2=
=A0 =C2=A0address and the corresponding full-length prefix are considered</=
div><div>=C2=A0 =C2=A0aliases for the same entity.=C2=A0 Thus &quot;ipv4:19=
2.0.2.0&quot; and</div><div>=C2=A0 =C2=A0&quot;ipv4:<a href=3D"http://192.0=
.2.0/32">192.0.2.0/32</a>&quot; are equivalent, and have the same set of</d=
iv><div>=C2=A0 =C2=A0properties, as are &quot;ipv6:2001:db8::&quot; and &qu=
ot;ipv6:2001:db8::/128&quot;.</div><div><b>&lt;QX&gt; remove &quot;, as are=
 &quot;ipv6:2001:db8::&quot; and &quot;ipv6:2001:db8::/128&quot; because th=
is section is about IPv4 domain.</b></div><div><br></div><div>3.1.2.=C2=A0 =
IPV6 Domain</div><div><b>&lt;QX&gt; &quot;IPV6&quot; -&gt; &quot;IPv6&quot;=
</b></div><div><br></div><div>=C2=A0 =C2=A0 ...</div><div>3.1.2.2.=C2=A0 Do=
main-Specific Entity Addresses</div><div><br></div><div>=C2=A0 =C2=A0...</d=
iv><div>=C2=A0 =C2=A0For the purpose of defining properties, an individual =
internet</div><div>=C2=A0 =C2=A0address and the corresponding 128-bit prefi=
x are considered aliases</div><div>=C2=A0 =C2=A0for the same entity.=C2=A0 =
That is, &quot;ipv6:2001:db8::1&quot; and</div><div>=C2=A0 =C2=A0&quot;ipv:=
2001:db8::1/128&quot; are equivalent, and have the same set of</div><div>=
=C2=A0 =C2=A0properties.</div><div><b>&lt;QX&gt; &quot;ipv:2001:db8::1/128&=
quot; -&gt; &quot;ipv6:2001:db8::1/128&quot;</b></div><div><br></div><div><=
b>Page 8</b></div><div><br></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0=C2=
=A0 Then the following entities have the indicated values:<br></div><div><b=
r></div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http://192.=
0.2.0">192.0.2.0</a>: =C2=A0 =C2=A0P=3Dv4</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 ipv4:<a href=3D"http://192.0.2.1">192.0.2.1</a>: =C2=A0 =C2=
=A0P=3Dv3</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http=
://192.0.2.16">192.0.2.16</a>: =C2=A0 P=3Dv2</div><div><b>&lt;QX&gt; &quot;=
ipv4:<a href=3D"http://192.0.2.16">192.0.2.16</a>: =C2=A0 P=3Dv2&quot; -&gt=
; &quot;ipv4:<a href=3D"http://192.0.2.16">192.0.2.16</a>: =C2=A0 P=3Dv1&qu=
ot;, if we want an example of P=3Dv2, we can use &quot;ipv4:<a href=3D"http=
://192.0.2.8">192.0.2.8</a>: =C2=A0 P=3Dv2&quot;</b></div><div><br></div><d=
iv>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http://192.0.2.32">19=
2.0.2.32</a>: =C2=A0 P=3Dv1</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ip=
v4:<a href=3D"http://192.0.2.64">192.0.2.64</a>: =C2=A0 (not defined)</div>=
<div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http://192.0.2.0/32=
">192.0.2.0/32</a>: P=3Dv4</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv=
4:<a href=3D"http://192.0.2.0/31">192.0.2.0/31</a>: P=3Dv3</div><div>=C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http://192.0.2.0/29">192.0.2.0=
/29</a>: P=3Dv2</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=
=3D"http://192.0.2.0/27">192.0.2.0/27</a>: P=3Dv1</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http://192.0.2.0/25">192.0.2.0/25</a>:=
 (not defined)</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Inherited Property V=
alues</div><div>=C2=A0 =C2=A0 ...</div><div>3.3.=C2=A0 Internet Address Pro=
perties vs. PID Properties<br></div><div><br></div><div>=C2=A0 =C2=A0...</d=
iv><div><br></div><div>=C2=A0 =C2=A0For example, because internet addresses=
 are allocated to server</div><div><b>&lt;QX&gt; &quot;server&quot; -&gt; &=
quot;service&quot;</b></div><div><br></div><div><b>Page 10</b></div><div><b=
r></div><div>4.=C2=A0 Property Map Resource</div><div><br></div><div>=C2=A0=
 =C2=A0A Property Map returns the properties defined for all entities in on=
e</div><div>=C2=A0 =C2=A0of more domains.</div><div><b>&lt;QX&gt; &quot;of =
more&quot; -&gt; &quot;or more&quot;</b></div><div><br></div><div>=C2=A0 =
=C2=A0...</div><div><br></div><div><b>Page 11</b></div><div><br></div><div>=
=C2=A0 =C2=A0For each entity in the Property Map, the ALTO Server returns t=
he</div><div>=C2=A0 =C2=A0value defined for each of the properties specifie=
d in this resource&#39;s</div><div>=C2=A0 =C2=A0&quot;capabilities&quot; li=
st.=C2=A0 For efficiency, the ALTO Server SHOULD omit</div><div>=C2=A0 =C2=
=A0property values that are inherited rather than explicitly defined; if</d=
iv><div>=C2=A0 =C2=A0a client needs inherited values, the client SHOULD use=
 the domain&#39;s</div><div>=C2=A0 =C2=A0inheritance rules to deduce those =
values.</div><div><b>&lt;QX??&gt; in the current draft, inheritance is defi=
ned in an all-or-nothing form. Either a domain allows inheritance or it doe=
s not. Since the computation of a property is up to the implementation, sho=
uldn&#39;t we let the implementation decide how properties are inherited fr=
om a larger block to a smaller block of entities? Consider the example in S=
ection 7.6, the current draft seems to tell the admin: either you come up w=
ith a better property map stored in the ALTO server to avoid failed/inaccur=
ate query, or there is zero flexibility for you to compute or update proper=
ty map on demand. My feeling is this may not be the right way...=C2=A0</b><=
/div><div><b><br></b></div><div><b>Page 12</b></div><div><br></div><div>=C2=
=A0 =C2=A0 ...</div><div>5.2.=C2=A0 HTTP Method</div><div><br></div><div>=
=C2=A0 =C2=A0An ALTO Property Map resource is requested using the HTTP POST=
</div><div>=C2=A0 =C2=A0method.</div><div><b>&lt;QX&gt; &quot;an ALTO Prope=
rty Map&quot; -&gt; &quot;an ALTO Filtered Property Map&quot;</b></div><div=
><br></div><div><br></div><div><b>Page 13</b></div><div><br></div><div>5.6.=
=C2=A0 Response</div><div><br></div><div>=C2=A0 =C2=A0The response is the s=
ame as for the property map (Section 4.6),</div><div><b>&lt;QX&gt; &quot;pr=
operty map&quot; -&gt; &quot;Property Map&quot;</b></div><div><br></div><di=
v>=C2=A0 =C2=A0except that it only includes the entities and properties req=
uested by</div><div>=C2=A0 =C2=A0the client.</div><div><br></div><div>=C2=
=A0 =C2=A0Also, the Filtered Property Map response MUST include all inherit=
ed</div><div>=C2=A0 =C2=A0property values for the specified entities (unlik=
e the Full Property</div><div><b>&lt;QX&gt; &quot;Full&quot; -&gt; &quot;fu=
ll&quot;, since Full Property Map is not a term defined in this document.</=
b></div><div><br></div><div>=C2=A0 =C2=A0Map, the Filtered Property Map res=
ponse does not include enough</div><div>=C2=A0 =C2=A0information for the cl=
ient to calculate the inherited values).</div><div><br></div><div>6.=C2=A0 =
Impact On Legacy Servers And Clients</div><div><b>&lt;QX&gt; &quot;Legacy S=
ervers And Clients&quot; -&gt; &quot;Legacy ALTO Servers And ALTO Clients&q=
uot;</b></div><div><br></div><div>6.1.=C2=A0 Impact on Endpoint Property Se=
rvice</div><div><br></div><div>=C2=A0 =C2=A0The property maps defined in th=
is document provide the same</div><div><b>&lt;QX&gt; &quot;property maps&qu=
ot; -&gt; &quot;Property Map&quot;</b></div><div><br></div><div>=C2=A0 =C2=
=A0functionality as the Endpoint Property Service (EPS) defined in</div><di=
v>=C2=A0 =C2=A0Section 11.4 of [RFC7285].=C2=A0 Accordingly, it is RECOMMEN=
DED that the</div><div>=C2=A0 =C2=A0EPS be deprecated in favor of property =
maps.=C2=A0 However, ALTO servers</div><div><b>&lt;QX&gt; &quot;property ma=
ps&quot; -&gt; &quot;Property Map&quot;</b></div><div><br></div><div>=C2=A0=
 =C2=A0MAY provide an EPS for the benefit of legacy clients.</div><div><br>=
</div><div><b>Page 14</b></div><div>=C2=A0 =C2=A0</div><div>=C2=A0 =C2=A0..=
.</div><div>=C2=A0=C2=A0 However, when used with property maps, this docume=
nt amends the<br></div><div><b>&lt;QX&gt; &quot;property maps&quot; -&gt; &=
quot;Property Map&quot;</b></div><div><br></div><div>=C2=A0 =C2=A0definitio=
n of the &quot;pid&quot; property as follows.</div><div><br></div><div>=C2=
=A0 =C2=A0First, the name of the property is simply &quot;pid&quot;; the na=
me is not</div><div>=C2=A0 =C2=A0prefixed with the resource ID of a network=
 map.=C2=A0 The &quot;uses&quot;</div><div>=C2=A0 =C2=A0capability of the p=
roperty map resource indicates the associated</div><div>=C2=A0 =C2=A0networ=
k map.=C2=A0 This implies that a property map can only return the</div><div=
>=C2=A0 =C2=A0&quot;pid&quot; property for one network map; if an ALTO serv=
er provides</div><div>=C2=A0 =C2=A0several network maps, it must provide a =
property map resource for</div><div>=C2=A0 =C2=A0each one.</div><div><b>&lt=
;QX&gt; &quot;must provide&quot; -&gt; &quot;MUST provide&quot;</b></div><d=
iv><br></div><div><br></div><div><b>Page 15</b></div><div><br></div><div>=
=C2=A0 =C2=A0 ...</div><div>=C2=A0 =C2=A0 7.3.=C2=A0 Information Resource D=
irectory (IRD)</div><div><br></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0 =
=C2=A0The Property Maps for the &quot;ISP&quot;, &quot;ASN&quot;, &quot;cou=
ntry&quot; and &quot;state&quot;</div><div><b>&lt;QX&gt; &quot;Property Map=
s&quot; -&gt; &quot;Filtered Property Map&quot;</b></div><div><br></div><di=
v>=C2=A0 =C2=A0properties do not depend on the default network map (they do=
 not have</div><div><b>&lt;QX&gt; &quot;do not depend on the default networ=
k map (they do not have&quot; -&gt;</b></div><div><b>=C2=A0 =C2=A0 =C2=A0&q=
uot;does not depend on the default network map (it does not have&quot;</b><=
/div><div><br></div><div><b>Page 18</b></div><div><br></div><div>=C2=A0 =C2=
=A0 ...</div><div>7.6.=C2=A0 Filtered Property Map Example #2</div><div><br=
></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0 =C2=A0Also note the &quot;ASN=
&quot; property has the value &quot;12345&quot; for both the</div><div>=C2=
=A0 =C2=A0blocks &quot;ipv4:<a href=3D"http://192.0.2.0/28">192.0.2.0/28</a=
>&quot; and &quot;ipv4:<a href=3D"http://192.0.2.16/28">192.0.2.16/28</a>&q=
uot;, so every address</div><div>=C2=A0 =C2=A0in the block &quot;ipv4:<a hr=
ef=3D"http://192.0.2.0/27">192.0.2.0/27</a>&quot; has that property value.=
=C2=A0 However</div><div>=C2=A0 =C2=A0the block &quot;ipv4:<a href=3D"http:=
//192.0.2.0/27">192.0.2.0/27</a>&quot; itself does not have a value for &qu=
ot;ASN&quot;:</div><div>=C2=A0 =C2=A0address blocks cannot inherit properti=
es from blocks with longer</div><div>=C2=A0 =C2=A0prefixes, even if every s=
uch block has the same value.</div><div><b>&lt;QX&gt; This is a very good e=
xample. Please see my comments makred in &lt;QX??&gt; for page 11. And if w=
e eventually insist the all-or-nothing inheritance design, it would make th=
e inheritance of properties much clearer to readers if we use it in Section=
 3.1.3, instead of explaining the reasons here.</b></div><div><br></div><di=
v><b>Page 19</b></div><div><br></div><div>7.7.=C2=A0 Filtered Property Map =
Example #3</div><div><br></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0 =C2=
=A0Note that the value of &quot;pid&quot; for the prefix &quot;ipv4:<a href=
=3D"http://10.0.0.0/15">10.0.0.0/15</a>&quot; is</div><div>=C2=A0 =C2=A0&qu=
ot;pid1&quot;, even though all addresses in that block are in &quot;pid2&qu=
ot;,</div><div>=C2=A0 =C2=A0because &quot;ipv4:<a href=3D"http://10.0.0.0/8=
">10.0.0.0/8</a>&quot; is the longest prefix in the network map</div><div>=
=C2=A0 =C2=A0which prefix-matches &quot;ipv4:<a href=3D"http://10.0.0.0/15"=
>10.0.0.0/15</a>&quot;, and that prefix is in</div><div>=C2=A0 =C2=A0&quot;=
pid1&quot;.</div><div><b>&lt;QX&gt; I agree with Shenzhen&#39;s comments. <=
a href=3D"http://10.0.0.0/XX">10.0.0.0/XX</a> is inconsistent with the sett=
ings in Section 7.1. It should be fixed in the next version.</b></div><div>=
<br></div><div><b>Page 21</b></div><div>=C2=A0 =C2=A0</div><div>=C2=A0 =C2=
=A0Also, while technically this document does not introduce any security</d=
iv><div>=C2=A0 =C2=A0risks not inherent in the Endpoint Property Service de=
fined by</div><div>=C2=A0 =C2=A0[RFC7285], the GET-mode property map resour=
ce defined in this</div><div>=C2=A0 =C2=A0document does make it easier for =
a client to download large numbers</div><div>=C2=A0 =C2=A0of property value=
s.=C2=A0 Accordingly, an ALTO Server should limit GET-</div><div>=C2=A0 =C2=
=A0mode property maps for to properties which do not contain sensitive</div=
><div>=C2=A0 =C2=A0data.</div><div><b>&lt;QX&gt; &quot;for to properties&qu=
ot; -&gt; &quot;to properties&quot;</b></div><div><br></div><div>9.1. =C2=
=A0application/alto-* Media Types<br></div><div>=C2=A0 =C2=A0...</div><div>=
=C2=A0 =C2=A0Security considerations: =C2=A0Security considerations relatin=
g to the</div><div><b>&lt;QX&gt; &quot;relating&quot; -&gt; &quot;related&q=
uot;</b></div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 generation and consu=
mption of ALTO Protocol messages are discussed</div><div>=C2=A0 =C2=A0 =C2=
=A0 in Section 15 of [RFC7285].</div><div><br></div><div>=C2=A0 =C2=A0Inter=
operability considerations: =C2=A0This document specifies format of</div><d=
iv><b>&lt;QX&gt; &quot;format&quot; -&gt; &quot;formats&quot;</b></div><div=
><br></div></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On Mon, Jun 26, 2017 at 11:58 PM, Shenshen Chen <span dir=3D"ltr">&lt=
;<a href=3D"mailto:cs90911@gmail.com" target=3D"_blank">cs90911@gmail.com</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><di=
v>Dear authors of alto-unified-props and all,</div><div><br></div><div>In s=
ection 2.5, I feel &quot;property type&quot; could be better (because RFC72=
85 names</div><div>sections using &quot;property type&quot;, but not &quot;=
property name&quot;) and &quot;property value&quot;=C2=A0</div><div>should =
be mentioned (includes the &quot;null&quot; value mentioned in section 4.6)=
.</div><div>I also suggest showing=C2=A0the &quot;null&quot; value can be i=
nherited explicitly</div><div>in the section 3.1.3 or emphasizing it as a n=
ormal property value.</div><div><br></div><div>Here is a list of typos (com=
ments are marked with &quot;&gt;&gt;&gt;&quot;):</div><div><br></div><div>[=
Page 2]</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.1.3.=C2=A0 Heirarchy And Inh=
eritance . . . . . . . . . . . . . . =C2=A0 7</div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A03.1.4.=C2=A0 Relationship To Network Maps =C2=A0. . . . . . . . .=
 . . . =C2=A0 8</div><div>=C2=A0 =C2=A0 =C2=A03.2.=C2=A0 PID Domain =C2=A0.=
 . . . . . . . . . . . . . . . . . . . . . . =C2=A0 9</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A03.2.1.=C2=A0 Domain Name . . . . . . . . . . . . . . . . .=
 . . . . =C2=A0 9</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.2.2.=C2=A0 Domain-=
Specific Entity Addresses =C2=A0. . . . . . . . . . =C2=A0 9</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A03.2.3.=C2=A0 Heirarchy And Inheritance . . . . . . =
. . . . . . . . =C2=A0 9</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.2.4.=C2=A0 =
Relationship To Internet Addresses Domains =C2=A0. . . . . =C2=A0 9</div><d=
iv><br></div><div>&gt;&gt;&gt; &quot;To&quot; =3D&gt; &quot;to&quot;, &quot=
;And&quot; =3D&gt; &quot;and&quot;, &quot;Heirarchy&quot; =3D&gt; &quot;Hie=
rarchy&quot;</div><div><br></div><div><br></div><div>[Page 3]</div><div>=C2=
=A0 =C2=A0Second, the EPS is only defined as a POST-mode service.=C2=A0 Cli=
ents must</div><div>=C2=A0 =C2=A0request the properties for an explicit set=
 of addresses.=C2=A0 By</div><div>=C2=A0 =C2=A0contrast, [RFC7285] defines =
a GET-mode Cost Map resource which</div><div>=C2=A0 =C2=A0returns all avail=
able costs, so a client can get the full set of</div><div>=C2=A0 =C2=A0cost=
s once, and then lookup costs without querying the ALTO server.</div><div>=
=C2=A0 =C2=A0RFC7285 does not define an equivalent service for endpoint</di=
v><div>=C2=A0 =C2=A0properties.=C2=A0 Granted, it is not be practical to en=
umerate the</div><div><br></div><div>&gt;&gt;&gt; &quot;is not be&quot; =3D=
&gt; &quot;is not&quot;</div><div><br></div><div><br></div><div>[Page 4]</d=
iv><div>=C2=A0 =C2=A0This document proposes a new approach to ALTO properti=
es.</div><div>=C2=A0 =C2=A0Specifically, it defines two new resource types,=
 namely Property Maps</div><div>=C2=A0 =C2=A0and Filtered Property Maps.=C2=
=A0 The former are GET-mode resources which</div><div>=C2=A0 =C2=A0return t=
he property values for all entities in a domain, and are</div><div>=C2=A0 =
=C2=A0analogous the ALTO&#39;s Network Map and Cost Map resources.=C2=A0 Th=
e latter</div><div><br></div><div>&gt;&gt;&gt; &quot;Network Map and Cost M=
ap resources&quot; =3D&gt; &quot;Network Maps and Cost Maps&quot;</div><div=
>=C2=A0 =C2=A0 I think it should keep the same format with &quot;Filtered N=
etwork Maps=C2=A0</div><div>=C2=A0 =C2=A0 and Filtered Cost Maps&quot; in t=
he last sentence of this paragraph.</div><div><br></div><div>=C2=A0 =C2=A0a=
re POST-mode resources which return the values for a set of</div><div>=C2=
=A0 =C2=A0properties and entities requested by the client, and are analogou=
s to</div><div>=C2=A0 =C2=A0ALTO&#39;s Filtered Network Maps and Filtered C=
ost Maps.</div><div><br></div><div>[Page 7]</div><div>3.1.3.=C2=A0 Heirarch=
y And Inheritance</div><div><br></div><div>[Page 9]</div><div>3.2.3.=C2=A0 =
Heirarchy And Inheritance</div><div><br></div><div>&gt;&gt;&gt; &quot;Heira=
rchy&quot; =3D&gt; &quot;Hierarchy&quot;</div><div><br></div><div>[Page 19]=
</div><div>=C2=A0 =C2=A0Note that the value of &quot;pid&quot; for the pref=
ix &quot;ipv4:<a href=3D"http://10.0.0.0/15" target=3D"_blank">10.0.0.0/15<=
/a>&quot; is</div><div>=C2=A0 =C2=A0&quot;pid1&quot;, even though all addre=
sses in that block are in &quot;pid2&quot;,</div><div>=C2=A0 =C2=A0because =
&quot;ipv4:<a href=3D"http://10.0.0.0/8" target=3D"_blank">10.0.0.0/8</a>&q=
uot; is the longest prefix in the network map</div><div>=C2=A0 =C2=A0which =
prefix-matches &quot;ipv4:<a href=3D"http://10.0.0.0/15" target=3D"_blank">=
10.0.0.0/15</a>&quot;, and that prefix is in</div><div>=C2=A0 =C2=A0&quot;p=
id1&quot;.</div><div><br></div><div>=C2=A0 =C2=A0POST /propmap/lookup/pid H=
TTP/1.1</div><div>=C2=A0 =C2=A0Host: <a href=3D"http://alto.example.com" ta=
rget=3D"_blank">alto.example.com</a></div><div>=C2=A0 =C2=A0Accept: applica=
tion/alto-propmap+json,<wbr>application/alto-error+json</div><div>=C2=A0 =
=C2=A0Content-Length: ###</div><div>=C2=A0 =C2=A0Content-Type: application/=
alto-<wbr>propmapparams+json</div><div><br></div><div>=C2=A0 =C2=A0{</div><=
div>=C2=A0 =C2=A0 =C2=A0&quot;entities&quot; : [</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.0=
 =C2=A010.0.0.0&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.16 10.1.0.0&quot;,</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;=
ipv4:192.0.2.64 =C2=A010.3.0.0&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.128 =C2=A011.0=
.0.0&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0&quot;ipv4:<a href=3D"http://192.0.2.0/26" target=3D"_blan=
k">192.0.2.0/26</a> <a href=3D"http://10.0.0.0/15" target=3D"_blank">10.0.0=
.0/15</a>&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:<a href=3D"http://192.0.2.0/30" target=3D"_=
blank">192.0.2.0/30</a> <a href=3D"http://10.0.0.0/17" target=3D"_blank">10=
.0.0.0/17</a>&quot; ],</div><div>=C2=A0 =C2=A0 =C2=A0&quot;properties&quot;=
 : [ &quot;pid&quot; ]</div><div>=C2=A0 =C2=A0}</div><div><br></div><div>&g=
t;&gt;&gt; This part should be modified into:</div><div><br></div><div>=C2=
=A0 =C2=A0Note that the value of &quot;pid&quot; for the prefix &quot;ipv4:=
<a href=3D"http://192.0.2.0/26" target=3D"_blank">192.0.2.0/26</a>&quot; is=
</div><div>=C2=A0 =C2=A0&quot;pid1&quot;, even though all addresses in that=
 block are in &quot;pid2&quot;,</div><div>=C2=A0 =C2=A0because &quot;ipv4:<=
a href=3D"http://192.0.2.0/25" target=3D"_blank">192.0.2.0/25</a>&quot; is =
the longest prefix in the network map</div><div>=C2=A0 =C2=A0which prefix-m=
atches &quot;ipv4:<a href=3D"http://192.0.2.0/26" target=3D"_blank">192.0.2=
.0/26</a>&quot;, and that prefix is in</div><div>=C2=A0 =C2=A0&quot;pid1&qu=
ot;.</div><div><br></div><div>=C2=A0 =C2=A0POST /propmap/lookup/pid HTTP/1.=
1</div><div>=C2=A0 =C2=A0Host: <a href=3D"http://alto.example.com" target=
=3D"_blank">alto.example.com</a></div><div>=C2=A0 =C2=A0Accept: application=
/alto-propmap+json,<wbr>application/alto-error+json</div><div>=C2=A0 =C2=A0=
Content-Length: ###</div><div>=C2=A0 =C2=A0Content-Type: application/alto-<=
wbr>propmapparams+json</div><div><br></div><div>=C2=A0 =C2=A0{</div><div>=
=C2=A0 =C2=A0 =C2=A0&quot;entities&quot; : [</div><div>=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.0&quot;=
,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&quot;ipv4:192.0.2.16&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.64&quot;,</div>=
<div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&=
quot;ipv4:192.0.2.128&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:<a href=3D"http://192.0.2.0/26=
" target=3D"_blank">192.0.2.0/26</a>&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:<a href=3D"http:=
//192.0.2.0/30" target=3D"_blank">192.0.2.0/30</a>&quot; ],</div><div>=C2=
=A0 =C2=A0 =C2=A0&quot;properties&quot; : [ &quot;pid&quot; ]</div><div>=C2=
=A0 =C2=A0}</div><div><br></div><div>[Page 23]</div><div>=C2=A0 =C2=A0New A=
LTO entity domains are assigned after IETF Review [RFC5226] to</div><div>=
=C2=A0 =C2=A0ensure that proper documentation regarding the new ALTO entity=
</div><div>=C2=A0 =C2=A0domains and their security considerations has been =
provided.=C2=A0 RFCs</div><div><br></div><div>&gt;&gt;&gt; &quot;has been&q=
uot; =3D&gt; &quot;have been&quot;</div><div><br></div><div>=C2=A0 =C2=A0de=
fining new entity domains should indicate how an entity in a</div><div>=C2=
=A0 =C2=A0registered domain is encoded as an EntityName, and, if applicable=
,</div><div>=C2=A0 =C2=A0the rules defining the entity hierarchy and proper=
ty inheritance.</div><div>=C2=A0 =C2=A0Updates and deletions of ALTO entity=
 domains follow the same</div><div>=C2=A0 =C2=A0procedure.</div><div><br></=
div><div><br></div><div>Best Regards,</div><div>Shenshen</div><div><br></di=
v></div>
<br>______________________________<wbr>_________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/alto</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div cla=
ss=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">=
<div><div dir=3D"ltr"><div><div dir=3D"ltr"><font size=3D"2">Qiao Xiang<br>=
Postdoctoral Fellow,=C2=A0</font></div><div dir=3D"ltr"><font size=3D"2">De=
partment of Computer Science,</font></div><div dir=3D"ltr"><font size=3D"2"=
>Yale University</font></div></div></div></div></div></div>
</div>

--001a114c887a3546e4055304e3b1--


From nobody Wed Jun 28 07:17:59 2017
Return-Path: <dawn_chen_f@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 C9B5712783A; Wed, 28 Jun 2017 07:17:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.127
X-Spam-Level: 
X-Spam-Status: No, score=-1.127 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_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 4-xaQfQ446-e; Wed, 28 Jun 2017 07:17:56 -0700 (PDT)
Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-oln040092253012.outbound.protection.outlook.com [40.92.253.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61997126557; Wed, 28 Jun 2017 07:17:55 -0700 (PDT)
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=E/7tl5NlugbYKABK+FWaf1xxXZTT1aLkVokxU2Cj2to=; b=OzYC2j7NLnFNN1H2VcULRKg6RDm4tHHOJl5nl0qT4zjFlN1Y28zsWsm/VeJCJGDJwyeYDVPJWgOWdt6PWR6F0JlsGzxjhxRnSlYiOi6+AefeKqRiX2jNJ3QF8YskT101mBFiwh80rpz5BgKvM9dYdXl5bUWhfZOWoKICCJkCZ024u5jvR8ji2NQS8vGintZR946IFmaoXTQ+OBpQF2yeO/K2YrHxADv4WVQ98lVjH1UFJyvY/Iz9jY4a0ApBA27ZHjU9YkiHCOoHhfgfWqERezaMLwthGDZJ4gcuLya+ofT5u3fXVbl1wP04uiwtW1kRiCZr/P3QEt2YBiQqMOaMgw==
Received: from PU1APC01FT024.eop-APC01.prod.protection.outlook.com (10.152.252.55) by PU1APC01HT103.eop-APC01.prod.protection.outlook.com (10.152.253.100) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1157.12; Wed, 28 Jun 2017 14:17:52 +0000
Received: from HK2PR0401MB1588.apcprd04.prod.outlook.com (10.152.252.56) by PU1APC01FT024.mail.protection.outlook.com (10.152.252.233) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.9 via Frontend Transport; Wed, 28 Jun 2017 14:17:52 +0000
Received: from HK2PR0401MB1588.apcprd04.prod.outlook.com ([fe80::9c4:7e35:e642:38db]) by HK2PR0401MB1588.apcprd04.prod.outlook.com ([fe80::9c4:7e35:e642:38db%14]) with mapi id 15.01.1199.019; Wed, 28 Jun 2017 14:17:52 +0000
From: Dawn Chan <dawn_chen_f@hotmail.com>
To: "draft-randriamasy-alto-cost-context@ietf.org" <draft-randriamasy-alto-cost-context@ietf.org>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: Review of draft-randriamasy-alto-cost-context-01
Thread-Index: AQHS8BlUHfiQe8Zz1ECQt8At9uacyQ==
Date: Wed, 28 Jun 2017 14:17:52 +0000
Message-ID: <HK2PR0401MB158840B5686317F82633A1ABB5DD0@HK2PR0401MB1588.apcprd04.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:88D286CDE2740B2A6D8D23F5F0BD54017A9D6EC391A713D99D227FEF8BE17ED8; UpperCasedChecksum:0F95C270C00EE657B112723018110B0563F661FDBA91B2A91B71098423B8F38B; SizeAsReceived:7227; Count:43
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [cuhYdFA4vNrGq0BBEHb5LNnsGCiiEbSp]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; PU1APC01HT103; 7:1IAl7ptXRHQkOSzhmxH6zRPzCDbcD88XvACUZ51y8n6vYoNgnXPdSthPQR1iwl68PeqlB/wita7qndnCT8vuuZ7eNEM4cj3IqKoi0xIJ9RsKmgxAn7i6gWLckXvloKYW90A67fuD5pGfptipvolm/za+mrw08IaBxpRCpbegWPsR+SEi9jjyI29hvwB3S73Yo66P+ErF97Pl45jg9Rwm3tYO4g1FB9XmaGMSy05/0Qam1t1w7uuLqke4FA+qVqn9/1eGe7gV7GW/1df0dMWr6jPKQeRvu4C2RRjJOO7cHASW5bzSN290zD32QpBmd8yaYGM9qp9Tbd5Afy8hxnAPi0vPtCUb9FQBrmgf4FfDbKLqo7oBW2L7ildfABXDU5083G9XNpykqHgvmewjM/xnlV0+QWVmbAq5DzQM+NwxPS2xBHTj6vBA3uyp6MwSkxO65zln4oS8+AG5F4SLxJ789KJflIECwZPqEvXQOKYsGWbZyDSrrGvUiuvYLDK8pK5M3KV/BM2IKoyh9n3e6roydjb8rkdatW6SKEw+LT3LOjVgSqbv4Rl70/mDMNvzFtxmSv4fQg9TebX+7gywhETRhDwbyQNtOYMCgEliaWoop6kDkXWFq8/hoEwKa0DjUdLK0OAozAJjunbR5tLqwL618pnwFImjB2nYXIIOcLKmPK4XfYlLRQCOdfnJbcLlyNEj5SBTfw0FbuV39Hftux0dhUXyZuV4vXLjNOskpuVCw97iSQbP6fY5rMzK4+/vITbjHGu7RIJ7831PkNAUqfOcWQ==
x-incomingheadercount: 43
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:PU1APC01HT103; H:HK2PR0401MB1588.apcprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-traffictypediagnostic: PU1APC01HT103:
x-ms-office365-filtering-correlation-id: 39babd49-a859-4c1b-1d12-08d4be307612
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(300000502095)(300135100095)(22001)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:PU1APC01HT103; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:PU1APC01HT103; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:PU1APC01HT103; 
x-forefront-prvs: 03524FBD26
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <0CC75434F9E64E4B8B6A2AEAB19E4A92@apcprd04.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jun 2017 14:17:52.3126 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT103
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/tgQeAf67TzPNm4PzgrIx187YWZA>
Subject: [alto] Review of draft-randriamasy-alto-cost-context-01
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: Wed, 28 Jun 2017 14:17:58 -0000

SGkgU2FiaW5lIGFuZCBhbGwsDQoNCkFmdGVyIHJldmlld2luZyBjb3N0IGNvbnRleHQsIEkgdGhp
bmsgYSBwb3NzaWJsZSBzb2x1dGlvbiB0byBpbnRyb2R1Y2UgY29zdCBjb250ZXh0IGlzIHRvIGV4
dGVuZCB0aGUgZXhpc3Rpbmcgc3BlY2lmaWNhdGlvbiBvZiBDb3N0VHlwZS4gQmVsb3cgaXMgbXkg
cHJvcG9zYWwuDQoNClRoZSBDb3N0VHlwZSBkZWZpbmVkIGluIFtSRkM3Mjg1XSBpczoNCg0Kb2Jq
ZWN0IENvc3RUeXBlIHsNCglDb3N0TWV0cmljIGNvc3QtbWV0cmljOw0KCUNvc3RNb2RlIGNvc3Qt
bW9kZTsNCglbSlNPTlN0cmluZyBkZXNjcmlwdGlvbjtdDQp9DQoNClNpbmNlIGNvc3QtY29udGV4
dCBpcyB1c2VkIHRvIGRlc2NyaWJlIHRoZSBkaWZmZXJlbnQgcGFyYW1ldGVycyBmb3Igb25lIG1l
dHJpYywgc28gSSBwcm9wb3NlIHRvIGV4dGVuZCBDb3N0VHlwZSBhcyBmb2xsb3dzOg0KDQpvYmpl
Y3QgQ29zdFR5cGUgew0KCUNvc3RNZXRyaWMgY29zdC1tZXRyaWM7DQoJQ29zdE1vZGUgY29zdC1t
b2RlOw0KCVtDb3N0Q29udGV4dCBjb3N0LWNvbnRleHQ8MS4uKj47XQ0KCVtKU09OU3RyaW5nIGRl
c2NyaXB0aW9uO10NCn0NCg0KVGhlIGRlZmluaXRpb24gb2YgQ29zdENvbnRleHQgY2FuIGJlIGRv
bmUgbGF0ZXIuIEVhY2ggY29zdC1jb250ZXh0IG1heSBiZSBsaWtlIFsidWRhIiwgInVwbGluayJd
IHdoaWNoIGRlc2NyaWJlIGEgc3BlY2lmaWMgbWV0cmljIGNvbnRleHQuDQoNClNvLCB0aGUgSVJE
IG1heSBiZToNCg0Kew0KICAibWV0YSIgOiB7DQogICAgImNvc3QtdHlwZSIgOiB7DQogICAgICAi
bnVtLXJvdXRpbmdjb3N0Ijogew0KICAgICAgICAiY29zdC1tb2RlIjogIm51bWVyaWNhbCIsDQog
ICAgICAgICJjb3N0LW1ldHJpYyIgOiAicm91dGluZ2Nvc3QiDQogICAgICB9LA0KICAgICAgIm51
bS1SRmNvc3QiIDogew0KICAgICAgICAiY29zdC1tb2RlIiA6ICJudW1lcmljYWwiLA0KICAgICAg
ICAiY29zdC1tZXRyaWMiIDogIlJGY29zdCINCiAgICAgICAgImNvc3QtY29udGV4dCIgOiBbWyJ1
ZGEiLCAidXBsaW5rIl0sDQogICAgICAgICAgICAgICAgICAgICAgICAgIFsidWRhIiwgImRvd25s
aW5rIl0sDQogICAgICAgICAgICAgICAgICAgICAgICAgIFsidWRuYSIsICJ1cGxpbmsiXSwNCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgWyJ1ZG5hIiwgImRvd25saW5rIl1dDQogICAgICB9DQog
ICAgfQ0KICB9DQogICJyZXNvdXJjZXMiIDogew0KICAgIC4uLkFuIGVuZHBvaW50Y29zdCByZXNv
dXJjZSB3aGljaCBzdXBwb3J0cyBtdWx0aS1jb3N0IGFuZCBjb3N0LWNhbGVuZGFyLi4uDQogICAg
ImNhbGVuZGFyZWQtZW5kcG9pbnRjb3N0LW1hcCIgOiB7DQogICAgICAidXJpIjogImh0dHA6Ly9h
bHRvLmxvY2FsLmV4YW1wbGUuY29tL2VuZHBvaW50Y29zdG1hcC8vbG9va3VwL2NvbnRleHQiLA0K
ICAgICAgIm1lZGlhLXR5cGVzIiA6IFsgImFwcGxpY2F0aW9uL2FsdG8tZW5kcG9pbnRjb3N0K2pz
b24iIF0sDQogICAgICAiYWNjZXB0cyIgOiBbICJhcHBsaWNhdGlvbi9hbHRvLWVuZHBvaW50Y29z
dHBhcmFtcytqc29uIiBdLA0KICAgICAgImNhcGFiaWxpdGllcyIgOiB7DQogICAgICAgICJjb3N0
LXR5cGUtbmFtZXMiIDogWyAibnVtLXJvdXRpbmdjb3N0IiwNCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICJudW0tUkZjb3N0IiBdLA0KICAgICAgICAiY2FsZW5kYXItYXR0cmlidXRlcyIg
OiBbDQogICAgICAgICAgeyAiY29zdC10eXBlLW5hbWVzIiA6ICJudW0tcm91dGluZ2Nvc3QiLA0K
ICAgICAgICAgICAgInRpbWUtaW50ZXJ2YWwtc2l6ZSIgOiAiMSBob3VyIiwNCiAgICAgICAgICAg
ICJudW1iZXItb2YtaW50ZXJ2YWxzIiA6IDI0IH0sDQogICAgICAgICAgeyAiY29zdC10eXBlLW5h
bWVzIiA6ICJudW0tUkZjb3N0IiwNCiAgICAgICAgICAgICJ0aW1lLWludGVydmFsLXNpemUiIDog
IjUgbWludXRlIiwNCiAgICAgICAgICAgICJudW1iZXItb2YtaW50ZXJ2YWxzIiA6IDEyIH0NCiAg
ICAgICAgXQ0KICAgICAgfQ0KICAgIH0NCiAgfQ0KfQ0KDQpBIHBvc3NpYmxlIHF1ZXJ5IGFuZCBy
ZXNwb25zZSB3b3VsZCBiZSBsaWtlOg0KDQpQT1NUIC9lbmRwb2ludGNvc3QvbG9va3VwL2NvbnRl
eHQgSFRUUC8xLjENCkhvc3Q6IGFsdG8ubG9jYWwuZXhhbXBsZS5jb20NCkNvbnRlbnQtTGVuZ3Ro
OiBbVE9ET10NCkNvbnRlbnQtVHlwZTogYXBwbGljYXRpb24vYWx0by1lbmRwb2ludGNvc3RwYXJh
bXMranNvbg0KQWNjZXB0OiBhcHBsaWNhdGlvbi9hbHRvLWVuZHBvaW50Y29zdCtqc29uLGFwcGxp
Y2F0aW9uL2FsdG8tZXJyb3IranNvbg0Kew0KICAiY29zdC10eXBlIiA6IHt9LA0KICAibXVsdGkt
Y29zdC10eXBlcyIgOiBbIHsgImNvc3QtbW9kZSIgOiAibnVtZXJpY2FsIiwgImNvc3QtbWV0cmlj
IiA6ICJyb3V0aW5nY29zdCIgfSwNCiAgICAgICAgICAgICAgICAgICAgICAgICAgeyAiY29zdC1t
b2RlIiA6ICJudW1lcmljYWwiLCAiY29zdC1tZXRyaWMiIDogIlJGY3NvdCIsICJjb3N0LWNvbnRl
eHQiIDogWyBbICJ1ZGEiLCAidXBsaW5rIiBdLFsgInVkYSIsICJkb3dubGlua+KAnSBdIF0gfQ0K
ICBdDQogICJlbmRwb2ludHMiIDogew0KICAgICJzcmNzIjogWyAiaXB2NDoxOTIuMC4yLjIiIF0s
DQogICAgImRzdHMiOiBbICJpcHY0OjE5Mi4wLjIuODkiLA0KICAgICAgICAgICAgICAiaXB2Njoy
MDAwOjoxOjIzNDU6Njc4OTphYmNkIl0NCiAgfQ0KfQ0KDQpIVFRQLzEuMSAyMDAgT0sNCkNvbnRl
bnQtTGVuZ3RoOiBbVE9ET10NCkNvbnRlbnQtVHlwZTogYXBwbGljYXRpb24vYWx0by1lbmRwb2lu
dGNvc3QranNvbg0Kew0KICAibWV0YSIgOiB7DQogICAgIm11bHRpLWNvc3QtdHlwZXMiIDogWw0K
ICAgICAgeyAiY29zdC1tb2RlIiA6ICJudW1lcmljYWwiLCAiY29zdC1tZXRyaWMiIDogInJvdXRp
bmdjb3N0IiB9LA0KICAgICAgeyAiY29zdC1tb2RlIiA6ICJudW1lcmljYWwiLCAiY29zdC1tZXRy
aWMiIDogIlJGY3NvdCIsICJjb3N0LWNvbnRleHQiIDogW1sgInVkYSIsICJ1cGxpbmsiIF0sWyAi
dWRhIiwgImRvd25saW5rIiBdXQ0KICAgICAgLy8gSGVyZSwgc3VwcG9zZSBvbmx5IHRoZSBjb250
ZXh0dWFsIHBhcmFtZXRlcnMgWyJ1ZGEiLCAidXBsaW5rIl0gYW5kIFsidWRhIiwgImRvd25saW5r
Il0gYXJlIG5lZWRlZC4NCiAgICAgIH0NCiAgICBdLA0KICAgICJjYWxlbmRhci1yZXNwb25zZS1h
dHRyaWJ1dGVzIiA6IFsNCiAgICAgIHsgImNvc3QtdHlwZS1uYW1lIDogbnVtLXJvdXRpbmdjb3N0
Ig0KICAgICAgICAiY2FsZW5kYXItc3RhcnQtdGltZSIgOiBNb24sIDMwIEp1biAyMDE0IDAwOjAw
OjAwIEdNVCwNCiAgICAgICAgInRpbWUtaW50ZXJ2YWwtc2l6ZSIgOiAiMSBob3VyIiwNCiAgICAg
ICAgIm51bWItaW50ZXJ2YWxzIiA6IDI0LA0KICAgICAgfSwNCiAgICAgIHsgImNvc3QtdHlwZS1u
YW1lIDogbnVtLWxhdGVuY3kiDQogICAgICAgICJjYWxlbmRhci1zdGFydC10aW1lIiA6IFR1ZSwg
MSBKdWwgMjAxNCAxMzowMDowMCBHTVQsDQogICAgICAgICJ0aW1lLWludGVydmFsLXNpemUiIDog
IjUgbWludXRlIiwNCiAgICAgICAgIm51bWItaW50ZXJ2YWxzIiA6IDEyDQogICAgICB9DQogICAg
XSwNCiAgfSAvLyBlbmQgbWV0YQ0KICAiZW5kcG9pbnQtY29zdC1tYXAiIDogew0KICAiaXB2NDox
OTIuMC4yLjIiOiB7DQogICAgImlwdjQ6MTkyLjAuMi44OSIgICAgOiBbIFtyMSwgcjIsIC4uLiBy
MjRdLCBbIFtsMS11ZGEtdXBsaW5rLGwxLXVkYS1kb3dubGlua10sIFtsMi11ZGEtdXBsaW5rLGwy
LXVkYS1kb3dubGlua10sIC4uLiBbbDEyLXVkYS11cGxpbmssbDEyLXVkYS1kb3dubGlua10gXSBd
LA0KICAgICJpcHY2OjIwMDA6OjE6MjM0NTo2Nzg5OmFiY2QiIDogWyBbcjEsIHIyLCAuLi4gcjI0
XSwgWyBbbDEtdWRhLXVwbGluayxsMS11ZGEtZG93bmxpbmtdLCBbbDItdWRhLXVwbGluayxsMi11
ZGEtZG93bmxpbmtdLCAuLi4gW2wxMi11ZGEtdXBsaW5rLGwxMi11ZGEtZG93bmxpbmtdIF0gXQ0K
fSB9DQp9DQoNCg0KSGVyZSB3ZSBtYXkgY2hhbmdlIHRoZSBrbm93bGVkZ2Ugb2YgY29zdCB2YWx1
ZS4gRWFjaCBjb3N0IHZhbHVlIHJlcHJlc2VudGVkIGEgY29tYmluYXRpb24gb2YgYSBjb3N0LW1v
ZGUgYW5kIGEgY29zdC1tZXRyaWMgYXMgZGVmaW5lZCBpbiBSRkM3Mjg1LCBidXQgbm93LCBlYWNo
IGNvc3QgdmFsdWUgbWF5IHJlcHJlc2VudCBhIGNvbWJpbmF0aW9uIG9mIGEgY29zdC1tb2RlLCBh
IGNvc3QtbWV0cmljIGFuZCBhIHNwZWNpZmljIGNvc3QtY29udGV4dCB2YWx1ZS4NCg0KU3VjaCBk
ZXNpZ24gaWRlYSBzZWVtcyB0byBiZSBjb21wYXRpYmxlIHdpdGggbXVsdGktY29zdCBhbmQgY29z
dC1jYWxlbmRhci4NCg0KV2hhdCBkbyB5b3UgdGhpbmsgb2YgdGhpcyBpZGVhPyBXaXNoIHRvIGhl
YXIgeW91ciByZXBseS4NCg0KQmVzdCBSZWdhcmRzLA0KRGF3bg0KDQo=


From nobody Wed Jun 28 07:54:35 2017
Return-Path: <cs90911@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 A4AD112EC0A; Wed, 28 Jun 2017 07:54:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 v5d_asYtl_5B; Wed, 28 Jun 2017 07:54:31 -0700 (PDT)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (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 A11CF129C04; Wed, 28 Jun 2017 07:54:31 -0700 (PDT)
Received: by mail-ua0-x22b.google.com with SMTP id z22so39368610uah.1; Wed, 28 Jun 2017 07:54:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=Uvn7fqyjuyuGOz131USc0CThze3G4w2iUXyD8IuIdzE=; b=tUaTEsEqIwc3aLoOzrGITm0QfqrYqB+9oeNwVj9DBzgVTGw4k6XnOl2bFZ1uEazzxS 1hGRY1WciJOSiokMqbbIUCNNqKXwzui3qnNRl1qe95WGJQBJ6FojYoOXyUngdq4ZGZUT e2XSz9IKV4v26/XvLDnDn+zIabT2UlidO7NKIuNUlHz/VSoABpz+sPFDoYV7BgjpBgAr 7B1RLP/ectVWEtITFDGeitdSofyrx2E+kcG3xbcCvvMaU0grgj5wZ455OF5wdRaWcrA6 ucE/TdMRcgI9qQlwnX5IAS095nNRLT9Xixg8ZpRSdKFoka1/CUTPf9Fm1SOCdyRDxipd H+kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Uvn7fqyjuyuGOz131USc0CThze3G4w2iUXyD8IuIdzE=; b=N14C7w+ZnQ0CvyXUzWpjOpOiI7yK/aEhilpLwl3dykel0jpVRy7lTdvK/sohgxW5mW pZJM5uiSHMgMJZvrSI+SZQO3D8DMu2HR/FHqtppccz54x3rzrz8IRWQ658DIsnI6Wnox SNcWslLUqJlLlk6eWokHyK1wqNQXJo7g9zlXviJ6UU0ZJc3Qe56GDejwf39RqLDGiFSe iEqv41IjHORpQlmCEkxf6BfYK9KKr9VlaQhBl8D9895mjaOUToWOrvl49xKEDP7OFRF1 85+szbHL6509GmY7NTaKIedVVTq5Qe+3174u+LM7COU7NjjUQ2CITq6B4/mRKGqfpq75 /59Q==
X-Gm-Message-State: AKS2vOzvXet3cBnLMevufLPHhlGfrvDrFNUXRAprj04fOTkW41s6uQAG Ej8vhcSQQERZwdZ1WuYhcw9AQdi2PU2ATQA=
X-Received: by 10.176.9.3 with SMTP id w3mr5645600uag.115.1498661670474; Wed, 28 Jun 2017 07:54:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.236.199 with HTTP; Wed, 28 Jun 2017 07:53:49 -0700 (PDT)
From: Shenshen Chen <cs90911@gmail.com>
Date: Wed, 28 Jun 2017 22:53:49 +0800
Message-ID: <CAKRjQSD2Md+dCZNrjvAYh6SaqFEgMNbLSK7ZyrBUwy3NJXirvQ@mail.gmail.com>
To: draft-ietf-alto-path-vector@ietf.org, alto@ietf.org
Content-Type: multipart/alternative; boundary="f403043c490c81dcd20553065c1d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/H_m96AIEGsCxTWCigvw4V6LKNyM>
Subject: [alto]  Review of draft-ietf-alto-path-vector-00
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: Wed, 28 Jun 2017 14:54:34 -0000

--f403043c490c81dcd20553065c1d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Dear authors of alto-path-vector and all,

After reviewing this draft, I have two comments:

1. To avoid confusion, I suggest replacing every network element (NE) by
network abstract element (ANE), since every network element in this draft
is "abstract" network element.
   An alternative solution is to remove ANE. The network element is
"abstract" according to the definition in Wikipedia ("A network element
is usually defined as a manageable logical entity uniting one or more
physical devices."), which makes it redundant to emphasize "abstract" so
many times.

2. The title of section 4.4 should be "Query-specific Attribute", which
is the noun this section introduced. And the title of section 6.4 should
be "Filtered Cost Map Example" corresponding to section 5.8.

Here is a list of typos (comments are marked with ">>>"):

[Page 3]
     5.8.  Filtered Cost Map Extensions  . . . . . . . . . . . . . .  12
       5.8.1.  Capabilities  . . . . . . . . . . . . . . . . . . . .  12
       5.8.2.  Accept Input Parameters . . . . . . . . . . . . . . .  13
       5.8.3.  Propertymap . . . . . . . . . . . . . . . . . . . . .  14
       5.8.4.  Response  . . . . . . . . . . . . . . . . . . . . . .  14
     5.9.  Endpoint Cost Service Extensions  . . . . . . . . . . . .  14
       5.9.1.  Capabilities  . . . . . . . . . . . . . . . . . . . .  15
       5.9.2.  Accept Input Parameters . . . . . . . . . . . . . . .  15

>>> Accept Input Parameters =3D> Acceptable Input Parameters

[Page 3]
 7.  Compatibility . . . . . . . . . . . . . . . . . . . . . . . .  25

[Page 25]
 7.  Compatibility

>>> Compatibility =3D> Compatibility Considerations/Compatibilities

[Page 4, 5]
   The document is organized as follows.  Section 3 gives an example of
   flow scheduling to illustrate the need to introduce cost mode "path-
   vector" and cost metric "ane".  Section 4 gives an overview of the
   path-vector extension.  Section 5 specifies the new cost mode and
   cost metric, new domain type, entity properties and protocol
   extensions for (Filtered) Cost Maps and Endpoint Cost Services.
   Section 6 presents several examples.  Section 7 discusses the
   compatibility issues with some other proposed ALTO extensions.
   Section 8 discusses the time to live problem.  Section 9 discusses
   several design decisions.  Section 10 and Section 11 discusses about

>>> discusses about =3D> discusses

   security and IANA Considerations.

2.  Terminology

   This document uses the following terms: Network Element, Network
   Element Name, Network Element Property, Network Element Property Map
   and Path Vector.

   o  Network Element (NE): A Network Element is an abstract network
      element, which can be a link, a network switching device, or a set
      of devices.

   o  Network Element Name (NEN): The id of a NE.  It can be referenced

>>> a NE =3D> an NE (which pronounced as [=C9=9Bn'i=CB=90])

      by Cost Map, Filtered Cost Map, Endpoint Cost Service and Property
      Map.

   o  Network Element Property (NEP): The property of a NE.  It can be
      the available bandwidth of a link, the delay or other available
      properties.

[Page 10]
5.4.2.  Domain-Specific Entity Addresses

   The entity address of ane domain is encoded as a JSON string.  The
   string MUST be no more than 64 characters, and it MUST NOT contain
   characters other than US-ASCII alphanumeric characters
   (U+0030-U+0039, U+0041-U+005A, and U+0061-U+007A), the hyphen ('-',
   U+002D), the colon (':', U+003A), the at sign ('@', code point
   U+0040), the low line ('_', U+005F), or the '.' separator (U+002E).
   The '.' separator is reserved for future use and MUST NOT be used
   unless specifically indicated in this document, or an extension

>>> delete the comma before "or" (since there're only two items in a series=
)
   document.

[Page 16]
6.1.  Workflow

   o  Send the GET request for the whole Information Resource Directory.

   o  Look for the resource of the (Filtered) Cost Map/Endpoint Cost
      Service which contains the path-vector cost type and get the

>>> get =3D> gets

      resource id of the property map.

[Page 20]
6.4.  Multi-Cost Filtered Cost Map Example

   The following example presents the request and response of "filtered-
   multi-cost-map".  In this example, the client is interested in the
   path-vector and numerical routing cost information.  The client uses
   "or-constraints" but all the results satisfy the conditions.  In
   resposne, the extended "vtag" field is included in "meta" to provide

[Page 22]
6.5.  Endpoint Cost Service Example

   If the ALTO client expects the routing state information between
   endpoints, it can also query the "default-endpoint-cost-map" resource
   which supports path vector.  In resposne, the extended "vtag" field

>>> resposne =3D> response

[Page 23]
6.6.  Network Element Property Map Example # 1

   After the client send the query to the Multi-Cost Filtered Cost Map
   "filtered-multi-cost-map" and get the response with query-id "query1"
   (See Section 6.4).  The client send request to the "ane-property-map-

[Page 24]
6.7.  Network Element Property Map Example # 2

   After the client send the query to the Endpoint Cost Service
   "default-endpoint-cost-map" and get the response with query-id
   "query2" (See Section 6.5).  The client send request to the "ane-

>>> The client send =3D> The client sends

[Page 27]
9.3.  Snapshot and real-time update

   As the suggested workflow mentioned in Section 6.1, the properties of
   the abstract network elements are computed ahead of the query of
   these properties.  So the properties of abstract network elements are
   likely to be snapshot rather than realt-time value when queried.

>>> (a) snapshot, (a) real-time value, realt-time =3D> real-time

10.  Security Considerations

   We can identify multiple potential security issues.  A main security

>>> A main =3D> The main

   issue is network privacy, as the path-vector information may reveal
   more network internal structures than the more abstract single-node
   abstraction.  The network should consider protection mechanisms to
   reduce information exposure, in particular, in settings where the
   network and the application do not belong to the same trust domain.
   On the other hand, in a setting of the same trust domain, a key
   benefit of the path-vector abstraction is reduced information
   transfer from the network to the application.


Best Regards,
Shenshen

--f403043c490c81dcd20553065c1d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Dear authors of alto-path-vector and all,</div><div><=
br></div><div>After reviewing this draft, I have two comments:</div><div><b=
r></div><div>1. To avoid confusion, I suggest replacing every network eleme=
nt (NE) by=C2=A0</div><div>network abstract element (ANE), since every netw=
ork element in this draft=C2=A0</div><div>is &quot;abstract&quot; network e=
lement.=C2=A0</div><div>=C2=A0 =C2=A0An alternative solution is to remove A=
NE. The network element is=C2=A0</div><div>&quot;abstract&quot; according t=
o the definition in Wikipedia (&quot;A network element=C2=A0</div><div>is u=
sually defined as a manageable logical entity uniting one or more=C2=A0</di=
v><div>physical devices.&quot;), which makes it redundant to emphasize &quo=
t;abstract&quot; so=C2=A0</div><div>many times.</div><div><br></div><div>2.=
 The title of section 4.4 should be &quot;Query-specific Attribute&quot;, w=
hich=C2=A0</div><div>is the noun this section introduced. And the title of =
section 6.4 should=C2=A0</div><div>be &quot;Filtered Cost Map Example&quot;=
 corresponding to section 5.8.</div><div><br></div><div>Here is a list of t=
ypos (comments are marked with &quot;&gt;&gt;&gt;&quot;):</div><div><br></d=
iv><div>[Page 3]</div><div>=C2=A0 =C2=A0 =C2=A05.8.=C2=A0 Filtered Cost Map=
 Extensions =C2=A0. . . . . . . . . . . . . . =C2=A012</div><div>=C2=A0 =C2=
=A0 =C2=A0 =C2=A05.8.1.=C2=A0 Capabilities =C2=A0. . . . . . . . . . . . . =
. . . . . . . =C2=A012</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A05.8.2.=C2=A0 Ac=
cept Input Parameters . . . . . . . . . . . . . . . =C2=A013</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A05.8.3.=C2=A0 Propertymap . . . . . . . . . . . . . =
. . . . . . . . =C2=A014</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A05.8.4.=C2=A0 =
Response =C2=A0. . . . . . . . . . . . . . . . . . . . . . =C2=A014</div><d=
iv>=C2=A0 =C2=A0 =C2=A05.9.=C2=A0 Endpoint Cost Service Extensions =C2=A0. =
. . . . . . . . . . . =C2=A014</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A05.9.1.=
=C2=A0 Capabilities =C2=A0. . . . . . . . . . . . . . . . . . . . =C2=A015<=
/div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A05.9.2.=C2=A0 Accept Input Parameters .=
 . . . . . . . . . . . . . . =C2=A015</div><div><br></div><div>&gt;&gt;&gt;=
 Accept Input Parameters =3D&gt; Acceptable Input Parameters</div><div><br>=
</div><div>[Page 3]</div><div>=C2=A07.=C2=A0 Compatibility . . . . . . . . =
. . . . . . . . . . . . . . . . =C2=A025</div><div><br></div><div>[Page 25]=
</div><div>=C2=A07.=C2=A0 Compatibility</div><div><br></div><div>&gt;&gt;&g=
t; Compatibility =3D&gt; Compatibility Considerations/Compatibilities</div>=
<div><br></div><div>[Page 4, 5]</div><div>=C2=A0 =C2=A0The document is orga=
nized as follows.=C2=A0 Section 3 gives an example of</div><div>=C2=A0 =C2=
=A0flow scheduling to illustrate the need to introduce cost mode &quot;path=
-</div><div>=C2=A0 =C2=A0vector&quot; and cost metric &quot;ane&quot;.=C2=
=A0 Section 4 gives an overview of the</div><div>=C2=A0 =C2=A0path-vector e=
xtension.=C2=A0 Section 5 specifies the new cost mode and</div><div>=C2=A0 =
=C2=A0cost metric, new domain type, entity properties and protocol</div><di=
v>=C2=A0 =C2=A0extensions for (Filtered) Cost Maps and Endpoint Cost Servic=
es.</div><div>=C2=A0 =C2=A0Section 6 presents several examples.=C2=A0 Secti=
on 7 discusses the</div><div>=C2=A0 =C2=A0compatibility issues with some ot=
her proposed ALTO extensions.</div><div>=C2=A0 =C2=A0Section 8 discusses th=
e time to live problem.=C2=A0 Section 9 discusses</div><div>=C2=A0 =C2=A0se=
veral design decisions.=C2=A0 Section 10 and Section 11 discusses about</di=
v><div><br></div><div>&gt;&gt;&gt; discusses about =3D&gt; discusses</div><=
div><br></div><div>=C2=A0 =C2=A0security and IANA Considerations.</div><div=
><br></div><div>2.=C2=A0 Terminology</div><div><br></div><div>=C2=A0 =C2=A0=
This document uses the following terms: Network Element, Network</div><div>=
=C2=A0 =C2=A0Element Name, Network Element Property, Network Element Proper=
ty Map</div><div>=C2=A0 =C2=A0and Path Vector.</div><div><br></div><div>=C2=
=A0 =C2=A0o =C2=A0Network Element (NE): A Network Element is an abstract ne=
twork</div><div>=C2=A0 =C2=A0 =C2=A0 element, which can be a link, a networ=
k switching device, or a set</div><div>=C2=A0 =C2=A0 =C2=A0 of devices.</di=
v><div><br></div><div>=C2=A0 =C2=A0o =C2=A0Network Element Name (NEN): The =
id of a NE.=C2=A0 It can be referenced</div><div><br></div><div>&gt;&gt;&gt=
; a NE =3D&gt; an NE (which pronounced as [=C9=9Bn&#39;i=CB=90])</div><div>=
<br></div><div>=C2=A0 =C2=A0 =C2=A0 by Cost Map, Filtered Cost Map, Endpoin=
t Cost Service and Property</div><div>=C2=A0 =C2=A0 =C2=A0 Map.</div><div><=
br></div><div>=C2=A0 =C2=A0o =C2=A0Network Element Property (NEP): The prop=
erty of a NE.=C2=A0 It can be</div><div>=C2=A0 =C2=A0 =C2=A0 the available =
bandwidth of a link, the delay or other available</div><div>=C2=A0 =C2=A0 =
=C2=A0 properties.</div><div><br></div><div>[Page 10]</div><div>5.4.2.=C2=
=A0 Domain-Specific Entity Addresses</div><div><br></div><div>=C2=A0 =C2=A0=
The entity address of ane domain is encoded as a JSON string.=C2=A0 The</di=
v><div>=C2=A0 =C2=A0string MUST be no more than 64 characters, and it MUST =
NOT contain</div><div>=C2=A0 =C2=A0characters other than US-ASCII alphanume=
ric characters</div><div>=C2=A0 =C2=A0(U+0030-U+0039, U+0041-U+005A, and U+=
0061-U+007A), the hyphen (&#39;-&#39;,</div><div>=C2=A0 =C2=A0U+002D), the =
colon (&#39;:&#39;, U+003A), the at sign (&#39;@&#39;, code point</div><div=
>=C2=A0 =C2=A0U+0040), the low line (&#39;_&#39;, U+005F), or the &#39;.&#3=
9; separator (U+002E).</div><div>=C2=A0 =C2=A0The &#39;.&#39; separator is =
reserved for future use and MUST NOT be used</div><div>=C2=A0 =C2=A0unless =
specifically indicated in this document, or an extension</div><div><br></di=
v><div>&gt;&gt;&gt; delete the comma before &quot;or&quot; (since there&#39=
;re only two items in a series)</div><div>=C2=A0 =C2=A0document.</div><div>=
<br></div><div>[Page 16]</div><div>6.1.=C2=A0 Workflow</div><div><br></div>=
<div>=C2=A0 =C2=A0o =C2=A0Send the GET request for the whole Information Re=
source Directory.</div><div><br></div><div>=C2=A0 =C2=A0o =C2=A0Look for th=
e resource of the (Filtered) Cost Map/Endpoint Cost</div><div>=C2=A0 =C2=A0=
 =C2=A0 Service which contains the path-vector cost type and get the</div><=
div><br></div><div>&gt;&gt;&gt; get =3D&gt; gets</div><div><br></div><div>=
=C2=A0 =C2=A0 =C2=A0 resource id of the property map.</div><div><br></div><=
div>[Page 20]</div><div>6.4.=C2=A0 Multi-Cost Filtered Cost Map Example</di=
v><div><br></div><div>=C2=A0 =C2=A0The following example presents the reque=
st and response of &quot;filtered-</div><div>=C2=A0 =C2=A0multi-cost-map&qu=
ot;.=C2=A0 In this example, the client is interested in the</div><div>=C2=
=A0 =C2=A0path-vector and numerical routing cost information.=C2=A0 The cli=
ent uses</div><div>=C2=A0 =C2=A0&quot;or-constraints&quot; but all the resu=
lts satisfy the conditions.=C2=A0 In</div><div>=C2=A0 =C2=A0resposne, the e=
xtended &quot;vtag&quot; field is included in &quot;meta&quot; to provide</=
div><div><br></div><div>[Page 22]</div><div>6.5.=C2=A0 Endpoint Cost Servic=
e Example</div><div><br></div><div>=C2=A0 =C2=A0If the ALTO client expects =
the routing state information between</div><div>=C2=A0 =C2=A0endpoints, it =
can also query the &quot;default-endpoint-cost-map&quot; resource</div><div=
>=C2=A0 =C2=A0which supports path vector.=C2=A0 In resposne, the extended &=
quot;vtag&quot; field</div><div><br></div><div>&gt;&gt;&gt; resposne =3D&gt=
; response</div><div><br></div><div>[Page 23]</div><div>6.6.=C2=A0 Network =
Element Property Map Example # 1</div><div><br></div><div>=C2=A0 =C2=A0Afte=
r the client send the query to the Multi-Cost Filtered Cost Map</div><div>=
=C2=A0 =C2=A0&quot;filtered-multi-cost-map&quot; and get the response with =
query-id &quot;query1&quot;</div><div>=C2=A0 =C2=A0(See Section 6.4).=C2=A0=
 The client send request to the &quot;ane-property-map-</div><div><br></div=
><div>[Page 24]</div><div>6.7.=C2=A0 Network Element Property Map Example #=
 2</div><div><br></div><div>=C2=A0 =C2=A0After the client send the query to=
 the Endpoint Cost Service</div><div>=C2=A0 =C2=A0&quot;default-endpoint-co=
st-map&quot; and get the response with query-id</div><div>=C2=A0 =C2=A0&quo=
t;query2&quot; (See Section 6.5).=C2=A0 The client send request to the &quo=
t;ane-</div><div><br></div><div>&gt;&gt;&gt; The client send =3D&gt; The cl=
ient sends</div><div><br></div><div>[Page 27]</div><div>9.3.=C2=A0 Snapshot=
 and real-time update</div><div><br></div><div>=C2=A0 =C2=A0As the suggeste=
d workflow mentioned in Section 6.1, the properties of</div><div>=C2=A0 =C2=
=A0the abstract network elements are computed ahead of the query of</div><d=
iv>=C2=A0 =C2=A0these properties.=C2=A0 So the properties of abstract netwo=
rk elements are</div><div>=C2=A0 =C2=A0likely to be snapshot rather than re=
alt-time value when queried.</div><div><br></div><div>&gt;&gt;&gt; (a) snap=
shot, (a) real-time value, realt-time =3D&gt; real-time</div><div><br></div=
><div>10.=C2=A0 Security Considerations</div><div><br></div><div>=C2=A0 =C2=
=A0We can identify multiple potential security issues.=C2=A0 A main securit=
y</div><div><br></div><div>&gt;&gt;&gt; A main =3D&gt; The main</div><div><=
br></div><div>=C2=A0 =C2=A0issue is network privacy, as the path-vector inf=
ormation may reveal</div><div>=C2=A0 =C2=A0more network internal structures=
 than the more abstract single-node</div><div>=C2=A0 =C2=A0abstraction.=C2=
=A0 The network should consider protection mechanisms to</div><div>=C2=A0 =
=C2=A0reduce information exposure, in particular, in settings where the</di=
v><div>=C2=A0 =C2=A0network and the application do not belong to the same t=
rust domain.</div><div>=C2=A0 =C2=A0On the other hand, in a setting of the =
same trust domain, a key</div><div>=C2=A0 =C2=A0benefit of the path-vector =
abstraction is reduced information</div><div>=C2=A0 =C2=A0transfer from the=
 network to the application.</div><div><br></div><div><br></div><div>Best R=
egards,</div><div>Shenshen</div><div><br></div></div>

--f403043c490c81dcd20553065c1d--


From nobody Wed Jun 28 18:01:13 2017
Return-Path: <geng.li@yale.edu>
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 5E22D126C83; Wed, 28 Jun 2017 18:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yale.edu
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 JaqqpO1apEEP; Wed, 28 Jun 2017 18:01:10 -0700 (PDT)
Received: from mx0b-00135301.pphosted.com (mx0b-00135301.pphosted.com [148.163.159.240]) (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 CE13012708C; Wed, 28 Jun 2017 18:01:08 -0700 (PDT)
Received: from pps.filterd (m0109490.ppops.net [127.0.0.1]) by mx0b-00135301.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v5T1087U002098; Wed, 28 Jun 2017 21:01:06 -0400
Authentication-Results: ppops.net; spf=pass smtp.mailfrom=geng.li@yale.edu
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0055.outbound.protection.outlook.com [216.32.180.55]) by mx0b-00135301.pphosted.com with ESMTP id 2bcjd5rhgg-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 28 Jun 2017 21:01:06 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=f4qRg3ckB02LMn2x61pS/aYZuXn0+KkA+wQlussSAgg=; b=B1UH4Qg6/bnO2l1YRI84wBYVbDDQ9yjIu9lR1lh/Kv8+uk8MNMpkIG2X5vCJKU7isW6Q3Luh43F16sQu4pmS9UlJGaNWbnVPFjqPhKonVrMUlRgqbeu8a4WlFla9LRYq/CXSmFf/euq64Mow7gKw/9V45lLAo3isNqljg5Kc1ME=
Received: from CY4PR08MB3526.namprd08.prod.outlook.com (10.171.254.13) by CY4PR08MB3527.namprd08.prod.outlook.com (10.171.254.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.11; Thu, 29 Jun 2017 01:01:03 +0000
Received: from CY4PR08MB3526.namprd08.prod.outlook.com ([10.171.254.13]) by CY4PR08MB3526.namprd08.prod.outlook.com ([10.171.254.13]) with mapi id 15.01.1220.014; Thu, 29 Jun 2017 01:01:03 +0000
From: "Li, Geng" <geng.li@yale.edu>
To: "alto@ietf.org" <alto@ietf.org>, "draft-ietf-alto-cost-calendar@ietf.org" <draft-ietf-alto-cost-calendar@ietf.org>
Thread-Topic: Review on draft-ietf-alto-cost-calendar-01 by Geng
Thread-Index: AQHS8HMuQLzTwfvpkkCJkJ4bp1yyrQ==
Date: Thu, 29 Jun 2017 01:01:03 +0000
Message-ID: <CY4PR08MB3526BFB8A5CA44375C4FED8191D20@CY4PR08MB3526.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=yale.edu;
x-originating-ip: [2601:180:e:532:4ac:3e63:c05f:7ec5]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR08MB3527; 7:u34QYQXiLN6RMPenolYYIo/0r9n+sI6TkrOh56TXHf2tUa21eL3q1bntaWMBcoEFLsXKxDZLgoQVNszeFdJAY620Mnn0FSPah2Sp+TbT6TESAs+x4sCPzccvn9qSmmk+THH0Wr8rPUpTexJc28bfaspIhX0KxUke7bYzJe8TxHcMzJsaJipOvivOxunb1jrVKLfSukaDmrDKkRGzbmj3obGGIg+NQR7Meb4O1p97PXnD534WDc7V+c9On5J1xu6I5g09avG5J65WroE/zpBUuc5VYgHW3Z8V1fVDTOKScMYdXIfvDE5rLHXPlliy6wJE2SLMKkmN0lcfoat3MD1oHSXTKdN7rEFz5j8vpNIAO40EWcGi+f8OlR0PP/x9rroKG3Xbv6zy61TVaV0ARBSBPfEXJgwYHiEcbx6mq+YuyLHeajU4SH0hKUuQFEjLSvVZf8BFEpeA5cjiBp/xiXuNM+MZ5/Hqm3aJ9p+5efZIP8bY+G3AXYWIToFGHUbFcSvbYvBDZLh2cBVboCvPPR1r/4QHSyhMLwV56va9q5p/oHyYR/oEfqn4aAJHbHZ3fdNO5obnxRnAUnBs6TLpdD23Gcv1CauBwWbdUtqSl6CLXi4f5NpfG4aBVftuSOwnmDoK7L5Q1BwknjA8qAv4janSEPoCDpY6ybnrqJAJutBg8sB8O8qxRYBd9unAHLGyxRcXcMbAuNd65kXXEIno4blGNTyMCovNqzju2HyaGkw+pw/dj3nWEzTlXEMED9dm5PeSAq/4DXNDnwCgkmp0nMjFWFoHOcJv/7FnJ2TK0merRos=
x-ms-office365-filtering-correlation-id: 112ed880-93d1-4ee3-6683-08d4be8a50d9
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:CY4PR08MB3527; 
x-ms-traffictypediagnostic: CY4PR08MB3527:
x-microsoft-antispam-prvs: <CY4PR08MB3527F91F826C6F4E2583800C91D20@CY4PR08MB3527.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(236129657087228)(48057245064654)(148574349560750)(92977632026198);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(100000703101)(100105400095)(93006095)(93001095)(6041248)(20161123558100)(20161123562025)(20161123555025)(20161123564025)(201703131423075)(201702281528075)(201702281529075)(201703061421075)(201703061406153)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY4PR08MB3527; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY4PR08MB3527; 
x-forefront-prvs: 0353563E2B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(39400400002)(39850400002)(39410400002)(39840400002)(8936002)(3660700001)(7696004)(53336002)(88552002)(53936002)(14454004)(6116002)(2906002)(2900100001)(6506006)(8676002)(75432002)(38730400002)(6436002)(25786009)(86362001)(6606003)(55016002)(2501003)(19627405001)(413944005)(77096006)(102836003)(99286003)(54896002)(9686003)(189998001)(478600001)(230783001)(7736002)(54356999)(50986999)(81166006)(5660300001)(3280700002)(33656002)(450100002)(74316002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR08MB3527; H:CY4PR08MB3526.namprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY4PR08MB3526BFB8A5CA44375C4FED8191D20CY4PR08MB3526namp_"
MIME-Version: 1.0
X-OriginatorOrg: yale.edu
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jun 2017 01:01:03.5460 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: dd8cbebb-2139-4df8-b411-4e3e87abeb5c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR08MB3527
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-29_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706290014
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/47FrwhlCpcqd_urcfKYo65FuZGg>
Subject: [alto] Review on draft-ietf-alto-cost-calendar-01 by Geng
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: Thu, 29 Jun 2017 01:01:12 -0000

--_000_CY4PR08MB3526BFB8A5CA44375C4FED8191D20CY4PR08MB3526namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Dear authors,



Your work on cost calendar makes a lot of sense to me, and here are some co=
mments I have.



Issues:

1. In the 4th paragraph of section 1 (Page 4), here is supposed to introduc=
e the advantages of cost calendar. I would like to add another significant =
advantage which is the reduction of the frequent information exchange betwe=
en ALTO client and ALTO server. And I think it may be the salient benefit t=
hat leads to saving the network resources for ALTO protocol.

2. In section 2.2.1, the word =93time-sensitive=94 comes up several times, =
but what is the exact definition for =93time-sensitive=94? Maybe I=92m wron=
g, but I reckon it is used to describe the data for real-time service. I su=
ggest the authors can give a definition and examples here, or provide the r=
eferences where the word is interpreted.

3. I think maybe the authors missed a point which many audiences are concer=
ned about. When the network state is getting changed by e.g., link failures=
, node crashed, and if there is a conflict between the cost calendar that h=
as already been conveyed and the current new cost map, then how the client =
can be aware of it? The ALTO server needs to notify the clients before they=
 schedule data transfers according to the old cost calendar.



Typos:

1. In the first line of section 3.1, there is a redundant space before the =
comma.

2. At the end of the 3rd paragraph of section 3.1,  =93ressources=94 =3D=3D=
> =93resources=94.



Hope these are helpful.



Best, Geng

Computer Science, Yale

--_000_CY4PR08MB3526BFB8A5CA44375C4FED8191D20CY4PR08MB3526namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" dir=3D"ltr" style=3D"font-size: 12pt; colo=
r: rgb(0, 0, 0); font-family: Calibri,Helvetica,sans-serif,&quot;EmojiFont&=
quot;,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;,NotoColorEmo=
ji,&quot;Segoe UI Symbol&quot;,&quot;Android Emoji&quot;,EmojiSymbols;">
<p></p>
<div>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">Dear authors,</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">&nbsp;</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">Your work on cost calendar makes a lot of sense to me,=
 and here are some comments I have.</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">&nbsp;</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">Issues:</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">1. In the 4th paragraph of section 1 (Page 4), here is=
 supposed to introduce the advantages of cost calendar. I would like to add=
 another significant advantage which is the reduction of the frequent infor=
mation exchange between ALTO client
 and ALTO server. And I think it may be the salient benefit that leads to s=
aving the network resources for ALTO protocol.</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">2. In section 2.2.1, the word =93time-sensitive=94 com=
es up several times, but what is the exact definition for =93time-sensitive=
=94? Maybe I=92m wrong, but I reckon it is used to describe the data for re=
al-time service. I suggest the authors can give
 a definition and examples here, or provide the references where the word i=
s interpreted.</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">3. I think maybe the authors missed a point which many=
 audiences are concerned about. When the network state is getting changed b=
y e.g., link failures, node crashed, and if there is a conflict between the=
 cost calendar that has already been
 conveyed and the current new cost map, then how the client can be aware of=
 it? The ALTO server needs to notify the clients before they schedule data =
transfers according to the old cost calendar.</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">&nbsp;</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">Typos:</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">1. In the first line of section 3.1, there is a redund=
ant space before the comma.</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">2. At the end of the 3rd paragraph of section 3.1, <sp=
an style=3D"">
&nbsp;</span></span><span style=3D"font-family:&#23435;&#20307;">=93</span>=
<span lang=3D"EN-US">ressources=94 =3D=3D&gt; =93resources=94.</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">&nbsp;</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">Hope these are helpful.</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">&nbsp;</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">Best, Geng</span></p>
<p style=3D"margin:0cm 0cm 0.0001pt; text-align:justify; font-size:14pt; fo=
nt-family:&quot;Times New Roman&quot;; color:black">
<span lang=3D"EN-US">Computer Science, Yale</span></p>
</div>
<p></p>
</div>
</body>
</html>

--_000_CY4PR08MB3526BFB8A5CA44375C4FED8191D20CY4PR08MB3526namp_--


From nobody Wed Jun 28 18:34:35 2017
Return-Path: <geng.li@yale.edu>
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 99CC5129AE9; Wed, 28 Jun 2017 18:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yale.edu
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 2GjoyfC8oEHQ; Wed, 28 Jun 2017 18:34:32 -0700 (PDT)
Received: from mx0a-00135301.pphosted.com (mx0a-00135301.pphosted.com [67.231.145.237]) (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 6600A126E64; Wed, 28 Jun 2017 18:34:32 -0700 (PDT)
Received: from pps.filterd (m0109486.ppops.net [127.0.0.1]) by mx0b-00135301.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v5T1YEtV021009; Wed, 28 Jun 2017 21:34:30 -0400
Authentication-Results: ppops.net; spf=pass smtp.mailfrom=geng.li@yale.edu
Received: from nam01-sn1-obe.outbound.protection.outlook.com (mail-sn1nam01lp0112.outbound.protection.outlook.com [207.46.163.112]) by mx0b-00135301.pphosted.com with ESMTP id 2bcjmygk7d-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 28 Jun 2017 21:34:30 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=FMtPFliL9fHOo/AyjYtdXn0wpMl7nSY/0JxOU3a27/A=; b=swcUe4GE603saJDVpE60iPBOtfruTSKzK5NwLLwNoue4dCPAXx/DGW9RMplWmBjO1YuloNGru+Mi0yeYtVqaXU/MmqDeExFng2B01rQ+0M7MPBoiFC5aKXbNrbEUjfjTXjLyXjyvmLMVPh0jwv6760fs9UrE6iKGLcE3pXGi4oY=
Received: from CY4PR08MB3526.namprd08.prod.outlook.com (10.171.254.13) by CY4PR08MB3525.namprd08.prod.outlook.com (10.171.254.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.11; Thu, 29 Jun 2017 01:34:28 +0000
Received: from CY4PR08MB3526.namprd08.prod.outlook.com ([10.171.254.13]) by CY4PR08MB3526.namprd08.prod.outlook.com ([10.171.254.13]) with mapi id 15.01.1220.014; Thu, 29 Jun 2017 01:34:28 +0000
From: "Li, Geng" <geng.li@yale.edu>
To: "alto@ietf.org" <alto@ietf.org>, "draft-ietf-alto-performance-metrics@ietf.org" <draft-ietf-alto-performance-metrics@ietf.org>
Thread-Topic: Review on draft-ietf-alto-performance-metrics-01 by Geng
Thread-Index: AQHS8HfYt8rCC6ciPE6maaEoxvOQyw==
Date: Thu, 29 Jun 2017 01:34:28 +0000
Message-ID: <CY4PR08MB3526919211B51665A5855A5091D20@CY4PR08MB3526.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=yale.edu;
x-originating-ip: [2601:180:e:532:4ac:3e63:c05f:7ec5]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR08MB3525; 7:YN2WzlJBHkzdjADyDC5w0Ccv3o0IODmLygrlmD7GOqJi+cU0GJJCzPV4owqFXbclSRlJ/U83a28rVK+PY+3bcLt8uB1pQEnB3hG5jCtuWU46lK+EhXGS32Axbu8/0d4hMiRLLT1xR2JqxsMVnKc29zWg9LyE2le29tAsFZPzJFU+RhSL7tdxzJG+/wVI1K5Qsa2m1LXrbdpVTQx3zsvcoQcb103kOUBvy6yH+8lZDgntgWI0rRQ3Nh2TzmTIqTdRnZgIj9Q32s5TgWmjNSigxPxrvigVnc0AvssQdM/OfUJ6xqmLo+TefF5ayHJPB05BAbCXcHrmC7PbBcY/DOR6ukWtdG00/psfZKlDbAVPuzGSAy6tQOGXVX4XKGMsHlYUZnKUoFUKfqI+0ONsXK+T9LK4ND5QIc12FgV+vwGmt5bNMzFAH6qGistlillj0UFifrrPmyrW0HNQCZpUse/TIF8efe+vLJxKvGxAjhBrLFIGypBjb+WMnNN3MOhZEtFmWE+VR6MYuFvh6RxZBpOe96aa9mViuLKnxtw0vlwE1ENYczBBs0eC6jgdR2vk7qhyAldEqmqieHlr8xlyc+umm3fVV7bGTH4i28yTFMtkbRPN7p2aSmCHi9DySEPLIq0j8DCy7yzIvf+Dta9q/CC1bbr3rU1HrJD1oJrsIAFA11XfKSb0keUZxsdJo7bn3b4sX3MAMlbZEGLNhu0khMbCx2fNwQ/IOw9FW3ToHgA+gglZkwfRH/2JwPTLZ4z/6F5Q97QkZzBv2uXi9SLflvGdxnmNb4k5oqXzspnpnu8YG+M=
x-ms-office365-filtering-correlation-id: 66afce5b-554d-4dac-a72b-08d4be8efbe8
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:CY4PR08MB3525; 
x-ms-traffictypediagnostic: CY4PR08MB3525:
x-microsoft-antispam-prvs: <CY4PR08MB35255E3D2D3E1BB9E019F1F491D20@CY4PR08MB3525.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(278428928389397)(236129657087228)(192374486261705)(48057245064654)(148574349560750)(92977632026198)(247924648384137);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(100000703101)(100105400095)(6041248)(20161123558100)(20161123564025)(201703131423075)(201702281528075)(201702281529075)(201703061421075)(201703061406153)(20161123562025)(20161123560025)(20161123555025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY4PR08MB3525; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY4PR08MB3525; 
x-forefront-prvs: 0353563E2B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39840400002)(39860400002)(39410400002)(39450400003)(39400400002)(39850400002)(50986999)(54356999)(230783001)(14454004)(413944005)(75432002)(33656002)(8676002)(81166006)(7736002)(77096006)(5660300001)(8936002)(19627405001)(478600001)(53336002)(25786009)(7696004)(450100002)(6606003)(74316002)(3660700001)(88552002)(9686003)(3280700002)(38730400002)(54896002)(2906002)(189998001)(53936002)(99286003)(2900100001)(6436002)(102836003)(6506006)(6116002)(2501003)(86362001)(55016002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR08MB3525; H:CY4PR08MB3526.namprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY4PR08MB3526919211B51665A5855A5091D20CY4PR08MB3526namp_"
MIME-Version: 1.0
X-OriginatorOrg: yale.edu
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jun 2017 01:34:28.5143 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: dd8cbebb-2139-4df8-b411-4e3e87abeb5c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR08MB3525
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-29_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706290023
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/-leJxV7kgyY9ycmo0zdGNoMa14E>
Subject: [alto] Review on draft-ietf-alto-performance-metrics-01 by Geng
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: Thu, 29 Jun 2017 01:34:35 -0000

--_000_CY4PR08MB3526919211B51665A5855A5091D20CY4PR08MB3526namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Dear authors,



Your work is quite excellent, and here are some suggestions I have.



1. The ALTO server should have the capability to track and record the most =
frequently used or requested cost metrics of each ALTO client. I=92m not su=
re if it is true, that each client may only run one or two certain applicat=
ions at most of the time. Then, the benefit is that the ALTO server can pre=
pare the cost metrics in advanced and respond the clients fast after receiv=
ing the request.

2. Another benefit of recording the type of cost metrics of each client is =
that the ALTO server can detect abnormal behavior of client or application,=
 such as database resource leaks, illegal occupation, or other security iss=
ues.

3. A variety of performance cost metrics also raise an interesting scheduli=
ng problem. For example, client =93A=94 requests two metrics, client =93B=
=94 just requests one, and client =93C=94 requests three metrics, then how =
the ALTO server schedules to respond them in the constraint of given resour=
ces for workload processing and network transmitting. And for each client, =
what is the order of the cost metric types to be returned?



Hope these are helpful.



Best, Geng

Computer Science, Yale

--_000_CY4PR08MB3526919211B51665A5855A5091D20CY4PR08MB3526namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p></p>
<div>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">Dear authors,</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">&nbsp;</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">Your work is quite excellent, and here are some sugges=
tions I have.</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">&nbsp;</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">1. The ALTO server should have the capability to track=
 and record the most frequently used or requested cost metrics of each ALTO=
 client. I=92m not sure if it is true, that each client may only run one or=
 two certain applications at most of
 the time. Then, the benefit is that the ALTO server can prepare the cost m=
etrics in advanced and respond the clients fast after receiving the request=
.</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">2. Another benefit of recording the type of cost metri=
cs of each client is that the ALTO server can detect abnormal behavior of c=
lient or application, such as database resource leaks, illegal occupation, =
or other security issues.</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">3. A variety of performance cost metrics also raise an=
 interesting scheduling problem. For example, client =93A=94 requests two m=
etrics, client =93B=94 just requests one, and client =93C=94 requests three=
 metrics, then how the ALTO server schedules to
 respond them in the constraint of given resources for workload processing =
and network transmitting. And for each client, what is the order of the cos=
t metric types to be returned?</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">&nbsp;</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">Hope these are helpful.</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">&nbsp;</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">Best, Geng</span></p>
<p style=3D"margin: 0cm 0cm 0.0001pt; text-align: justify; font-size: 14pt;=
 font-family: &quot;Times New Roman&quot;; color: black;">
<span lang=3D"EN-US">Computer Science, Yale</span></p>
</div>
<p></p>
</div>
</body>
</html>

--_000_CY4PR08MB3526919211B51665A5855A5091D20CY4PR08MB3526namp_--


From nobody Wed Jun 28 18:46:01 2017
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 A415F127419; Wed, 28 Jun 2017 18:45:59 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 O6xtRUPbP_er; Wed, 28 Jun 2017 18:45:57 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255072.outbound.protection.outlook.com [40.92.255.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C176126E64; Wed, 28 Jun 2017 18:45:57 -0700 (PDT)
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=uO7B29yABQexhkcM3IYmbLKRllSPbr3rvkLLybr8HnE=; b=hbY86fMt0VIO+sZVE+cvM9CQEuNRIXqyeonK8F3qPbvuS9pjYHHuPy8GNKjfBwYTH6HB0BySzZWVMqi4NqqMDuc361Sk7JF4kvkQbmg/e7tct/aDGH3f3YQM6Q8yUxE+BIUUZCrlPKM5/Q4yvaF291Y2P5PCn21if4qeqOahs3vlodSFCRIJpqMzMXw3slrBsBfPvQgMKdFmWhLhpiod1nAux3raHgLnH5UG8th+LYso3ZX/p8sNSQdIj2KxqDxZ3E7Rl7VdHwOfRVpVJmrMLTYhi2wnXV1R3aYWbFnq1Oy0tCQNGzmq9ccNq7bucWJacbLCYgI1TFeDpykWEtegMg==
Received: from PU1APC01FT013.eop-APC01.prod.protection.outlook.com (10.152.252.58) by PU1APC01HT128.eop-APC01.prod.protection.outlook.com (10.152.253.57) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1199.9; Thu, 29 Jun 2017 01:45:54 +0000
Received: from PS1PR0302MB2457.apcprd03.prod.outlook.com (10.152.252.52) by PU1APC01FT013.mail.protection.outlook.com (10.152.252.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.9 via Frontend Transport; Thu, 29 Jun 2017 01:45:54 +0000
Received: from PS1PR0302MB2457.apcprd03.prod.outlook.com ([fe80::290a:8d10:d903:ff49]) by PS1PR0302MB2457.apcprd03.prod.outlook.com ([fe80::290a:8d10:d903:ff49%18]) with mapi id 15.01.1240.006; Thu, 29 Jun 2017 01:45:54 +0000
From: xin wang <xinwang2014@hotmail.com>
To: "draft-randriamasy-alto-cost-context@ietf.org" <draft-randriamasy-alto-cost-context@ietf.org>
CC: IETF ALTO <alto@ietf.org>, "draft-gao-alto-fcs@ietf.org" <draft-gao-alto-fcs@ietf.org>
Thread-Topic: =?Windows-1252?Q?Some_thinkings_about_=93ALTO_Contextual_Cost_Values=94?=
Thread-Index: AQHS8HknUko/b1Tu8ke5Ux/hvcIynQ==
Date: Thu, 29 Jun 2017 01:45:54 +0000
Message-ID: <PS1PR0302MB24576A66B1A751B6C5604477A8D20@PS1PR0302MB2457.apcprd03.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:EBD6A21EF0F30494C152ED4F1EECFBB14DA5380327FEAB5E817A184A87063C9F; UpperCasedChecksum:7498EC70F6BB9019C864BA605CD5E702DCE60C1E2A5F29BEC4A03D9162E5F246; SizeAsReceived:7314; Count:44
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [GNc8pQVe3wlrNh6dc/Am+KU9ByrULb+b]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; PU1APC01HT128; 7:iQS47GLVVXS+9b/iUzILqrHc3aRUXz99N/7NzFucj3HZZdL3eAfwABfdFRy3SZrIHJ6YSsNwB1GUTvELadVEz1tpYYJWuKJLgnaZ7njrnjZJZwTGtmp+3TrzMn/S1lv82dETpMl+EGhi4oQyb2kujWZ/KsZ++bxnsgEP8txwLl21/AiMQx7bY7rkJjVCD7qFFpAsV8dcyv0UXx4M3j+IuqiguP+SGP4S5/OswYQIGPgEtwWzxhFwiggdNx3aqERp/OZr9mjmjPPhtXx9PqtVrTbxGNzniZrJdyFz/kyvFnG5Bg05dKHzaA8BPDW1F/rScMEXwd/KhGIiPzTobfsTypcA9QmD8BN6kaGCi7J384OWI7CYncFfUyZN7mleBjHvYzMs58WfrsPgsjh11BaX5KhdJ+p4eADf/s43cftYekIvTt/+WtknXTbVEOWDz4VgNjaGw3DPFcOAyf3VhUSzQPq7VSCo12vM45bfGv4xURdr6Zf+8c/qW2CrupVZ5woRSygHVLqWmXwx8Yj0rtmLawIVUWrnaHw0jc+mIK85stoBxW483ZEbWg15q2q55UA4ALIZeHlF+dEg+MFB5MLRiBdApuiuKKg6fOfgoMW+Y0+rQutmHb6TU+GoaxcBJfbRBya6JVW5r6NNw2iKP+JuPna1Bc+d6tUxNcs6dbBO3cank6YbEnVVAC1E/0QAcIofUdJElpEJ71flD6EF4v+bf7nPQmWLWtFNq7oU9R/zS5YJLKpRBix1NugvPdSJoqUkuNbR9fuwh7SPow2Sf8M7Vg==
x-incomingheadercount: 44
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:PU1APC01HT128; H:PS1PR0302MB2457.apcprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 0cdfbcfa-e8fc-4a0d-c9ed-08d4be9094d1
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:PU1APC01HT128; 
x-ms-traffictypediagnostic: PU1APC01HT128:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:PU1APC01HT128; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:PU1APC01HT128; 
x-forefront-prvs: 0353563E2B
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_PS1PR0302MB24576A66B1A751B6C5604477A8D20PS1PR0302MB2457_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jun 2017 01:45:54.4458 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT128
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/8vPehw9s2oi13UaQ7ahgvzzo2rk>
Subject: [alto] =?windows-1252?q?Some_thinkings_about_=93ALTO_Contextual_C?= =?windows-1252?q?ost_Values=94?=
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: Thu, 29 Jun 2017 01:45:59 -0000

--_000_PS1PR0302MB24576A66B1A751B6C5604477A8D20PS1PR0302MB2457_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Dear authors of =93ALTO Contextual Cost Values=94,


There are already several reviews for your draft, and my thinking would be =
the potential collaboration with Flow Cost Service (fcs) (https://datatrack=
er.ietf.org/doc/draft-gao-alto-fcs/) which aims to extend ALTO query with O=
penFlow format. The flow concept in fcs goes beyond source, destination end=
points/PIDs, which makes fine-grained query service available. Your draft, =
from my perspective, also extends original ALTO query by adding context par=
ameters, such as =93RFcost=94. Data transmissions with different context pa=
rameters would be treated differently in networks. For example, flows with =
different network environments (e.g., wifi or cell) would have different de=
lays; flows with different timing would have different limitations. However=
, these constraints are missing in OpenFlow format. By merging the flow in =
fcs and the context in your draft, "context available=94 flow-based cost qu=
ery should be a generic solution. The "context available=94 flow extends or=
iginal flow in OpenFlow by adding context, such as environments, user-side =
limitations, and makes it more flexible to express requirements in differen=
t situations.

draft-gao-alto-fcs-01 - ALTO Extension: Flow-based Cost Query<https://datat=
racker.ietf.org/doc/draft-gao-alto-fcs/>
datatracker.ietf.org
ALTO Extension: Flow-based Cost Query (Internet-Draft, 2017)




Also there are some typos you may fix:

Page 4: =93advatageously=94 -> =93 advantageously=94;

Page 5: =93aforementionned=94 -> =93 aforementioned=94;

Page 6: =93unpredictible=94 -> =93unpredictable=94, =93patrameters=94 -> =
=93parameters=94, =93explicitely=94 -> =93explicitly=94;

Page 7: =93a an=94 -> =93an=94, =93the the=94 -> =93the=94, =93specfied=94 =
-> =93specified=94;

Page 15: add space in =93local=94ALTO;


Best,

Xin

--_000_PS1PR0302MB24576A66B1A751B6C5604477A8D20PS1PR0302MB2457_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Dear authors of =93ALTO Contextual Cost=
 Values=94,</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">There are already several reviews for y=
our draft, and my thinking would be the potential collaboration with&nbsp;F=
low Cost Service (fcs) (<a href=3D"https://datatracker.ietf.org/doc/draft-g=
ao-alto-fcs/" id=3D"LPlnk492048" previewremoved=3D"true"><span style=3D"tex=
t-decoration: underline; font-kerning: none; color: rgb(158, 74, 47); -webk=
it-text-stroke: 0px rgb(158, 74, 47);">https://datatracker.ietf.org/doc/dra=
ft-gao-alto-fcs/</span></a>)
 which aims to extend ALTO query with OpenFlow format. The flow concept in =
fcs goes beyond source, destination endpoints/PIDs, which makes fine-graine=
d query service available. Your draft, from my perspective, also extends or=
iginal ALTO query by adding context
 parameters, such as =93RFcost=94. Data transmissions with different contex=
t parameters would be treated differently in networks. For example, flows w=
ith different network environments (e.g., wifi or cell) would have differen=
t delays; flows with different timing
 would have different limitations. However, these constraints are missing i=
n OpenFlow format. By merging the flow in fcs and the context in your draft=
, &quot;context available=94 flow-based cost query should be a generic solu=
tion. The &quot;context available=94 flow extends
 original flow in OpenFlow by adding context, such as environments, user-si=
de limitations, and makes it more flexible to express requirements in diffe=
rent situations.</span></p>
<div id=3D"LPBorder_GT_14987003860860.9813944890004154" style=3D"margin-bot=
tom: 20px; overflow: auto; width: 100%; text-indent: 0px;">
<table id=3D"LPContainer_14987003860820.10917505597458965" role=3D"presenta=
tion" cellspacing=3D"0" style=3D"width: 90%; background-color: rgb(255, 255=
, 255); position: relative; overflow: auto; padding-top: 20px; padding-bott=
om: 20px; margin-top: 20px; border-top: 1px dotted rgb(200, 200, 200); bord=
er-bottom: 1px dotted rgb(200, 200, 200);">
<tbody>
<tr valign=3D"top" style=3D"border-spacing: 0px;">
<td id=3D"TextCell_14987003860840.21102919154976463" colspan=3D"2" style=3D=
"vertical-align: top; position: relative; padding: 0px; display: table-cell=
;">
<div id=3D"LPRemovePreviewContainer_14987003860840.6561049768471887"></div>
<div id=3D"LPTitle_14987003860840.8062142302916384" style=3D"top: 0px; colo=
r: rgb(0, 120, 215); font-weight: normal; font-size: 21px; font-family: wf_=
segoe-ui_light, &quot;Segoe UI Light&quot;, &quot;Segoe WP Light&quot;, &qu=
ot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial, sans-serif; line-he=
ight: 21px;">
<a id=3D"LPUrlAnchor_14987003860850.7789399182547609" href=3D"https://datat=
racker.ietf.org/doc/draft-gao-alto-fcs/" target=3D"_blank" style=3D"text-de=
coration: none;">draft-gao-alto-fcs-01 - ALTO Extension: Flow-based Cost Qu=
ery</a></div>
<div id=3D"LPMetadata_14987003860850.8615115919148415" style=3D"margin: 10p=
x 0px 16px; color: rgb(102, 102, 102); font-weight: normal; font-family: wf=
_segoe-ui_normal, &quot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial=
, sans-serif; font-size: 14px; line-height: 14px;">
datatracker.ietf.org</div>
<div id=3D"LPDescription_14987003860860.5004396247576073" style=3D"display:=
 block; color: rgb(102, 102, 102); font-weight: normal; font-family: wf_seg=
oe-ui_normal, &quot;Segoe UI&quot;, &quot;Segoe WP&quot;, Tahoma, Arial, sa=
ns-serif; font-size: 14px; line-height: 20px; max-height: 100px; overflow: =
hidden;">
ALTO Extension: Flow-based Cost Query (Internet-Draft, 2017)</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
<p></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0); min-height: 14px;">
<span style=3D"font-kerning: none;"></span><br>
</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Also there are some typos you may fix:<=
/span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 4: =93advatageously=94 -&gt; =93 a=
dvantageously=94;</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 5: =93aforementionned=94 -&gt; =93=
 aforementioned=94;</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 6: =93unpredictible=94 -&gt; =93un=
predictable=94, =93patrameters=94 -&gt; =93parameters=94, =93explicitely=94=
 -&gt; =93explicitly=94;</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 7: =93a an=94 -&gt; =93an=94, =93t=
he the=94 -&gt; =93the=94, =93specfied=94 -&gt; =93specified=94;</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;">Page 15: add space in =93local=94ALTO;<=
/span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
<span style=3D"font-kerning: none;"><br>
</span></p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
Best,</p>
<p style=3D"margin: 0px; font-style: normal; font-variant-ligatures: normal=
; font-variant-caps: normal; font-weight: normal; font-stretch: normal; fon=
t-size: 12px; line-height: normal; font-family: &quot;Helvetica Neue&quot;;=
 -webkit-text-stroke: rgb(0, 0, 0);">
Xin</p>
</div>
</body>
</html>

--_000_PS1PR0302MB24576A66B1A751B6C5604477A8D20PS1PR0302MB2457_--


From nobody Wed Jun 28 20:50:10 2017
Return-Path: <92yichenqian@tongji.edu.cn>
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 6AB091276AF; Wed, 28 Jun 2017 20:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 oBqG5mDPofMH; Wed, 28 Jun 2017 20:50:07 -0700 (PDT)
Received: from tongji.edu.cn (mailusrsvr1.tongji.edu.cn [202.120.164.61]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4227D126CBF; Wed, 28 Jun 2017 20:50:05 -0700 (PDT)
Received: from [192.168.3.40] (unknown [100.64.11.108]) by mailusersvr1 (Coremail) with SMTP id PaR4ygB320TpeFRZsLiXAA--.5705S2; Thu, 29 Jun 2017 11:50:02 +0800 (CST)
From: Yichen Qian <92yichenqian@tongji.edu.cn>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8EEB3F5-1CF6-4E6E-BE40-740BD5F2D46A@tongji.edu.cn>
Date: Thu, 29 Jun 2017 11:50:01 +0800
To: IETF ALTO <alto@ietf.org>, draft-randriamasy-alto-cost-context@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-CM-TRANSID: PaR4ygB320TpeFRZsLiXAA--.5705S2
X-Coremail-Antispam: 1UD129KBjvJXoWxAFy5Gw45Gr43Gw1xCFy8Zrb_yoW5tr18pr W5uFyUKFs8G3ZFk3s7Xw1vvF4rArWFya15W3sYy34UZ39xGF92vF4SgF4YyFnF9rW2qF1Y qr4jqryUZ34DZFJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUkjb7Iv0xC_KF4lb4IE77IF4wAFc2x0x2IEx4CE42xK8VAvwI8I cIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2 AK021l84ACjcxK6xIIjxv20xvE14v26w1j6s0DM28EF7xvwVC0I7IYx2IY6xkF7I0E14v2 6F4UJVW0owA2z4x0Y4vEx4A2jsIE14v26rxl6s0DM28EF7xvwVC2z280aVCY1x0267AKxV W0oVCq3wAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40EFcxC0VAKzVAqx4xG6I80ewAv 7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r 1j6r4UM4x0Y48IcxkI7VAKI48JMxAIw28IcxkI7VAKI48JMxAIw28IcVCjz48v1sIEY20_ Cr1UJr1UMxC20s026xCaFVCjc4AY6r1j6r4UMI8I3I0E5I8CrVAFwI0_Jr0_Jr4lx2IqxV Cjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUXVWUAwCIc40Y0x0EwIxGrwCI42IY 6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxVWUJVW8JwCI42IY6x AIw20EY4v20xvaj40_WFyUJVCq3wCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv 6xkF7I0E14v26r1j6r4UYxBIdaVFxhVjvjDU0xZFpf9x07j04E_UUUUU=
X-CM-SenderInfo: qrqrmmmu6w00xjmlhvlgxou0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/IFzUEXHIU8Diq0GGquaTL5yfh78>
Subject: [alto] Review of draft-randriamasy-alto-cost-context-01
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: Thu, 29 Jun 2017 03:50:09 -0000

Dear authors and all,

I think it's interesting to introduce wireless scenario into ALTO. =
Here's my review of this draft.

The draft introduces the cost calendar in providing the contextual cost =
(cell load), while it doesn=E2=80=99t elaborate how to use the calendar. =
One possible way is to use the calendar as a reference to do the =
prediction for the decision, while I wonder if it is accurate and useful =
for the user as much movement is involved in the wireless scenario and =
the cell load can be unpredictable.

Some detailed comments:=20
1.  Introduction
=E2=80=9CThis draft brings a use case where providing different values =
for a same cost metric can help in optimizing the application path =
selection.=E2=80=9D
- a same -> the same

=E2=80=9CThe present draft proposes to extend the cost information =
specified in [RFC7285] by providing, for a same cost metric, several =
possible cost values.=E2=80=9D
- a same -> the same

=E2=80=9CPrevious ALTO WG discussions have suggested to introduce "the =
ability to "name" cost maps =E2=80=A6=E2=80=9D
- suggested to introduce -> suggested introducing

2.1.  Use Case 1
=E2=80=9CThe UE thus can advatageously combine the non-real time ALTO =
information with the real-time UDI provided by the LTE network.=E2=80=9D
- advatageously -> advantageously

3.  Required ALTO extensions
=E2=80=9CThe aforementionned use cases can be supported with a few =
simple extensions to the ALTO protocol.=E2=80=9D
- aforementionned  -> aforementioned

=E2=80=9Cthese features would extend current proposals in the WG,that =
could be added to [draft-ietf-alto-performance-metrics]=E2=80=9D
- missing a space before =E2=80=9Cthat=E2=80=9D

4.  Design options and examples
=E2=80=9CContext attributes taking numerous or unpredictible values =
should be handled as values properties or metrics expressed in =
constraints.=E2=80=9D
- unpredictible -> unpredictable

4.2.  Example IRD
=E2=80=9CThe values of 'RFcost' are provided as a an ALTO Calendar as =
specified in [draft-ietf-alto-cost-calendar-00] in shorter time =
intervals.=E2=80=9C
- as a an ALTO Calendar -> as an ALTO Calendar

=E2=80=9CIn addition they differ, depending on the	the context =
values "uda" and "udna=E2=80=9D.=E2=80=9D
- on the the context -> on the context

=E2=80=9CBesides, the IRD provides metric 'routingcost' as a MUST =
specfied in [RFC7285]=E2=80=9D
- specfied -> specified

4.3.  Use case 1
=E2=80=9CAs a Network Map may cover a large number of cells, the =
Filtered Cost Map Service can be used to reduce data exchange and get =
information on a restricted number of cells, say PID1 and PID2.=E2=80=9D	=
				=09
- I think Cell1 and Cell2 may be more accurate here since they have been =
named =E2=80=9CCell-k=E2=80=9D

=E2=80=9CIn this scenario, C1 is limited by its uplink capacity, C2 is =
limited by its downlink capacity.=E2=80=9D
- I think the naming here for the cells is confused as there are both =
=E2=80=9CCell1=E2=80=9D and =E2=80=9CC1=E2=80=9D in this section. I =
suppose they refer to the same thing and can be represented in a =
consistent way.

4.4.2.  Network Map
- The request above has four (=E2=80=9Csrc=E2=80=9D,=E2=80=9Ddat=E2=80=9D)=
 pairs (Cell 1->1, 1->2, 2->1, 2->2), while in the response there are =
only cost maps of two pairs (Cell1->1, Cell2->2).

4.5.1.  Use case 2
=E2=80=9CThe ALTO Server will provide costs w.r.t. the AND combination =
accross and within arrays.=E2=80=9D
- accross -> across

5.  Deployment case
=E2=80=9CTo maintain scalability, the ALTO coverage network zone can be =
decomposed in one "local"ALTO Server part covering a restricted local =
network zone=E2=80=9D
- missing a space before =E2=80=9CALTO=E2=80=9D

Best wishes,
Eason=


From nobody Thu Jun 29 02:40:12 2017
Return-Path: <duhaizhou@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 7ADF612ECBD; Thu, 29 Jun 2017 02:40:09 -0700 (PDT)
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, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 hZyYbHrLEAkt; Thu, 29 Jun 2017 02:40:04 -0700 (PDT)
Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (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 91FFE12EC05; Thu, 29 Jun 2017 02:40:03 -0700 (PDT)
Received: by mail-wr0-x22c.google.com with SMTP id c11so186588523wrc.3; Thu, 29 Jun 2017 02:40:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7pxOlRO8wlZTntpZ0Z6h46tz0WFhGBqsaTTD6NLYr4Q=; b=EorVjsja0uxIbIHyiG8Eb0ehM2zOPHhNlAoIowba1N/6k6Y/ULhTFQygvk9VVBztpo VytyG1GH0ABNGbf2LFPmEzWAvA3PpasZs/AwY0MSB5Avd9HRXNifayZHBQkefNAd1wE/ zGN5Np7BHA/5798FqxFKFkktUokU0ltJkJC22ngJXNwm48IahKLmAVsn0cnGcjQg/LK+ JwD1OuAkYom4TgiolYHU2A2vy+XsDx5QcBP8TnsCt8q95kGpZMbe2eIdeXEcLLrJmks/ 9t+c9rZo30WcbAkLtiGWu2vFpJAwYd/a4PH8H/X/amPpPEJqMsc8nVUPa+TnPMOs1l/E H5ng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7pxOlRO8wlZTntpZ0Z6h46tz0WFhGBqsaTTD6NLYr4Q=; b=tDggABSrNgg0s7daZNR4eEwJX6rn2enl88us4mNoEAvHdz8W8Lo1g7esyvMtRoMib2 QLJfn3ZiHuE9dd4kSRwpiv1r7mUK/9R58N2Df511QyOiu24ecLKpJs2Q8chTVXT9pg5L 92X1c2NUoiDYHyzaWsHFmPVn5R5umYriPtnOPlW2vF6K6eyoEeKckKb1kjkPx5se1w6W GLhWUciI0ViwEF33la9zTgDJ32W8PE4ytMmpyhfaMJHANOGEUorxRy4YJUrsUx7g5W7s HGzaJVKkFXmfoYtMajyEjZDc96jmfkPK4aoNAR2v1TMbn87aao/wZPT2QyxHAFOflBG4 7C7w==
X-Gm-Message-State: AKS2vOwnZxNcqI7TzyoWzMfYGQGAnDzbJPu6/rdyXIIZsqPHCo9FBqt3 V0X0ZprxCfasZjvYlB2GvttUVTU+WNCZ
X-Received: by 10.223.160.68 with SMTP id l4mr6130240wrl.90.1498729201730; Thu, 29 Jun 2017 02:40:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.171.210 with HTTP; Thu, 29 Jun 2017 02:40:01 -0700 (PDT)
In-Reply-To: <CAOB1xS_3GD1p7_qkEfwBGQ131xLNQB+Njg6=4tZx_sMNo_52Hg@mail.gmail.com>
References: <CAKRjQSDOPoiWW_HCyawv34bkiN4H2y749i3vTCOc=3ngyyhaow@mail.gmail.com> <CAOB1xS_3GD1p7_qkEfwBGQ131xLNQB+Njg6=4tZx_sMNo_52Hg@mail.gmail.com>
From: Haizhou Du <duhaizhou@gmail.com>
Date: Thu, 29 Jun 2017 17:40:01 +0800
Message-ID: <CADdws+yHB1NfUt_iQB4nDTTAoyTkQHPWTKHWG6-f6ZDn1YPHTw@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>
Cc: draft-roome-alto-unified-props-new@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c065238af0de20553161598"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/fD6Do6aauoXNM5QoIgatnBqy1us>
Subject: Re: [alto] Review of draft-roome-alto-unified-props-new-00
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: Thu, 29 Jun 2017 09:40:10 -0000

--94eb2c065238af0de20553161598
Content-Type: text/plain; charset="UTF-8"

Hi all,
I reviewed the unified property map draft. I agree with all Shenshen and
Qiao's comments.  And I want to give some comments for Qiao's discussions:
 (1) how does property map handle dynamic entity, e.g., ane defined in the
path-vector draft?
I think we can handle Property Map of the dynamic entity in the path-vector
draft.  We can extend the ane property.
 (2) is the inheritance design in the property map draft too rigid?
I agree with Qiao. We can inherit all kinds of value for that
property, Including "null" in the Property Map. If the entity and his son
entity inherits a "null"  value, the ALTO server MAY  just omit all of them
from the root entity.
 (3) How should we modify/improve the designs of both path vector and
property map to make the whole solution a unified one?
I think we can extend the ane property in path vector draft. And we can
define the inheritance and hierarchy of ane property for unified one.

If you have any comments, please share with me? Thank you so much. In
addition, please see my other comments in the following.

*Page 5*
Note that entity addresses may NOT have a unique textual representation.
*[HZ] "may NOT" is not defined in RFC2119. "may NOT have a unique" -> "MAY
have different"*

*Page 10*

3.2.3.  Hierarchy And Inheritance


*[HZ]"And"->"and"*
*Page 23*
Accordingly, an ALTO Server should limit GET-mode property maps for to
properties which do not contain sensitive data.
*[HZ] "should" -> "SHOULD"*

On Wed, Jun 28, 2017 at 9:08 PM, Qiao Xiang <xiangq27@gmail.com> wrote:

> Hi Wendy, Richard and all,
>
> I reviewed the unified property map draft. I agree with
> all Shenshen's comments. In addition, please see my other comments in the
> following.
>
> In addition to the review, the key design questions I want to raise
> discussions are (1) how does property map handle dynamic entity, e.g., ane
> defined in the path-vector draft? (2) is the inheritance design in the
> property map draft too rigid? (see my comments marked with <QX??>) and (3)
> in the current path vector draft the ane is defined with no inheritance or
> hierarchy, but aggregating/compressing multiple ane's is an important
> process for the path vector service to reduce overhead and provide privacy
> of networks. how should we modify/improve the designs of both path vector
> and property map to make the whole solution a unified one. I will work on
> these three questions in the next few days and share my thoughts.
> Menawhile, would you please also share any comments/thoughts you may have?
> Thank you very much.
>
>
> *Reviews:*
> *Page 4*
>
>    This document proposes a new approach to ALTO properties.
> *<QX> "approach to ALTO properties" -> "approach to retrieve ALTO
> properties"*
>
>    Specifically, it defines two new resource types, namely Property Maps
>    and Filtered Property Maps.  The former are GET-mode resources which
>    return the property values for all entities in a domain, and are
>    analogous the ALTO's Network Map and Cost Map resources.  The latter
> *<QX> "analogous the ALTO's " -> "analogous to the ALTO's "*
>
>    are POST-mode resources which return the values for a set of
>    properties and entities requested by the client, and are analogous to
> *<QX> "the values for a set of properties and entities" -> "the values of
> a set of properties for a set of entities"*
>
>    ALTO's Filtered Network Maps and Filtered Cost Maps.
>
> *Page 5*
>
>    The format of the second part of an entity address depends on the
>    domain, and must be specified when registering a new domain.
> *<QX> "must" -> "MUST"*
>
>    Addresses may be hierarchical, and properties may be inherited based
>    on that hierarchy.  Again, the rules defining any hierarchy or
>    inheritance must be defined when the domain is registered.
> *<QX> "must" -> "MUST"*
>
>    Note that entity addresses do NOT have a unique textual
>    representation.  For example, the strings "ipv6:2001:db8::1" and
>    "ipv6:2001:db8:0:0:0:0:0:1" refer to the same entity.
> *<QX> "NOT" is not defined in RFC2119. "do NOT have a unique" -> "MAY have
> different"*
>
>    ...
>
>    Domain names must be registered with the IANA, and the format of the
>    entity addresses in that domain, as well as any hierarchical or
>    inheritance rules for those entities, must be specified at the same
>    time.
> *<QX> "must"->"MUST"*
>
>    ...
>
>    Property names are not specific to a domain, although some properties
>    may only be applicable for particular domains, and the interpretation
>    of the value may depend on the domain.  For example, suppose the
>    "geo-location" property is defined as the coordinates of a point,
>    encoded as (say) "latitude longitude [altitude]."  When applied to an
> *<QX> "as (say)" -> "as"*
>
> *Page 6*
>
>    ...
>
>    [RFC7285] recognizes that some properties may be specific to another
>    ALTO resource, such as a network map.  Accordingly [RFC7285] defines
>    the concept of "resource-specific endpoint properties"
>    (Section 10.8.1), and indicates that dependency by prefixing the
>    property name with the ID of the resource on which it depends.  That
>    document defines one resource-specific property, namely the "pid"
>    property, whose value is the name of the name of the PID containing
> *<QX> "the name of the name of the PID" -> "the name of the PID"*
>
>    that endpoint in the associated network map.
>
>    ...
>    According to [RFC7285], an ALTO server with two network maps, with
> *<QX> "an ALTO server" -> "a legacy ALTO server"*
>
> *Page 7*
>
> 3.1.  Internet Address Domains
>
>    The domain of internet addresses consists of two domains (IPv4 and
>    IPv6).  Both domains include individual addresses and blocks of
>    addresses.
> *<QX> After reading the beginning of Sec 3.2, I feel that Section 3.1
> should add a sentence like "this domain does not have to depend on an ALTO
> network map resource." in the beginning.*
>
> 3.1.1.  IPV4 Domain
> *<QX> "IPV4" -> "IPv4"*
>
>    ...
>    For the purpose of defining properties, an individual internet
>    address and the corresponding full-length prefix are considered
>    aliases for the same entity.  Thus "ipv4:192.0.2.0" and
>    "ipv4:192.0.2.0/32" are equivalent, and have the same set of
>    properties, as are "ipv6:2001:db8::" and "ipv6:2001:db8::/128".
> *<QX> remove ", as are "ipv6:2001:db8::" and "ipv6:2001:db8::/128" because
> this section is about IPv4 domain.*
>
> 3.1.2.  IPV6 Domain
> *<QX> "IPV6" -> "IPv6"*
>
>     ...
> 3.1.2.2.  Domain-Specific Entity Addresses
>
>    ...
>    For the purpose of defining properties, an individual internet
>    address and the corresponding 128-bit prefix are considered aliases
>    for the same entity.  That is, "ipv6:2001:db8::1" and
>    "ipv:2001:db8::1/128" are equivalent, and have the same set of
>    properties.
> *<QX> "ipv:2001:db8::1/128" -> "ipv6:2001:db8::1/128"*
>
> *Page 8*
>
>    ...
>    Then the following entities have the indicated values:
>
>           ipv4:192.0.2.0:    P=v4
>           ipv4:192.0.2.1:    P=v3
>           ipv4:192.0.2.16:   P=v2
> *<QX> "ipv4:192.0.2.16 <http://192.0.2.16>:   P=v2" -> "ipv4:192.0.2.16
> <http://192.0.2.16>:   P=v1", if we want an example of P=v2, we can use
> "ipv4:192.0.2.8 <http://192.0.2.8>:   P=v2"*
>
>           ipv4:192.0.2.32:   P=v1
>           ipv4:192.0.2.64:   (not defined)
>           ipv4:192.0.2.0/32: P=v4
>           ipv4:192.0.2.0/31: P=v3
>           ipv4:192.0.2.0/29: P=v2
>           ipv4:192.0.2.0/27: P=v1
>           ipv4:192.0.2.0/25: (not defined)
>
>                          Inherited Property Values
>     ...
> 3.3.  Internet Address Properties vs. PID Properties
>
>    ...
>
>    For example, because internet addresses are allocated to server
> *<QX> "server" -> "service"*
>
> *Page 10*
>
> 4.  Property Map Resource
>
>    A Property Map returns the properties defined for all entities in one
>    of more domains.
> *<QX> "of more" -> "or more"*
>
>    ...
>
> *Page 11*
>
>    For each entity in the Property Map, the ALTO Server returns the
>    value defined for each of the properties specified in this resource's
>    "capabilities" list.  For efficiency, the ALTO Server SHOULD omit
>    property values that are inherited rather than explicitly defined; if
>    a client needs inherited values, the client SHOULD use the domain's
>    inheritance rules to deduce those values.
> *<QX??> in the current draft, inheritance is defined in an all-or-nothing
> form. Either a domain allows inheritance or it does not. Since the
> computation of a property is up to the implementation, shouldn't we let the
> implementation decide how properties are inherited from a larger block to a
> smaller block of entities? Consider the example in Section 7.6, the current
> draft seems to tell the admin: either you come up with a better property
> map stored in the ALTO server to avoid failed/inaccurate query, or there is
> zero flexibility for you to compute or update property map on demand. My
> feeling is this may not be the right way... *
>
> *Page 12*
>
>     ...
> 5.2.  HTTP Method
>
>    An ALTO Property Map resource is requested using the HTTP POST
>    method.
> *<QX> "an ALTO Property Map" -> "an ALTO Filtered Property Map"*
>
>
> *Page 13*
>
> 5.6.  Response
>
>    The response is the same as for the property map (Section 4.6),
> *<QX> "property map" -> "Property Map"*
>
>    except that it only includes the entities and properties requested by
>    the client.
>
>    Also, the Filtered Property Map response MUST include all inherited
>    property values for the specified entities (unlike the Full Property
> *<QX> "Full" -> "full", since Full Property Map is not a term defined in
> this document.*
>
>    Map, the Filtered Property Map response does not include enough
>    information for the client to calculate the inherited values).
>
> 6.  Impact On Legacy Servers And Clients
> *<QX> "Legacy Servers And Clients" -> "Legacy ALTO Servers And ALTO
> Clients"*
>
> 6.1.  Impact on Endpoint Property Service
>
>    The property maps defined in this document provide the same
> *<QX> "property maps" -> "Property Map"*
>
>    functionality as the Endpoint Property Service (EPS) defined in
>    Section 11.4 of [RFC7285].  Accordingly, it is RECOMMENDED that the
>    EPS be deprecated in favor of property maps.  However, ALTO servers
> *<QX> "property maps" -> "Property Map"*
>
>    MAY provide an EPS for the benefit of legacy clients.
>
> *Page 14*
>
>    ...
>    However, when used with property maps, this document amends the
> *<QX> "property maps" -> "Property Map"*
>
>    definition of the "pid" property as follows.
>
>    First, the name of the property is simply "pid"; the name is not
>    prefixed with the resource ID of a network map.  The "uses"
>    capability of the property map resource indicates the associated
>    network map.  This implies that a property map can only return the
>    "pid" property for one network map; if an ALTO server provides
>    several network maps, it must provide a property map resource for
>    each one.
> *<QX> "must provide" -> "MUST provide"*
>
>
> *Page 15*
>
>     ...
>     7.3.  Information Resource Directory (IRD)
>
>    ...
>    The Property Maps for the "ISP", "ASN", "country" and "state"
> *<QX> "Property Maps" -> "Filtered Property Map"*
>
>    properties do not depend on the default network map (they do not have
> *<QX> "do not depend on the default network map (they do not have" ->*
> *     "does not depend on the default network map (it does not have"*
>
> *Page 18*
>
>     ...
> 7.6.  Filtered Property Map Example #2
>
>    ...
>    Also note the "ASN" property has the value "12345" for both the
>    blocks "ipv4:192.0.2.0/28" and "ipv4:192.0.2.16/28", so every address
>    in the block "ipv4:192.0.2.0/27" has that property value.  However
>    the block "ipv4:192.0.2.0/27" itself does not have a value for "ASN":
>    address blocks cannot inherit properties from blocks with longer
>    prefixes, even if every such block has the same value.
> *<QX> This is a very good example. Please see my comments makred in <QX??>
> for page 11. And if we eventually insist the all-or-nothing inheritance
> design, it would make the inheritance of properties much clearer to readers
> if we use it in Section 3.1.3, instead of explaining the reasons here.*
>
> *Page 19*
>
> 7.7.  Filtered Property Map Example #3
>
>    ...
>    Note that the value of "pid" for the prefix "ipv4:10.0.0.0/15" is
>    "pid1", even though all addresses in that block are in "pid2",
>    because "ipv4:10.0.0.0/8" is the longest prefix in the network map
>    which prefix-matches "ipv4:10.0.0.0/15", and that prefix is in
>    "pid1".
> *<QX> I agree with Shenzhen's comments. 10.0.0.0/XX <http://10.0.0.0/XX>
> is inconsistent with the settings in Section 7.1. It should be fixed in the
> next version.*
>
> *Page 21*
>
>    Also, while technically this document does not introduce any security
>    risks not inherent in the Endpoint Property Service defined by
>    [RFC7285], the GET-mode property map resource defined in this
>    document does make it easier for a client to download large numbers
>    of property values.  Accordingly, an ALTO Server should limit GET-
>    mode property maps for to properties which do not contain sensitive
>    data.
> *<QX> "for to properties" -> "to properties"*
>
> 9.1.  application/alto-* Media Types
>    ...
>    Security considerations:  Security considerations relating to the
> *<QX> "relating" -> "related"*
>
>       generation and consumption of ALTO Protocol messages are discussed
>       in Section 15 of [RFC7285].
>
>    Interoperability considerations:  This document specifies format of
> *<QX> "format" -> "formats"*
>
>
> On Mon, Jun 26, 2017 at 11:58 PM, Shenshen Chen <cs90911@gmail.com> wrote:
>
>> Dear authors of alto-unified-props and all,
>>
>> In section 2.5, I feel "property type" could be better (because RFC7285
>> names
>> sections using "property type", but not "property name") and "property
>> value"
>> should be mentioned (includes the "null" value mentioned in section 4.6).
>> I also suggest showing the "null" value can be inherited explicitly
>> in the section 3.1.3 or emphasizing it as a normal property value.
>>
>> Here is a list of typos (comments are marked with ">>>"):
>>
>> [Page 2]
>>        3.1.3.  Heirarchy And Inheritance . . . . . . . . . . . . . .   7
>>        3.1.4.  Relationship To Network Maps  . . . . . . . . . . . .   8
>>      3.2.  PID Domain  . . . . . . . . . . . . . . . . . . . . . . .   9
>>        3.2.1.  Domain Name . . . . . . . . . . . . . . . . . . . . .   9
>>        3.2.2.  Domain-Specific Entity Addresses  . . . . . . . . . .   9
>>        3.2.3.  Heirarchy And Inheritance . . . . . . . . . . . . . .   9
>>        3.2.4.  Relationship To Internet Addresses Domains  . . . . .   9
>>
>> >>> "To" => "to", "And" => "and", "Heirarchy" => "Hierarchy"
>>
>>
>> [Page 3]
>>    Second, the EPS is only defined as a POST-mode service.  Clients must
>>    request the properties for an explicit set of addresses.  By
>>    contrast, [RFC7285] defines a GET-mode Cost Map resource which
>>    returns all available costs, so a client can get the full set of
>>    costs once, and then lookup costs without querying the ALTO server.
>>    RFC7285 does not define an equivalent service for endpoint
>>    properties.  Granted, it is not be practical to enumerate the
>>
>> >>> "is not be" => "is not"
>>
>>
>> [Page 4]
>>    This document proposes a new approach to ALTO properties.
>>    Specifically, it defines two new resource types, namely Property Maps
>>    and Filtered Property Maps.  The former are GET-mode resources which
>>    return the property values for all entities in a domain, and are
>>    analogous the ALTO's Network Map and Cost Map resources.  The latter
>>
>> >>> "Network Map and Cost Map resources" => "Network Maps and Cost Maps"
>>     I think it should keep the same format with "Filtered Network Maps
>>     and Filtered Cost Maps" in the last sentence of this paragraph.
>>
>>    are POST-mode resources which return the values for a set of
>>    properties and entities requested by the client, and are analogous to
>>    ALTO's Filtered Network Maps and Filtered Cost Maps.
>>
>> [Page 7]
>> 3.1.3.  Heirarchy And Inheritance
>>
>> [Page 9]
>> 3.2.3.  Heirarchy And Inheritance
>>
>> >>> "Heirarchy" => "Hierarchy"
>>
>> [Page 19]
>>    Note that the value of "pid" for the prefix "ipv4:10.0.0.0/15" is
>>    "pid1", even though all addresses in that block are in "pid2",
>>    because "ipv4:10.0.0.0/8" is the longest prefix in the network map
>>    which prefix-matches "ipv4:10.0.0.0/15", and that prefix is in
>>    "pid1".
>>
>>    POST /propmap/lookup/pid HTTP/1.1
>>    Host: alto.example.com
>>    Accept: application/alto-propmap+json,application/alto-error+json
>>    Content-Length: ###
>>    Content-Type: application/alto-propmapparams+json
>>
>>    {
>>      "entities" : [
>>                    "ipv4:192.0.2.0  10.0.0.0",
>>                    "ipv4:192.0.2.16 10.1.0.0",
>>                    "ipv4:192.0.2.64  10.3.0.0",
>>                    "ipv4:192.0.2.128  11.0.0.0",
>>                    "ipv4:192.0.2.0/26 10.0.0.0/15",
>>                    "ipv4:192.0.2.0/30 10.0.0.0/17" ],
>>      "properties" : [ "pid" ]
>>    }
>>
>> >>> This part should be modified into:
>>
>>    Note that the value of "pid" for the prefix "ipv4:192.0.2.0/26" is
>>    "pid1", even though all addresses in that block are in "pid2",
>>    because "ipv4:192.0.2.0/25" is the longest prefix in the network map
>>    which prefix-matches "ipv4:192.0.2.0/26", and that prefix is in
>>    "pid1".
>>
>>    POST /propmap/lookup/pid HTTP/1.1
>>    Host: alto.example.com
>>    Accept: application/alto-propmap+json,application/alto-error+json
>>    Content-Length: ###
>>    Content-Type: application/alto-propmapparams+json
>>
>>    {
>>      "entities" : [
>>                    "ipv4:192.0.2.0",
>>                    "ipv4:192.0.2.16",
>>                    "ipv4:192.0.2.64",
>>                    "ipv4:192.0.2.128",
>>                    "ipv4:192.0.2.0/26",
>>                    "ipv4:192.0.2.0/30" ],
>>      "properties" : [ "pid" ]
>>    }
>>
>> [Page 23]
>>    New ALTO entity domains are assigned after IETF Review [RFC5226] to
>>    ensure that proper documentation regarding the new ALTO entity
>>    domains and their security considerations has been provided.  RFCs
>>
>> >>> "has been" => "have been"
>>
>>    defining new entity domains should indicate how an entity in a
>>    registered domain is encoded as an EntityName, and, if applicable,
>>    the rules defining the entity hierarchy and property inheritance.
>>    Updates and deletions of ALTO entity domains follow the same
>>    procedure.
>>
>>
>> Best Regards,
>> Shenshen
>>
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>
>>
>
>
> --
> Qiao Xiang
> Postdoctoral Fellow,
> Department of Computer Science,
> Yale University
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>


-- 
Thanks a lot!
Sincerely!
*************************************************************
Haizhou Du,
Department of Computer Science
*************************************************************

--94eb2c065238af0de20553161598
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><span style=3D"font-size:12.8px">Hi all,</span><div s=
tyle=3D"font-size:12.8px"><span style=3D"font-size:12.8px">I reviewed the u=
nified property map draft. I agree with all=C2=A0</span>Shenshen<span style=
=3D"font-size:12.8px">=C2=A0and Qiao&#39;s comments.=C2=A0 And I want to gi=
ve some comments for Qiao&#39;s discussions:</span><br></div><div style=3D"=
font-size:12.8px"><span style=3D"font-size:12.8px">=C2=A0(1) how does prope=
rty map handle dynamic entity, e.g., </span>ane<span style=3D"font-size:12.=
8px"> defined in the path-vector draft?</span></div><div style=3D"font-size=
:12.8px"><span style=3D"font-size:12.8px">I think we can handle Property Ma=
p of the dynamic entity in the path-vector draft.=C2=A0 We can extend the=
=C2=A0ane=C2=A0property.</span></div><div style=3D"font-size:12.8px"><span =
style=3D"font-size:12.8px">=C2=A0(2) is the inheritance design in the prope=
rty map draft too rigid?=C2=A0</span></div><div style=3D"font-size:12.8px">=
<span style=3D"font-size:12.8px">I agree with Qiao. We can=C2=A0</span><spa=
n style=3D"color:rgb(0,0,0);font-family:Courier;font-size:13.3px">inherit</=
span><span style=3D"font-size:12.8px">=C2=A0all kinds of value=C2=A0</span>=
<span style=3D"color:rgb(0,0,0);font-family:Courier;font-size:13.3px">for t=
hat property,=C2=A0Including &quot;null&quot; in the=C2=A0</span><span styl=
e=3D"font-size:12.8px">Property Map. </span><span style=3D"color:rgb(0,0,0)=
;font-family:Courier;font-size:13.3px">If the entity and his son entity=C2=
=A0</span><span style=3D"font-size:small">inherits a &quot;null&quot; =C2=
=A0value, the ALTO server MAY =C2=A0just omit all of them from the root ent=
ity.</span></div>







<div style=3D"font-size:12.8px"><span style=3D"font-size:12.8px">=C2=A0(3) =
H</span><span style=3D"font-size:12.8px">ow should we modify/improve the de=
signs of both path vector and property map to make the whole solution a uni=
fied </span>one?</div><div style=3D"font-size:12.8px">I think we can extend=
 the=C2=A0ane property in path vector draft. And we can define the=C2=A0<sp=
an style=3D"font-size:small">inheritance and=C2=A0</span><span style=3D"fon=
t-size:small">hierarchy of ane property for unified one.</span></div><div s=
tyle=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px"><span s=
tyle=3D"font-size:12.8px">If you have any comments, please share with me? T=
hank you so much.=C2=A0</span><span style=3D"font-size:12.8px">In addition,=
 please see my other comments in the following.</span></div></div><div><br>=
</div><div><b>Page 5</b></div><div><div style=3D"font-size:12.8px">Note tha=
t entity addresses may NOT have a unique textual=C2=A0<span style=3D"font-s=
ize:12.8px">representation. =C2=A0</span></div><div style=3D"font-size:12.8=
px"><b>[HZ] &quot;may NOT&quot; is not defined in RFC2119. &quot;may NOT ha=
ve a unique&quot; -&gt; &quot;MAY have different&quot;</b></div></div><div =
style=3D"font-size:12.8px"><b><br></b></div><div><b>Page 10</b></div><div>
<p class=3D"gmail-p2"><span class=3D"gmail-s1">3.2.3.=C2=A0 Hierarchy And I=
nheritance</span></p><p class=3D"gmail-p2"><span class=3D"gmail-s1"><b>[HZ]=
&quot;And&quot;-&gt;&quot;and&quot;<br></b></span></p></div><b>Page 23</b><=
div><span class=3D"gmail-s1">Accordingly, an ALTO Server should limit GET-<=
/span>mode property maps for to properties which do not contain sensitive d=
ata.</div><div><b>[HZ] &quot;should&quot; -&gt; &quot;SHOULD&quot;</b></div=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Jun 28, =
2017 at 9:08 PM, Qiao Xiang <span dir=3D"ltr">&lt;<a href=3D"mailto:xiangq2=
7@gmail.com" target=3D"_blank">xiangq27@gmail.com</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hi Wendy=
, Richard and all,<div><br></div><div>I reviewed the unified property map d=
raft. I agree with all=C2=A0Shenshen&#39;s=C2=A0comments. In addition, plea=
se see my other comments in the following.</div><div><br></div><div>In addi=
tion to the review, the key design=C2=A0questions I want to raise discussio=
ns are (1) how does property map handle dynamic entity, e.g., ane defined i=
n the path-vector draft? (2) is the inheritance design in the property map =
draft too rigid? (see my comments marked with &lt;QX??&gt;) and (3) in the =
current path vector draft the ane is defined with no inheritance or hierarc=
hy, but aggregating/compressing multiple ane&#39;s is an important process =
for the path vector service to reduce overhead and provide privacy of netwo=
rks. how should we modify/improve the designs of both path vector and prope=
rty map to make the whole solution a unified one. I will work on these thre=
e questions in the next few days and share my thoughts. Menawhile, would yo=
u please also share any comments/thoughts you may have? Thank you very much=
.</div><div><br></div><div><br></div><div><b>Reviews:</b></div><div><div><b=
>Page 4</b></div><div><br></div><div>=C2=A0 =C2=A0This document proposes a =
new approach to ALTO properties.</div><div><b>&lt;QX&gt; &quot;approach to =
ALTO properties&quot; -&gt; &quot;approach to retrieve ALTO properties&quot=
;</b></div><div><br></div><div>=C2=A0 =C2=A0Specifically, it defines two ne=
w resource types, namely Property Maps</div><div>=C2=A0 =C2=A0and Filtered =
Property Maps.=C2=A0 The former are GET-mode resources which</div><div>=C2=
=A0 =C2=A0return the property values for all entities in a domain, and are<=
/div><div>=C2=A0 =C2=A0analogous the ALTO&#39;s Network Map and Cost Map re=
sources.=C2=A0 The latter</div><div><b>&lt;QX&gt; &quot;analogous the ALTO&=
#39;s &quot; -&gt; &quot;analogous to the ALTO&#39;s &quot;</b></div><div><=
br></div><div>=C2=A0 =C2=A0are POST-mode resources which return the values =
for a set of</div><div>=C2=A0 =C2=A0properties and entities requested by th=
e client, and are analogous to</div><div><b>&lt;QX&gt; &quot;the values for=
 a set of properties and entities&quot; -&gt; &quot;the values of a set of =
properties for a set of entities&quot;</b></div><div><br></div><div>=C2=A0 =
=C2=A0ALTO&#39;s Filtered Network Maps and Filtered Cost Maps.</div><div><b=
r></div><div><b>Page 5</b></div><div>=C2=A0 =C2=A0</div><div>=C2=A0 =C2=A0T=
he format of the second part of an entity address depends on the</div><div>=
=C2=A0 =C2=A0domain, and must be specified when registering a new domain.</=
div><div><b>&lt;QX&gt; &quot;must&quot; -&gt; &quot;MUST&quot;</b></div><di=
v><br></div><div>=C2=A0 =C2=A0Addresses may be hierarchical, and properties=
 may be inherited based</div><div>=C2=A0 =C2=A0on that hierarchy.=C2=A0 Aga=
in, the rules defining any hierarchy or</div><div>=C2=A0 =C2=A0inheritance =
must be defined when the domain is registered.</div><div><b>&lt;QX&gt; &quo=
t;must&quot; -&gt; &quot;MUST&quot;</b></div><div><br></div><div>=C2=A0 =C2=
=A0Note that entity addresses do NOT have a unique textual</div><div>=C2=A0=
 =C2=A0representation.=C2=A0 For example, the strings &quot;ipv6:2001:db8::=
1&quot; and</div><div>=C2=A0 =C2=A0&quot;ipv6:2001:db8:0:0:0:0:0:1&quot; re=
fer to the same entity.</div><div><b>&lt;QX&gt; &quot;NOT&quot; is not defi=
ned in RFC2119. &quot;do NOT have a unique&quot; -&gt; &quot;MAY have diffe=
rent&quot;</b></div><div><br></div><div>=C2=A0 =C2=A0...</div><div><br></di=
v><div>=C2=A0 =C2=A0Domain names must be registered with the IANA, and the =
format of the</div><div>=C2=A0 =C2=A0entity addresses in that domain, as we=
ll as any hierarchical or</div><div>=C2=A0 =C2=A0inheritance rules for thos=
e entities, must be specified at the same</div><div>=C2=A0 =C2=A0time.</div=
><div><b>&lt;QX&gt; &quot;must&quot;-&gt;&quot;MUST&quot;</b></div><div><br=
></div><div>=C2=A0 =C2=A0...</div><div><br></div><div>=C2=A0 =C2=A0Property=
 names are not specific to a domain, although some properties</div><div>=C2=
=A0 =C2=A0may only be applicable for particular domains, and the interpreta=
tion</div><div>=C2=A0 =C2=A0of the value may depend on the domain.=C2=A0 Fo=
r example, suppose the</div><div>=C2=A0 =C2=A0&quot;geo-location&quot; prop=
erty is defined as the coordinates of a point,</div><div>=C2=A0 =C2=A0encod=
ed as (say) &quot;latitude longitude [altitude].&quot; =C2=A0When applied t=
o an</div><div><b>&lt;QX&gt; &quot;as (say)&quot; -&gt; &quot;as&quot;</b><=
/div><div><br></div><div><b>Page 6</b></div><div>=C2=A0 =C2=A0</div><div>=
=C2=A0 =C2=A0...</div><div><br></div><div>=C2=A0 =C2=A0[RFC7285] recognizes=
 that some properties may be specific to another</div><div>=C2=A0 =C2=A0ALT=
O resource, such as a network map.=C2=A0 Accordingly [RFC7285] defines</div=
><div>=C2=A0 =C2=A0the concept of &quot;resource-specific endpoint properti=
es&quot;</div><div>=C2=A0 =C2=A0(Section 10.8.1), and indicates that depend=
ency by prefixing the</div><div>=C2=A0 =C2=A0property name with the ID of t=
he resource on which it depends.=C2=A0 That</div><div>=C2=A0 =C2=A0document=
 defines one resource-specific property, namely the &quot;pid&quot;</div><d=
iv>=C2=A0 =C2=A0property, whose value is the name of the name of the PID co=
ntaining</div><div><b>&lt;QX&gt; &quot;the name of the name of the PID&quot=
; -&gt; &quot;the name of the PID&quot;</b></div><div><br></div><div>=C2=A0=
 =C2=A0that endpoint in the associated network map.</div><div><br></div><di=
v>=C2=A0 =C2=A0...</div><div>=C2=A0 =C2=A0According to [RFC7285], an ALTO s=
erver with two network maps, with</div><div><b>&lt;QX&gt; &quot;an ALTO ser=
ver&quot; -&gt; &quot;a legacy ALTO server&quot;</b></div><div><br></div><d=
iv><b>Page 7</b></div><div>=C2=A0 =C2=A0</div><div>3.1.=C2=A0 Internet Addr=
ess Domains</div><div><br></div><div>=C2=A0 =C2=A0The domain of internet ad=
dresses consists of two domains (IPv4 and</div><div>=C2=A0 =C2=A0IPv6).=C2=
=A0 Both domains include individual addresses and blocks of</div><div>=C2=
=A0 =C2=A0addresses.</div><div><b>&lt;QX&gt; After reading the beginning of=
 Sec 3.2, I feel that Section 3.1 should add a sentence like &quot;this dom=
ain does not have to depend on an ALTO network map resource.&quot; in the b=
eginning.</b></div><div><br></div><div>3.1.1.=C2=A0 IPV4 Domain</div><div><=
b>&lt;QX&gt; &quot;IPV4&quot; -&gt; &quot;IPv4&quot;</b></div><div><br></di=
v><div>=C2=A0 =C2=A0...</div><div>=C2=A0 =C2=A0For the purpose of defining =
properties, an individual internet</div><div>=C2=A0 =C2=A0address and the c=
orresponding full-length prefix are considered</div><div>=C2=A0 =C2=A0alias=
es for the same entity.=C2=A0 Thus &quot;ipv4:192.0.2.0&quot; and</div><div=
>=C2=A0 =C2=A0&quot;ipv4:<a href=3D"http://192.0.2.0/32" target=3D"_blank">=
192.0.2.0/32</a>&quot; are equivalent, and have the same set of</div><div>=
=C2=A0 =C2=A0properties, as are &quot;ipv6:2001:db8::&quot; and &quot;ipv6:=
2001:db8::/128&quot;.</div><div><b>&lt;QX&gt; remove &quot;, as are &quot;i=
pv6:2001:db8::&quot; and &quot;ipv6:2001:db8::/128&quot; because this secti=
on is about IPv4 domain.</b></div><div><br></div><div>3.1.2.=C2=A0 IPV6 Dom=
ain</div><div><b>&lt;QX&gt; &quot;IPV6&quot; -&gt; &quot;IPv6&quot;</b></di=
v><div><br></div><div>=C2=A0 =C2=A0 ...</div><div>3.1.2.2.=C2=A0 Domain-Spe=
cific Entity Addresses</div><div><br></div><div>=C2=A0 =C2=A0...</div><div>=
=C2=A0 =C2=A0For the purpose of defining properties, an individual internet=
</div><div>=C2=A0 =C2=A0address and the corresponding 128-bit prefix are co=
nsidered aliases</div><div>=C2=A0 =C2=A0for the same entity.=C2=A0 That is,=
 &quot;ipv6:2001:db8::1&quot; and</div><div>=C2=A0 =C2=A0&quot;ipv:2001:db8=
::1/128&quot; are equivalent, and have the same set of</div><div>=C2=A0 =C2=
=A0properties.</div><div><b>&lt;QX&gt; &quot;ipv:2001:db8::1/128&quot; -&gt=
; &quot;ipv6:2001:db8::1/128&quot;</b></div><div><br></div><div><b>Page 8</=
b></div><div><br></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0=C2=A0 Then th=
e following entities have the indicated values:<br></div><div><br></div><di=
v>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http://192.0.2.0" targ=
et=3D"_blank">192.0.2.0</a>: =C2=A0 =C2=A0P=3Dv4</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http://192.0.2.1" target=3D"_blank">19=
2.0.2.1</a>: =C2=A0 =C2=A0P=3Dv3</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 ipv4:<a href=3D"http://192.0.2.16" target=3D"_blank">192.0.2.16</a>: =
=C2=A0 P=3Dv2</div><div><b>&lt;QX&gt; &quot;ipv4:<a href=3D"http://192.0.2.=
16" target=3D"_blank">192.0.2.16</a>: =C2=A0 P=3Dv2&quot; -&gt; &quot;ipv4:=
<a href=3D"http://192.0.2.16" target=3D"_blank">192.0.2.16</a>: =C2=A0 P=3D=
v1&quot;, if we want an example of P=3Dv2, we can use &quot;ipv4:<a href=3D=
"http://192.0.2.8" target=3D"_blank">192.0.2.8</a>: =C2=A0 P=3Dv2&quot;</b>=
</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=
=3D"http://192.0.2.32" target=3D"_blank">192.0.2.32</a>: =C2=A0 P=3Dv1</div=
><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http://192.0.2.64"=
 target=3D"_blank">192.0.2.64</a>: =C2=A0 (not defined)</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http://192.0.2.0/32" target=3D"=
_blank">192.0.2.0/32</a>: P=3Dv4</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 ipv4:<a href=3D"http://192.0.2.0/31" target=3D"_blank">192.0.2.0/31</a>=
: P=3Dv3</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http:=
//192.0.2.0/29" target=3D"_blank">192.0.2.0/29</a>: P=3Dv2</div><div>=C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ipv4:<a href=3D"http://192.0.2.0/27" target=3D=
"_blank">192.0.2.0/27</a>: P=3Dv1</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 ipv4:<a href=3D"http://192.0.2.0/25" target=3D"_blank">192.0.2.0/25</a>=
: (not defined)</div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Inherited Property =
Values</div><div>=C2=A0 =C2=A0 ...</div><div>3.3.=C2=A0 Internet Address Pr=
operties vs. PID Properties<br></div><div><br></div><div>=C2=A0 =C2=A0...</=
div><div><br></div><div>=C2=A0 =C2=A0For example, because internet addresse=
s are allocated to server</div><div><b>&lt;QX&gt; &quot;server&quot; -&gt; =
&quot;service&quot;</b></div><div><br></div><div><b>Page 10</b></div><div><=
br></div><div>4.=C2=A0 Property Map Resource</div><div><br></div><div>=C2=
=A0 =C2=A0A Property Map returns the properties defined for all entities in=
 one</div><div>=C2=A0 =C2=A0of more domains.</div><div><b>&lt;QX&gt; &quot;=
of more&quot; -&gt; &quot;or more&quot;</b></div><div><br></div><div>=C2=A0=
 =C2=A0...</div><div><br></div><div><b>Page 11</b></div><div><br></div><div=
>=C2=A0 =C2=A0For each entity in the Property Map, the ALTO Server returns =
the</div><div>=C2=A0 =C2=A0value defined for each of the properties specifi=
ed in this resource&#39;s</div><div>=C2=A0 =C2=A0&quot;capabilities&quot; l=
ist.=C2=A0 For efficiency, the ALTO Server SHOULD omit</div><div>=C2=A0 =C2=
=A0property values that are inherited rather than explicitly defined; if</d=
iv><div>=C2=A0 =C2=A0a client needs inherited values, the client SHOULD use=
 the domain&#39;s</div><div>=C2=A0 =C2=A0inheritance rules to deduce those =
values.</div><div><b>&lt;QX??&gt; in the current draft, inheritance is defi=
ned in an all-or-nothing form. Either a domain allows inheritance or it doe=
s not. Since the computation of a property is up to the implementation, sho=
uldn&#39;t we let the implementation decide how properties are inherited fr=
om a larger block to a smaller block of entities? Consider the example in S=
ection 7.6, the current draft seems to tell the admin: either you come up w=
ith a better property map stored in the ALTO server to avoid failed/inaccur=
ate query, or there is zero flexibility for you to compute or update proper=
ty map on demand. My feeling is this may not be the right way...=C2=A0</b><=
/div><div><b><br></b></div><div><b>Page 12</b></div><div><br></div><div>=C2=
=A0 =C2=A0 ...</div><div>5.2.=C2=A0 HTTP Method</div><div><br></div><div>=
=C2=A0 =C2=A0An ALTO Property Map resource is requested using the HTTP POST=
</div><div>=C2=A0 =C2=A0method.</div><div><b>&lt;QX&gt; &quot;an ALTO Prope=
rty Map&quot; -&gt; &quot;an ALTO Filtered Property Map&quot;</b></div><div=
><br></div><div><br></div><div><b>Page 13</b></div><div><br></div><div>5.6.=
=C2=A0 Response</div><div><br></div><div>=C2=A0 =C2=A0The response is the s=
ame as for the property map (Section 4.6),</div><div><b>&lt;QX&gt; &quot;pr=
operty map&quot; -&gt; &quot;Property Map&quot;</b></div><div><br></div><di=
v>=C2=A0 =C2=A0except that it only includes the entities and properties req=
uested by</div><div>=C2=A0 =C2=A0the client.</div><div><br></div><div>=C2=
=A0 =C2=A0Also, the Filtered Property Map response MUST include all inherit=
ed</div><div>=C2=A0 =C2=A0property values for the specified entities (unlik=
e the Full Property</div><div><b>&lt;QX&gt; &quot;Full&quot; -&gt; &quot;fu=
ll&quot;, since Full Property Map is not a term defined in this document.</=
b></div><div><br></div><div>=C2=A0 =C2=A0Map, the Filtered Property Map res=
ponse does not include enough</div><div>=C2=A0 =C2=A0information for the cl=
ient to calculate the inherited values).</div><div><br></div><div>6.=C2=A0 =
Impact On Legacy Servers And Clients</div><div><b>&lt;QX&gt; &quot;Legacy S=
ervers And Clients&quot; -&gt; &quot;Legacy ALTO Servers And ALTO Clients&q=
uot;</b></div><div><br></div><div>6.1.=C2=A0 Impact on Endpoint Property Se=
rvice</div><div><br></div><div>=C2=A0 =C2=A0The property maps defined in th=
is document provide the same</div><div><b>&lt;QX&gt; &quot;property maps&qu=
ot; -&gt; &quot;Property Map&quot;</b></div><div><br></div><div>=C2=A0 =C2=
=A0functionality as the Endpoint Property Service (EPS) defined in</div><di=
v>=C2=A0 =C2=A0Section 11.4 of [RFC7285].=C2=A0 Accordingly, it is RECOMMEN=
DED that the</div><div>=C2=A0 =C2=A0EPS be deprecated in favor of property =
maps.=C2=A0 However, ALTO servers</div><div><b>&lt;QX&gt; &quot;property ma=
ps&quot; -&gt; &quot;Property Map&quot;</b></div><div><br></div><div>=C2=A0=
 =C2=A0MAY provide an EPS for the benefit of legacy clients.</div><div><br>=
</div><div><b>Page 14</b></div><div>=C2=A0 =C2=A0</div><div>=C2=A0 =C2=A0..=
.</div><div>=C2=A0=C2=A0 However, when used with property maps, this docume=
nt amends the<br></div><div><b>&lt;QX&gt; &quot;property maps&quot; -&gt; &=
quot;Property Map&quot;</b></div><div><br></div><div>=C2=A0 =C2=A0definitio=
n of the &quot;pid&quot; property as follows.</div><div><br></div><div>=C2=
=A0 =C2=A0First, the name of the property is simply &quot;pid&quot;; the na=
me is not</div><div>=C2=A0 =C2=A0prefixed with the resource ID of a network=
 map.=C2=A0 The &quot;uses&quot;</div><div>=C2=A0 =C2=A0capability of the p=
roperty map resource indicates the associated</div><div>=C2=A0 =C2=A0networ=
k map.=C2=A0 This implies that a property map can only return the</div><div=
>=C2=A0 =C2=A0&quot;pid&quot; property for one network map; if an ALTO serv=
er provides</div><div>=C2=A0 =C2=A0several network maps, it must provide a =
property map resource for</div><div>=C2=A0 =C2=A0each one.</div><div><b>&lt=
;QX&gt; &quot;must provide&quot; -&gt; &quot;MUST provide&quot;</b></div><d=
iv><br></div><div><br></div><div><b>Page 15</b></div><div><br></div><div>=
=C2=A0 =C2=A0 ...</div><div>=C2=A0 =C2=A0 7.3.=C2=A0 Information Resource D=
irectory (IRD)</div><div><br></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0 =
=C2=A0The Property Maps for the &quot;ISP&quot;, &quot;ASN&quot;, &quot;cou=
ntry&quot; and &quot;state&quot;</div><div><b>&lt;QX&gt; &quot;Property Map=
s&quot; -&gt; &quot;Filtered Property Map&quot;</b></div><div><br></div><di=
v>=C2=A0 =C2=A0properties do not depend on the default network map (they do=
 not have</div><div><b>&lt;QX&gt; &quot;do not depend on the default networ=
k map (they do not have&quot; -&gt;</b></div><div><b>=C2=A0 =C2=A0 =C2=A0&q=
uot;does not depend on the default network map (it does not have&quot;</b><=
/div><div><br></div><div><b>Page 18</b></div><div><br></div><div>=C2=A0 =C2=
=A0 ...</div><div>7.6.=C2=A0 Filtered Property Map Example #2</div><div><br=
></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0 =C2=A0Also note the &quot;ASN=
&quot; property has the value &quot;12345&quot; for both the</div><div>=C2=
=A0 =C2=A0blocks &quot;ipv4:<a href=3D"http://192.0.2.0/28" target=3D"_blan=
k">192.0.2.0/28</a>&quot; and &quot;ipv4:<a href=3D"http://192.0.2.16/28" t=
arget=3D"_blank">192.0.2.16/28</a>&quot;, so every address</div><div>=C2=A0=
 =C2=A0in the block &quot;ipv4:<a href=3D"http://192.0.2.0/27" target=3D"_b=
lank">192.0.2.0/27</a>&quot; has that property value.=C2=A0 However</div><d=
iv>=C2=A0 =C2=A0the block &quot;ipv4:<a href=3D"http://192.0.2.0/27" target=
=3D"_blank">192.0.2.0/27</a>&quot; itself does not have a value for &quot;A=
SN&quot;:</div><div>=C2=A0 =C2=A0address blocks cannot inherit properties f=
rom blocks with longer</div><div>=C2=A0 =C2=A0prefixes, even if every such =
block has the same value.</div><div><b>&lt;QX&gt; This is a very good examp=
le. Please see my comments makred in &lt;QX??&gt; for page 11. And if we ev=
entually insist the all-or-nothing inheritance design, it would make the in=
heritance of properties much clearer to readers if we use it in Section 3.1=
.3, instead of explaining the reasons here.</b></div><div><br></div><div><b=
>Page 19</b></div><div><br></div><div>7.7.=C2=A0 Filtered Property Map Exam=
ple #3</div><div><br></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0 =C2=A0Not=
e that the value of &quot;pid&quot; for the prefix &quot;ipv4:<a href=3D"ht=
tp://10.0.0.0/15" target=3D"_blank">10.0.0.0/15</a>&quot; is</div><div>=C2=
=A0 =C2=A0&quot;pid1&quot;, even though all addresses in that block are in =
&quot;pid2&quot;,</div><div>=C2=A0 =C2=A0because &quot;ipv4:<a href=3D"http=
://10.0.0.0/8" target=3D"_blank">10.0.0.0/8</a>&quot; is the longest prefix=
 in the network map</div><div>=C2=A0 =C2=A0which prefix-matches &quot;ipv4:=
<a href=3D"http://10.0.0.0/15" target=3D"_blank">10.0.0.0/15</a>&quot;, and=
 that prefix is in</div><div>=C2=A0 =C2=A0&quot;pid1&quot;.</div><div><b>&l=
t;QX&gt; I agree with Shenzhen&#39;s comments. <a href=3D"http://10.0.0.0/X=
X" target=3D"_blank">10.0.0.0/XX</a> is inconsistent with the settings in S=
ection 7.1. It should be fixed in the next version.</b></div><div><br></div=
><div><b>Page 21</b></div><div>=C2=A0 =C2=A0</div><div>=C2=A0 =C2=A0Also, w=
hile technically this document does not introduce any security</div><div>=
=C2=A0 =C2=A0risks not inherent in the Endpoint Property Service defined by=
</div><div>=C2=A0 =C2=A0[RFC7285], the GET-mode property map resource defin=
ed in this</div><div>=C2=A0 =C2=A0document does make it easier for a client=
 to download large numbers</div><div>=C2=A0 =C2=A0of property values.=C2=A0=
 Accordingly, an ALTO Server should limit GET-</div><div>=C2=A0 =C2=A0mode =
property maps for to properties which do not contain sensitive</div><div>=
=C2=A0 =C2=A0data.</div><div><b>&lt;QX&gt; &quot;for to properties&quot; -&=
gt; &quot;to properties&quot;</b></div><div><br></div><div>9.1. =C2=A0appli=
cation/alto-* Media Types<br></div><div>=C2=A0 =C2=A0...</div><div>=C2=A0 =
=C2=A0Security considerations: =C2=A0Security considerations relating to th=
e</div><div><b>&lt;QX&gt; &quot;relating&quot; -&gt; &quot;related&quot;</b=
></div><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 generation and consumption =
of ALTO Protocol messages are discussed</div><div>=C2=A0 =C2=A0 =C2=A0 in S=
ection 15 of [RFC7285].</div><div><br></div><div>=C2=A0 =C2=A0Interoperabil=
ity considerations: =C2=A0This document specifies format of</div><div><b>&l=
t;QX&gt; &quot;format&quot; -&gt; &quot;formats&quot;</b></div><div><br></d=
iv></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On=
 Mon, Jun 26, 2017 at 11:58 PM, Shenshen Chen <span dir=3D"ltr">&lt;<a href=
=3D"mailto:cs90911@gmail.com" target=3D"_blank">cs90911@gmail.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr"><div>Dear authors of alto-unified-props and all,</div><div><br></d=
iv><div>In section 2.5, I feel &quot;property type&quot; could be better (b=
ecause RFC7285 names</div><div>sections using &quot;property type&quot;, bu=
t not &quot;property name&quot;) and &quot;property value&quot;=C2=A0</div>=
<div>should be mentioned (includes the &quot;null&quot; value mentioned in =
section 4.6).</div><div>I also suggest showing=C2=A0the &quot;null&quot; va=
lue can be inherited explicitly</div><div>in the section 3.1.3 or emphasizi=
ng it as a normal property value.</div><div><br></div><div>Here is a list o=
f typos (comments are marked with &quot;&gt;&gt;&gt;&quot;):</div><div><br>=
</div><div>[Page 2]</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.1.3.=C2=A0 Heira=
rchy And Inheritance . . . . . . . . . . . . . . =C2=A0 7</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A03.1.4.=C2=A0 Relationship To Network Maps =C2=A0. . . .=
 . . . . . . . . =C2=A0 8</div><div>=C2=A0 =C2=A0 =C2=A03.2.=C2=A0 PID Doma=
in =C2=A0. . . . . . . . . . . . . . . . . . . . . . . =C2=A0 9</div><div>=
=C2=A0 =C2=A0 =C2=A0 =C2=A03.2.1.=C2=A0 Domain Name . . . . . . . . . . . .=
 . . . . . . . . . =C2=A0 9</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.2.2.=C2=
=A0 Domain-Specific Entity Addresses =C2=A0. . . . . . . . . . =C2=A0 9</di=
v><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.2.3.=C2=A0 Heirarchy And Inheritance . =
. . . . . . . . . . . . . =C2=A0 9</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.2=
.4.=C2=A0 Relationship To Internet Addresses Domains =C2=A0. . . . . =C2=A0=
 9</div><div><br></div><div>&gt;&gt;&gt; &quot;To&quot; =3D&gt; &quot;to&qu=
ot;, &quot;And&quot; =3D&gt; &quot;and&quot;, &quot;Heirarchy&quot; =3D&gt;=
 &quot;Hierarchy&quot;</div><div><br></div><div><br></div><div>[Page 3]</di=
v><div>=C2=A0 =C2=A0Second, the EPS is only defined as a POST-mode service.=
=C2=A0 Clients must</div><div>=C2=A0 =C2=A0request the properties for an ex=
plicit set of addresses.=C2=A0 By</div><div>=C2=A0 =C2=A0contrast, [RFC7285=
] defines a GET-mode Cost Map resource which</div><div>=C2=A0 =C2=A0returns=
 all available costs, so a client can get the full set of</div><div>=C2=A0 =
=C2=A0costs once, and then lookup costs without querying the ALTO server.</=
div><div>=C2=A0 =C2=A0RFC7285 does not define an equivalent service for end=
point</div><div>=C2=A0 =C2=A0properties.=C2=A0 Granted, it is not be practi=
cal to enumerate the</div><div><br></div><div>&gt;&gt;&gt; &quot;is not be&=
quot; =3D&gt; &quot;is not&quot;</div><div><br></div><div><br></div><div>[P=
age 4]</div><div>=C2=A0 =C2=A0This document proposes a new approach to ALTO=
 properties.</div><div>=C2=A0 =C2=A0Specifically, it defines two new resour=
ce types, namely Property Maps</div><div>=C2=A0 =C2=A0and Filtered Property=
 Maps.=C2=A0 The former are GET-mode resources which</div><div>=C2=A0 =C2=
=A0return the property values for all entities in a domain, and are</div><d=
iv>=C2=A0 =C2=A0analogous the ALTO&#39;s Network Map and Cost Map resources=
.=C2=A0 The latter</div><div><br></div><div>&gt;&gt;&gt; &quot;Network Map =
and Cost Map resources&quot; =3D&gt; &quot;Network Maps and Cost Maps&quot;=
</div><div>=C2=A0 =C2=A0 I think it should keep the same format with &quot;=
Filtered Network Maps=C2=A0</div><div>=C2=A0 =C2=A0 and Filtered Cost Maps&=
quot; in the last sentence of this paragraph.</div><div><br></div><div>=C2=
=A0 =C2=A0are POST-mode resources which return the values for a set of</div=
><div>=C2=A0 =C2=A0properties and entities requested by the client, and are=
 analogous to</div><div>=C2=A0 =C2=A0ALTO&#39;s Filtered Network Maps and F=
iltered Cost Maps.</div><div><br></div><div>[Page 7]</div><div>3.1.3.=C2=A0=
 Heirarchy And Inheritance</div><div><br></div><div>[Page 9]</div><div>3.2.=
3.=C2=A0 Heirarchy And Inheritance</div><div><br></div><div>&gt;&gt;&gt; &q=
uot;Heirarchy&quot; =3D&gt; &quot;Hierarchy&quot;</div><div><br></div><div>=
[Page 19]</div><div>=C2=A0 =C2=A0Note that the value of &quot;pid&quot; for=
 the prefix &quot;ipv4:<a href=3D"http://10.0.0.0/15" target=3D"_blank">10.=
0.0.0/15</a>&quot; is</div><div>=C2=A0 =C2=A0&quot;pid1&quot;, even though =
all addresses in that block are in &quot;pid2&quot;,</div><div>=C2=A0 =C2=
=A0because &quot;ipv4:<a href=3D"http://10.0.0.0/8" target=3D"_blank">10.0.=
0.0/8</a>&quot; is the longest prefix in the network map</div><div>=C2=A0 =
=C2=A0which prefix-matches &quot;ipv4:<a href=3D"http://10.0.0.0/15" target=
=3D"_blank">10.0.0.0/15</a>&quot;, and that prefix is in</div><div>=C2=A0 =
=C2=A0&quot;pid1&quot;.</div><div><br></div><div>=C2=A0 =C2=A0POST /propmap=
/lookup/pid HTTP/1.1</div><div>=C2=A0 =C2=A0Host: <a href=3D"http://alto.ex=
ample.com" target=3D"_blank">alto.example.com</a></div><div>=C2=A0 =C2=A0Ac=
cept: application/alto-propmap+json,<wbr>application/alto-error+json</div><=
div>=C2=A0 =C2=A0Content-Length: ###</div><div>=C2=A0 =C2=A0Content-Type: a=
pplication/alto-propmapparams<wbr>+json</div><div><br></div><div>=C2=A0 =C2=
=A0{</div><div>=C2=A0 =C2=A0 =C2=A0&quot;entities&quot; : [</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv=
4:192.0.2.0 =C2=A010.0.0.0&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.16 10.1.0.0&quot;,=
</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0&quot;ipv4:192.0.2.64 =C2=A010.3.0.0&quot;,</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.1=
28 =C2=A011.0.0.0&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:<a href=3D"http://192.0.2.0/26" t=
arget=3D"_blank">192.0.2.0/26</a> <a href=3D"http://10.0.0.0/15" target=3D"=
_blank">10.0.0.0/15</a>&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:<a href=3D"http://192.0.2.0/3=
0" target=3D"_blank">192.0.2.0/30</a> <a href=3D"http://10.0.0.0/17" target=
=3D"_blank">10.0.0.0/17</a>&quot; ],</div><div>=C2=A0 =C2=A0 =C2=A0&quot;pr=
operties&quot; : [ &quot;pid&quot; ]</div><div>=C2=A0 =C2=A0}</div><div><br=
></div><div>&gt;&gt;&gt; This part should be modified into:</div><div><br><=
/div><div>=C2=A0 =C2=A0Note that the value of &quot;pid&quot; for the prefi=
x &quot;ipv4:<a href=3D"http://192.0.2.0/26" target=3D"_blank">192.0.2.0/26=
</a>&quot; is</div><div>=C2=A0 =C2=A0&quot;pid1&quot;, even though all addr=
esses in that block are in &quot;pid2&quot;,</div><div>=C2=A0 =C2=A0because=
 &quot;ipv4:<a href=3D"http://192.0.2.0/25" target=3D"_blank">192.0.2.0/25<=
/a>&quot; is the longest prefix in the network map</div><div>=C2=A0 =C2=A0w=
hich prefix-matches &quot;ipv4:<a href=3D"http://192.0.2.0/26" target=3D"_b=
lank">192.0.2.0/26</a>&quot;, and that prefix is in</div><div>=C2=A0 =C2=A0=
&quot;pid1&quot;.</div><div><br></div><div>=C2=A0 =C2=A0POST /propmap/looku=
p/pid HTTP/1.1</div><div>=C2=A0 =C2=A0Host: <a href=3D"http://alto.example.=
com" target=3D"_blank">alto.example.com</a></div><div>=C2=A0 =C2=A0Accept: =
application/alto-propmap+json,<wbr>application/alto-error+json</div><div>=
=C2=A0 =C2=A0Content-Length: ###</div><div>=C2=A0 =C2=A0Content-Type: appli=
cation/alto-propmapparams<wbr>+json</div><div><br></div><div>=C2=A0 =C2=A0{=
</div><div>=C2=A0 =C2=A0 =C2=A0&quot;entities&quot; : [</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:19=
2.0.2.0&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.16&quot;,</div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:192.0.2.6=
4&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&quot;ipv4:192.0.2.128&quot;,</div><div>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:<a href=3D"http:=
//192.0.2.0/26" target=3D"_blank">192.0.2.0/26</a>&quot;,</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;ipv4:<a=
 href=3D"http://192.0.2.0/30" target=3D"_blank">192.0.2.0/30</a>&quot; ],</=
div><div>=C2=A0 =C2=A0 =C2=A0&quot;properties&quot; : [ &quot;pid&quot; ]</=
div><div>=C2=A0 =C2=A0}</div><div><br></div><div>[Page 23]</div><div>=C2=A0=
 =C2=A0New ALTO entity domains are assigned after IETF Review [RFC5226] to<=
/div><div>=C2=A0 =C2=A0ensure that proper documentation regarding the new A=
LTO entity</div><div>=C2=A0 =C2=A0domains and their security considerations=
 has been provided.=C2=A0 RFCs</div><div><br></div><div>&gt;&gt;&gt; &quot;=
has been&quot; =3D&gt; &quot;have been&quot;</div><div><br></div><div>=C2=
=A0 =C2=A0defining new entity domains should indicate how an entity in a</d=
iv><div>=C2=A0 =C2=A0registered domain is encoded as an EntityName, and, if=
 applicable,</div><div>=C2=A0 =C2=A0the rules defining the entity hierarchy=
 and property inheritance.</div><div>=C2=A0 =C2=A0Updates and deletions of =
ALTO entity domains follow the same</div><div>=C2=A0 =C2=A0procedure.</div>=
<div><br></div><div><br></div><div>Best Regards,</div><div>Shenshen</div><d=
iv><br></div></div>
<br>______________________________<wbr>_________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/alto</a><br>
<br></blockquote></div><span class=3D"gmail-HOEnZb"><font color=3D"#888888"=
><br><br clear=3D"all"><div><br></div>-- <br><div class=3D"gmail-m_-7395265=
687878885407gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><d=
iv dir=3D"ltr"><font size=3D"2">Qiao Xiang<br>Postdoctoral Fellow,=C2=A0</f=
ont></div><div dir=3D"ltr"><font size=3D"2">Department of Computer Science,=
</font></div><div dir=3D"ltr"><font size=3D"2">Yale University</font></div>=
</div></div></div></div></div>
</font></span></div>
<br>______________________________<wbr>_________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/alto</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div cla=
ss=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=
=3D"ltr"><div dir=3D"ltr"><div style=3D"text-align:justify"><font face=3D"C=
alibri, sans-serif"><span style=3D"font-size:14px">Thanks a lot!</span></fo=
nt></div><div style=3D"text-align:justify"><font face=3D"Calibri, sans-seri=
f"><span style=3D"font-size:14px">Sincerely!</span></font></div><div style=
=3D"text-align:justify"><font face=3D"Calibri, sans-serif"><span style=3D"f=
ont-size:14px">************************************************************=
*</span></font></div><div style=3D"text-align:justify"><div style=3D"color:=
rgb(136,136,136);font-size:small"><span style=3D"font-size:14px;font-family=
:Calibri,sans-serif">Haizhou Du, =C2=A0</span><br></div><div style=3D"color=
:rgb(136,136,136);font-size:small"><span style=3D"font-size:14px;font-famil=
y:Calibri,sans-serif">Department of Computer Science</span></div></div><div=
 style=3D"text-align:justify"><span style=3D"font-size:14px;font-family:Cal=
ibri,sans-serif">**********************************************************=
***</span><br></div></div></div></div></div></div></div></div>
</div></div>

--94eb2c065238af0de20553161598--


From nobody Thu Jun 29 02:44:06 2017
Return-Path: <bill.wu@huawei.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 C1C1312ECCE; Thu, 29 Jun 2017 02:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 0fKMvXcyiEwm; Thu, 29 Jun 2017 02:44:02 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37FB512ECBC; Thu, 29 Jun 2017 02:44:01 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DQA74692; Thu, 29 Jun 2017 09:43:59 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 29 Jun 2017 10:43:58 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.25]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Thu, 29 Jun 2017 17:43:52 +0800
From: Qin Wu <bill.wu@huawei.com>
To: xin wang <xinwang2014@hotmail.com>, "draft-ietf-alto-performance-metrics@ietf.org" <draft-ietf-alto-performance-metrics@ietf.org>
CC: IETF ALTO <alto@ietf.org>
Thread-Topic: Here is a review of draft-ietf-alto-performance-metrics-01
Thread-Index: AQHS77KHjlFF1/I4VEOSeLJnKnux4aI7lZ+w
Date: Thu, 29 Jun 2017 09:43:51 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9A98C73C@nkgeml513-mbx.china.huawei.com>
References: <PS1PR0302MB24575EB8EFEB9023D40F4530A8DD0@PS1PR0302MB2457.apcprd03.prod.outlook.com>
In-Reply-To: <PS1PR0302MB24575EB8EFEB9023D40F4530A8DD0@PS1PR0302MB2457.apcprd03.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.136.78.218]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9A98C73Cnkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.5954CBDF.014B, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.1.25, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: af2ec23c730ef40819d9c5ea70052ec3
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/BjTN7swj75vR8Gl70OgC7Nr6V4s>
Subject: Re: [alto] Here is a review of draft-ietf-alto-performance-metrics-01
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: Thu, 29 Jun 2017 09:44:05 -0000

--_000_B8F9A780D330094D99AF023C5877DABA9A98C73Cnkgeml513mbxchi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

VGhhbmtzIFhpbiwgc2VlIHJlcGx5IGlubGluZSBiZWxvdy4NCreivP7IyzogeGluIHdhbmcgW21h
aWx0bzp4aW53YW5nMjAxNEBob3RtYWlsLmNvbV0NCreiy83KsbzkOiAyMDE3xOo21MIyOMjVIDEw
OjA2DQrK1bz+yMs6IGRyYWZ0LWlldGYtYWx0by1wZXJmb3JtYW5jZS1tZXRyaWNzQGlldGYub3Jn
DQqzrcvNOiBJRVRGIEFMVE8NCtb3zOI6IEhlcmUgaXMgYSByZXZpZXcgb2YgZHJhZnQtaWV0Zi1h
bHRvLXBlcmZvcm1hbmNlLW1ldHJpY3MtMDENCg0KDQpEZWFyIGF1dGhvcnMgb2YgIkFMVE8gUGVy
Zm9ybWFuY2UgQ29zdCBNZXRyaWNzobEsDQoNCg0KDQpZb3VyIGRyYWZ0IGFib3V0IGV4dGVuZGlu
ZyBjb3N0IG1ldHJpY3Mgb2YgQUxUTyBsb29rcyB2ZXJ5IHVzZWZ1bCwgZXNwZWNpYWxseSBmb3Ig
dmFyaWV0aWVzIG9mIGFwcGxpY2F0aW9ucyB3aXRoIGRpZmZlcmVudCBjcml0ZXJpYSB0byBtYWtl
IGRlY2lzaW9ucyBmb3IgdHJhZmZpYyBlbmdpbmVlcmluZy4gVGhlIGZvbGxvd2luZyBpcyBhIHJl
dmlldyBvZiB5b3VyIGRyYWZ0Og0KDQoNCg0KYS4gTGluayBNYXhpbXVtIFJlc2VydmFibGUgQmFu
ZHdpZHRoIGFuZCBMaW5rIFJlc2lkdWUgQmFuZHdpZHRoDQoNCg0KDQpUaGVzZSB0aHJlZSBjb3N0
IG1ldHJpY3MgbG9vayB2ZXJ5IHNpbWlsYXIgYnV0IGhhdmUgZGlmZmVyZW50IG1lYW5pbmdzIGFj
Y29yZGluZyB0byB5b3VyIGRyYWZ0LiBJbiBteSB1bmRlcnN0YW5kaW5nLCBiYXNlZCBvbiB0aGUg
Y29uY2VwdCBvZiBiYW5kd2lkdGggb3ZlcnN1YnNjcmlwdGlvbiwgYSByZXNlcnZlZCBiYW5kd2lk
dGggY291bGQgYmUgbGFyZ2VyIHRoYW4gY3VycmVudCByZW1haW5pbmcgYmFuZHdpZHRoIChlcXVh
bHMgdG8gbWF4IGJhbmR3aWR0aCBzdWJ0cmFjdCB0aGUgc3VtIG9mIGFsbCByZXNlcnZlZCBiYW5k
d2lkdGgpLiBUaGVuLCBMaW5rIE1heGltdW0gUmVzZXJ2YWJsZSBCYW5kd2lkdGggc2hvdWxkIGJl
IHNsaWdodGx5IGxhcmdlciB0aGFuIExpbmsgUmVzaWR1ZSBCYW5kd2lkdGguIElzIHRoaXMgcmln
aHQ/DQoNCg0KDQpbUWluXTogU2hvcnQgYW5zd2VyIGlzIFllcy4gTG9uZyBhbnN3ZXIgaXM6DQoN
ClJlc2lkYncgPSBtYXhidyAtICB0dW5uZWwgcmVzZXJ2YXRpb24gYncNCg0KTWF4cmVzYncgY2Fu
IGJlIGxhcmdlciB0aGFuIG1heGJ3IGlmIHRoZSBsaW5rIGlzIG92ZXJzdWJzY2lyYmVkDQoNClRo
ZXJlZm9yZSBNYXhyZXNidyBjb3VsZCBiZSBsYXJnZXIgdGhhbiBSZXNpZGJ3Lg0KDQoNCg0KYi4g
VW5pdGxlc3MgcGVyZm9ybWFuY2Ugc2NvcmVzDQoNCg0KDQpJbiBzZWN0aW9uIDIuMSwgdGhlIGRy
YWZ0IHN1Z2dlc3RzIHByb3ZpZGluZyB1bml0bGVzcyBwZXJmb3JtYW5jZSBzY29yZXMgZm9yIHBy
aXZhY3kgaXNzdWVzLiBJbiBBTFRPIGNvc3QgbW9kZSwgaXQgZGVmaW5lcyChsG9yZGluYWyhsSB3
aGljaCBpbmRpY2F0ZXMgdGhlIHJhbmtpbmcgb2YgdGhlIGNvc3QgdmFsdWVzIGluc3RlYWQgb2Yg
YWN0dWFsIGNvc3RzLiBEbyB5b3Ugc3VnZ2VzdCB0byBhZGQgbW9yZSBpbnRlbGxpZ2VudCBhYnN0
cmFjdGlvbiBvZiBjb3N0IHZhbHVlcyBiZXNpZGVzIG9mIHJhbmtpbmc/DQoNCltRaW5dOiBJIHRo
aW5rIGFkZGluZyBtb3JlIGludGVsbGlnZW50IGFic3RyYWN0aW9uIG9mIGNvc3QgdmFsdWVzIGJl
c2lkZXMgb2YgcmFua2luZyB1c2VmdWwsIGJ1dCB3ZSBuZWVkIHRvIGlkZW50aWZ5IHVzZSBjYXNl
IHRvIHNob3cgZGVmaWNpZW5jeSBvZiByYW5raW5nIGJlZm9yZSBpbnRyb2R1Y2luZyBuZXcgaW50
ZWxsaWdlbnQgYWJzdHJhY3Rpb24uDQoNCg0KDQpjLiBQYWNrZXQgRGVsYXkgVmFyaWF0aW9uDQoN
Cg0KDQpUaGUgZHJhZnQgdXNlcyB0aGUgbWluaW11bSBkZWxheSBvYnNlcnZlZCBhcyB0aGUgZGVm
aW5pdGlvbiBvZiBwYWNrZXQgZGVsYXkgdmFyaWF0aW9uLiBJIGFtIG5vdCBzdXJlIGl0IGlzIGEg
Z29vZCBzb2x1dGlvbi4gVGhlcmUgYXJlIHNvbWUgb3RoZXIgYXBwcm9hY2hlcyB5b3UgbWF5IGNv
bnNpZGVyLCBzdWNoIGFzIHN0YW5kYXJkIGRldmlhdGlvbi4NCg0KDQoNCltRaW5dOiBUaGUgbWlu
aW11bSBkZWxheSAgb2JzZXJ2ZWQgaXMganVzdCB1c2VkIGFzIHJlZmVyZW5jZSBkZWxheSwgc2Vl
IHRoZSBjb21wbGV0ZSBkZWZpbml0aW9uIGFzIGZvbGxvd3M6DQoNCqGwDQogICBNZXRyaWMgbmFt
ZToNCiAgICAgIFBhY2tldCBEZWxheSBWYXJpYXRpb24NCiAgIE1ldHJpYyBEZXNjcmlwdGlvbjoN
CiAgICAgIFRvIHNwZWNpZnkgc3BhdGlhbCBhbmQgdGVtcG9yYWwgYWdncmVnYXRlZCBqaXR0ZXIg
KHBhY2tldCBkZWxheQ0KICAgICAgdmFyaWF0aW9uKSB3aXRoIHJlc3BlY3QgdG8gdGhlIG1pbmlt
dW0gZGVsYXkgb2JzZXJ2ZWQgb24gdGhlDQoNCiAgICAgIHN0cmVhbSBvdmVyIHRoZSBzcGVjaWZp
ZWQgc291cmNlIGFuZCBkZXN0aW5hdGlvbi4NCg0KobENCg0KWW91IGFyZSByaWdodCwgc3RhbmRh
cmQgZGV2aWF0aW9uIHdpbGwgYmUgdXNlZC4NCg0KDQoNCmQuIFRoZSB1bml0IG9mIFBlcmlvZGlj
IE9uZSBXYXkgRGVsYXkNCg0KDQoNClRoZSBkcmFmdCB1c2VzIHNlY29uZHMgYXMgdGhlIHVuaXQg
b2YgUGVyaW9kaWMgT25lIFdheSBEZWxheS4gSSBhbSBub3Qgc3VyZSBpdCBpcyB0eXBvcyBvciBu
b3Qgc2luY2UgdGhlIGV4YW1wbGUgc2hvd3MgdGhlIHBvd2RlbGF5IGNvc3QgdmFsdWVzIGFyZSAx
MCwgMjAsIGFuZCAzMC4NCg0KDQoNCltRaW5dOiBJdCBpcyBub3QgdHlwbywgaXQgaXMgaW50ZW5k
ZWQuIFNlZSBzZWN0aW9uIDcuNC4zIG9mIGRyYWZ0LWlldGYtaXBwbS1pbml0aWFsLXJlZ2lzdHJ5
LTAzLg0KDQpXZSBkb26hr3QgZGVmaW5lIGFueSBuZXcgbWV0cmljIHdpdGggbmV3IG1lYXN1cmVt
ZW50IHVuaXQgaGVyZS4NCg0KDQoNCkFsc28gdGhlcmUgYXJlIHNvbWUgdHlwb3MgeW91IG1heSBm
aXg6DQoNCg0KDQpBYnN0cmFjdGlvbjogYWRkIHNwYWNlIGJldHdlZW4gIkJHUC1MUyxPU1BGLVRF
IjsNCg0KUGFnZSAyOiChsGRlbGF5IHNlbnNpdGl2ZaGxIC0+IKGwZGVsYXktc2Vuc2l0aXZlobE7
DQoNClBhZ2UgMjogobBhIHNldCBuZXehsSAtPiChsGEgc2V0IG9mIG5ld6GxOw0KDQpQYWdlIDI6
IKGwIGV4cGxpY2l0ZWx5obEgLT4gobAgZXhwbGljaXRseaGxDQoNClBhZ2UgNDogobAgaW52bG92
ZaGxIC0+IKGwIGludm9sdmUiDQoNCg0KDQpbUWluXTogRml4ZWQsIHRoYW5rcy4NCg0KDQoNCkJl
c3QsDQoNClhpbg0KDQo=

--_000_B8F9A780D330094D99AF023C5877DABA9A98C73Cnkgeml513mbxchi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Helvetica Neue";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML =D4=A4=C9=E8=B8=F1=CA=BD Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=CB=CE=CC=E5;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLChar
	{mso-style-name:"HTML =D4=A4=C9=E8=B8=F1=CA=BD Char";
	mso-style-priority:99;
	mso-style-link:"HTML =D4=A4=C9=E8=B8=F1=CA=BD";
	font-family:=CB=CE=CC=E5;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks Xin=
, see reply inline below.<o:p></o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:=CB=
=CE=CC=E5">=B7=A2=BC=FE=C8=CB<span lang=3D"EN-US">:</span></span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5"> xin wan=
g [mailto:xinwang2014@hotmail.com]
<br>
</span><b><span style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5">=B7=A2=
=CB=CD=CA=B1=BC=E4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5"> 2017</span><span s=
tyle=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5">=C4=EA<span lang=3D"EN-U=
S">6</span>=D4=C2<span lang=3D"EN-US">28</span>=C8=D5<span lang=3D"EN-US">
 10:06<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> draft-ietf-alto-performance-metrics@ietf.org<br>
</span><b>=B3=AD=CB=CD<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> IETF ALTO<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Here is a review of draft-ietf-alto-performance-metrics-01<o:p></o:p></sp=
an></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div id=3D"divtagdefaultwrapper">
<p><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetic=
a Neue&quot;,&quot;serif&quot;;color:black">Dear authors of &quot;ALTO Perf=
ormance Cost Metrics=A1=B1,<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">Your draft about extending cost me=
trics of ALTO looks very useful, especially for varieties of applications w=
ith different criteria to make decisions for traffic engineering.
 The following is a review of your draft:<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">a. Link Maximum Reservable Bandwid=
th and Link Residue Bandwidth<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">These three cost metrics look&nbsp=
;very similar but have different meanings according to your draft. In my un=
derstanding, based on the concept of bandwidth oversubscription,
 a reserved bandwidth could be larger than current remaining bandwidth (equ=
als to max bandwidth subtract the sum of all reserved bandwidth). Then, Lin=
k Maximum Reservable Bandwidth should be slightly larger than Link Residue =
Bandwidth. Is this right?<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">[Qin]: Short answer is Yes. Lo=
ng answer is:<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">Residbw =3D maxbw -&nbsp; tunn=
el reservation bw
<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">Maxresbw can be larger than ma=
xbw if the link is oversubscirbed
<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">Therefore Maxresbw could be la=
rger than Residbw.<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">b. Unitless performance scores<o:p=
></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">In section 2.1, the draft suggests=
 providing unitless performance scores for privacy issues. In ALTO cost mod=
e, it defines =A1=B0ordinal=A1=B1 which indicates the&nbsp;ranking of the
 cost values instead of actual costs. Do you suggest to add more intelligen=
t abstraction of cost values besides of ranking?<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">[Qin]: I think adding more int=
elligent abstraction of cost values besides of ranking useful, but we need =
to identify use case to show deficiency of ranking before
 introducing new intelligent abstraction.<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">c. Packet Delay Variation<o:p></o:=
p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">The draft uses the minimum delay o=
bserved as the definition of packet delay variation. I am not sure it is a =
good solution. There are some other approaches you may consider,
 such as standard deviation.<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">[Qin]: The minimum delay &nbsp=
;observed is just used as reference delay, see the complete definition as f=
ollows:<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">=A1=B0<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbs=
p; Metric name:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; Packet Delay Variation<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbs=
p; Metric Description:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; To specify spatial and temporal aggregated jitter (pac=
ket delay<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; variation) with respect to the minimum delay observed =
on the<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 stream over the specified source and destination.<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">=A1=B1<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:#1F497D">You are right, standard deviatio=
n will be used.<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">d. The unit of Periodic One Way De=
lay<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">The draft uses seconds as the unit=
 of Periodic One Way Delay. I am not sure it is typos or not since the exam=
ple shows the powdelay cost values are 10, 20, and 30.<o:p></o:p></span></p=
>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">[Qin]: It is not typo, it is i=
ntended. See section 7.4.3 of draft-ietf-ippm-initial-registry-03.<o:p></o:=
p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">We don=A1=AFt define any new m=
etric with new measurement unit here.<o:p></o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">Also there are some typos you may =
fix:<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0);min-height: 14px">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">Abstraction: add space between &qu=
ot;BGP-LS,OSPF-TE&quot;;<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">Page 2: =A1=B0delay sensitive=A1=
=B1 -&gt; =A1=B0delay-sensitive=A1=B1;<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">Page 2: =A1=B0a set new=A1=B1 -&gt=
; =A1=B0a set of new=A1=B1;<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">Page 2: =A1=B0 explicitely=A1=B1 -=
&gt; =A1=B0 explicitly=A1=B1<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">Page 4: =A1=B0 invlove=A1=B1 -&gt;=
 =A1=B0 involve&quot;<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:#1F497D">[Qin]: Fixed, thanks.<o:p></o:=
p></span></p>
<p><span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetic=
a Neue&quot;,&quot;serif&quot;;color:black"><br>
<br>
<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">Best,<o:p></o:p></span></p>
<p style=3D"font-variant-ligatures: normal;font-variant-caps: normal;font-s=
tretch: normal;-webkit-text-stroke: rgb(0, 0, 0)">
<span lang=3D"EN-US" style=3D"font-size:9.0pt;font-family:&quot;Helvetica N=
eue&quot;,&quot;serif&quot;;color:black">Xin<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_B8F9A780D330094D99AF023C5877DABA9A98C73Cnkgeml513mbxchi_--


From nobody Thu Jun 29 03:29:05 2017
Return-Path: <bill.wu@huawei.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 7134612EBFA; Thu, 29 Jun 2017 03:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 fR6H6HPFcjay; Thu, 29 Jun 2017 03:29:01 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7035B127876; Thu, 29 Jun 2017 03:29:00 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DQA82248; Thu, 29 Jun 2017 10:28:58 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 29 Jun 2017 11:28:56 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.25]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Thu, 29 Jun 2017 18:28:52 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Li, Geng" <geng.li@yale.edu>, "alto@ietf.org" <alto@ietf.org>, "draft-ietf-alto-performance-metrics@ietf.org" <draft-ietf-alto-performance-metrics@ietf.org>
Thread-Topic: Review on draft-ietf-alto-performance-metrics-01 by Geng
Thread-Index: AQHS8HfYt8rCC6ciPE6maaEoxvOQy6I7ohGA
Date: Thu, 29 Jun 2017 10:28:51 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9A98C8B3@nkgeml513-mbx.china.huawei.com>
References: <CY4PR08MB3526919211B51665A5855A5091D20@CY4PR08MB3526.namprd08.prod.outlook.com>
In-Reply-To: <CY4PR08MB3526919211B51665A5855A5091D20@CY4PR08MB3526.namprd08.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.136.78.218]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9A98C8B3nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.5954D66A.0066, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.1.25, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 8a77e176b53efc78ede77fda33ffe0f5
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/b_mHb4S7YTi9kY6t_OCFNnGaRtE>
Subject: Re: [alto] Review on draft-ietf-alto-performance-metrics-01 by Geng
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: Thu, 29 Jun 2017 10:29:04 -0000

--_000_B8F9A780D330094D99AF023C5877DABA9A98C8B3nkgeml513mbxchi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

VGhhbmtzIEdlbmcgZm9yIHlvdXIgaW50ZXJlc3RpbmcgY29tbWVudHMsIHBsZWFzZSBzZWUgbXkg
cmVwbHkgaW5saW5lIGJlbG93Lg0KDQotUWluDQq3orz+yMs6IExpLCBHZW5nIFttYWlsdG86Z2Vu
Zy5saUB5YWxlLmVkdV0NCreiy83KsbzkOiAyMDE3xOo21MIyOcjVIDk6MzQNCsrVvP7IyzogYWx0
b0BpZXRmLm9yZzsgZHJhZnQtaWV0Zi1hbHRvLXBlcmZvcm1hbmNlLW1ldHJpY3NAaWV0Zi5vcmcN
Ctb3zOI6IFJldmlldyBvbiBkcmFmdC1pZXRmLWFsdG8tcGVyZm9ybWFuY2UtbWV0cmljcy0wMSBi
eSBHZW5nDQoNCg0KRGVhciBhdXRob3JzLA0KDQoNCg0KWW91ciB3b3JrIGlzIHF1aXRlIGV4Y2Vs
bGVudCwgYW5kIGhlcmUgYXJlIHNvbWUgc3VnZ2VzdGlvbnMgSSBoYXZlLg0KDQoNCg0KMS4gICAg
IFRoZSBBTFRPIHNlcnZlciBzaG91bGQgaGF2ZSB0aGUgY2FwYWJpbGl0eSB0byB0cmFjayBhbmQg
cmVjb3JkIHRoZSBtb3N0IGZyZXF1ZW50bHkgdXNlZCBvciByZXF1ZXN0ZWQgY29zdCBtZXRyaWNz
IG9mIGVhY2ggQUxUTyBjbGllbnQuIEmhr20gbm90IHN1cmUgaWYgaXQgaXMgdHJ1ZSwgdGhhdCBl
YWNoIGNsaWVudCBtYXkgb25seSBydW4gb25lIG9yIHR3byBjZXJ0YWluIGFwcGxpY2F0aW9ucyBh
dCBtb3N0IG9mIHRoZSB0aW1lLiBUaGVuLCB0aGUgYmVuZWZpdCBpcyB0aGF0IHRoZSBBTFRPIHNl
cnZlciBjYW4gcHJlcGFyZSB0aGUgY29zdCBtZXRyaWNzIGluIGFkdmFuY2VkIGFuZCByZXNwb25k
IHRoZSBjbGllbnRzIGZhc3QgYWZ0ZXIgcmVjZWl2aW5nIHRoZSByZXF1ZXN0Lg0KDQpbUWluXTog
VGhpcyBkcmFmdCBhbGxvd3MgQUxUTyBzZXJ2ZXIgY29sbGVjdCBhbmQgcmVjb3JkIGEgYnVuY2gg
b2YgZGF0YSBvbiB0aW1lIHBlcmlvZCBjb3ZlcmluZyBwYXN0IGFuZCBwcmVzZW50LCBidXQgSSBh
bSBub3Qgc3VyZSBob3cgeW91IGNhbiBwcmVwYXJlIGNvc3QgbWV0cmljcyBpbiBhZHZhbmNlLCB1
bmxlc3MgeW91IGNhbiBwcmVkaWN0IHRoZSBjaGFuZ2UgcGF0dGVybiBvZiBzb21lIHBlcmZvcm1h
bmNlIG1ldHJpYyBvciBwcmVkaWN0IHRoZSBwb3NzaWJsZSB2YWx1ZSBvZiBjb3N0IG1ldHJpYyBp
biB0aGUgZnV0dXJlLg0KDQoNCg0KMi4gICAgIEFub3RoZXIgYmVuZWZpdCBvZiByZWNvcmRpbmcg
dGhlIHR5cGUgb2YgY29zdCBtZXRyaWNzIG9mIGVhY2ggY2xpZW50IGlzIHRoYXQgdGhlIEFMVE8g
c2VydmVyIGNhbiBkZXRlY3QgYWJub3JtYWwgYmVoYXZpb3Igb2YgY2xpZW50IG9yIGFwcGxpY2F0
aW9uLCBzdWNoIGFzIGRhdGFiYXNlIHJlc291cmNlIGxlYWtzLCBpbGxlZ2FsIG9jY3VwYXRpb24s
IG9yIG90aGVyIHNlY3VyaXR5IGlzc3Vlcy4NCg0KW1Fpbl06IFRoZSBwZXJmb3JtYW5jZSBtZXRy
aWMgd2UgZXhwb3NlZCB0byB0aGUgY2xpZW50IGlzIHVzZWQgdG8gaGVscCB0aGUgY2xpZW50IHRv
IHNlbGVjdCB0aGUgcmlnaHQgYWNjZXNzIHBvaW50IG9yIHNlbGVjdCBhcHByb3ByaWF0ZSBzaXRl
IGluIHRoZSBkYXRhIGNlbnRlciBiYXNlZCBvbiBuZXR3b3JrIHBlcmZvcm1hbmNlIGNyaXRlcmlh
LiBJIGFtIG5vdCBzdXJlIHdlIGNhbiB1c2VkIHRoZXNlIHBlcmZvcm1hbmNlIG1ldHJpYyB0byBk
ZXRlY3QgYWJub3JtYWwgYmVoYXZpb3Igb2YgY2xpZW50IG9yIHByZXZlbnQgYW55IHJlc291cmNl
IGxlYWsgdW5sZXNzIHlvdSBwcm92aWRlIG1lICBhIGNsZWFyIHVzZSBjYXNlcyBmb3IgdGhhdC4N
Cg0KMy4gQSB2YXJpZXR5IG9mIHBlcmZvcm1hbmNlIGNvc3QgbWV0cmljcyBhbHNvIHJhaXNlIGFu
IGludGVyZXN0aW5nIHNjaGVkdWxpbmcgcHJvYmxlbS4gRm9yIGV4YW1wbGUsIGNsaWVudCChsEGh
sSByZXF1ZXN0cyB0d28gbWV0cmljcywgY2xpZW50IKGwQqGxIGp1c3QgcmVxdWVzdHMgb25lLCBh
bmQgY2xpZW50IKGwQ6GxIHJlcXVlc3RzIHRocmVlIG1ldHJpY3MsIHRoZW4gaG93IHRoZSBBTFRP
IHNlcnZlciBzY2hlZHVsZXMgdG8gcmVzcG9uZCB0aGVtIGluIHRoZSBjb25zdHJhaW50IG9mIGdp
dmVuIHJlc291cmNlcyBmb3Igd29ya2xvYWQgcHJvY2Vzc2luZyBhbmQgbmV0d29yayB0cmFuc21p
dHRpbmcuIEFuZCBmb3IgZWFjaCBjbGllbnQsIHdoYXQgaXMgdGhlIG9yZGVyIG9mIHRoZSBjb3N0
IG1ldHJpYyB0eXBlcyB0byBiZSByZXR1cm5lZD8NCg0KW1Fpbl06IEkgYW0gbm90IHN1cmUgd2Ug
bmVlZCBhIHNvcGhpc3RpY2F0ZWQgc2NoZWR1bGluZyBmZWF0dXJlIGhlcmUuIFRoZSBBTFRPIHNl
cnZlciB3aWxsIHByb2Nlc3MgcmVxdWVzdCBmcm9tIGVhY2ggY2xpZW50IGJ5IG9yZGVyLCB3aG8g
cmVxdWVzdCBmaXJzdCwgd2hvc2UgcmVxdWVzdCB3aWxsIGJlIHByb2Nlc3NlZCBmaXJzdC4NCg0K
DQoNCkhvcGUgdGhlc2UgYXJlIGhlbHBmdWwuDQoNCg0KDQpCZXN0LCBHZW5nDQoNCkNvbXB1dGVy
IFNjaWVuY2UsIFlhbGUNCg==

--_000_B8F9A780D330094D99AF023C5877DABA9A98C8B3nkgeml513mbxchi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:2105610996;
	mso-list-type:hybrid;
	mso-list-template-ids:-1765360416 -1488842482 67698713 67698715 67698703 6=
7698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:18.0pt;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks Gen=
g for your interesting comments, please see my reply inline below.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">-Qin<o:p><=
/o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:=CB=
=CE=CC=E5">=B7=A2=BC=FE=C8=CB<span lang=3D"EN-US">:</span></span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5"> Li, Gen=
g [mailto:geng.li@yale.edu]
<br>
</span><b><span style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5">=B7=A2=
=CB=CD=CA=B1=BC=E4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5"> 2017</span><span s=
tyle=3D"font-size:10.0pt;font-family:=CB=CE=CC=E5">=C4=EA<span lang=3D"EN-U=
S">6</span>=D4=C2<span lang=3D"EN-US">29</span>=C8=D5<span lang=3D"EN-US">
 9:34<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> alto@ietf.org; draft-ietf-alto-performance-metrics@ietf.org<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Review on draft-ietf-alto-performance-metrics-01 by Geng<o:p></o:p></span=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div id=3D"divtagdefaultwrapper">
<div>
<p style=3D"text-align:justify;text-justify:inter-ideograph"><span lang=3D"=
EN-US" style=3D"font-size:14.0pt;color:black">Dear authors,<o:p></o:p></spa=
n></p>
<p style=3D"text-align:justify;text-justify:inter-ideograph"><span lang=3D"=
EN-US" style=3D"font-size:14.0pt;color:black">&nbsp;<o:p></o:p></span></p>
<p style=3D"text-align:justify;text-justify:inter-ideograph"><span lang=3D"=
EN-US" style=3D"font-size:14.0pt;color:black">Your work is quite excellent,=
 and here are some suggestions I have.<o:p></o:p></span></p>
<p style=3D"text-align:justify;text-justify:inter-ideograph"><span lang=3D"=
EN-US" style=3D"font-size:14.0pt;color:black">&nbsp;<o:p></o:p></span></p>
<p style=3D"margin-left:18.0pt;text-align:justify;text-justify:inter-ideogr=
aph;text-indent:-18.0pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN-US" style=3D"font-size:14.0pt;color:b=
lack"><span style=3D"mso-list:Ignore">1.<span style=3D"font:7.0pt &quot;Tim=
es New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US" style=3D"font-size:14.0=
pt;color:black">The ALTO server should have the capability to track and rec=
ord the most frequently used or requested cost metrics of each ALTO client.=
 I=A1=AFm not sure if it is true, that each
 client may only run one or two certain applications at most of the time. T=
hen, the benefit is that the ALTO server can prepare the cost metrics in ad=
vanced and respond the clients fast after receiving the request.<o:p></o:p>=
</span></p>
<p style=3D"margin-left:18.0pt;text-align:justify;text-justify:inter-ideogr=
aph"><span lang=3D"EN-US" style=3D"font-size:14.0pt;color:#1F497D">[Qin]: T=
his draft allows ALTO server collect and record a bunch of data on time per=
iod covering past and present, but I am
 not sure how you can prepare cost metrics in advance, unless you can predi=
ct the change pattern of some performance metric or predict the possible va=
lue of cost metric in the future.<o:p></o:p></span></p>
<p style=3D"margin-left:18.0pt;text-align:justify;text-justify:inter-ideogr=
aph"><span lang=3D"EN-US" style=3D"font-size:14.0pt;color:#1F497D"><o:p>&nb=
sp;</o:p></span></p>
<p style=3D"margin-left:18.0pt;text-align:justify;text-justify:inter-ideogr=
aph;text-indent:-18.0pt;mso-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN-US" style=3D"font-size:14.0pt;color:b=
lack"><span style=3D"mso-list:Ignore">2.<span style=3D"font:7.0pt &quot;Tim=
es New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US" style=3D"font-size:14.0=
pt;color:black">Another benefit of recording the type of cost metrics of ea=
ch client is that the ALTO server can detect abnormal behavior of client or=
 application, such as database resource
 leaks, illegal occupation, or other security issues.<o:p></o:p></span></p>
<p style=3D"margin-left:18.0pt;text-align:justify;text-justify:inter-ideogr=
aph"><span lang=3D"EN-US" style=3D"font-size:14.0pt;color:#1F497D">[Qin]: T=
he performance metric we exposed to the client is used to help the client t=
o select the right access point or select
 appropriate site in the data center based on network performance criteria.=
 I am not sure we can used these performance metric to detect abnormal beha=
vior of client or prevent any resource leak unless you provide me&nbsp; a c=
lear use cases for that.<o:p></o:p></span></p>
<p style=3D"text-align:justify;text-justify:inter-ideograph"><span lang=3D"=
EN-US" style=3D"font-size:14.0pt;color:black">3. A variety of performance c=
ost metrics also raise an interesting scheduling problem. For example, clie=
nt =A1=B0A=A1=B1 requests two metrics, client =A1=B0B=A1=B1
 just requests one, and client =A1=B0C=A1=B1 requests three metrics, then h=
ow the ALTO server schedules to respond them in the constraint of given res=
ources for workload processing and network transmitting. And for each clien=
t, what is the order of the cost metric types
 to be returned?<o:p></o:p></span></p>
<p style=3D"text-align:justify;text-justify:inter-ideograph;text-indent:15.=
0pt"><span lang=3D"EN-US" style=3D"font-size:14.0pt;color:#1F497D">[Qin]: I=
 am not sure we need a sophisticated scheduling feature here. The ALTO serv=
er will process request from each client
 by order, who request first, whose request will be processed first.</span>=
<span lang=3D"EN-US" style=3D"font-size:14.0pt;color:black"><o:p></o:p></sp=
an></p>
<p style=3D"text-align:justify;text-justify:inter-ideograph"><span lang=3D"=
EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p style=3D"text-align:justify;text-justify:inter-ideograph"><span lang=3D"=
EN-US" style=3D"font-size:14.0pt;color:black">Hope these are helpful.<o:p><=
/o:p></span></p>
<p style=3D"text-align:justify;text-justify:inter-ideograph"><span lang=3D"=
EN-US" style=3D"font-size:14.0pt;color:black">&nbsp;<o:p></o:p></span></p>
<p style=3D"text-align:justify;text-justify:inter-ideograph"><span lang=3D"=
EN-US" style=3D"font-size:14.0pt;color:black">Best, Geng<o:p></o:p></span><=
/p>
<p style=3D"text-align:justify;text-justify:inter-ideograph"><span lang=3D"=
EN-US" style=3D"font-size:14.0pt;color:black">Computer Science, Yale<o:p></=
o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_B8F9A780D330094D99AF023C5877DABA9A98C8B3nkgeml513mbxchi_--


From nobody Thu Jun 29 10:55:08 2017
Return-Path: <92yichenqian@tongji.edu.cn>
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 BDF97129B23; Thu, 29 Jun 2017 10:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 2LUQrRXKKLD5; Thu, 29 Jun 2017 10:55:04 -0700 (PDT)
Received: from tongji.edu.cn (mailusrsvr2.tongji.edu.cn [202.120.164.62]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D28BC129ADF; Thu, 29 Jun 2017 10:55:03 -0700 (PDT)
Received: from [180.160.22.66] (unknown [180.160.22.66]) by mailusersvr2 (Coremail) with SMTP id PqR4ygBnr7PwPlVZO_iZAA--.4329S2; Fri, 30 Jun 2017 01:54:58 +0800 (CST)
From: Yichen Qian <92yichenqian@tongji.edu.cn>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <299945C8-58C4-4BEA-98B7-9187F0F263CC@tongji.edu.cn>
Date: Fri, 30 Jun 2017 01:54:57 +0800
To: IETF ALTO <alto@ietf.org>, draft-ietf-alto-cost-calendar@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
X-CM-TRANSID: PqR4ygBnr7PwPlVZO_iZAA--.4329S2
X-Coremail-Antispam: 1UD129KBjvJXoWxCr45Cr4xZr13uFW8Wr4xXrb_yoW5Wr17pF 4S9FW7Kwsxtry2kanaq3WxKryS939rJFyjk34jqw4UAa15CF90vFZIg390kF47Gr1kCw1D Xw4jv398W3sFkr7anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUk0b7Iv0xC_Kw4lb4IE77IF4wAFc2x0x2IEx4CE42xK8VAvwI8I cIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGwA2ocxC64kIII0Yj41l84x0c7CEw4AK67xGY2 AK021l84ACjcxK6xIIjxv20xvE14v26w1j6s0DM28EF7xvwVC0I7IYx2IY6xkF7I0E14v2 6r4UJVWxJr1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAFwI 0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG64xvF2IEw4CE5I8CrVC2j2Wl Yx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4IE7xkEbV WUJVW8JwACjcxG0xvY0x0EwIxGrwCF04k20xvY0x0EwIxGrwCF04k20xvE74AGY7Cv6cx2 6F4UJr1UJwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r1j6r18MI8I3I 0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jrv_JF1lIxkGc2Ij64vIr41lIxAI cVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcV CF04k26cxKx2IYs7xG6rW3Jr0E3s1lIxAIcVC2z280aVAFwI0_Jr0_Gr1lIxAIcVC2z280 aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxUqEoXUUUUU
X-CM-SenderInfo: qrqrmmmu6w00xjmlhvlgxou0/
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/vatFqTj-set7ibQMHyqXmjck7zI>
Subject: [alto] Review of draft-ietf-alto-cost-calendar-01
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: Thu, 29 Jun 2017 17:55:07 -0000

Dear authors,

I think it=E2=80=99s quit useful to provide cost calendar for the users. =
Here=E2=80=99s my review of this draft.=20

1. One concern is that the query result of Cost Calendar is not only =
related to regular data changes, but also can be affected by some =
unexpected topology changes, say link failures. So some cost in Cost =
Calendar can be abnormal and may mislead the user to do the =
inappropriate choice.

2. In the current design, the ALTO client only chooses if it needs the =
calendar.  Is it possible that the ALTO server has several options of =
different combinations of =E2=80=9Ctime-interval-size=E2=80=9D and =
=E2=80=9Cnumber-of intervals=E2=80=9D for ALTO client to choose for more =
fine-grained Cost Calendars?

Other detailed modification:

In the 3rd paragraph of section 2.2, =E2=80=9CA calendar and its =
capabilities are associated to a given information resource=E2=80=9D
- associated to -> associated with

In the 1st paragraph of section 3, =E2=80=9CA calendar is associated to =
an information resource rather than a cost type.=E2=80=9D
- associated to -> associated with

In the 1st paragraph of section 3.1, =E2=80=9Dby an object of type =
'CalendarAttributes', associated to this Cost Type and specified =
below.=E2=80=9D
- associated to -> associated with

In the 3rd paragraph of section 3.1, =E2=80=9Don this "cost-type-name" =
for this ressource entry.=E2=80=9D
- ressource -> resource

In the 1st paragraph of section 4.1.3, =E2=80=9Das specified in the IRD =
to shedule its bulk data transfers as described in the use cases.=E2=80=9D=

- shedule -> schedule

In section 4.2.2, =E2=80=9Cinclude the same addifional member =
"calendar-response-attributes" as =E2=80=A6=E2=80=9D
- addifional ->additional

In the 1st paragraph of section 4.2.3, =E2=80=9CLet us assume an =
Application Client is located in an end sytem with limited resources and =
=E2=80=A6=E2=80=9D=20
- sytem -> system

In the 2nd paragraph of section 4.2.3, =E2=80=9Cthe 'routingcost' is =
assumed to be time sentitive with values provided as ALTO Calendars.=E2=80=
=9D
- sentitive -> sensitive

In the 3rd paragraph of section 4.2.3, "The ALTO Client associated to =
the Application Client =E2=80=A6=E2=80=9D
- associated to -> associated with

In the 4th paragraph of section 4.2.3, =E2=80=9Cthe sollicited ALTO =
Server has =E2=80=A6=E2=80=9D
- sollicited -> solicited

In the 2nd paragraph of section 4.3, =E2=80=9CAn ALTO Server aquiring =
cost values in limited time intervals =E2=80=A6=E2=80=9D
- aquiring -> acquiring

In the 6th paragraph of section 5.1, =E2=80=9Ca small topology with low =
density and low capacity that carries inpredictable=E2=80=9D
- inpredictable -> unpredictable

In the 3rd paragraph of section 5.2, =E2=80=9Cthe interaction with =
Endpoints can be orchestratrated and scheduled at the time slots =E2=80=A6=
=E2=80=9D		=09
- orchestratrated -> orchestrated

The subtitle of section 6.2, =E2=80=9CInformation for IANA on proposed =
Endpoint Propeeries=E2=80=9D
- Propeeries -> Properties

Best wishes,
Eason=


From lili.liu@yale.edu  Thu Jun 29 15:25:46 2017
Return-Path: <lili.liu@yale.edu>
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 5384412773A for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 15:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yale.edu
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 ldmggdYIajhB for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 15:25:43 -0700 (PDT)
Received: from mail-qt0-x244.google.com (mail-qt0-x244.google.com [IPv6:2607:f8b0:400d:c0d::244]) (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 6C86A12EA6A for <alto@ietf.org>; Thu, 29 Jun 2017 15:25:42 -0700 (PDT)
Received: by mail-qt0-x244.google.com with SMTP id w12so13013713qta.2 for <alto@ietf.org>; Thu, 29 Jun 2017 15:25:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd;  h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=uP/umbp2HFXoBGon0f//94B/po6W439HLLdS9T/aLIE=; b=fWRF6JSuo14tk7pmIT02be0rDaKvJ0DjRs5aTDvbUzrNShwisYmvriNM9sw+0jqmfl AKUMbzgQIfqxdiFHrpXH8PD4HAbkOiGPHG32Z3YSPFpGiNz3Ly5nX9yfZVouzvxoSrRU nYh2k7C30Gq9qBusnoI3F10BGNEBXpU7UCPUo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=uP/umbp2HFXoBGon0f//94B/po6W439HLLdS9T/aLIE=; b=dk87594UmQ6ZfM/LaikSO7I9khf3UjG/IMq/9fCsilrpGJYAtzhSSUx+HuTnu7mdvS r9N1htr7keaTi62cdsnP3E3q8fdFIPuNBE8fo2BMhUlHnJ3E5M6b2bty1p6a3jf40L9Y AZ6UbLOBMFFUU2IJmoj5Si4RaT4KbIErlombhXgnHA2cTA2Q5+axCITATxQdgqDajSfn AjeUqBfp1C6czDdTgQ/YKyQdrnK9GTEwWmuv21Msozge3qogmuFH904QxeoK6497aUNV AWX6hXVQMVpvfxHUMduqhM/ebvP625BDy0AIACrT530Zb+pQnc2iySxIc3FrFQFuBssa 8tKw==
X-Gm-Message-State: AKS2vOw9ukfCa0OThvYtoA2WMyFxG8JyLuIfwZYn9G8yy8YePT0vJtwU 7XYiBYb1e+btJFkorS4vDA==
X-Received: by 10.200.42.27 with SMTP id k27mr23969123qtk.40.1498775141230; Thu, 29 Jun 2017 15:25:41 -0700 (PDT)
Received: from [192.168.0.19] (cpe-66-108-205-11.nyc.res.rr.com. [66.108.205.11]) by smtp.gmail.com with ESMTPSA id m3sm4612254qkd.58.2017.06.29.15.25.40 for <alto@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 29 Jun 2017 15:25:40 -0700 (PDT)
From: Lili Liu <lili.liu@yale.edu>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C5FEE81-4696-4817-9C57-3139E4CD7223@yale.edu>
Date: Thu, 29 Jun 2017 18:25:39 -0400
To: alto@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/7cuCZgtsTPq2iz8qiQtR5J3kYqw>
Subject: [alto] some comments on "ALTO for the blockchain draft-hommes-alto-blockchain-02"
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: Thu, 29 Jun 2017 22:26:47 -0000

Dear everyone,

I=A1=AFve been reading "ALTO for the blockchain =
draft-hommes-alto-blockchain-02=A1=B1 recently, and I have some opinions =
on the draft.

The authors present the benefits of ALTO in a blockchain network, and =
consider three categories of blockchain networks: private, consortium =
and public. The authors introduce the background and three kinds of =
blockchain networks in detail.  But the problem is that the author =
describe the benefits and deployment too simply, which makes it hard to =
become a standard and to understand well. In addition, the authors =
didn=A1=AFt introduce how to deploy ALTO in a blockchain network and how =
blockchain network benefits from ALTO. All we know is that ALTO can =
provide guidance by selecting the optimal route to other peers in order =
to optimize the network metrics and to assure QoS requirements, but not =
how in detail.

And there=A1=AFre some grammar errors in the draft:
page7 last para:
line 2: send->sent
line 3: a similar message-> similar messages

In total, this draft is written with good logic. If it could be =
completed in detail, it would be much better.=20

Best,
Lili=


From nobody Thu Jun 29 15:30:56 2017
Return-Path: <lili.liu@yale.edu>
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 290ED12EA6A for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 15:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yale.edu
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 CFFn3VapJpeM for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 15:30:52 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (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 7C7B912773A for <alto@ietf.org>; Thu, 29 Jun 2017 15:30:52 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id 16so88431591qkg.2 for <alto@ietf.org>; Thu, 29 Jun 2017 15:30:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd;  h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=VAN1USFLbap8luKopOxs/iD586lAjxmiF6qFmbknYVw=; b=UJ7O2kpNAhFqFo7tcfGSIyFJMkzD/k1KhcDS11xqE2zbV1Xqd8dRO1nmLSt6enPPKG /W+8G9CLL3FA7y2TxfNBxOYkPBqN0Wcep18iL5xKgYOI7BWGQKJrUrco8EG9499iteqC yD4zLT9Sec27kqWr9WXJLB8IPV0sBTh8KA1P8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=VAN1USFLbap8luKopOxs/iD586lAjxmiF6qFmbknYVw=; b=W4DOj6+S32k9bqMCGuBlJa3GbBx0UvGfK5s9dEBKhAUi8i/7gHjzFqlYqsviLqqxD1 4Q4Y8yXoRTxd2pYupDmxsGT7DTGlU8Idls6qlr8kUOkB0zLkjwSwObjNentu4M5DZ3hP VcOu4ZyWSZa+05IdO7xrmPnjF55ZZMaZ6s9mKDTGUppQafp2gp9vvuiMBBdZDRY7ieD2 MNrQjiZuH5oSTbAWP3DrhHnbOLsTZck6dMJtqKuda5C4ycTKOPQiQq58Ir3en9DntpZw TtcXVGQrXvzGbTNRfxXFu5W+DD5IivlLqP1fxUkWZ+nyL2hA8oJR4g4GL8pPSVOM5qKQ RB/A==
X-Gm-Message-State: AKS2vOyZF8kdxjJ0J19XddAMSpi/cUSKfwNXM/hcZlUSD1LkgZuonzM5 wL3oVd32piyDvQzVOcbwHw==
X-Received: by 10.55.79.198 with SMTP id d189mr20846616qkb.37.1498775451587; Thu, 29 Jun 2017 15:30:51 -0700 (PDT)
Received: from [192.168.0.19] (cpe-66-108-205-11.nyc.res.rr.com. [66.108.205.11]) by smtp.gmail.com with ESMTPSA id h17sm5355905qte.20.2017.06.29.15.30.51 for <alto@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 29 Jun 2017 15:30:51 -0700 (PDT)
From: Lili Liu <lili.liu@yale.edu>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: quoted-printable
Message-Id: <48620123-48B5-4415-BE14-DDD229ABC1FC@yale.edu>
Date: Thu, 29 Jun 2017 18:30:50 -0400
To: alto@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/_6zUe41GKzUFi_tg1C4X6bJDNZ4>
Subject: [alto] several comments on "Application Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery-- draft-ietf-alto-xdom-disc-00"
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: Thu, 29 Jun 2017 22:30:54 -0000

Dear everyone,

I=A1=AFve beed reading the draft "Application Layer Traffic Optimization =
(ALTO) Cross-Domain Server  Discovery-- draft-ietf-alto-xdom-disc-00=A1=B1=
 these days and have some comments as follows:
The authors present cross-domain server discovery in ALTO, which is =
important in multi-domains network. They consider multi domains in the =
network and different ALTO servers might have not the same knowledge. =
Then they design a method to pick up the optimized server for an ALTO =
client. The authors describe the procedures in detail and consider both =
IPv4 and IPv6, which is very considerate.=20

I just have a few opinions on other part of the draft:
page5 sec1.1.2 para 2 line1: for the 1.?->the =A1=AF?=A1=AF seems an =
mistake here.
page5 2.2: what=A1=AFs "a small to-be-defined extension of the ALTO =
protocol=A1=B1?-> No reference, no explanation about the extension =
version, so the readers would be confused here.
The last problem is that the authors list all the figures in the draft =
at the end of the draft, making the draft hard to read. If the figure =
appears at where it was mentioned, that would be better.

Best,
Lili=


From nobody Thu Jun 29 15:31:32 2017
Return-Path: <lili.liu@yale.edu>
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 8945112773A for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 15:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yale.edu
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 kik-ASbr73YY for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 15:31:29 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (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 D68B6126C7A for <alto@ietf.org>; Thu, 29 Jun 2017 15:31:28 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id p21so88382347qke.3 for <alto@ietf.org>; Thu, 29 Jun 2017 15:31:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yale.edu; s=googleprd;  h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=H4Lv8rPP5GhdGz0Hdcqw68wdCC/p9a/DbQzWZrYkHC4=; b=M3PWq2lcSQV7/SdT1x31m11n7HPlpd3cYsDRCW9QRuZYr/sqFk/r+fWGPLG0Eci5Bw cKbJp9DSA4llM9NBcp1dO6Ms81/OT3eIPID5wf9KC21aq0tN8+5dXPtI7bp7ZdBCdipC eQNiD+yXgKwInvSFxvbhuGHZlmsLsEh3JxEtA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=H4Lv8rPP5GhdGz0Hdcqw68wdCC/p9a/DbQzWZrYkHC4=; b=FfFtMecVZ7fIlqnQ+lL/jvc6tHEm+KIfYtzDJCCclIiXnq2tBJfMLmJojCV0+I695s i+gCx6rMjMaA2GZ6MpQKkuVolWYmR9HBcfntElgPHQ49hBXuwhyUrwQjS5GjM/YXAY2y Z67+gLpssyL/Gga9jDgRw01oqKJJrG6vsBMxLnlGDypzSAqLX/1bY4pfomovwmIB7h0P lKtFbBSYNXXQQ/LCmnLqh1kMF6OlEWS+kom03ns5Wbki74OHQoH8np72hBWkmxemuFJx rcXygPWxmZfu/LCbVLWYwKKikiitOZgcgwqHKF64jGu9yyx26ZYnHJbH/om6WWUfmTPt UDaA==
X-Gm-Message-State: AKS2vOw5OHbWvXlSY9N+HxPOrlOxYjGo0daa3uiHx1G4XlkFgSLZjwmG sD31tzX0c80rdJD7B+rN3w==
X-Received: by 10.55.164.88 with SMTP id n85mr21465052qke.159.1498775487912; Thu, 29 Jun 2017 15:31:27 -0700 (PDT)
Received: from [192.168.0.19] (cpe-66-108-205-11.nyc.res.rr.com. [66.108.205.11]) by smtp.gmail.com with ESMTPSA id h17sm5355905qte.20.2017.06.29.15.31.27 for <alto@ietf.org> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 29 Jun 2017 15:31:27 -0700 (PDT)
From: Lili Liu <lili.liu@yale.edu>
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5802735-CF8D-4711-9E74-6DBFAB69A703@yale.edu>
Date: Thu, 29 Jun 2017 18:31:26 -0400
To: alto@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/ipctUw0bQlYP8msEGtizNV9zTUM>
Subject: [alto] =?gb2312?b?c2V2ZXJhbCB2aWV3cyBvbiAiQUxUTyBQZXJmb3JtYW5j?= =?gb2312?b?ZSBDb3N0IE1ldHJpY3MgZHJhZnQtaWV0Zi1hbHRvLXBlcmZvcm1hbmNlLW1l?= =?gb2312?b?dHJpY3MtMDGhsQ==?=
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: Thu, 29 Jun 2017 22:31:30 -0000

Hi everyone,

I=A1=AFve been reading  "ALTO Performance Cost Metrics =
draft-ietf-alto-performance-metrics-01=A1=B1 these days and have some =
comments as follows:
This draft is written in good organization. The authors present a set of =
Cost Metrics which work for ALTO system, give them a detailed =
description and give some examples for them.=20
But there=A1=AFre still some grammar errors in the draft as follows:

page1:
para2 line 3: offers->offer
para3 line 3: end to end-> end-to-end

page4:
para 3 line 2: policy->policies
para 3 line 3: end to end->end-to-end
para 3 line 4: ALTO may convey such information, not available via 3rd =
party measurement tools.->seems strange
para 4 line 2: if they feel-> how could applications feel something?

page5:
para 1 to para 2: unnatural transition
para 2 line 5: them->the
para 4 line 4: on time periods covering the past and present-> based on =
both previous and current time

page6:
para 1 line 2: bandwidth related->bandwidth-related

page16:
para 2 line 2: neighbor->neighbors

page24:
pare1 line 1:Indeed, TE performance is a highly sensitive ISP =
information and sharing TE metric values in numerical mode requires full =
mutual confidence between the entities managing the ALTO Server and =
Client.-> Indeed, TE performance is a kind of highly sensitive ISP =
information. Therefore, sharing TE metric values in numerical mode =
requires full mutual confidence between the entities managing the ALTO =
Server and Client.

Best,
Lili



From nobody Thu Jun 29 16:13:07 2017
Return-Path: <sabine.randriamasy@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 C9FC512EB03 for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 16:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 led0mufhbrWC for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 16:13:02 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0109.outbound.protection.outlook.com [104.47.0.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75F3212EAF2 for <alto@ietf.org>; Thu, 29 Jun 2017 16:13:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=swnAs/6I+uq+ykRMvoi8nT9d5h94CECFZvRksVuICgM=; b=cM9IedlMFnebZEbJF+4bN4EiXB3DU3dqxy9or/4wOobmByBfZ+jsmAw6kjtFQSbNB65fXdJOwcZ97Nw/OJiJIf52ETfXFaJYnwC/ZpEFSJSATA6Lk0JsEbbitGgWiyHnPaSX2gbHlTsQP6iAioy5iMxWwQ8XXHBkJ9cuZxrsA1U=
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) by DB6PR0701MB1736.eurprd07.prod.outlook.com (10.168.10.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.6; Thu, 29 Jun 2017 23:12:58 +0000
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com ([fe80::79f9:96c:a3c5:3ecc]) by DB6PR0701MB2454.eurprd07.prod.outlook.com ([fe80::79f9:96c:a3c5:3ecc%17]) with mapi id 15.01.1220.015; Thu, 29 Jun 2017 23:12:58 +0000
From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: New Version Notification for draft-randriamasy-alto-cellular-adresses-00.txt
Thread-Index: AQHS8Sz1sFndM7XE2EmChLiGoGq2lKI8d8XA
Date: Thu, 29 Jun 2017 23:12:57 +0000
Message-ID: <DB6PR0701MB2454676034308E11DF8C2E4B95D20@DB6PR0701MB2454.eurprd07.prod.outlook.com>
References: <149877783604.4674.4124420883476203809.idtracker@ietfa.amsl.com>
In-Reply-To: <149877783604.4674.4124420883476203809.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [135.245.212.26]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB6PR0701MB1736; 7:5hkxeOa+Y43JdCeGgNvM3YyHgAI8oOBv0u+4xFZFlCmaeFVMrhqQL08eIkuBXxLlpqZ7R4CHizF4HZOFLzKuybZtGOt1sivU1XK1RymjQxxxIkfSGyf3/u2IvHY12EZeDnA4rqsEGopPpdpsv8pCK2kCXknuZZ46SNSZ7ED8yJ0uK7VWgtIO+z+yqvWPSfKeZPhLBxUGz67KT2GiIf+d5I0kpTBTEedXMaipJfHJREwYmP3sW97Yn9K7GAYkfx2z79NCaX2zGd6/AYBGoH11m/yD8J6mwPw0AKkw7a/gWAtDlydbwvzwHFPjm3UnXHytTVa9OuTWG3uvqq7U9At82MZnWToSbX814NxN3VIG2J3rBcG0DKLL6mcAROrLlHCU8hHTZYsVkCfl5rnmbczSHEj4a5dsXSjG27Vbsx+CAPXNW76hhKMFMND5fw15uRIVMjOzsN5yIMjeO8PjQXGEPQZ+nCuh2xmzu448+S2A5SLOrHMDt9cHnLK6oISgDMtFI6/+Ll4wbujxxtoHS8v6n5ca5UpVs84rqtpyRn/ZYjiGThvvShZOtG7MQOsGPiK3Q7H8DgrwrxhggqmMB9wTBjW+VSiL9wcqqbqCSyCr6l5vOCGW3HwMsI+ZmFoZrmgtsXAIWJm7FE4mxXUeD1JDzX2f/dUXsUQNghlL1jSYKiAlEoSHJJnw82dDQX34nIdWcNBM3XhxxmsbQk5tPRhsuUtrrhZ9/dpzC9x16V/AwmEQCpxZ2yLf5jveiQSSr12ZlAA1tPTSfS7tf+KiSoz2uDBoDikK0r5CukWvSJ+rlNE=
x-ms-office365-filtering-correlation-id: 1aa00ccc-e361-48fc-ffd0-08d4bf4461b1
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(48565401081)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:DB6PR0701MB1736; 
x-ms-traffictypediagnostic: DB6PR0701MB1736:
x-microsoft-antispam-prvs: <DB6PR0701MB1736AE426FADC05E49AF226D95D20@DB6PR0701MB1736.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278178393323532)(120809045254105)(236129657087228)(131327999870524)(48057245064654)(148574349560750)(247924648384137);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(3002001)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123560025)(20161123564025)(20161123555025)(20161123562025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB6PR0701MB1736; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB6PR0701MB1736; 
x-forefront-prvs: 0353563E2B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39860400002)(39850400002)(39450400003)(39400400002)(39840400002)(13464003)(377424004)(55016002)(25786009)(14454004)(99286003)(305945005)(110136004)(7696004)(38730400002)(966005)(6506006)(2950100002)(6916009)(74316002)(478600001)(5660300001)(102836003)(6116002)(3846002)(33656002)(50986999)(189998001)(76176999)(2501003)(54356999)(2900100001)(3660700001)(2351001)(86362001)(8676002)(5250100002)(230783001)(7736002)(3280700002)(5640700003)(9686003)(81166006)(2473003)(8936002)(6436002)(6306002)(2906002)(1730700003)(53936002)(15650500001)(66066001)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB1736; H:DB6PR0701MB2454.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jun 2017 23:12:58.0716 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB1736
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/KjLP3F71Xv_qOUfTLvayQxnmRFk>
Subject: [alto] FW: New Version Notification for draft-randriamasy-alto-cellular-adresses-00.txt
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: Thu, 29 Jun 2017 23:13:05 -0000

SGVsbG8sDQoNClRoZXJlIGhhdmUgYmVlbiBzZXZlcmFsIGRpc2N1c3Npb25zIGFuZCBkcmFmdHMg
b24gQUxUTyB1c2UgY2FzZXMgaW52b2x2aW5nIGNlbGx1bGFyIG5ldHdvcmtzIGFuZCBpdCBhcHBl
YXJzIGFzIG5lY2Vzc2FyeSB0byBhZ3JlZSB1cG9uIGFuIEFMVE8gZm9ybWF0IGZvciBDZWxsIElk
ZW50aWZpZXJzLg0KDQpUaGlzIHJlbGF0ZXMgdG8gc2V2ZXJhbCBkcmFmdHMgKHBlcmZvcm1hbmNl
LCB1bmlmaWVkIHByb3BlcnRpZXMsIG1vYmlsaXR5IG1vZGVscy4uLikuIFNvIEkgaGF2ZSBwb3N0
ZWQgdGhpcyBzaG9ydCBvbmUganVzdCB0byBwcm92aWRlIGEgZGlzY3Vzc2lvbiBzdXBwb3J0LiBU
aGVyZSBhcmUgYWN0dWFsbHkgb25seSAyLjUgcGFnZXMgdG8gcmVhZC4gDQoNCkZvciBzaG9ydCwg
dGhpcyBkcmFmdCBwcm9wb3NlcyB0byB1c2UgdGhlIGNlbGx1bGFyIGFkZHJlc3MgZm9ybWF0IGNv
bXBvc2VkIG9mDQogZWxlbWVudHMgYXMgc3BlY2lmaWVkIGJ5IDNHUFAgYW5kIGNhbGxlZCBFQ0dJ
LiBFQ0dJDQogc3RhbmRzIGZvciBFLVVUUkFOIENlbGwgR2xvYmFsIElkZW50aWZpZXIgYW5kIGlz
IHVzZWQgaW4gUHVibGljIExhbmQNCiBNb2JpbGUgTmV0d29ya3MgYmFzZWQgb24gRS1VVFJBTi4g
ICANCg0KTG9va2luZyBmb3J3YXJkIHRvIGhhdmluZyB5b3VyIGZlZWRiYWNrIGFuZCBwcm9wb3Nh
bHMuIA0KVGhhbmtzLA0KU2FiaW5lDQoNCj4+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+
RnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGll
dGYub3JnXQ0KPj5TZW50OiAzMCBKdW5lIDIwMTcgMDE6MTENCj4+VG86IFJhbmRyaWFtYXN5LCBT
YWJpbmUgKE5va2lhIC0gRlIvTm96YXkpIDxzYWJpbmUucmFuZHJpYW1hc3lAbm9raWEtDQo+PmJl
bGwtbGFicy5jb20+DQo+PlN1YmplY3Q6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJh
ZnQtcmFuZHJpYW1hc3ktYWx0by1jZWxsdWxhci0NCj4+YWRyZXNzZXMtMDAudHh0DQo+Pg0KPj4N
Cj4+QSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LXJhbmRyaWFtYXN5LWFsdG8tY2VsbHVsYXIt
YWRyZXNzZXMtMDAudHh0DQo+PmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgU2Fi
aW5lIFJhbmRyaWFtYXN5IGFuZCBwb3N0ZWQgdG8gdGhlDQo+PklFVEYgcmVwb3NpdG9yeS4NCj4+
DQo+Pk5hbWU6CQlkcmFmdC1yYW5kcmlhbWFzeS1hbHRvLWNlbGx1bGFyLWFkcmVzc2VzDQo+PlJl
dmlzaW9uOgkwMA0KPj5UaXRsZToJCUFMVE8gY2VsbHVsYXIgYWRkcmVzc2VzDQo+PkRvY3VtZW50
IGRhdGU6CTIwMTctMDYtMzANCj4+R3JvdXA6CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj4+UGFn
ZXM6CQk1DQo+PlVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1k
cmFmdHMvZHJhZnQtcmFuZHJpYW1hc3ktYWx0by0NCj4+Y2VsbHVsYXItYWRyZXNzZXMtMDAudHh0
DQo+PlN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFm
dC1yYW5kcmlhbWFzeS1hbHRvLWNlbGx1bGFyLQ0KPj5hZHJlc3Nlcy8NCj4+SHRtbGl6ZWQ6ICAg
ICAgIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1yYW5kcmlhbWFzeS1hbHRvLWNl
bGx1bGFyLQ0KPj5hZHJlc3Nlcy0wMA0KPj5IdG1saXplZDogICAgICAgaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvaHRtbC9kcmFmdC1yYW5kcmlhbWFzeS1hbHRvLQ0KPj5jZWxsdWxh
ci1hZHJlc3Nlcy0wMA0KPj4NCj4+DQo+PkFic3RyYWN0Og0KPj4gICBUaGlzIGRyYWZ0IHByb3Bv
c2VzIHRvIHVzZSB0aGUgY2VsbHVsYXIgYWRkcmVzcyBmb3JtYXQgY29tcG9zZWQgb2YNCj4+ICAg
ZWxlbWVudHMgYXMgc3BlY2lmaWVkIGJ5IDNHUFAgYW5kIGNhbGxlZCBFQ0dJLiAgRUNHSSBzdGFu
ZHMgZm9yDQo+PiAgIEUtVVRSQU4gQ2VsbCBHbG9iYWwgSWRlbnRpZmllciBhbmQgaXMgdXNlZCBp
biBQdWJsaWMgTGFuZCBNb2JpbGUNCj4+ICAgTmV0d29ya3MgYmFzZWQgb24gRS1VVFJBTi4NCj4+
DQo+Pg0KPj4NCj4+DQo+Pg0KPj5QbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxl
IG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQo+PnVudGlsIHRoZSBodG1s
aXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMuaWV0Zi5vcmcuDQo+
Pg0KPj5UaGUgSUVURiBTZWNyZXRhcmlhdA0KDQo=


From nobody Thu Jun 29 18:37:03 2017
Return-Path: <bill.wu@huawei.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 32BB0126B7F for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 18:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 3ys7-s-L5fge for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 18:37:00 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C22F124D68 for <alto@ietf.org>; Thu, 29 Jun 2017 18:36:59 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DQB86498; Fri, 30 Jun 2017 01:36:58 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 30 Jun 2017 02:36:57 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.25]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Fri, 30 Jun 2017 09:36:50 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Lili Liu <lili.liu@yale.edu>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: =?gb2312?B?W2FsdG9dIHNldmVyYWwgdmlld3Mgb24gIkFMVE8gUGVyZm9ybWFuY2UgQ29z?= =?gb2312?B?dCBNZXRyaWNzIGRyYWZ0LWlldGYtYWx0by1wZXJmb3JtYW5jZS1tZXRyaWNz?= =?gb2312?B?LTAxobE=?=
Thread-Index: AQHS8Sd9RNkaCnY6CkeQuErWJMIq5qI8oEAA
Date: Fri, 30 Jun 2017 01:36:50 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9A98E4D1@nkgeml513-mbx.china.huawei.com>
References: <C5802735-CF8D-4711-9E74-6DBFAB69A703@yale.edu>
In-Reply-To: <C5802735-CF8D-4711-9E74-6DBFAB69A703@yale.edu>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.136.78.218]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.5955AB3A.007A, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.1.25, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c2aaf2a6c6fd895487412547c3957d5d
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/vVIIwiDmvxjO9IoNiUkdg8TnORU>
Subject: Re: [alto]  =?gb2312?b?c2V2ZXJhbCB2aWV3cyBvbiAiQUxUTyBQZXJmb3JtYW5j?= =?gb2312?b?ZSBDb3N0IE1ldHJpY3MgZHJhZnQtaWV0Zi1hbHRvLXBlcmZvcm1hbmNlLW1l?= =?gb2312?b?dHJpY3MtMDGhsQ==?=
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, 30 Jun 2017 01:37:02 -0000

VGhhbmsgTGlsaSwgd2lsbCBmaXggdGhlc2Ugbml0cyBpbiB0aGUgbmV4dCB2ZXJzaW9uLg0KDQot
UWluDQotLS0tLdPKvP7Urbz+LS0tLS0NCreivP7IyzogYWx0byBbbWFpbHRvOmFsdG8tYm91bmNl
c0BpZXRmLm9yZ10gtPqx7SBMaWxpIExpdQ0Kt6LLzcqxvOQ6IDIwMTfE6jbUwjMwyNUgNjozMQ0K
ytW8/sjLOiBhbHRvQGlldGYub3JnDQrW98ziOiBbYWx0b10gc2V2ZXJhbCB2aWV3cyBvbiAiQUxU
TyBQZXJmb3JtYW5jZSBDb3N0IE1ldHJpY3MgZHJhZnQtaWV0Zi1hbHRvLXBlcmZvcm1hbmNlLW1l
dHJpY3MtMDGhsQ0KDQpIaSBldmVyeW9uZSwNCg0KSaGvdmUgYmVlbiByZWFkaW5nICAiQUxUTyBQ
ZXJmb3JtYW5jZSBDb3N0IE1ldHJpY3MgZHJhZnQtaWV0Zi1hbHRvLXBlcmZvcm1hbmNlLW1ldHJp
Y3MtMDGhsSB0aGVzZSBkYXlzIGFuZCBoYXZlIHNvbWUgY29tbWVudHMgYXMgZm9sbG93czoNClRo
aXMgZHJhZnQgaXMgd3JpdHRlbiBpbiBnb29kIG9yZ2FuaXphdGlvbi4gVGhlIGF1dGhvcnMgcHJl
c2VudCBhIHNldCBvZiBDb3N0IE1ldHJpY3Mgd2hpY2ggd29yayBmb3IgQUxUTyBzeXN0ZW0sIGdp
dmUgdGhlbSBhIGRldGFpbGVkIGRlc2NyaXB0aW9uIGFuZCBnaXZlIHNvbWUgZXhhbXBsZXMgZm9y
IHRoZW0uIA0KQnV0IHRoZXJloa9yZSBzdGlsbCBzb21lIGdyYW1tYXIgZXJyb3JzIGluIHRoZSBk
cmFmdCBhcyBmb2xsb3dzOg0KDQpwYWdlMToNCnBhcmEyIGxpbmUgMzogb2ZmZXJzLT5vZmZlcg0K
cGFyYTMgbGluZSAzOiBlbmQgdG8gZW5kLT4gZW5kLXRvLWVuZA0KDQpwYWdlNDoNCnBhcmEgMyBs
aW5lIDI6IHBvbGljeS0+cG9saWNpZXMNCnBhcmEgMyBsaW5lIDM6IGVuZCB0byBlbmQtPmVuZC10
by1lbmQNCnBhcmEgMyBsaW5lIDQ6IEFMVE8gbWF5IGNvbnZleSBzdWNoIGluZm9ybWF0aW9uLCBu
b3QgYXZhaWxhYmxlIHZpYSAzcmQgcGFydHkgbWVhc3VyZW1lbnQgdG9vbHMuLT5zZWVtcyBzdHJh
bmdlIHBhcmEgNCBsaW5lIDI6IGlmIHRoZXkgZmVlbC0+IGhvdyBjb3VsZCBhcHBsaWNhdGlvbnMg
ZmVlbCBzb21ldGhpbmc/DQoNCnBhZ2U1Og0KcGFyYSAxIHRvIHBhcmEgMjogdW5uYXR1cmFsIHRy
YW5zaXRpb24NCnBhcmEgMiBsaW5lIDU6IHRoZW0tPnRoZQ0KcGFyYSA0IGxpbmUgNDogb24gdGlt
ZSBwZXJpb2RzIGNvdmVyaW5nIHRoZSBwYXN0IGFuZCBwcmVzZW50LT4gYmFzZWQgb24gYm90aCBw
cmV2aW91cyBhbmQgY3VycmVudCB0aW1lDQoNCnBhZ2U2Og0KcGFyYSAxIGxpbmUgMjogYmFuZHdp
ZHRoIHJlbGF0ZWQtPmJhbmR3aWR0aC1yZWxhdGVkDQoNCnBhZ2UxNjoNCnBhcmEgMiBsaW5lIDI6
IG5laWdoYm9yLT5uZWlnaGJvcnMNCg0KcGFnZTI0Og0KcGFyZTEgbGluZSAxOkluZGVlZCwgVEUg
cGVyZm9ybWFuY2UgaXMgYSBoaWdobHkgc2Vuc2l0aXZlIElTUCBpbmZvcm1hdGlvbiBhbmQgc2hh
cmluZyBURSBtZXRyaWMgdmFsdWVzIGluIG51bWVyaWNhbCBtb2RlIHJlcXVpcmVzIGZ1bGwgbXV0
dWFsIGNvbmZpZGVuY2UgYmV0d2VlbiB0aGUgZW50aXRpZXMgbWFuYWdpbmcgdGhlIEFMVE8gU2Vy
dmVyIGFuZCBDbGllbnQuLT4gSW5kZWVkLCBURSBwZXJmb3JtYW5jZSBpcyBhIGtpbmQgb2YgaGln
aGx5IHNlbnNpdGl2ZSBJU1AgaW5mb3JtYXRpb24uIFRoZXJlZm9yZSwgc2hhcmluZyBURSBtZXRy
aWMgdmFsdWVzIGluIG51bWVyaWNhbCBtb2RlIHJlcXVpcmVzIGZ1bGwgbXV0dWFsIGNvbmZpZGVu
Y2UgYmV0d2VlbiB0aGUgZW50aXRpZXMgbWFuYWdpbmcgdGhlIEFMVE8gU2VydmVyIGFuZCBDbGll
bnQuDQoNCkJlc3QsDQpMaWxpDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCmFsdG8gbWFpbGluZyBsaXN0DQphbHRvQGlldGYub3JnDQpodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FsdG8NCg==


From nobody Thu Jun 29 19:19:46 2017
Return-Path: <bill.wu@huawei.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 2FE21129B74 for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 19:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level: 
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, 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 Ogbzwx0gecLe for <alto@ietfa.amsl.com>; Thu, 29 Jun 2017 19:19:43 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F824129A9C for <alto@ietf.org>; Thu, 29 Jun 2017 19:19:42 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DJL10656; Fri, 30 Jun 2017 02:19:40 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 30 Jun 2017 03:19:39 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.25]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Fri, 30 Jun 2017 10:19:34 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: New Version Notification for draft-randriamasy-alto-cellular-adresses-00.txt
Thread-Index: AQHS8Sz1sFndM7XE2EmChLiGoGq2lKI8d8XAgAAwBtA=
Date: Fri, 30 Jun 2017 02:19:33 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9A98E559@nkgeml513-mbx.china.huawei.com>
References: <149877783604.4674.4124420883476203809.idtracker@ietfa.amsl.com> <DB6PR0701MB2454676034308E11DF8C2E4B95D20@DB6PR0701MB2454.eurprd07.prod.outlook.com>
In-Reply-To: <DB6PR0701MB2454676034308E11DF8C2E4B95D20@DB6PR0701MB2454.eurprd07.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.136.78.218]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.5955B53D.007C, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.1.25, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 61c23bddc333d01cab9d820a8e1d191f
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/Wci3OOg0aD38EIuQ_6WflQvm68I>
Subject: Re: [alto] New Version Notification for draft-randriamasy-alto-cellular-adresses-00.txt
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, 30 Jun 2017 02:19:45 -0000

SGksIFNhYmluZToNClRoYW5rIGZvciB3cml0aW5nIHRoaXMgc2hvcnQgZHJhZnQuIEl0IGlzIGEg
Z29vZCBzdGFydC4NCkkgaGF2ZSBhIGZldyBjb21tZW50czoNCjEuIFNlY3Rpb24gMy4yDQpNTkMg
aXMgZGVmaW5lZCBhcyAyLTMgZGlnaXRhbCBkZWNpbWFsIG51bWJlciB3aXRob3V0IGxlYWRpbmcg
emVyb3M/DQpCdXQgaW4gdGhlIGV4YW1wbGUgZm9sbG93aW5nIE1OQyBkZWZpbml0aW9uLCB5b3Ug
Z2l2ZSBhbiBleGFtcGxlIE1OQyB2YWx1ZSAwMjAsDQpJIGFtIG5vdCBzdXJlIGlmIHRoZSBmaXJz
dCBkaWdpdGFsIG51bWJlciAiMCIgaXMgbGVhZGluZyB6ZXJvPw0KMi5TZWN0aW9uIDMuMg0KRm9y
IEVuZHBvaW50IGFkZHJlc3MgZm9ybWF0LCANCk1DQyBhbmQgTU5DIGlzIGRlZmluZWQgYXMgZGln
aXRhbCBkZWNpbWFsIG51bWJlciwNCkVDSSBpcyBkZWZpbmVkIGFzIGRpZ2l0YWwgaGV4IG51bWJl
ciwNCkkgYW0gd29uZGVyaW5nIHdoeSBub3Qgc3BlY2lmeSBNQ0MsIE1OQywgRUNJIGluIHRoZSBz
YW1lIGZvcm1hdD8NCjMuIFNlY3Rpb24gMy4yIEV4YW1wbGU6DQpXb3VsZCBpdCBiZSBncmVhdCB0
byBtYWtlIHRoZSB0ZXh0IGNvbnNpc3RlbnQgd2l0aCB0aGUgZXhhbXBsZSAiZWNnaToyMTE6NDgx
OjEyMzRhYmMiPw0KRm9yIGV4YW1wbGUsIHdoYXQgZG8gd2UgbWVhbiBieSAzMTE/IFdoYXQgZG8g
d2UgbWVhbiBieSA0ODE/DQo0LiBIb3cgQUxUTyBDZWxsIElkIGZvcm1hdCBpcyByZWxhdGVkIHRv
IGVuZHBvaW50IGFkZHJlc3MgZm9ybWF0Pw0KNS4gc2VjdGlvbiAzLjQNCnMvNy1kaWdpdGEgRUNJ
IHRoYXQgc3RhcnRzIHdpdGggdGhlIDE4IGJpdHMgMHgxMjM0OC83LWRpZ2l0YWwgRUNJIEhleCBu
dW1iZXIgdGhhdCBzdGFydHMgd2l0aCAxOCBiaXRzIDB4MTIzNDgNCjYuIFNlY3Rpb24gMy40DQpJ
IHRoaW5rICdlY2dpOjMxMS40ODE6MTIzNDgwMC8xOCcgZG9lc24ndCBtYXRjaGVzICdlY2dpOjMx
MS40ODE6MTIzNGFiYycuDQpNYXliZSAnZWNnaTozMTEuNDgxOjEyMzRhYmMnIHNob3VsZCBiZSBy
ZXBsYWNlZCB3aXRoICdlY2dpOjMxMS40ODE6MTIzNGNiYScNCg0KLVFpbg0KLS0tLS3Tyrz+1K28
/i0tLS0tDQq3orz+yMs6IGFsdG8gW21haWx0bzphbHRvLWJvdW5jZXNAaWV0Zi5vcmddILT6se0g
UmFuZHJpYW1hc3ksIFNhYmluZSAoTm9raWEgLSBGUi9Ob3pheSkNCreiy83KsbzkOiAyMDE3xOo2
1MIzMMjVIDc6MTMNCsrVvP7IyzogYWx0b0BpZXRmLm9yZw0K1vfM4jogW2FsdG9dIEZXOiBOZXcg
VmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LXJhbmRyaWFtYXN5LWFsdG8tY2VsbHVsYXIt
YWRyZXNzZXMtMDAudHh0DQoNCkhlbGxvLA0KDQpUaGVyZSBoYXZlIGJlZW4gc2V2ZXJhbCBkaXNj
dXNzaW9ucyBhbmQgZHJhZnRzIG9uIEFMVE8gdXNlIGNhc2VzIGludm9sdmluZyBjZWxsdWxhciBu
ZXR3b3JrcyBhbmQgaXQgYXBwZWFycyBhcyBuZWNlc3NhcnkgdG8gYWdyZWUgdXBvbiBhbiBBTFRP
IGZvcm1hdCBmb3IgQ2VsbCBJZGVudGlmaWVycy4NCg0KVGhpcyByZWxhdGVzIHRvIHNldmVyYWwg
ZHJhZnRzIChwZXJmb3JtYW5jZSwgdW5pZmllZCBwcm9wZXJ0aWVzLCBtb2JpbGl0eSBtb2RlbHMu
Li4pLiBTbyBJIGhhdmUgcG9zdGVkIHRoaXMgc2hvcnQgb25lIGp1c3QgdG8gcHJvdmlkZSBhIGRp
c2N1c3Npb24gc3VwcG9ydC4gVGhlcmUgYXJlIGFjdHVhbGx5IG9ubHkgMi41IHBhZ2VzIHRvIHJl
YWQuIA0KDQpGb3Igc2hvcnQsIHRoaXMgZHJhZnQgcHJvcG9zZXMgdG8gdXNlIHRoZSBjZWxsdWxh
ciBhZGRyZXNzIGZvcm1hdCBjb21wb3NlZCBvZiAgZWxlbWVudHMgYXMgc3BlY2lmaWVkIGJ5IDNH
UFAgYW5kIGNhbGxlZCBFQ0dJLiBFQ0dJICBzdGFuZHMgZm9yIEUtVVRSQU4gQ2VsbCBHbG9iYWwg
SWRlbnRpZmllciBhbmQgaXMgdXNlZCBpbiBQdWJsaWMgTGFuZA0KIE1vYmlsZSBOZXR3b3JrcyBi
YXNlZCBvbiBFLVVUUkFOLiAgIA0KDQpMb29raW5nIGZvcndhcmQgdG8gaGF2aW5nIHlvdXIgZmVl
ZGJhY2sgYW5kIHByb3Bvc2Fscy4gDQpUaGFua3MsDQpTYWJpbmUNCg0KPj4tLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KPj5Gcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzpp
bnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddDQo+PlNlbnQ6IDMwIEp1bmUgMjAxNyAwMToxMQ0KPj5U
bzogUmFuZHJpYW1hc3ksIFNhYmluZSAoTm9raWEgLSBGUi9Ob3pheSkgPHNhYmluZS5yYW5kcmlh
bWFzeUBub2tpYS0gDQo+PmJlbGwtbGFicy5jb20+DQo+PlN1YmplY3Q6IE5ldyBWZXJzaW9uIE5v
dGlmaWNhdGlvbiBmb3IgZHJhZnQtcmFuZHJpYW1hc3ktYWx0by1jZWxsdWxhci0gDQo+PmFkcmVz
c2VzLTAwLnR4dA0KPj4NCj4+DQo+PkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1yYW5kcmlh
bWFzeS1hbHRvLWNlbGx1bGFyLWFkcmVzc2VzLTAwLnR4dA0KPj5oYXMgYmVlbiBzdWNjZXNzZnVs
bHkgc3VibWl0dGVkIGJ5IFNhYmluZSBSYW5kcmlhbWFzeSBhbmQgcG9zdGVkIHRvIA0KPj50aGUg
SUVURiByZXBvc2l0b3J5Lg0KPj4NCj4+TmFtZToJCWRyYWZ0LXJhbmRyaWFtYXN5LWFsdG8tY2Vs
bHVsYXItYWRyZXNzZXMNCj4+UmV2aXNpb246CTAwDQo+PlRpdGxlOgkJQUxUTyBjZWxsdWxhciBh
ZGRyZXNzZXMNCj4+RG9jdW1lbnQgZGF0ZToJMjAxNy0wNi0zMA0KPj5Hcm91cDoJCUluZGl2aWR1
YWwgU3VibWlzc2lvbg0KPj5QYWdlczoJCTUNCj4+VVJMOiAgICAgICAgICAgIGh0dHBzOi8vd3d3
LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1yYW5kcmlhbWFzeS1hbHRvLQ0KPj5jZWxs
dWxhci1hZHJlc3Nlcy0wMC50eHQNCj4+U3RhdHVzOiAgICAgICAgIGh0dHBzOi8vZGF0YXRyYWNr
ZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXJhbmRyaWFtYXN5LWFsdG8tY2VsbHVsYXItDQo+PmFkcmVz
c2VzLw0KPj5IdG1saXplZDogICAgICAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LXJhbmRyaWFtYXN5LWFsdG8tY2VsbHVsYXItDQo+PmFkcmVzc2VzLTAwDQo+Pkh0bWxpemVkOiAg
ICAgICBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2RyYWZ0LXJhbmRyaWFt
YXN5LWFsdG8tDQo+PmNlbGx1bGFyLWFkcmVzc2VzLTAwDQo+Pg0KPj4NCj4+QWJzdHJhY3Q6DQo+
PiAgIFRoaXMgZHJhZnQgcHJvcG9zZXMgdG8gdXNlIHRoZSBjZWxsdWxhciBhZGRyZXNzIGZvcm1h
dCBjb21wb3NlZCBvZg0KPj4gICBlbGVtZW50cyBhcyBzcGVjaWZpZWQgYnkgM0dQUCBhbmQgY2Fs
bGVkIEVDR0kuICBFQ0dJIHN0YW5kcyBmb3INCj4+ICAgRS1VVFJBTiBDZWxsIEdsb2JhbCBJZGVu
dGlmaWVyIGFuZCBpcyB1c2VkIGluIFB1YmxpYyBMYW5kIE1vYmlsZQ0KPj4gICBOZXR3b3JrcyBi
YXNlZCBvbiBFLVVUUkFOLg0KPj4NCj4+DQo+Pg0KPj4NCj4+DQo+PlBsZWFzZSBub3RlIHRoYXQg
aXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIA0KPj5zdWJt
aXNzaW9uIHVudGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUg
YXQgdG9vbHMuaWV0Zi5vcmcuDQo+Pg0KPj5UaGUgSUVURiBTZWNyZXRhcmlhdA0KDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KYWx0byBtYWlsaW5nIGxp
c3QNCmFsdG9AaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
YWx0bw0K


From nobody Fri Jun 30 01:13:27 2017
Return-Path: <jingxuan.n.zhang@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 94574128D40 for <alto@ietfa.amsl.com>; Fri, 30 Jun 2017 01:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 Sfj4duCUAQ8A for <alto@ietfa.amsl.com>; Fri, 30 Jun 2017 01:13:23 -0700 (PDT)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (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 5F3FD127977 for <alto@ietf.org>; Fri, 30 Jun 2017 01:13:23 -0700 (PDT)
Received: by mail-vk0-x22c.google.com with SMTP id r126so62708595vkg.0 for <alto@ietf.org>; Fri, 30 Jun 2017 01:13:23 -0700 (PDT)
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=qDKB8xKAib/h2xlmmEL4PGNaDwz6gzRHGQ87XmZpyT8=; b=jtf26MAVhU0m10e7xBUawDeCbOGice+j7BUJka2PkoRGLtdMz96+Em+nbwsf+4u2rl qAOQOo4jhkP6q0n3Ax9r1sBhkafmPAfYF2Lpx1sqmh8MVJ+JVCrUSlJG+FsJZkHxRXQ5 4Hd9YSNJffrsTZOJ5FRHTywpn8HiwGt8tBITypKyB29ROx89QvG2N5LyZahA2IKyyZku wTja7YzKMVR9qGbPEMDlygskkZHOeEfzmcktwT2cQ2FZu+8Ne56S3Y/RK2K2va9k/7Yx 9kE/KljxyN44jzgjKLLUbfcoK5F7Y/ZijW405W4TVhuQx9lZIdIWcqrcPZynwBM2zqpB gN5Q==
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=qDKB8xKAib/h2xlmmEL4PGNaDwz6gzRHGQ87XmZpyT8=; b=ZinwX8U1iV3oTU3ysc3Y7LKiO/ylw3bvhRZbfKVyMOGOTnSXjIV03dBf9N/oAKwLQM Vml2ZfdeHjRrpCuUPA+PdicH7v399k8NBRYvtDUDE5szA1QsHO36pyxA3y2Y4nbC44Fb 9iy7iceaBP+XQWqBMJs5EO53HhEWVoTFEN1vn7J1yRS7auEEApO7Ul23rVuWpcJxqABB SatP+prUVKMlt34IfSkxgfcQiMExrGp5mWBcK0fYWHy67082/dvzIYDiThlH/lA+B8BB gxzwdT63Yy7avaP6OXIQ2nq6tKGDOnT3UY9+dT16DUBcUQFHys60b4BmGHV+QHJo0w2f voSA==
X-Gm-Message-State: AKS2vOwLeH1tT5MwgJobdL19v1DzZc8KmS8qXNbI6LdPDn7/hkOtY/JG S1ZMoCoeHdprAZknkuS+/dA0YrwnJw==
X-Received: by 10.31.16.22 with SMTP id g22mr9391428vki.94.1498810402523; Fri, 30 Jun 2017 01:13:22 -0700 (PDT)
MIME-Version: 1.0
References: <07e102bd-999a-c6b3-de5c-e5f01bc5b924@mails.tsinghua.edu.cn> <CAN-YqX2=qFJOyHAVKSGgzJJjGpuJpca2Kht6w0+bPKNQi2cW5g@mail.gmail.com>
In-Reply-To: <CAN-YqX2=qFJOyHAVKSGgzJJjGpuJpca2Kht6w0+bPKNQi2cW5g@mail.gmail.com>
From: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Date: Fri, 30 Jun 2017 08:13:11 +0000
Message-ID: <CAAbpuyqZF5ZzOm1bwXFYuSscFAK2sEHcimNyY3AsBZ8Ok49Baw@mail.gmail.com>
To: Dennis Yu <dennis.yht@gmail.com>, Kai Gao <gaok12@mails.tsinghua.edu.cn>
Cc: IETF ALTO <alto@ietf.org>
Content-Type: multipart/alternative; boundary="001a11436218a0d139055328fddd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/tiw-KjFR3MyqJOCIagKbWkfe8Mk>
Subject: Re: [alto] Reviews on draft-gao-alto-fcs-02
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, 30 Jun 2017 08:13:26 -0000

--001a11436218a0d139055328fddd
Content-Type: text/plain; charset="UTF-8"

Kai and Dennis, thanks a lot for your reviews.

I have fixed typos and grammar issues according to your comments. About
some of your suggestions, see my comments inline.

On Wed, Jun 28, 2017 at 12:24 AM Dennis Yu <dennis.yht@gmail.com> wrote:

> Dear authors of draft-gao-alto-fcs-02,
>
> Yet another review of draft-gao-alto-fcs-02 :)
> Here are some opinions that maybe have some help,
>
> 1.
> Some inconsistency with draft-ietf-alto-multi-cost-10,
>
> the definition of ReqFilteredCostMap in "multi-cost" section 4.1.2 is as
> follows,
> (the comments are appended)
>
>     object {
>         [CostType cost-type;]
>         [CostType multi-cost-types<1..*>;]
>         [CostType testable-cost-types<1..*>;]
>         [JSONString constraints<0..*>;]
>         [JSONString or-constraints<1..*><1..*>;]
>         [PIDFilter pids];   //<---- likely a typo
>     } ReqFilteredCostMap;
>
> and the extended definition in "fcs" section 3.1.2 is,
>
>     object {
>         [CostType cost-type;]
>         [CostType multi-cost-types<1..*>;]
>         [CostType testable-cost-types<1..*>;]
>         [JSONString constraints<0..*>;]
>         [JSONString or-constraints<0..*><0..*>;]  //  1 --> 0
>         [PIDFilter  pids;]
>         [PIDFilter  pid-flows<1..*>;]
>     } ReqFilteredCostMap;
>
> also see the definition of ReqEndpointCostMap. Although the difference
> between "1" and "0" is tiny, but I think it's better to agree on one
> definition.
>
> 2.
> the definition of FlowCostResponse in section 4.2.5 is as follows,
>
>     object {
>         FlowCostMap     flow-cost-map;
>         [FlowCostMap    flow-cost-confidences;]
>     } FlowCostResponse : ResponseEntityBase;
>
>     object-map {
>         FlowId -> JSONValue;
>     } FlowCostMap;
>
> Firstly, I'm not sure the "JSONValue" is well-defined. According to
> RFC7159 section 3, "A JSON value MUST be an object, array, number, or
> string, or one of the following three literal names: false null true"
>
>
JSONValue is OK here. See Section 11.2.3.6 and Section 11.5.1.6 of RFC7285.


> Secondly, I think the "flow-cost-confidences" could have its clear type
> definition, maybe
>
>     object-map {
>         FlowId -> JSONValue;
>     } FlowCostConfidence
>
>
Maybe.


> Thirdly, I personally think that the cost confidence should better be
> defined as a JSON fractional number between 0 to 1.
>
>
Actually, I prefer to deprecate flow-cost-confidences from the draft, since
it can be supported by introducing new cost types (cost-mode). Defining an
additional field does not convince me. For example, we can define
cost-mode=range, cost-metric=delay:

meta:
  ...
  cost-type:
    cost-mode: range
    cost-metric: delay
cost-map:
  PID1:
    PID2: [100, 110]
    PID3: [220, 240]

Kai, the original idea of the cost confidence is proposed by you. Do you
have any comments?

3.
> A missing comma in the example of page 19 (l3-flow-aggr)
> Two redundant commas in the example of page 19 (cost-type) and page 10
> (dependent-vtags)
>
> 4.
> The change log of section 2 can be composed as an appendix.
>
>
Not necessary. It is a temporary section and will be removed when the
content is ready.


> 5.
> Section 8.2, "Openflow" and "openflow" -> "OpenFlow"
>
> Sincerely,
> Dennis Yu
>
> On Tue, Jun 27, 2017 at 9:09 PM, Kai Gao <gaok12@mails.tsinghua.edu.cn>
> wrote:
>
>> Dear authors of draft-gao-alto-fcs,
>>
>> I have roughly reviewed the latest FCS draft. Please see the comments
>> below.
>>
>>
>> Regards,
>> Kai
>>
>> Terminology:
>>
>> sX: section X
>> ppX: page X
>> pX: paragraph X
>> lX: line X
>>
>> pp3, s1, p1
>> l2: scenario -> scenarios
>> l3-4: "... the P2P application ..." -> "... P2P applications ..."
>>
>> pp3, s1
>> p2, l2: central -> centralized
>> p2 & p3: I think these two paragraphs can benefit from some restructuring
>> to
>> make the motivations for flow-based query more explicit and also easier
>> to read.
>>
>> pp3, s1, p5
>> l1: consider -> describe
>> l3: schema -> schemas
>>
>>
>> pp4, s1, p1
>> l2: "... 5-tuples of ..." -> Use the explicit form of the 5-tuple: "...
>> 5-tuple <ip-protocol, ...>"
>> l6: "SHOULD support" -> "supports"
>> l7: "to satisfy" -> "and satisfies"
>>
>> pp5, s3.1.2, p5
>> l4: "appeared" -> "appear"
>>
>> pp6, s3.2
>> title: "Extend" -> "Extended"
>> p2, l2: "... to measure the cost" -> "... to specify the request"
>> p2, l3: "SHOULD" -> "MUST"
>> p2, l4: "be" -> "have"
>> p2, l5: "format" -> "formats"
>> p4, l2: Extra space after "TypedEndpointAddr"
>>
>> pp6, s3.2.1, p1
>> l1: "contain" -> "can be"
>> l4: "specified" -> remove it.
>> l5: "be conflict" -> "conflict"
>> l6: "is conflict" -> "conflicts"
>>
>> pp7, s3.2.3, p1: Use "Protocol" instead of "protocol" to make it explicit
>> that
>> it represents the value contained in the query.
>>
>> pp8
>> s3.3.1, p1, l1: Remove "then"
>> s3.3.2, p6, l4: "appeared" -> "appear"
>> s3.3.3, p1, l2: "exactly" -> "exactly the same"
>> s4, title: Example -> Examples
>>
>> pp14, s4.2.3, p4, l3: "value types" -> "value type"
>>
>> pp15, s4.2.5.1, p1, l5: ", the servers" -> ". The servers"
>>
>> pp16, s4.2.5, p3, l3: "TypedHeadreField" -> "TypedHeaderField"
>>
>>
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

--001a11436218a0d139055328fddd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Kai and Dennis, thanks a lot for your reviews.<div><br></d=
iv><div>I have fixed typos and grammar issues according to your comments. A=
bout some of your suggestions,=C2=A0see my comments inline.</div><div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Jun 28, 2017 at 12:24 AM=
 Dennis Yu &lt;<a href=3D"mailto:dennis.yht@gmail.com">dennis.yht@gmail.com=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><d=
iv style=3D"font-size:12.8px">Dear authors of draft-gao-alto-fcs-02,</div><=
div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px">Ye=
t another review of draft-gao-alto-fcs-02 :)</div><div style=3D"font-size:1=
2.8px">Here are some opinions that maybe have some help,</div><div style=3D=
"font-size:12.8px"><br></div><div style=3D"font-size:12.8px">1.</div><div s=
tyle=3D"font-size:12.8px">Some inconsistency with draft-ietf-alto-multi-cos=
t-10,</div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-siz=
e:12.8px">the definition of ReqFilteredCostMap in &quot;multi-cost&quot; se=
ction 4.1.2 is as follows,</div><div style=3D"font-size:12.8px">(the commen=
ts are appended)</div><div style=3D"font-size:12.8px"><br></div><div style=
=3D"font-size:12.8px">=C2=A0 =C2=A0 object {</div><div style=3D"font-size:1=
2.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [CostType cost-type;]</div><div style=3D=
"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [CostType multi-cost-types&l=
t;1..*&gt;;]</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 [CostType testable-cost-types&lt;1..*&gt;;]</div><div style=3D"font-siz=
e:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [JSONString constraints&lt;0..*&gt;;]=
</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [JSONStri=
ng or-constraints&lt;1..*&gt;&lt;1..*&gt;;]</div><div style=3D"font-size:12=
.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [PIDFilter pids]; =C2=A0 //&lt;---- likel=
y a typo</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 } ReqFilteredCo=
stMap;</div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-si=
ze:12.8px">and the extended definition in &quot;fcs&quot; section 3.1.2 is,=
</div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.=
8px">=C2=A0 =C2=A0 object {</div><div style=3D"font-size:12.8px">=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 [CostType cost-type;]</div><div style=3D"font-size:12.8px=
">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [CostType multi-cost-types&lt;1..*&gt;;]</div=
><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [CostType test=
able-cost-types&lt;1..*&gt;;]</div><div style=3D"font-size:12.8px">=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 [JSONString constraints&lt;0..*&gt;;]</div><div style=
=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [JSONString or-constraint=
s&lt;0..*&gt;&lt;0..*&gt;;] =C2=A0// =C2=A01 --&gt; 0</div><div style=3D"fo=
nt-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [PIDFilter =C2=A0pids;]</div><d=
iv style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [PIDFilter =C2=A0=
pid-flows&lt;1..*&gt;;]</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =
} ReqFilteredCostMap;</div><div style=3D"font-size:12.8px"><br></div><div s=
tyle=3D"font-size:12.8px">also see the definition of ReqEndpointCostMap. Al=
though the difference between &quot;1&quot; and &quot;0&quot; is tiny, but =
I think it&#39;s better to agree on one definition.</div><div style=3D"font=
-size:12.8px"><br></div><div style=3D"font-size:12.8px">2.</div><div style=
=3D"font-size:12.8px">the definition of FlowCostResponse in section 4.2.5 i=
s as follows,</div><div style=3D"font-size:12.8px"><br></div><div style=3D"=
font-size:12.8px">=C2=A0 =C2=A0 object {</div><div style=3D"font-size:12.8p=
x">=C2=A0 =C2=A0 =C2=A0 =C2=A0 FlowCostMap =C2=A0 =C2=A0 flow-cost-map;</di=
v><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 [FlowCostMap =
=C2=A0 =C2=A0flow-cost-confidences;]</div><div style=3D"font-size:12.8px">=
=C2=A0 =C2=A0 } FlowCostResponse : ResponseEntityBase;</div><div style=3D"f=
ont-size:12.8px"><br></div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 ob=
ject-map {</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 FlowId -&gt; JSONValue;</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0=
 } FlowCostMap;</div><div style=3D"font-size:12.8px"><br></div><div style=
=3D"font-size:12.8px">Firstly, I&#39;m not sure the &quot;JSONValue&quot; i=
s well-defined. According to RFC7159 section 3, &quot;A JSON value MUST be =
an object, array, number, or string, or one of the following three literal =
names: false null true&quot;</div><div style=3D"font-size:12.8px"><br></div=
></div></blockquote><div><br></div><div>JSONValue is OK here. See Section 1=
1.2.3.6 and Section 11.5.1.6 of RFC7285.</div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex"><div dir=3D"ltr"><div style=3D"font-size:12.8px"></div><=
div style=3D"font-size:12.8px">Secondly, I think the &quot;flow-cost-confid=
ences&quot; could have its clear type definition, maybe</div><div style=3D"=
font-size:12.8px"><br></div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 o=
bject-map {</div><div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 FlowId -&gt; JSONValue;</div><div style=3D"font-size:12.8px">=C2=A0 =C2=
=A0 } FlowCostConfidence</div><div style=3D"font-size:12.8px"><br></div></d=
iv></blockquote><div><br></div><div>Maybe.</div><div>=C2=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex"><div dir=3D"ltr"><div style=3D"font-size:12.8px"></div=
><div style=3D"font-size:12.8px">Thirdly, I personally think that the cost =
confidence should better be defined as a JSON fractional number between 0 t=
o 1.</div><div style=3D"font-size:12.8px"><br></div></div></blockquote><div=
><br></div><div>Actually, I prefer to deprecate flow-cost-confidences from =
the draft, since it can be supported by introducing new cost types (cost-mo=
de). Defining an additional field does not convince me. For example, we can=
 define cost-mode=3Drange, cost-metric=3Ddelay:</div><div><br></div><div>me=
ta:</div><div>=C2=A0 ...</div><div>=C2=A0 cost-type:</div><div>=C2=A0 =C2=
=A0 cost-mode: range</div><div>=C2=A0 =C2=A0 cost-metric: delay</div><div>c=
ost-map:</div><div>=C2=A0 PID1:</div><div>=C2=A0 =C2=A0 PID2: [100, 110]</d=
iv><div>=C2=A0 =C2=A0 PID3: [220, 240]</div><div><br></div><div>Kai, the or=
iginal idea of the cost confidence is proposed by you. Do you have any comm=
ents?</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><=
div style=3D"font-size:12.8px"></div><div style=3D"font-size:12.8px">3.</di=
v><div style=3D"font-size:12.8px">A missing comma in the example of page 19=
 (l3-flow-aggr)</div><div style=3D"font-size:12.8px">Two redundant commas i=
n the example of page 19 (cost-type) and page 10 (dependent-vtags)</div><di=
v style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px">4.</=
div><div style=3D"font-size:12.8px">The change log of section 2 can be comp=
osed as an appendix.</div><div style=3D"font-size:12.8px"><br></div></div><=
/blockquote><div><br></div><div>Not necessary. It is a temporary section an=
d will be removed when the content is ready.</div><div>=C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex"><div dir=3D"ltr"><div style=3D"font-size:12.8px"></d=
iv><div style=3D"font-size:12.8px">5.</div><div style=3D"font-size:12.8px">=
Section 8.2, &quot;Openflow&quot; and &quot;openflow&quot; -&gt; &quot;Open=
Flow&quot;=C2=A0</div><div style=3D"font-size:12.8px"><br></div><div style=
=3D"font-size:12.8px">Sincerely,</div><div style=3D"font-size:12.8px">Denni=
s Yu</div></div><div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Jun 27, 2017 at 9:09 PM, Kai Gao <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:gaok12@mails.tsinghua.edu.cn" target=3D"_blank">gaok=
12@mails.tsinghua.edu.cn</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">Dear authors of draft-gao-alto-fcs,<br>
<br>
I have roughly reviewed the latest FCS draft. Please see the comments below=
.<br>
<br>
<br>
Regards,<br>
Kai<br>
<br>
Terminology:<br>
<br>
sX: section X<br>
ppX: page X<br>
pX: paragraph X<br>
lX: line X<br>
<br>
pp3, s1, p1<br>
l2: scenario -&gt; scenarios<br>
l3-4: &quot;... the P2P application ...&quot; -&gt; &quot;... P2P applicati=
ons ...&quot;<br>
<br>
pp3, s1<br>
p2, l2: central -&gt; centralized<br>
p2 &amp; p3: I think these two paragraphs can benefit from some restructuri=
ng to<br>
make the motivations for flow-based query more explicit and also easier to =
read.<br>
<br>
pp3, s1, p5<br>
l1: consider -&gt; describe<br>
l3: schema -&gt; schemas<br>
<br>
<br>
pp4, s1, p1<br>
l2: &quot;... 5-tuples of ...&quot; -&gt; Use the explicit form of the 5-tu=
ple: &quot;... 5-tuple &lt;ip-protocol, ...&gt;&quot;<br>
l6: &quot;SHOULD support&quot; -&gt; &quot;supports&quot;<br>
l7: &quot;to satisfy&quot; -&gt; &quot;and satisfies&quot;<br>
<br>
pp5, s3.1.2, p5<br>
l4: &quot;appeared&quot; -&gt; &quot;appear&quot;<br>
<br>
pp6, s3.2<br>
title: &quot;Extend&quot; -&gt; &quot;Extended&quot;<br>
p2, l2: &quot;... to measure the cost&quot; -&gt; &quot;... to specify the =
request&quot;<br>
p2, l3: &quot;SHOULD&quot; -&gt; &quot;MUST&quot;<br>
p2, l4: &quot;be&quot; -&gt; &quot;have&quot;<br>
p2, l5: &quot;format&quot; -&gt; &quot;formats&quot;<br>
p4, l2: Extra space after &quot;TypedEndpointAddr&quot;<br>
<br>
pp6, s3.2.1, p1<br>
l1: &quot;contain&quot; -&gt; &quot;can be&quot;<br>
l4: &quot;specified&quot; -&gt; remove it.<br>
l5: &quot;be conflict&quot; -&gt; &quot;conflict&quot;<br>
l6: &quot;is conflict&quot; -&gt; &quot;conflicts&quot;<br>
<br>
pp7, s3.2.3, p1: Use &quot;Protocol&quot; instead of &quot;protocol&quot; t=
o make it explicit that<br>
it represents the value contained in the query.<br>
<br>
pp8<br>
s3.3.1, p1, l1: Remove &quot;then&quot;<br>
s3.3.2, p6, l4: &quot;appeared&quot; -&gt; &quot;appear&quot;<br>
s3.3.3, p1, l2: &quot;exactly&quot; -&gt; &quot;exactly the same&quot;<br>
s4, title: Example -&gt; Examples<br>
<br>
pp14, s4.2.3, p4, l3: &quot;value types&quot; -&gt; &quot;value type&quot;<=
br>
<br>
pp15, s4.2.5.1, p1, l5: &quot;, the servers&quot; -&gt; &quot;. The servers=
&quot;<br>
<br>
pp16, s4.2.5, p3, l3: &quot;TypedHeadreField&quot; -&gt; &quot;TypedHeaderF=
ield&quot;<br>
<br>
<br>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote></div><br></div></div>
_______________________________________________<br>
alto mailing list<br>
<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/alto" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote></div></div></div>

--001a11436218a0d139055328fddd--


From nobody Fri Jun 30 06:20:39 2017
Return-Path: <cs90911@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 5B37E12955F for <alto@ietfa.amsl.com>; Fri, 30 Jun 2017 06:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 nBq9ZxA748Nx for <alto@ietfa.amsl.com>; Fri, 30 Jun 2017 06:20:34 -0700 (PDT)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (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 C05CC1205F0 for <alto@ietf.org>; Fri, 30 Jun 2017 06:20:33 -0700 (PDT)
Received: by mail-vk0-x230.google.com with SMTP id 191so65849876vko.2 for <alto@ietf.org>; Fri, 30 Jun 2017 06:20:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Du9EQb33WtDfVYlL+wOstkQFOgh1A2YaahtnlAgmfo4=; b=TqNAuriTxumdIFE5P8pqJ94FAqjAmSi4/IsjfN3PcqVvZHud/1/wvMxG41MxUo6on8 77aF4YtzVI8frAH9irbM67g8s3LoHt+sRbbgJXpCNimSB5bUgnVgn9I88Fs+Y9J+1PwQ aD7nSrLOtaumLrTjXy/ZBa5J5vD1BKLzCaivso4QeQq3vXSjCck8TjVBNL8bgMVFPsP1 ABh1zGh5LR2voXKlKDNw10HtDHSWc8WEN0shHRUSWHdQwxJBEchisqFuYj4UI74mernd 1/c0PCrmFDzk/WaD9YZFUVyLumEKOJBDnUFgDqOWUkBEFIzq7KYnHyJsnp7QeyAgULnO xaEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Du9EQb33WtDfVYlL+wOstkQFOgh1A2YaahtnlAgmfo4=; b=QRtYX1LBEDMCk8PD01ZCwJEnI8UR1ZLnoB8uZ7n9GkTXsheDmPwk+w97fsfyLBHvup jIHW4K0XrPa3Bf2LX3EaWcQpAsbsBkr6GNaSdBhSg18lzIK7IjKJIOemKdpivCa3l4H5 Cgj9Ba5suk6smPkDgi74q4GFe8w5qH2FxPW2XbUpd4ao6Ugr2c9WtgBn1gFmxHoC6vIZ 4gnjxueEt01x+lPU5tPjaEaipl8eaaBSh2Mf+kL44RqBqbQbNYtSxXBfQLLA6rz6kj0+ sogHnoyo69tjsshreAAx6aCroFDiWGfP7f3+ThIyS3nJQlOnn+mojghr0iP9Avk/MH15 oeSg==
X-Gm-Message-State: AKS2vOy2Im6H9NmGot0YX8mm2UKU9ooiQFioqeuGgYhVzjtT9LKq2oTc 7VtFKKJCiuwjK1erUshmXHlAevZicw==
X-Received: by 10.31.53.4 with SMTP id c4mr11647179vka.12.1498828832792; Fri, 30 Jun 2017 06:20:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.236.199 with HTTP; Fri, 30 Jun 2017 06:19:52 -0700 (PDT)
In-Reply-To: <CAAbpuyqZF5ZzOm1bwXFYuSscFAK2sEHcimNyY3AsBZ8Ok49Baw@mail.gmail.com>
References: <07e102bd-999a-c6b3-de5c-e5f01bc5b924@mails.tsinghua.edu.cn> <CAN-YqX2=qFJOyHAVKSGgzJJjGpuJpca2Kht6w0+bPKNQi2cW5g@mail.gmail.com> <CAAbpuyqZF5ZzOm1bwXFYuSscFAK2sEHcimNyY3AsBZ8Ok49Baw@mail.gmail.com>
From: Shenshen Chen <cs90911@gmail.com>
Date: Fri, 30 Jun 2017 21:19:52 +0800
Message-ID: <CAKRjQSC4taLhJ=PRdQrcwSXWm0YY5eWtuMsoxYSMvWkjzeQHnQ@mail.gmail.com>
To: Jensen Zhang <jingxuan.n.zhang@gmail.com>, dennis.yht@gmail.com,  gaok12@mails.tsinghua.edu.cn
Cc: alto@ietf.org
Content-Type: multipart/alternative; boundary="001a114476302865df05532d4887"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/AjpbjWDhWb6RjDeZTxr2wcpuCQA>
Subject: Re: [alto] Reviews on draft-gao-alto-fcs-02
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, 30 Jun 2017 13:20:36 -0000

--001a114476302865df05532d4887
Content-Type: text/plain; charset="UTF-8"

Hi all,

I'd like to join this discussion.

About the flow-cost-confidences, I prefer the original design.
The mean of cost makes sense (the expected cost if pick path randomly)
and can't be deduced from the range (since it may not be an
equal probability distribution).


Here is a list of typos (comments are marked with ">>>"):

[Page 1]
     3.1.  Flow-based Filtered Cost Map  . . . . . . . . . . . . . .   4
       3.1.1.  Capabilities  . . . . . . . . . . . . . . . . . . . .   4
       3.1.2.  Accept Input Parameters . . . . . . . . . . . . . . .   5

>>> Accept => Acceptable, also see 3.3.2. and 4.2.3.

[Page 1]
     3.4.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   8

>>> Example => Examples

>>> Also, the catalog doesn't include Section 4.2.5.1., 4.2.6.1., etc,
which looks weird.

[Page 1]
   The emergence of new networking datapath capabilities has
   substantially increased the flexibility of networking.  For example,
   OpenFlow has emerged as a major southbound protocol for Software-
   Defined Networking, and OpenFlow allows flexible routing beyond
   simple destination-based routing.  In this document, we define a new
   extention to ALTO, namely the Flow Cost Service, for ALTO clients in

>>> extention => extension

   an OpenFlow-enabled network to query ALTO network information.

[Page 6]
   The Protocol field is REQUIRED.  The available values contain
   different protocols including layer two protocols (e.g.  "eth") and
   layer three protocols (e.g.  "ipv4", "ipv6").  It can also be
   specified upper-layer protocols (e.g. "udp", "tcp", "ssh", "http" and
   "ftp").  The source and destination protocols MUST NOT be conflict.

>>> be conflict => be conflicted

   In every EndpointFilter object of either "endpoints" field or
   "endpoint-flows" field, if the source protocol is conflict with the

>>> is conflict with => has conflict with

   destination protocol, this endpoint pair is invalid.  For different
   protocols, some additional constraints are defined in Section 3.2.3.

[Page 7]
   protocols:  Defines a list of JSONString indicating the supported
      Protocol values of the EndpointURI in the request.  The ALTO
      server does not have to claim "ipv4" and "ipv6" in this field
      explictly, because they are supported by default.  If not present,

>>> explictly => explicitly

      this field MUST be interpreted as if it is specified the default
      supported protocols "ipv4" and "ipv6".

[Page 16]
   The ALTO servers can provide more information to the clients when
   requests have errors.  The FlowCostErrorMap below can provide basic
   information about two most common errors for the flow cost service.
   The ALTO servers MAY include it as the data component of an ALTO
   error response.  If multiple errors are identified, the ALTO server
   MUST return exactly one error code according to Section 8.5.2 of
   [RFC7285] .

[Page 20]
  Security considerations:  Security considerations are identical to
      those specified in Section 15 of [RFC7285] .

>>> remove the redundent space between [RFC7285] and full stop

[Page 16, 17]
   Some header fields may have conflicts.  For example, IPv4 fields and
   IPv6 fields can never appear in the same packet, nor can TCP and UDP
   ports.  These header fields MUST not be included in the same flow
   filter, otherwise the ALTO server MUST return an ALTO error response,
   with the error code "E_INVALID_FIELD_VALUE".  As specified in

>>> , otherwise => . Otherwise,
    remove the comma before "with"

   Section 8.5.2 of [RFC7285], the ALTO server MAY include the "field"
   and the "value" in the "meta" field.  In this case, the ALTO server
   MUST use the flow ID as the "field" and the flow filter as the
   "value".  However, the recommended approach is to use the
   FlowCostErrorMap, where the server CAN provide the conflicting typed
   header fields in the "conflicts" field of the FlowFilterError
   associated with the corresponding flow ID.

Best Regards,
Shenshen

--001a114476302865df05532d4887
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi all,</div><div><br></div><div>I&#39;d like to=
 join this discussion.</div><div><br></div><div>About the flow-cost-confide=
nces, I prefer the original design.</div><div>The mean of cost makes sense =
(the expected cost if pick path randomly)=C2=A0</div><div>and can&#39;t be =
deduced from the range (since it may not be an=C2=A0</div><div>equal probab=
ility distribution).=C2=A0</div><div><br></div><div><br></div><div>Here is =
a list of typos (comments are marked with &quot;&gt;&gt;&gt;&quot;):</div><=
div><br></div><div>[Page 1]</div><div>=C2=A0 =C2=A0 =C2=A03.1.=C2=A0 Flow-b=
ased Filtered Cost Map =C2=A0. . . . . . . . . . . . . . =C2=A0 4</div><div=
>=C2=A0 =C2=A0 =C2=A0 =C2=A03.1.1.=C2=A0 Capabilities =C2=A0. . . . . . . .=
 . . . . . . . . . . . . =C2=A0 4</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.1.=
2.=C2=A0 Accept Input Parameters . . . . . . . . . . . . . . . =C2=A0 5</di=
v><div><br></div><div>&gt;&gt;&gt; Accept =3D&gt; Acceptable, also see 3.3.=
2. and 4.2.3.</div><div>=C2=A0=C2=A0</div><div>[Page 1]</div><div>=C2=A0 =
=C2=A0 =C2=A03.4.=C2=A0 Example . . . . . . . . . . . . . . . . . . . . . .=
 . . . =C2=A0 8</div><div><br></div><div>&gt;&gt;&gt; Example =3D&gt; Examp=
les</div><div><br></div><div>&gt;&gt;&gt; Also, the catalog doesn&#39;t inc=
lude Section 4.2.5.1., 4.2.6.1., etc,</div><div>which looks weird.</div><di=
v><br></div><div>[Page 1]</div><div>=C2=A0 =C2=A0The emergence of new netwo=
rking datapath capabilities has</div><div>=C2=A0 =C2=A0substantially increa=
sed the flexibility of networking.=C2=A0 For example,</div><div>=C2=A0 =C2=
=A0OpenFlow has emerged as a major southbound protocol for Software-</div><=
div>=C2=A0 =C2=A0Defined Networking, and OpenFlow allows flexible routing b=
eyond</div><div>=C2=A0 =C2=A0simple destination-based routing.=C2=A0 In thi=
s document, we define a new</div><div>=C2=A0 =C2=A0extention to ALTO, namel=
y the Flow Cost Service, for ALTO clients in</div><div><br></div><div>&gt;&=
gt;&gt; extention =3D&gt; extension</div><div><br></div><div>=C2=A0 =C2=A0a=
n OpenFlow-enabled network to query ALTO network information.</div><div><br=
></div><div>[Page 6]</div><div>=C2=A0 =C2=A0The Protocol field is REQUIRED.=
=C2=A0 The available values contain</div><div>=C2=A0 =C2=A0different protoc=
ols including layer two protocols (e.g. =C2=A0&quot;eth&quot;) and</div><di=
v>=C2=A0 =C2=A0layer three protocols (e.g. =C2=A0&quot;ipv4&quot;, &quot;ip=
v6&quot;).=C2=A0 It can also be</div><div>=C2=A0 =C2=A0specified upper-laye=
r protocols (e.g. &quot;udp&quot;, &quot;tcp&quot;, &quot;ssh&quot;, &quot;=
http&quot; and</div><div>=C2=A0 =C2=A0&quot;ftp&quot;).=C2=A0 The source an=
d destination protocols MUST NOT be conflict.</div><div><br></div><div>&gt;=
&gt;&gt; be conflict =3D&gt; be conflicted</div><div><br></div><div>=C2=A0 =
=C2=A0In every EndpointFilter object of either &quot;endpoints&quot; field =
or</div><div>=C2=A0 =C2=A0&quot;endpoint-flows&quot; field, if the source p=
rotocol is conflict with the</div><div><br></div><div>&gt;&gt;&gt; is confl=
ict with =3D&gt; has conflict with</div><div><br></div><div>=C2=A0 =C2=A0de=
stination protocol, this endpoint pair is invalid.=C2=A0 For different</div=
><div>=C2=A0 =C2=A0protocols, some additional constraints are defined in Se=
ction 3.2.3.</div><div><br></div><div>[Page 7]</div><div>=C2=A0 =C2=A0proto=
cols: =C2=A0Defines a list of JSONString indicating the supported</div><div=
>=C2=A0 =C2=A0 =C2=A0 Protocol values of the EndpointURI in the request.=C2=
=A0 The ALTO</div><div>=C2=A0 =C2=A0 =C2=A0 server does not have to claim &=
quot;ipv4&quot; and &quot;ipv6&quot; in this field</div><div>=C2=A0 =C2=A0 =
=C2=A0 explictly, because they are supported by default.=C2=A0 If not prese=
nt,</div><div><br></div><div>&gt;&gt;&gt; explictly =3D&gt; explicitly</div=
><div><br></div><div>=C2=A0 =C2=A0 =C2=A0 this field MUST be interpreted as=
 if it is specified the default</div><div>=C2=A0 =C2=A0 =C2=A0 supported pr=
otocols &quot;ipv4&quot; and &quot;ipv6&quot;.</div><div><br></div><div>[Pa=
ge 16]</div><div>=C2=A0 =C2=A0The ALTO servers can provide more information=
 to the clients when</div><div>=C2=A0 =C2=A0requests have errors.=C2=A0 The=
 FlowCostErrorMap below can provide basic</div><div>=C2=A0 =C2=A0informatio=
n about two most common errors for the flow cost service.</div><div>=C2=A0 =
=C2=A0The ALTO servers MAY include it as the data component of an ALTO</div=
><div>=C2=A0 =C2=A0error response.=C2=A0 If multiple errors are identified,=
 the ALTO server</div><div>=C2=A0 =C2=A0MUST return exactly one error code =
according to Section 8.5.2 of</div><div>=C2=A0 =C2=A0[RFC7285] .</div><div>=
<br></div><div>[Page 20]</div><div>=C2=A0 Security considerations: =C2=A0Se=
curity considerations are identical to</div><div>=C2=A0 =C2=A0 =C2=A0 those=
 specified in Section 15 of [RFC7285] .</div><div><br></div><div>&gt;&gt;&g=
t; remove the redundent space between [RFC7285] and full stop</div><div><br=
></div><div>[Page 16, 17]</div><div>=C2=A0 =C2=A0Some header fields may hav=
e conflicts.=C2=A0 For example, IPv4 fields and</div><div>=C2=A0 =C2=A0IPv6=
 fields can never appear in the same packet, nor can TCP and UDP</div><div>=
=C2=A0 =C2=A0ports.=C2=A0 These header fields MUST not be included in the s=
ame flow</div><div>=C2=A0 =C2=A0filter, otherwise the ALTO server MUST retu=
rn an ALTO error response,</div><div>=C2=A0 =C2=A0with the error code &quot=
;E_INVALID_FIELD_VALUE&quot;.=C2=A0 As specified in</div><div><br></div><di=
v>&gt;&gt;&gt; , otherwise =3D&gt; . Otherwise,=C2=A0</div><div>=C2=A0 =C2=
=A0 remove the comma before &quot;with&quot; =C2=A0 =C2=A0</div><div><br></=
div><div>=C2=A0 =C2=A0Section 8.5.2 of [RFC7285], the ALTO server MAY inclu=
de the &quot;field&quot;</div><div>=C2=A0 =C2=A0and the &quot;value&quot; i=
n the &quot;meta&quot; field.=C2=A0 In this case, the ALTO server</div><div=
>=C2=A0 =C2=A0MUST use the flow ID as the &quot;field&quot; and the flow fi=
lter as the</div><div>=C2=A0 =C2=A0&quot;value&quot;.=C2=A0 However, the re=
commended approach is to use the</div><div>=C2=A0 =C2=A0FlowCostErrorMap, w=
here the server CAN provide the conflicting typed</div><div>=C2=A0 =C2=A0he=
ader fields in the &quot;conflicts&quot; field of the FlowFilterError</div>=
<div>=C2=A0 =C2=A0associated with the corresponding flow ID.=C2=A0</div><di=
v><br></div><div>Best Regards,</div><div>Shenshen</div></div><div><br></div=
></div>

--001a114476302865df05532d4887--


From nobody Fri Jun 30 06:56:38 2017
Return-Path: <jingxuan.n.zhang@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 D605D124B0A for <alto@ietfa.amsl.com>; Fri, 30 Jun 2017 06:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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_PASS=-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 TBA02wIW6KDB for <alto@ietfa.amsl.com>; Fri, 30 Jun 2017 06:56:34 -0700 (PDT)
Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::236]) (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 35CC01201F8 for <alto@ietf.org>; Fri, 30 Jun 2017 06:56:34 -0700 (PDT)
Received: by mail-ua0-x236.google.com with SMTP id g40so75926890uaa.3 for <alto@ietf.org>; Fri, 30 Jun 2017 06:56:34 -0700 (PDT)
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=d5ODInJibLlW9QpC7IHXiT3C1wsT8mj9xxNDxOk/LTg=; b=OdmuI0uI/oGyFOqdSg6TVrSs2xA7ENnxH42QSueKHVcThjff3F1jiHiR0cOfew9IyP hacYKDMobgTZOfA/YYj97AU2E6sOtPadaXk1W37WEz1oNrBrkfs2LfxwcX7oocB39xjT YAaH3aphEg6g5Pon/bVWf151lGFElCX4tVd6rnQndE44dMAGKidtdBEyvDA1Sken5r/B aPrYVT6pLuSnMNcaluWoFRcSB9N9GK6k8VV83JYr5izcbbanzncl4GWiVyhx+wjiy2AR khnuEdDI00sPd0gSs0wyOT7Y76Xb/hS/ls/hfN2nNCGGEd2LnXhGVuCjUHhQA8jTHVms 9XnA==
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=d5ODInJibLlW9QpC7IHXiT3C1wsT8mj9xxNDxOk/LTg=; b=G3uLJz+7ZuT0zPpalQA+HNfvexeVhcHzk1PoXvprR50MqExuqOjS4OGl3MJ8AEB/oV g5LKJCFqDs+PdcPxkJj5BCSLrpGGQxMxfdFFHSjfRZLoA9Op/byWczT3ZKBqmTuVIJol dRK1cgdTiZmKWDAQ8S/ER/7CA40nnMviT0bOiUdJ2lSc9hhLiHGldgXkBtHwTE2qimBr Kki9mgUjW1AoumEF80OvQf9gdiwVPLkJonO6ZdMwvDZ9sKvBjXZlhHC99ZMog2FAlmwp CLfJ1j6ZXBcq2xSBQ6EVevV6IIjXpxzfXF4anS2iJUgRyY5nXXYcKQ0anTaUMTDbzED9 wTIw==
X-Gm-Message-State: AKS2vOxtTJwNOc7EOeo9CU2yq8El3nvxzexIk8T/LuzeCOffW642vSRe wbDRulM0QlX/2vBJOvYChQrC+CIujQ==
X-Received: by 10.176.93.224 with SMTP id l32mr13027976uag.154.1498830993385;  Fri, 30 Jun 2017 06:56:33 -0700 (PDT)
MIME-Version: 1.0
References: <07e102bd-999a-c6b3-de5c-e5f01bc5b924@mails.tsinghua.edu.cn> <CAN-YqX2=qFJOyHAVKSGgzJJjGpuJpca2Kht6w0+bPKNQi2cW5g@mail.gmail.com> <CAAbpuyqZF5ZzOm1bwXFYuSscFAK2sEHcimNyY3AsBZ8Ok49Baw@mail.gmail.com> <CAKRjQSC4taLhJ=PRdQrcwSXWm0YY5eWtuMsoxYSMvWkjzeQHnQ@mail.gmail.com>
In-Reply-To: <CAKRjQSC4taLhJ=PRdQrcwSXWm0YY5eWtuMsoxYSMvWkjzeQHnQ@mail.gmail.com>
From: Jensen Zhang <jingxuan.n.zhang@gmail.com>
Date: Fri, 30 Jun 2017 13:56:22 +0000
Message-ID: <CAAbpuyoj0rUa1noFgpyVWZOEy3bQk+zmt_Zzojdk4LzMcW32Cw@mail.gmail.com>
To: Shenshen Chen <cs90911@gmail.com>, dennis.yht@gmail.com, gaok12@mails.tsinghua.edu.cn
Cc: alto@ietf.org
Content-Type: multipart/alternative; boundary="f403043ee0c4f06e8b05532dc8c9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/-f2Rl7rPP2tFJshxhWgzBPyKoHA>
Subject: Re: [alto] Reviews on draft-gao-alto-fcs-02
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, 30 Jun 2017 13:56:37 -0000

--f403043ee0c4f06e8b05532dc8c9
Content-Type: text/plain; charset="UTF-8"

Shenshen,

Thanks for your reply. Fixed the typos.

Jensen

On Fri, Jun 30, 2017 at 9:20 PM Shenshen Chen <cs90911@gmail.com> wrote:

> Hi all,
>
> I'd like to join this discussion.
>
> About the flow-cost-confidences, I prefer the original design.
> The mean of cost makes sense (the expected cost if pick path randomly)
> and can't be deduced from the range (since it may not be an
> equal probability distribution).
>
>
> Here is a list of typos (comments are marked with ">>>"):
>
> [Page 1]
>      3.1.  Flow-based Filtered Cost Map  . . . . . . . . . . . . . .   4
>        3.1.1.  Capabilities  . . . . . . . . . . . . . . . . . . . .   4
>        3.1.2.  Accept Input Parameters . . . . . . . . . . . . . . .   5
>
> >>> Accept => Acceptable, also see 3.3.2. and 4.2.3.
>
> [Page 1]
>      3.4.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   8
>
> >>> Example => Examples
>
> >>> Also, the catalog doesn't include Section 4.2.5.1., 4.2.6.1., etc,
> which looks weird.
>
> [Page 1]
>    The emergence of new networking datapath capabilities has
>    substantially increased the flexibility of networking.  For example,
>    OpenFlow has emerged as a major southbound protocol for Software-
>    Defined Networking, and OpenFlow allows flexible routing beyond
>    simple destination-based routing.  In this document, we define a new
>    extention to ALTO, namely the Flow Cost Service, for ALTO clients in
>
> >>> extention => extension
>
>    an OpenFlow-enabled network to query ALTO network information.
>
> [Page 6]
>    The Protocol field is REQUIRED.  The available values contain
>    different protocols including layer two protocols (e.g.  "eth") and
>    layer three protocols (e.g.  "ipv4", "ipv6").  It can also be
>    specified upper-layer protocols (e.g. "udp", "tcp", "ssh", "http" and
>    "ftp").  The source and destination protocols MUST NOT be conflict.
>
> >>> be conflict => be conflicted
>
>    In every EndpointFilter object of either "endpoints" field or
>    "endpoint-flows" field, if the source protocol is conflict with the
>
> >>> is conflict with => has conflict with
>
>    destination protocol, this endpoint pair is invalid.  For different
>    protocols, some additional constraints are defined in Section 3.2.3.
>
> [Page 7]
>    protocols:  Defines a list of JSONString indicating the supported
>       Protocol values of the EndpointURI in the request.  The ALTO
>       server does not have to claim "ipv4" and "ipv6" in this field
>       explictly, because they are supported by default.  If not present,
>
> >>> explictly => explicitly
>
>       this field MUST be interpreted as if it is specified the default
>       supported protocols "ipv4" and "ipv6".
>
> [Page 16]
>    The ALTO servers can provide more information to the clients when
>    requests have errors.  The FlowCostErrorMap below can provide basic
>    information about two most common errors for the flow cost service.
>    The ALTO servers MAY include it as the data component of an ALTO
>    error response.  If multiple errors are identified, the ALTO server
>    MUST return exactly one error code according to Section 8.5.2 of
>    [RFC7285] .
>
> [Page 20]
>   Security considerations:  Security considerations are identical to
>       those specified in Section 15 of [RFC7285] .
>
> >>> remove the redundent space between [RFC7285] and full stop
>
> [Page 16, 17]
>    Some header fields may have conflicts.  For example, IPv4 fields and
>    IPv6 fields can never appear in the same packet, nor can TCP and UDP
>    ports.  These header fields MUST not be included in the same flow
>    filter, otherwise the ALTO server MUST return an ALTO error response,
>    with the error code "E_INVALID_FIELD_VALUE".  As specified in
>
> >>> , otherwise => . Otherwise,
>     remove the comma before "with"
>
>    Section 8.5.2 of [RFC7285], the ALTO server MAY include the "field"
>    and the "value" in the "meta" field.  In this case, the ALTO server
>    MUST use the flow ID as the "field" and the flow filter as the
>    "value".  However, the recommended approach is to use the
>    FlowCostErrorMap, where the server CAN provide the conflicting typed
>    header fields in the "conflicts" field of the FlowFilterError
>    associated with the corresponding flow ID.
>
> Best Regards,
> Shenshen
>
>

--f403043ee0c4f06e8b05532dc8c9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Shenshen,<div><br></div><div>Thanks for your reply. Fixed =
the typos.</div><div><br></div><div>Jensen</div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr">On Fri, Jun 30, 2017 at 9:20 PM Shenshen Chen &l=
t;<a href=3D"mailto:cs90911@gmail.com">cs90911@gmail.com</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div>Hi all,</di=
v><div><br></div><div>I&#39;d like to join this discussion.</div><div><br><=
/div><div>About the flow-cost-confidences, I prefer the original design.</d=
iv><div>The mean of cost makes sense (the expected cost if pick path random=
ly)=C2=A0</div><div>and can&#39;t be deduced from the range (since it may n=
ot be an=C2=A0</div><div>equal probability distribution).=C2=A0</div><div><=
br></div><div><br></div><div>Here is a list of typos (comments are marked w=
ith &quot;&gt;&gt;&gt;&quot;):</div><div><br></div><div>[Page 1]</div><div>=
=C2=A0 =C2=A0 =C2=A03.1.=C2=A0 Flow-based Filtered Cost Map =C2=A0. . . . .=
 . . . . . . . . . =C2=A0 4</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.1.1.=C2=
=A0 Capabilities =C2=A0. . . . . . . . . . . . . . . . . . . . =C2=A0 4</di=
v><div>=C2=A0 =C2=A0 =C2=A0 =C2=A03.1.2.=C2=A0 Accept Input Parameters . . =
. . . . . . . . . . . . . =C2=A0 5</div><div><br></div><div>&gt;&gt;&gt; Ac=
cept =3D&gt; Acceptable, also see 3.3.2. and 4.2.3.</div><div>=C2=A0=C2=A0<=
/div><div>[Page 1]</div><div>=C2=A0 =C2=A0 =C2=A03.4.=C2=A0 Example . . . .=
 . . . . . . . . . . . . . . . . . . . . . =C2=A0 8</div><div><br></div><di=
v>&gt;&gt;&gt; Example =3D&gt; Examples</div><div><br></div><div>&gt;&gt;&g=
t; Also, the catalog doesn&#39;t include Section 4.2.5.1., 4.2.6.1., etc,</=
div><div>which looks weird.</div><div><br></div><div>[Page 1]</div><div>=C2=
=A0 =C2=A0The emergence of new networking datapath capabilities has</div><d=
iv>=C2=A0 =C2=A0substantially increased the flexibility of networking.=C2=
=A0 For example,</div><div>=C2=A0 =C2=A0OpenFlow has emerged as a major sou=
thbound protocol for Software-</div><div>=C2=A0 =C2=A0Defined Networking, a=
nd OpenFlow allows flexible routing beyond</div><div>=C2=A0 =C2=A0simple de=
stination-based routing.=C2=A0 In this document, we define a new</div><div>=
=C2=A0 =C2=A0extention to ALTO, namely the Flow Cost Service, for ALTO clie=
nts in</div><div><br></div><div>&gt;&gt;&gt; extention =3D&gt; extension</d=
iv><div><br></div><div>=C2=A0 =C2=A0an OpenFlow-enabled network to query AL=
TO network information.</div><div><br></div><div>[Page 6]</div><div>=C2=A0 =
=C2=A0The Protocol field is REQUIRED.=C2=A0 The available values contain</d=
iv><div>=C2=A0 =C2=A0different protocols including layer two protocols (e.g=
. =C2=A0&quot;eth&quot;) and</div><div>=C2=A0 =C2=A0layer three protocols (=
e.g. =C2=A0&quot;ipv4&quot;, &quot;ipv6&quot;).=C2=A0 It can also be</div><=
div>=C2=A0 =C2=A0specified upper-layer protocols (e.g. &quot;udp&quot;, &qu=
ot;tcp&quot;, &quot;ssh&quot;, &quot;http&quot; and</div><div>=C2=A0 =C2=A0=
&quot;ftp&quot;).=C2=A0 The source and destination protocols MUST NOT be co=
nflict.</div><div><br></div><div>&gt;&gt;&gt; be conflict =3D&gt; be confli=
cted</div><div><br></div><div>=C2=A0 =C2=A0In every EndpointFilter object o=
f either &quot;endpoints&quot; field or</div><div>=C2=A0 =C2=A0&quot;endpoi=
nt-flows&quot; field, if the source protocol is conflict with the</div><div=
><br></div><div>&gt;&gt;&gt; is conflict with =3D&gt; has conflict with</di=
v><div><br></div><div>=C2=A0 =C2=A0destination protocol, this endpoint pair=
 is invalid.=C2=A0 For different</div><div>=C2=A0 =C2=A0protocols, some add=
itional constraints are defined in Section 3.2.3.</div><div><br></div><div>=
[Page 7]</div><div>=C2=A0 =C2=A0protocols: =C2=A0Defines a list of JSONStri=
ng indicating the supported</div><div>=C2=A0 =C2=A0 =C2=A0 Protocol values =
of the EndpointURI in the request.=C2=A0 The ALTO</div><div>=C2=A0 =C2=A0 =
=C2=A0 server does not have to claim &quot;ipv4&quot; and &quot;ipv6&quot; =
in this field</div><div>=C2=A0 =C2=A0 =C2=A0 explictly, because they are su=
pported by default.=C2=A0 If not present,</div><div><br></div><div>&gt;&gt;=
&gt; explictly =3D&gt; explicitly</div><div><br></div><div>=C2=A0 =C2=A0 =
=C2=A0 this field MUST be interpreted as if it is specified the default</di=
v><div>=C2=A0 =C2=A0 =C2=A0 supported protocols &quot;ipv4&quot; and &quot;=
ipv6&quot;.</div><div><br></div><div>[Page 16]</div><div>=C2=A0 =C2=A0The A=
LTO servers can provide more information to the clients when</div><div>=C2=
=A0 =C2=A0requests have errors.=C2=A0 The FlowCostErrorMap below can provid=
e basic</div><div>=C2=A0 =C2=A0information about two most common errors for=
 the flow cost service.</div><div>=C2=A0 =C2=A0The ALTO servers MAY include=
 it as the data component of an ALTO</div><div>=C2=A0 =C2=A0error response.=
=C2=A0 If multiple errors are identified, the ALTO server</div><div>=C2=A0 =
=C2=A0MUST return exactly one error code according to Section 8.5.2 of</div=
><div>=C2=A0 =C2=A0[RFC7285] .</div><div><br></div><div>[Page 20]</div><div=
>=C2=A0 Security considerations: =C2=A0Security considerations are identica=
l to</div><div>=C2=A0 =C2=A0 =C2=A0 those specified in Section 15 of [RFC72=
85] .</div><div><br></div><div>&gt;&gt;&gt; remove the redundent space betw=
een [RFC7285] and full stop</div><div><br></div><div>[Page 16, 17]</div><di=
v>=C2=A0 =C2=A0Some header fields may have conflicts.=C2=A0 For example, IP=
v4 fields and</div><div>=C2=A0 =C2=A0IPv6 fields can never appear in the sa=
me packet, nor can TCP and UDP</div><div>=C2=A0 =C2=A0ports.=C2=A0 These he=
ader fields MUST not be included in the same flow</div><div>=C2=A0 =C2=A0fi=
lter, otherwise the ALTO server MUST return an ALTO error response,</div><d=
iv>=C2=A0 =C2=A0with the error code &quot;E_INVALID_FIELD_VALUE&quot;.=C2=
=A0 As specified in</div><div><br></div><div>&gt;&gt;&gt; , otherwise =3D&g=
t; . Otherwise,=C2=A0</div><div>=C2=A0 =C2=A0 remove the comma before &quot=
;with&quot; =C2=A0 =C2=A0</div><div><br></div><div>=C2=A0 =C2=A0Section 8.5=
.2 of [RFC7285], the ALTO server MAY include the &quot;field&quot;</div><di=
v>=C2=A0 =C2=A0and the &quot;value&quot; in the &quot;meta&quot; field.=C2=
=A0 In this case, the ALTO server</div><div>=C2=A0 =C2=A0MUST use the flow =
ID as the &quot;field&quot; and the flow filter as the</div><div>=C2=A0 =C2=
=A0&quot;value&quot;.=C2=A0 However, the recommended approach is to use the=
</div><div>=C2=A0 =C2=A0FlowCostErrorMap, where the server CAN provide the =
conflicting typed</div><div>=C2=A0 =C2=A0header fields in the &quot;conflic=
ts&quot; field of the FlowFilterError</div><div>=C2=A0 =C2=A0associated wit=
h the corresponding flow ID.=C2=A0</div><div><br></div><div>Best Regards,</=
div><div>Shenshen</div></div><div><br></div></div>
</blockquote></div>

--f403043ee0c4f06e8b05532dc8c9--


From nobody Fri Jun 30 07:49:18 2017
Return-Path: <duhaizhou@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 4FFEB129B28; Fri, 30 Jun 2017 07:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 sHTUCOS4n5rA; Fri, 30 Jun 2017 07:49:15 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 0CCAF129AF6; Fri, 30 Jun 2017 07:49:15 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id w126so112175395wme.0; Fri, 30 Jun 2017 07:49:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=Ub+k+c/pNJIEaoj4xXnQIwu8YKwNsiPdwqP1t88OCEY=; b=Pnx/TMtSRWabqTbgmlFGxE8JQuFUdXMlDacM8cAAp2R3+Ol6xiESrkgmh/G1Ls6g7N 86lpD2iGGiDKtILXP9fvmajxGX+Ld5Kc8zuRqQu7CqjEnu+wKKBUIb4Fsjr+d9ZoWU0D Xufx2AZPqs6W2mFBbefOqdtxt4OGBfssqyXR1uWTWz2/9t0CE6CDeDemRfsMljJS2/7A MtpMUv9tZYJo+nibixBjUC3cyU70I9WDHXlm44+UHf3pNVQBNnRkk4dctpNKSSJRm3XT A8KDB7nTt6Iyh1rmlQRs3VHFaqCCGNCccJvnGq00EaVt/8/w+vhT3cAl/j9A9M4YftV0 nZmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Ub+k+c/pNJIEaoj4xXnQIwu8YKwNsiPdwqP1t88OCEY=; b=Z1XLrCM26F0mJdtgGg8kBZI1sKauZx1FSnEzq9k6cNVUhw0AaKOsgkV0j0AzlRLD9E Li2pROcJp48KQg50MJHl1ck7EbLrKgXxXVhG5UxgI6hPulox+X8B5/Ak1E8eJaWi1j9T g/pKDQ/ecVHQsZ11UHmeQ76rw03TEiPqhrt9Ko3U/2SgaDVnRXmfOYIDG0ZLbSD0d+ug Wt/zKLkOeWY6fs1/1/HQylIMXY91ZAg29sxY0Bg9A0vOMVr08TVcAByHEql4vU9nNNqh fVpGhsDpINQYlTjRo6iU6EDb59ilReAmR7yifK7xJ5PaS4GAd8pmJSwP1FxDNS0sxOnL u0qQ==
X-Gm-Message-State: AKS2vOzzUW/L4b2xhZ1a/PmTXYe3cm1O/Yvuxgoio+fgfu9gqXoBtTBg LNBPuO7ACRaNZpmkO0lViYorSEqZAEca
X-Received: by 10.28.103.132 with SMTP id b126mr16720445wmc.10.1498834153400;  Fri, 30 Jun 2017 07:49:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.171.210 with HTTP; Fri, 30 Jun 2017 07:49:13 -0700 (PDT)
From: Haizhou Du <duhaizhou@gmail.com>
Date: Fri, 30 Jun 2017 22:49:13 +0800
Message-ID: <CADdws+y0SjCdX8Y0ks3srmXNJmyApw99ex3d9fFS1ttdixXnyA@mail.gmail.com>
To: IETF ALTO <alto@ietf.org>, draft-xiang-alto-exascale-network-optimization@ietf.org
Content-Type: multipart/alternative; boundary="001a114b75564a711005532e8514"
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/jJHu5pUanL5Msor0voFjsYnShQk>
Subject: [alto] Review of draft-xiang-alto-exascale-network-optimization-02
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, 30 Jun 2017 14:49:17 -0000

--001a114b75564a711005532e8514
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Qiao and all,
I reviewed the latest exascale network optimization draft. In addition to
the review, the key design questions I want to raise discussions are (1)
How to describe DAG of workflow converter in more detail=EF=BC=9F Could we =
give
some examples for different DAG? (2) We give some user API in section
7.2.1, Could we provide some JSON format for it? (3) In the query mode, we
also need some JSON string to describe it.

If you have any comments or suggestion, please share with me. Thank you so
much. In addition, please see my other comments in the following.

*Page 4*

Production ANd Distributed Analysis system (PanDA) in ATLAS and the Physics
Experiment Data Export system (PhEDEX) in CMS have been

*[HZ] =E2=80=9DAND=E2=80=9D -> =E2=80=9Dand=E2=80=9D*

*Page 5*

[DRAFT-CC] and etc. to encode information about multiple types of resources
in science networks,

*[HZ] =E2=80=9Dto=E2=80=9D -> =E2=80=9DTo=E2=80=9D*

*Page 6*

Different sites in this network belong to different administration domain.

*[HZ] =E2=80=9Ddomain=E2=80=9D -> =E2=80=9Ddomains=E2=80=9D*

the orchestrating framework must be able to collect sufficient resource
information about different clusters/sites in real-time as well as over the
longer term,

*[HZ]=E2=80=9Dmust=E2=80=9D->=E2=80=9DMUST=E2=80=9D*

*Page 7*

Hence the orchestrating framework must be modular so that it can support
different dataset management systems and different orchestrating algorithms=
.

*[HZ]=E2=80=9Dmust=E2=80=9D->=E2=80=9DMUST=E2=80=9D*

The orchestrating framework must support the interaction between the
multi-resource orchestration module

*[HZ]=E2=80=9Dmust=E2=80=9D->=E2=80=9DMUST=E2=80=9D*

abstraction, multi-cost, cost calendar, etc. have been proposed to provide
fine-grained network information to applications.

*[HZ]=E2=80=9Detc.=E2=80=9D -> =E2=80=9Detc.,=E2=80=9D*

*Page 10*

a large dataset transfer or analytic application always involve many
network elements in multiple clusters/sites and the absolute number of
involved network elements keep increasing as the scale of clusters increase=
.

*[HZ]=E2=80=9Dinvolve=E2=80=9D->=E2=80=9Dinvolves=E2=80=9D *

*Page 12*

STEP 6 The ALTO servers at each site accept the queries from the ALTO
client, collects resource information from the residing site and sends back
to the ALTO client.


*[HZ]=E2=80=9Dcollects=E2=80=9D->=E2=80=9Dcollect=E2=80=9D, =E2=80=9Csends=
=E2=80=9D->=E2=80=9Dsend=E2=80=9D*

*Page 13*

and the relative priorities may be modified by the resource orchestrator
depending on the role of users (regular users or administrators at
different levels),

*[HZ]=E2=80=9Dmay=E2=80=9D->=E2=80=9DMAY=E2=80=9D*

*Page 14*

The ALTO client should operate in different query modes depending on the
implementation of ALTO servers.

*[HZ]=E2=80=9Dshould=E2=80=9D->=E2=80=9DSHOULD=E2=80=9D*

*Page 15*

Each ALTO server must provide basic information services as specified in
[RFC7285] such as network map,

*[HZ]=E2=80=9Dmust=E2=80=9D->=E2=80=9DMUST=E2=80=9D*

*Page 16*

The multi-resource orchestrator should adjust the resource allocation decis=
ions
based on the progress of ongoing requests, the utilization and dynamics of
cluster resources.

*[HZ]=E2=80=9Dshould=E2=80=9D->=E2=80=9DSHOULD=E2=80=9D*

If we have any mistake, please feel free to figure out.
Thanks a lot!
Best Regards,
*************************************************************
Haizhou
*************************************************************

--001a114b75564a711005532e8514
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><span style=3D"font-size:12.8px">Hi Qiao and all,</sp=
an><div><span style=3D"font-size:12.8px">I reviewed the=C2=A0</span><span s=
tyle=3D"font-size:12.8px">latest=C2=A0</span><span style=3D"font-size:12.8p=
x">exascale network optimization draft.=C2=A0</span><span style=3D"font-siz=
e:12.8px">In addition to the review, the key design=C2=A0questions I want t=
o raise discussions are (1) How to=C2=A0describe DAG of=C2=A0</span><span s=
tyle=3D"font-size:13px;font-family:Courier">workflow converter</span><span =
style=3D"font-size:12.8px">=C2=A0in more detail=EF=BC=9F Could we give some=
 examples for different DAG? (2) We give some user API in section 7.2.1, Co=
uld we provide=C2=A0some </span>JSON<span style=3D"font-size:12.8px"> forma=
t for it? (3) In the query mode, we also need some JSON string to describe =
it.</span></div>















<div style=3D"font-size:12.8px"><br></div><div style=3D"font-size:12.8px"><=
span style=3D"font-size:12.8px">If you have any comments or suggestion, ple=
ase share with me. Thank you so much.=C2=A0</span><span style=3D"font-size:=
12.8px">In addition, please see my other comments in the following.</span><=
/div></div><div style=3D"font-size:12.8px"><br></div><div style=3D"font-siz=
e:12.8px"><b>Page 4</b></div><div style=3D"font-size:12.8px">







<p class=3D"gmail-p1"><span class=3D"gmail-s1">Production ANd Distributed A=
nalysis system (PanDA) in ATLAS and the=C2=A0</span><span style=3D"font-siz=
e:12.8px">Physics Experiment Data Export system (PhEDEX) in CMS </span>have=
<span style=3D"font-size:12.8px"> been</span></p><p class=3D"gmail-p1">







</p><p class=3D"gmail-p1"><span class=3D"gmail-s1"><b>[HZ] =E2=80=9DAND=E2=
=80=9D -&gt; =E2=80=9Dand=E2=80=9D</b></span></p><p class=3D"gmail-p1"><spa=
n class=3D"gmail-s1"><b>Page 5</b></span></p><p class=3D"gmail-p1"><span cl=
ass=3D"gmail-s1"> </span></p>







<p class=3D"gmail-p1"><span class=3D"gmail-s1">[DRAFT-CC] and etc. to encod=
e information about multiple types of=C2=A0</span><span style=3D"font-famil=
y:Courier;font-size:13px">resources in science networks,</span><span style=
=3D"font-family:Courier;font-size:13px">=C2=A0</span></p><p class=3D"gmail-=
p1"><span style=3D"font-size:12.8px"><b>[HZ] =E2=80=9Dto=E2=80=9D -&gt; =E2=
=80=9DTo=E2=80=9D</b></span></p><p class=3D"gmail-p1"><span style=3D"font-s=
ize:12.8px"><b>Page 6</b></span></p><p class=3D"gmail-p1"><span class=3D"gm=
ail-s1">Different sites in this network belong to different administration=
=C2=A0</span><span style=3D"font-size:12.8px">domain.</span></p></div><div>







<p class=3D"gmail-p1"><span class=3D"gmail-s1"><b>[HZ] =E2=80=9Ddomain=E2=
=80=9D -&gt; =E2=80=9Ddomains=E2=80=9D</b></span></p><p class=3D"gmail-p1">=
<span class=3D"gmail-s1">the orchestrating framework must be able to collec=
t sufficient=C2=A0</span><span class=3D"gmail-s1">resource information abou=
t different clusters/sites in real-time</span>=C2=A0as well as over the lon=
ger term,=C2=A0</p><p class=3D"gmail-p1">







</p><p class=3D"gmail-p1"><span class=3D"gmail-s1"><b>[HZ]=E2=80=9Dmust=E2=
=80=9D-&gt;=E2=80=9DMUST=E2=80=9D</b></span></p><p class=3D"gmail-p1"><span=
 class=3D"gmail-s1"><b>Page 7</b></span></p>







<p class=3D"gmail-p1"><span class=3D"gmail-s1"><span style=3D"font-family:C=
ourier;font-size:13px">Hence the orchestrating=C2=A0</span>framework must b=
e modular so that it can support different dataset=C2=A0</span>management s=
ystems and different orchestrating algorithms.</p><p class=3D"gmail-p1"><b>=
[HZ]=E2=80=9Dmust=E2=80=9D-&gt;=E2=80=9DMUST=E2=80=9D</b><br></p><p class=
=3D"gmail-p1"><span class=3D"gmail-s1">The orchestrating framework must sup=
port the interaction between the</span>=C2=A0 multi-resource orchestration =
module</p><p class=3D"gmail-p1"><b>[HZ]=E2=80=9Dmust=E2=80=9D-&gt;=E2=80=9D=
MUST=E2=80=9D</b><br></p><p class=3D"gmail-p1"><span class=3D"gmail-s1">abs=
traction, multi-cost, cost calendar, etc. have been proposed to</span>=C2=
=A0provide fine-grained network information to applications.</p><p class=3D=
"gmail-p1"><b> </b></p><p class=3D"gmail-p1"><span class=3D"gmail-s1"><b>[H=
Z]=E2=80=9Detc.=E2=80=9D -&gt; =E2=80=9Detc.,=E2=80=9D</b></span></p><p cla=
ss=3D"gmail-p1"><b>Page 10</b></p><p class=3D"gmail-p1"><span class=3D"gmai=
l-s1">a large=C2=A0</span>dataset transfer or analytic application always i=
nvolve many network elements in multiple clusters/sites and the absolute nu=
mber of involved network elements keep increasing as the scale of clusters =
increase.</p><p class=3D"gmail-p1"><b>[HZ]=E2=80=9Dinvolve=E2=80=9D-&gt;=E2=
=80=9Dinvolves=E2=80=9D=C2=A0</b></p><p class=3D"gmail-p1"><b>Page 12</b></=
p><p class=3D"gmail-p1"><span class=3D"gmail-s1">STEP 6 The ALTO servers at=
 each site accept the queries from the</span>=C2=A0ALTO client, collects re=
source information from the residing site and sends back to the ALTO client=
.</p><p class=3D"gmail-p1"><b>[HZ]=E2=80=9Dcollects=E2=80=9D-&gt;=E2=80=9Dc=
ollect=E2=80=9D, =E2=80=9Csends=E2=80=9D-&gt;=E2=80=9Dsend=E2=80=9D<br></b>=
</p><p class=3D"gmail-p1"><b>Page 13</b></p><p class=3D"gmail-p1"><span cla=
ss=3D"gmail-s1">and the relative=C2=A0</span>priorities may be modified by =
the resource orchestrator depending on the role of users (regular users or =
administrators at different levels),</p><p class=3D"gmail-p1"><b>[HZ]=E2=80=
=9Dmay=E2=80=9D-&gt;=E2=80=9DMAY=E2=80=9D</b>=C2=A0</p><p class=3D"gmail-p1=
"><b>Page 14</b></p><p class=3D"gmail-p1">The ALTO client should operate in=
 different query modes depending on the implementation of ALTO servers.</p>=
<p class=3D"gmail-p1">







</p><p class=3D"gmail-p1"><span class=3D"gmail-s1"><b>[HZ]=E2=80=9Dshould=
=E2=80=9D-&gt;=E2=80=9DSHOULD=E2=80=9D</b></span></p><p class=3D"gmail-p1">=
<span class=3D"gmail-s1"><b>Page 15</b></span></p><p class=3D"gmail-p1"><sp=
an class=3D"gmail-s1">Each=C2=A0</span>ALTO server must provide basic infor=
mation services as specified in [RFC7285] such as network map,</p><p class=
=3D"gmail-p1"><b>[HZ]=E2=80=9Dmust=E2=80=9D-&gt;=E2=80=9DMUST=E2=80=9D</b><=
br></p><p class=3D"gmail-p1"><b>Page 16</b></p><p class=3D"gmail-p1"><span =
class=3D"gmail-s1">The multi-resource orchestrator should adjust the resour=
ce allocation=C2=A0</span>decisions based on the progress of ongoing reques=
ts, the utilization and dynamics of cluster resources. =C2=A0</p><p class=
=3D"gmail-p1">







</p><p class=3D"gmail-p1"><span class=3D"gmail-s1"><b>[HZ]=E2=80=9Dshould=
=E2=80=9D-&gt;=E2=80=9DSHOULD=E2=80=9D</b></span></p><p class=3D"gmail-p1">=
If we have any mistake, please feel free to figure out.</p></div><div class=
=3D"gmail_signature"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><di=
v dir=3D"ltr"><div style=3D"text-align:justify"><font face=3D"Calibri, sans=
-serif"><span style=3D"font-size:14px">Thanks a lot!</span></font></div><di=
v style=3D"text-align:justify"><font face=3D"Calibri, sans-serif"><span sty=
le=3D"font-size:14px">Best Regards,</span></font></div><div style=3D"text-a=
lign:justify"><font face=3D"Calibri, sans-serif"><span style=3D"font-size:1=
4px">*************************************************************</span></=
font></div><div style=3D"text-align:justify"><div style=3D"color:rgb(136,13=
6,136);font-size:small"><span style=3D"font-size:14px;font-family:Calibri,s=
ans-serif">Haizhou</span></div></div><div style=3D"text-align:justify"><spa=
n style=3D"font-size:14px;font-family:Calibri,sans-serif">*****************=
********************************************</span><br></div></div></div></=
div></div></div>
</div>

--001a114b75564a711005532e8514--


From nobody Fri Jun 30 08:16:04 2017
Return-Path: <sabine.randriamasy@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 B299E129AFE for <alto@ietfa.amsl.com>; Fri, 30 Jun 2017 08:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.702
X-Spam-Level: 
X-Spam-Status: No, score=-4.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 XB2e03dTUE7i for <alto@ietfa.amsl.com>; Fri, 30 Jun 2017 08:16:01 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50096.outbound.protection.outlook.com [40.107.5.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60185129B01 for <alto@ietf.org>; Fri, 30 Jun 2017 08:16:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=PNZ3ayQfSEBzjLDXSboNY76zdl8KLTegXTaYyGoE+F0=; b=ltAVG4Xt6F5e8twGsNbj8ajPvPPStHK9l4kDnCIs6Z5s+03ROINXm5dtU3ApjXWsb3SOaYf1JZp7DfYnl0pbRcHi7hxE3FKVDaSg8jmEsPYIxFsAXo79xmfyr6YxXyBeSbsX304+2QwjWMrd7b7/FBRMa+s1P7SmK8DX1IP+XiE=
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) by DB6PR0701MB1750.eurprd07.prod.outlook.com (10.168.10.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.6; Fri, 30 Jun 2017 15:15:57 +0000
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com ([fe80::79f9:96c:a3c5:3ecc]) by DB6PR0701MB2454.eurprd07.prod.outlook.com ([fe80::79f9:96c:a3c5:3ecc%17]) with mapi id 15.01.1240.007; Fri, 30 Jun 2017 15:15:57 +0000
From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
To: Qin Wu <bill.wu@huawei.com>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: New Version Notification for draft-randriamasy-alto-cellular-adresses-00.txt
Thread-Index: AQHS8Sz1sFndM7XE2EmChLiGoGq2lKI8d8XAgAAwBtCAALzusA==
Date: Fri, 30 Jun 2017 15:15:57 +0000
Message-ID: <DB6PR0701MB245449E4EB673BEB59AB67A395D30@DB6PR0701MB2454.eurprd07.prod.outlook.com>
References: <149877783604.4674.4124420883476203809.idtracker@ietfa.amsl.com> <DB6PR0701MB2454676034308E11DF8C2E4B95D20@DB6PR0701MB2454.eurprd07.prod.outlook.com> <B8F9A780D330094D99AF023C5877DABA9A98E559@nkgeml513-mbx.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA9A98E559@nkgeml513-mbx.china.huawei.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [135.245.212.17]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB6PR0701MB1750; 7:JB9LnS8hpoN9w27hORq6L40CxIAAx7VzFW2Hj3Tw99/OfdxVyjasdi3xZnv2bH1e/QsqmrK+co8VJUlAS6CDVRYW8p3TDp507xEo8zZftLaUFmm8G6NQ8rqpRwSTf2HpcM4lSRXg1srnSg9XsPOpoj5/tpUknVTwqEOVpmOk7mtb04Adss2/GtvlJYrgZmNdAAUzP/hSrY/AlZPqz1f10jX6IRGCeqMu4Vdv5FYKi3aITJOBI68Da7cAwWrXRL5H/ob+8h6AcOIMQwbid0c17aiPJUS/DXH0e6yrBo8lcpRR2+1fHQlZjI27sMwTauGAWwRMCvfAqjLSo4KLJRbLqH+sbYdgiXuyh2FJs3lSWn3dqbIn1v2Eot+Vo/AKJh1VpGwNBqkwajZfNw/4w8/554DBvGCTxy2l9+HuTa/x56ZKvs2DpkLbplhnZ0lyuon4I6rvgndmAx3FCyA5SdHb0O7tt2d4ok0QWe11xMc57luAEXed6eHlHCKLo5ILh1oanFyQYTZ29UvihNgUy+/Djpmd2lEu3a1QGQ3pzTnFZTuAAmi+SnbQpL0DUjrUr+Td2XDcV3LfJnfcEmt8Y74t5NwwVB1JH24i4s6VrdSNmpXpDJHHBOM7WO6UXh7KU12mDF2fddxGq8nI4WRj8htDhZjbnbz83PhHaS/gdLVvMFvML9IcTKoMNNEaJCUhGUxx0g0ajb77jya5Ne1rn0H3sMqkgKAnaCgpbqwXKxd41UdHCealichfNoH35VLirjsqPcVCcNCRWspMapTKfGD8lPuLaUvrXC/TS18kv3zfB9s=
x-ms-office365-filtering-correlation-id: f1b71e40-b381-43af-ad56-08d4bfcae8e6
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(48565401081)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:DB6PR0701MB1750; 
x-ms-traffictypediagnostic: DB6PR0701MB1750:
x-microsoft-antispam-prvs: <DB6PR0701MB17508722100A701889F018A095D30@DB6PR0701MB1750.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278178393323532)(120809045254105)(236129657087228)(131327999870524)(50582790962513)(48057245064654)(148574349560750)(167848164394848)(209349559609743)(247924648384137);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(100000703101)(100105400095)(3002001)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123564025)(20161123555025)(20161123558100)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB6PR0701MB1750; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB6PR0701MB1750; 
x-forefront-prvs: 0354B4BED2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(39410400002)(39450400003)(39400400002)(39850400002)(39840400002)(377424004)(13464003)(2501003)(14454004)(8676002)(478600001)(3660700001)(2906002)(7736002)(38730400002)(53936002)(2950100002)(55016002)(3280700002)(3846002)(8936002)(966005)(102836003)(66066001)(9686003)(6306002)(99286003)(33656002)(86362001)(229853002)(230783001)(6436002)(6506006)(6116002)(76176999)(54356999)(50986999)(189998001)(81166006)(2900100001)(74316002)(305945005)(7696004)(25786009)(15650500001)(5660300001)(5250100002)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB1750; H:DB6PR0701MB2454.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jun 2017 15:15:57.6094 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB1750
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/C1RdyHUsG2X88A9thRpU7N10g40>
Subject: Re: [alto] New Version Notification for draft-randriamasy-alto-cellular-adresses-00.txt
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, 30 Jun 2017 15:16:04 -0000

SGkgUWluLA0KDQpUaGFua3MgYSBsb3QgZm9yIHlvdXIgcHJvbXB0IGZlZWRiYWNrLA0KUGxlYXNl
IHNlZSBteSBhbnN3ZXJzIGlubGluZS4gDQpUaGFua3MsDQpTYWJpbmUNCg0KPj4tLS0tLU9yaWdp
bmFsIE1lc3NhZ2UtLS0tLQ0KPj5Gcm9tOiBRaW4gV3UgW21haWx0bzpiaWxsLnd1QGh1YXdlaS5j
b21dDQo+PlNlbnQ6IDMwIEp1bmUgMjAxNyAwNDoyMA0KPj5UbzogUmFuZHJpYW1hc3ksIFNhYmlu
ZSAoTm9raWEgLSBGUi9Ob3pheSkgPHNhYmluZS5yYW5kcmlhbWFzeUBub2tpYS0NCj4+YmVsbC1s
YWJzLmNvbT47IGFsdG9AaWV0Zi5vcmcNCj4+U3ViamVjdDogUkU6IE5ldyBWZXJzaW9uIE5vdGlm
aWNhdGlvbiBmb3IgZHJhZnQtcmFuZHJpYW1hc3ktYWx0by1jZWxsdWxhci0NCj4+YWRyZXNzZXMt
MDAudHh0DQo+Pg0KPj5IaSwgU2FiaW5lOg0KPj5UaGFuayBmb3Igd3JpdGluZyB0aGlzIHNob3J0
IGRyYWZ0LiBJdCBpcyBhIGdvb2Qgc3RhcnQuDQo+PkkgaGF2ZSBhIGZldyBjb21tZW50czoNCj4+
MS4gU2VjdGlvbiAzLjINCj4+TU5DIGlzIGRlZmluZWQgYXMgMi0zIGRpZ2l0YWwgZGVjaW1hbCBu
dW1iZXIgd2l0aG91dCBsZWFkaW5nIHplcm9zPw0KPj5CdXQgaW4gdGhlIGV4YW1wbGUgZm9sbG93
aW5nIE1OQyBkZWZpbml0aW9uLCB5b3UgZ2l2ZSBhbiBleGFtcGxlIE1OQw0KPj52YWx1ZSAwMjAs
IEkgYW0gbm90IHN1cmUgaWYgdGhlIGZpcnN0IGRpZ2l0YWwgbnVtYmVyICIwIiBpcyBsZWFkaW5n
IHplcm8/DQoNCltTUiAgICAgXSBJbiB0aGUgcHJlc2VudCBjYXNlIHRoZSBwdXJwb3NlIHRvIGV4
dHJhY3QgdGhlIE1OQyBleGFjdGx5IGFzIGl0IGhhcyBiZWVuIA0KYXNzaWduZWQgYW5kIGVuY29k
ZWQgYW5kIHJhcGlkbHkgdXNlIHRoaXMgdmFsdWUgaW4gY2VsbHVsYXIgbmV0d29ya2luZyBmdW5j
dGlvbnMuIA0KVGhlIGRlc2lnbiBjb25zaWRlcnMgdGhhdCBhbiBNTkMxIG1heSBiZSBlbmNvZGVk
IHdpdGggIjAyMCIgYW5kIGFub3RoZXIgTU5DMiBtYXkgYmUgZW5jb2RlZCAiMjAiLiAgIA0KSSB0
aGluaywgaG93ZXZlciBNTkMxIGFuZCBNTkMyIHdpbGwgbGlrZWx5IGJlIGFzc29jaWF0ZWQgdG8g
ZGlmZmVyZW50IE1DQ3MuIA0KQ3VycmVudGx5LCBzb21lIE1DQ3MgKGxpa2UgNDA0LCA3MzgpIGhh
dmUgTU5DcyBlbmNvZGVkIGluIDIgYW5kIDMgZGlnaXRzIGJ1dCBubyBjYXNlcyBsaWtlICIyMCIg
YW5kICIwMjAiLg0KDQo+PjIuU2VjdGlvbiAzLjINCj4+Rm9yIEVuZHBvaW50IGFkZHJlc3MgZm9y
bWF0LA0KPj5NQ0MgYW5kIE1OQyBpcyBkZWZpbmVkIGFzIGRpZ2l0YWwgZGVjaW1hbCBudW1iZXIs
IEVDSSBpcyBkZWZpbmVkIGFzIGRpZ2l0YWwNCj4+aGV4IG51bWJlciwgSSBhbSB3b25kZXJpbmcg
d2h5IG5vdCBzcGVjaWZ5IE1DQywgTU5DLCBFQ0kgaW4gdGhlIHNhbWUNCj4+Zm9ybWF0Pw0KDQpb
U1IgICAgIF0gdGhlIG1vdGl2YXRpb24gaXMgdG8gc3RheSBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0
byB0aGUgM2dwcCBFQ0dJIGRlc2lnbiB0aGF0IHNwZWNpZmllcw0KIE1DQyBhbmQgTU5DIGJlaW5n
IGlkZW50aWZpZWQgd2l0aCBkZWNpbWFsIGRpZ2l0cyBhbmQgRUNJIHdpdGggaGV4YWRlY2ltYWwg
ZGlnaXRzDQoNCj4+My4gU2VjdGlvbiAzLjIgRXhhbXBsZToNCj4+V291bGQgaXQgYmUgZ3JlYXQg
dG8gbWFrZSB0aGUgdGV4dCBjb25zaXN0ZW50IHdpdGggdGhlIGV4YW1wbGUNCj4+ImVjZ2k6MjEx
OjQ4MToxMjM0YWJjIj8NCj4+Rm9yIGV4YW1wbGUsIHdoYXQgZG8gd2UgbWVhbiBieSAzMTE/IFdo
YXQgZG8gd2UgbWVhbiBieSA0ODE/DQoNCltTUiAgICAgXSAgSSBhZ3JlZS4gSSB3aWxsIHRyeSB0
byBsb29rIGZvciBmaWN0aXRpb3VzIE1DQyBhbmQgTU5DcyANCg0KPj40LiBIb3cgQUxUTyBDZWxs
IElkIGZvcm1hdCBpcyByZWxhdGVkIHRvIGVuZHBvaW50IGFkZHJlc3MgZm9ybWF0Pw0KDQpbU1Ig
ICAgIF0gQWN0dWFsbHkgUkZDNzI4NSBzcGVjaWZpZXMgZW5kcG9pbnQgYWRkcmVzcyBmb3JtYXRz
IGZvciBpcHY0IGFuZCBpcHY2IA0KYW5kIHRoZSBwdXJwb3NlIG9mIHRoaXMgZHJhZnQgaXMgdG8g
YWdyZWUgb24gYSBmb3JtYXQgZm9yIGNlbGx1bGFyIGVuZHBvaW50cy4NCldoZXJlYXMgSVAgYWRk
cmVzc2VzIGFyZSBhc3NvY2lhdGVkIHRvIGRvbWFpbnMgaXB2NCBhbmQgaXB2NiwgYSANCkNlbGwg
SWQgd2lsbCBiZSBhc3NvY2lhdGVkIHRvIHRoZSBkb21haW4gImVjZ2kiIA0KV2hlbiBhIGNlbGwg
aXMgbWFwcGVkIHRvIGEgUElELCBzYXkgIk15Q2VsbDMiIHRoZSBBTFRPIENlbGwgSWQgd2lsbCBi
ZSB1c2VkIA0KdG8gc3BlY2lmeSB0aGUgZW5kcG9pbnRzIHdpdGhpbiB0aGlzIFBJRC4NCg0KPj41
LiBzZWN0aW9uIDMuNA0KPj5zLzctZGlnaXRhIEVDSSB0aGF0IHN0YXJ0cyB3aXRoIHRoZSAxOCBi
aXRzIDB4MTIzNDgvNy1kaWdpdGFsIEVDSSBIZXggbnVtYmVyDQo+PnRoYXQgc3RhcnRzIHdpdGgg
MTggYml0cyAweDEyMzQ4IDYuIFNlY3Rpb24gMy40IEkgdGhpbmsgJ2VjZ2k6MzExLjQ4MToxMjM0
ODAwLzE4Jw0KPj5kb2Vzbid0IG1hdGNoZXMgJ2VjZ2k6MzExLjQ4MToxMjM0YWJjJy4NCj4+TWF5
YmUgJ2VjZ2k6MzExLjQ4MToxMjM0YWJjJyBzaG91bGQgYmUgcmVwbGFjZWQgd2l0aCAnZWNnaToz
MTEuNDgxOjEyMzRjYmEnDQoNCltTUiAgICAgXSBJJ2xsIGhhcm1vbml6ZSBhbmQgdXBkYXRlIHRo
ZSBleGFtcGxlcw0KPj4NCj4+LVFpbg0KPj4tLS0tLemCruS7tuWOn+S7ti0tLS0tDQo+PuWPkeS7
tuS6ujogYWx0byBbbWFpbHRvOmFsdG8tYm91bmNlc0BpZXRmLm9yZ10g5Luj6KGoIFJhbmRyaWFt
YXN5LCBTYWJpbmUNCj4+KE5va2lhIC0gRlIvTm96YXkpDQo+PuWPkemAgeaXtumXtDogMjAxN+W5
tDbmnIgzMOaXpSA3OjEzDQo+PuaUtuS7tuS6ujogYWx0b0BpZXRmLm9yZw0KPj7kuLvpopg6IFth
bHRvXSBGVzogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1yYW5kcmlhbWFzeS1h
bHRvLWNlbGx1bGFyLQ0KPj5hZHJlc3Nlcy0wMC50eHQNCj4+DQo+PkhlbGxvLA0KPj4NCj4+VGhl
cmUgaGF2ZSBiZWVuIHNldmVyYWwgZGlzY3Vzc2lvbnMgYW5kIGRyYWZ0cyBvbiBBTFRPIHVzZSBj
YXNlcyBpbnZvbHZpbmcNCj4+Y2VsbHVsYXIgbmV0d29ya3MgYW5kIGl0IGFwcGVhcnMgYXMgbmVj
ZXNzYXJ5IHRvIGFncmVlIHVwb24gYW4gQUxUTyBmb3JtYXQNCj4+Zm9yIENlbGwgSWRlbnRpZmll
cnMuDQo+Pg0KPj5UaGlzIHJlbGF0ZXMgdG8gc2V2ZXJhbCBkcmFmdHMgKHBlcmZvcm1hbmNlLCB1
bmlmaWVkIHByb3BlcnRpZXMsIG1vYmlsaXR5DQo+Pm1vZGVscy4uLikuIFNvIEkgaGF2ZSBwb3N0
ZWQgdGhpcyBzaG9ydCBvbmUganVzdCB0byBwcm92aWRlIGEgZGlzY3Vzc2lvbg0KPj5zdXBwb3J0
LiBUaGVyZSBhcmUgYWN0dWFsbHkgb25seSAyLjUgcGFnZXMgdG8gcmVhZC4NCj4+DQo+PkZvciBz
aG9ydCwgdGhpcyBkcmFmdCBwcm9wb3NlcyB0byB1c2UgdGhlIGNlbGx1bGFyIGFkZHJlc3MgZm9y
bWF0IGNvbXBvc2VkIG9mDQo+PmVsZW1lbnRzIGFzIHNwZWNpZmllZCBieSAzR1BQIGFuZCBjYWxs
ZWQgRUNHSS4gRUNHSSAgc3RhbmRzIGZvciBFLVVUUkFOIENlbGwNCj4+R2xvYmFsIElkZW50aWZp
ZXIgYW5kIGlzIHVzZWQgaW4gUHVibGljIExhbmQNCj4+IE1vYmlsZSBOZXR3b3JrcyBiYXNlZCBv
biBFLVVUUkFOLg0KPj4NCj4+TG9va2luZyBmb3J3YXJkIHRvIGhhdmluZyB5b3VyIGZlZWRiYWNr
IGFuZCBwcm9wb3NhbHMuDQo+PlRoYW5rcywNCj4+U2FiaW5lDQo+Pg0KPj4+Pi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+Pj4+RnJvbTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWls
dG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXQ0KPj4+PlNlbnQ6IDMwIEp1bmUgMjAxNyAwMTox
MQ0KPj4+PlRvOiBSYW5kcmlhbWFzeSwgU2FiaW5lIChOb2tpYSAtIEZSL05vemF5KSA8c2FiaW5l
LnJhbmRyaWFtYXN5QG5va2lhLQ0KPj4+PmJlbGwtbGFicy5jb20+DQo+Pj4+U3ViamVjdDogTmV3
IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1yYW5kcmlhbWFzeS1hbHRvLWNlbGx1bGFy
LQ0KPj4+PmFkcmVzc2VzLTAwLnR4dA0KPj4+Pg0KPj4+Pg0KPj4+PkEgbmV3IHZlcnNpb24gb2Yg
SS1ELCBkcmFmdC1yYW5kcmlhbWFzeS1hbHRvLWNlbGx1bGFyLWFkcmVzc2VzLTAwLnR4dA0KPj4+
PmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgU2FiaW5lIFJhbmRyaWFtYXN5IGFu
ZCBwb3N0ZWQgdG8NCj4+Pj50aGUgSUVURiByZXBvc2l0b3J5Lg0KPj4+Pg0KPj4+Pk5hbWU6CQlk
cmFmdC1yYW5kcmlhbWFzeS1hbHRvLWNlbGx1bGFyLWFkcmVzc2VzDQo+Pj4+UmV2aXNpb246CTAw
DQo+Pj4+VGl0bGU6CQlBTFRPIGNlbGx1bGFyIGFkZHJlc3Nlcw0KPj4+PkRvY3VtZW50IGRhdGU6
CTIwMTctMDYtMzANCj4+Pj5Hcm91cDoJCUluZGl2aWR1YWwgU3VibWlzc2lvbg0KPj4+PlBhZ2Vz
OgkJNQ0KPj4+PlVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1k
cmFmdHMvZHJhZnQtcmFuZHJpYW1hc3ktYWx0by0NCj4+Pj5jZWxsdWxhci1hZHJlc3Nlcy0wMC50
eHQNCj4+Pj5TdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtcmFuZHJpYW1hc3ktYWx0by0NCj4+Y2VsbHVsYXItDQo+Pj4+YWRyZXNzZXMvDQo+Pj4+
SHRtbGl6ZWQ6ICAgICAgIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1yYW5kcmlh
bWFzeS1hbHRvLWNlbGx1bGFyLQ0KPj4+PmFkcmVzc2VzLTAwDQo+Pj4+SHRtbGl6ZWQ6ICAgICAg
IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwvZHJhZnQtcmFuZHJpYW1hc3kt
DQo+PmFsdG8tDQo+Pj4+Y2VsbHVsYXItYWRyZXNzZXMtMDANCj4+Pj4NCj4+Pj4NCj4+Pj5BYnN0
cmFjdDoNCj4+Pj4gICBUaGlzIGRyYWZ0IHByb3Bvc2VzIHRvIHVzZSB0aGUgY2VsbHVsYXIgYWRk
cmVzcyBmb3JtYXQgY29tcG9zZWQgb2YNCj4+Pj4gICBlbGVtZW50cyBhcyBzcGVjaWZpZWQgYnkg
M0dQUCBhbmQgY2FsbGVkIEVDR0kuICBFQ0dJIHN0YW5kcyBmb3INCj4+Pj4gICBFLVVUUkFOIENl
bGwgR2xvYmFsIElkZW50aWZpZXIgYW5kIGlzIHVzZWQgaW4gUHVibGljIExhbmQgTW9iaWxlDQo+
Pj4+ICAgTmV0d29ya3MgYmFzZWQgb24gRS1VVFJBTi4NCj4+Pj4NCj4+Pj4NCj4+Pj4NCj4+Pj4N
Cj4+Pj4NCj4+Pj5QbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0
ZXMgZnJvbSB0aGUgdGltZSBvZg0KPj4+PnN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZl
cnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdA0KPj50b29scy5pZXRmLm9yZy4NCj4+Pj4N
Cj4+Pj5UaGUgSUVURiBTZWNyZXRhcmlhdA0KPj4NCj4+X19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4+YWx0byBtYWlsaW5nIGxpc3QNCj4+YWx0b0BpZXRm
Lm9yZw0KPj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FsdG8NCg==


From nobody Fri Jun 30 10:29:06 2017
Return-Path: <sabine.randriamasy@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 447C3131458; Fri, 30 Jun 2017 10:29:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 aH1N53asl9lA; Fri, 30 Jun 2017 10:29:01 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0133.outbound.protection.outlook.com [104.47.1.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87AC6131448; Fri, 30 Jun 2017 10:29:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Ps2Lb/WtD9Z+vZUbxC4FfnjS34+Ct+fkhh7oPYeeh4o=; b=RRcjJxoxGcTFSoQukLndZcE+rkF4dC5yDaWEJDM+L0Z61UL7kjBF/8qfiN75AbqTkp/6+OCmdo35dKCXf+XRIXPxX1vULvXiPWTOPr7zLIdoRq0u3z+WeFzDuPLJzzY6JN9vLS4fKb4MeQu+SKWg8jMDIEcVqMH34WqNrAJ71Kw=
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) by DB6PR0701MB1846.eurprd07.prod.outlook.com (10.168.10.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.6; Fri, 30 Jun 2017 17:28:57 +0000
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com ([fe80::79f9:96c:a3c5:3ecc]) by DB6PR0701MB2454.eurprd07.prod.outlook.com ([fe80::79f9:96c:a3c5:3ecc%17]) with mapi id 15.01.1240.007; Fri, 30 Jun 2017 17:28:57 +0000
From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
To: Dawn Chan <dawn_chen_f@hotmail.com>, "draft-ietf-alto-cost-calendar@ietf.org" <draft-ietf-alto-cost-calendar@ietf.org>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: Some opinions about cost calendar
Thread-Index: AQHS6kKO/F96ShC+eESr7CeYtldFgKI9qw6A
Date: Fri, 30 Jun 2017 17:28:57 +0000
Message-ID: <DB6PR0701MB2454A303AAC0459B781F9C2495D30@DB6PR0701MB2454.eurprd07.prod.outlook.com>
References: <HK2PR0401MB1588F6C5286616118F67FA48B5DA0@HK2PR0401MB1588.apcprd04.prod.outlook.com>
In-Reply-To: <HK2PR0401MB1588F6C5286616118F67FA48B5DA0@HK2PR0401MB1588.apcprd04.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: hotmail.com; dkim=none (message not signed) header.d=none;hotmail.com; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [135.245.212.17]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB6PR0701MB1846; 7:nF3mRxy1Y1hhXX3ZuB+DqrYeln3CHzGa755iGzJWdX3KitndsEH+2Xqz4MkRGDRf5b5eHJFnxy15JTDkXoo76ap+ZAjYN0gzqiADDWB23GuFBpQJByteM8rm+jbTR0wf9lHhs3mlUBu0VLDGz47+s5pQEZNtbyZCtKwrG1B8zEErY7kxiaEJ1UC0oOTCFM6q1/5b6/91uRTjnrtreKtkfrLIPVTVa3bDCD0MfAvkYDhIYg1Y6vILFhiarJhc87UeMQ18zb8/twxybqdh/fsTd0R1OALm0+MTyMYk9P1GCIz54AdtceLJWMxFw+v421HzH3PyJkV4iCbyPT7DM1czrNKqBYWlNftzcy8LXv1440HWgl3Hp5pnG2iCIBBQSEUzntXjGp4TL5CnXTuugODRY4EC5CwJ9IN4RYPEo5uNeXAT9S4Y/wuhCah6AsHkY8pjYJaJTV1+/HJbDaEE2uBQTWS8lR3aB5xt7CTFyaZrCBZNzrsAno1jncMdPOU+8JTkvpqO/6x6Q+YPwBQcQmh2VTkx1D6fmRVI9Rfu1dkk6fOihCA3iVmKkip+zZbpb91j6kFMKUmz5JxarjE7/31YLB3K2UzZaR1T7wtVml9OobJQpY8efNVPEYRWICzbC1SQF3IO8kXWgSqdwMqu9SLStpVpW8yAc/gQyNm8aga99YxWH6L67H2nQJIbuh3EOiJrHq+N67n97E30hxkuuO5IArVBt7aAvgw11hkpeqqfBCSKp0hYZOr5n4c2s29WLs5ism3Tihg8QUbFQjWTvDpY0MzRDvFJJkYOiUR8flaOXMc=
x-ms-office365-filtering-correlation-id: 193295c5-0e3d-4fdf-0e27-08d4bfdd7cff
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(48565401081)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:DB6PR0701MB1846; 
x-ms-traffictypediagnostic: DB6PR0701MB1846:
x-microsoft-antispam-prvs: <DB6PR0701MB18467F24B2BBB9EA35A713D095D30@DB6PR0701MB1846.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(151999592597050)(158342451672863)(133145235818549)(26388249023172)(236129657087228)(48057245064654)(148574349560750)(194151415913766)(21748063052155)(247924648384137);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041248)(20161123555025)(20161123562025)(201703131423075)(201703031522075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123560025)(20161123564025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB6PR0701MB1846; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB6PR0701MB1846; 
x-forefront-prvs: 0354B4BED2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39400400002)(39850400002)(39840400002)(39860400002)(39410400002)(39450400003)(790700001)(5250100002)(6116002)(2950100002)(14454004)(33656002)(8676002)(102836003)(53546010)(3846002)(39060400002)(81166006)(9686003)(76176999)(7696004)(66066001)(86362001)(54356999)(478600001)(3660700001)(3280700002)(7736002)(50986999)(25786009)(2201001)(2906002)(74316002)(6506006)(45080400002)(2501003)(5660300001)(38730400002)(99286003)(6306002)(8936002)(55016002)(2900100001)(54896002)(189998001)(53936002)(68736007)(6246003)(6436002)(229853002)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB1846; H:DB6PR0701MB2454.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB6PR0701MB2454A303AAC0459B781F9C2495D30DB6PR0701MB2454_"
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jun 2017 17:28:57.0287 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB1846
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/jxwxH_j9CzAGEGJXzWOaRvqYhIM>
Subject: Re: [alto] Some opinions about cost calendar
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, 30 Jun 2017 17:29:04 -0000

--_000_DB6PR0701MB2454A303AAC0459B781F9C2495D30DB6PR0701MB2454_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgRGF3biwNCg0KVGhhbmtzIGEgbG90IGZvciB5b3VyIHJldmlldyBhbmQgZmVlZGJhY2suDQpQ
bGVhc2Ugc2VlIG15IGFuc3dlcnMgaW5saW5lLA0KVGhhbmtzLA0KU2FiaW5lDQoNCg0KRnJvbTog
RGF3biBDaGFuIFttYWlsdG86ZGF3bl9jaGVuX2ZAaG90bWFpbC5jb21dDQpTZW50OiAyMSBKdW5l
IDIwMTcgMDU6NTgNClRvOiBkcmFmdC1pZXRmLWFsdG8tY29zdC1jYWxlbmRhckBpZXRmLm9yZzsg
YWx0b0BpZXRmLm9yZw0KU3ViamVjdDogU29tZSBvcGluaW9ucyBhYm91dCBjb3N0IGNhbGVuZGFy
DQoNCkhpIGF1dGhvcnMgb2YgYWx0by1jb3N0LWNhbGVuZGFyIGFuZCBhbGwsDQpBZnRlciByZXZp
ZXdpbmcgdGhlIGRyYWZ0IGNvc3QgY2FsZW5kYXIsIEkgdGhpbmsgdGhlcmUgYXJlIHR3byBwb2lu
dHMgdGhhdCBjb3VsZCBiZSBzcGVjaWZpZWQgbW9yZSBjbGVhcmx5IGluIHRoZSBjb3N0IGNhbGVu
ZGFyIGRlc2lnbi4NCkZpcnN0LCBpbiBTZWN0aW9uIDQuMS4xLCBmb3IgYSBtdWx0aS1jb3N0IGF3
YXJlIGNsaWVudCwgaWYgdGhlIG51bWJlciBvZiB2YWx1ZXMgb2YgZmllbGQg4oCcY2FsZW5kYXJl
ZOKAnSBpcyBsZXNzIHRoYW4gdGhlIOKAnGNvc3QtdHlwZS1uYW1lc+KAnSBxdWVyaWVkLCB0aGUg
QUxUTyBzZXJ2ZXIgbWF5IHJldHVybiBhbiBFUlJPUi4NCltTUiAgICAgXSBUaGUgdGV4dCBjbGVh
cmx5IHNheXMgdGhlIGNsaWVudCBNVVNUIGFkZCBhbiBhcnJheSBvZiBOIGJvb2xlYW4gdmFsdWVz
IGNvcnJlc3BvbmRpbmcgdG8gdGhlIE4gY29zdCB0eXBlcyByZXF1ZXN0ZWQuIERvIHlvdSBtZWFu
IHdlIHNob3VsZCBhZGQgYSBzZW50ZW5jZSBzYXlpbmcgdGhhdCBpZiB0aGUgc2l6ZSBvZiB0aGlz
IGFycmF5IGlzIGRpZmZlcmVudCBmcm9tIE4gdGhlIHNlcnZlciB3aWxsIHJldHVybiBhbiBlcnJv
cj8NCkFub3RoZXIgcHJvYmxlbSByZWxhdGVkIHRvIHRoZSBmaWVsZCDigJxjYWxlbmRhcmVk4oCd
IGlzIHRoYXQsIGlmIHRoZXJlIGlzIGEg4oCcZmFsc2XigJ0gaW4gZmllbGQg4oCcY2FsZW5kYXJl
ZOKAnWZvciBhIGNlcnRhaW4gY29zdCB0eXBlIHdoaWxlIGNvc3QgdHlwZXMgYXJlIOKAnHRydWXi
gJ0oZm9yIGV4YW1wbGUsIHRoZSBjbGllbnQgd2FudHMg4oCcbnVtLXJvdXRpbmdjb3N04oCdIHRv
IGJlIGNhbGVuZGFyZWQgd2hpbGUgZG8gbm90IHdhbnQg4oCcbnVtLWxhdGVuY3nigJ0gdG8gYmUg
Y2FsZW5kYXJlZCksIHdoZW4gd2lsbCB0aGUgY29zdCB2YWx1ZSBvZiDigJxudW0tbGF0ZW5jeeKA
nSBiZSByZXR1cm5lZD8gV2lsbCBpdCBiZSByZXR1cm5lZCB0b2dldGhlciB3aXRoIOKAnG51bS1y
b3V0aW5nY29zdOKAnSBhZnRlciBzb21lIHRpbWUgaW50ZXJ2YWxzPw0KW1NSICAgICBdIFRoZSBB
TFRPIFNlcnZlciBNVVNUIHJldHVybiBzaW5nbGUgdmFsdWVzIGFzIHNwZWNpZmllZCBpbiBSRkM3
Mjg1IGZvciB0aG9zZSBjb3N0IHR5cGVzIGZvciB3aGljaCBubyBjYWxlbmRhciBpcyByZXF1ZXN0
ZWQuIFRoaXMgaXMgd3JpdHRlbiBpbiBzZWN0aW9uIDQuMyBidXQgeW91IGFyZSByaWdodCwgaXQg
c2hvdWxkIGJlIGJldHRlciBzcGVjaWZpZWQgaW4gc2VjdGlvbnMgNC4yLjIgYW5kIDQuMS4yLiBU
aGFua3MgZm9yIHBvaW50aW5nIHRoaXMuDQoNClNlY29uZCwgdGhlIGZvbGxvd2luZyBpcyB0aGUg
ZXhhbXBsZSBvZiBoZSBjYXBhYmlsaXR5IG9mIEZpbHRlcmVkIENvc3QgTWFwIGluIFNlY3Rpb24g
My4zLiBBcyB3ZSBjYW4gc2VlLCB0aGUgY29zdC10eXBlIOKAnG51bS1yb3V0aW5nLWNvc3TigJ0g
YW5kIOKAnG51bS1wYXRoYmFuZHdpZHRo4oCdIHNoYXJlIHRoZSBzYW1lIOKAnHRpbWUtaW50ZXJ2
YWwtc2l6ZeKAnSBhbmQg4oCcbnVtYmVyLW9mLWludGVydmFsc+KAnSwgc28gdGhleSBhcmUgbGlz
dGVkIGluIG9uZSDigJxjYWxlbmRhci1hdHRyaWJ1dGVz4oCdLg0KImNhcGFiaWxpdGllcyIgOiB7
DQogICAgICAgICAgICAgICJjb3N0LWNvbnN0cmFpbnRzIiA6IHRydWUsDQogICAgICAgICAgICAg
ICJjb3N0LXR5cGUtbmFtZXMiICA6IFsgIm51bS1yb3V0aW5nY29zdCIsICJudW0tcGF0aGJhbmR3
aWR0aCIsDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgInN0cmluZy1zZXJ2
aWNlLXN0YXR1cyIgXSwNCiAgICAgICAgICAgICAgImNhbGVuZGFyLWF0dHJpYnV0ZXMiIDogWw0K
ICAgICAgICAgICAgICAgICB7ImNvc3QtdHlwZS1uYW1lcyIgOiBbICJudW0tcm91dGluZ2Nvc3Qi
LCAibnVtLXBhdGhiYW5kd2lkdGgiIF0sDQogICAgICAgICAgICAgICAgICAidGltZS1pbnRlcnZh
bC1zaXplIiA6ICIxIGhvdXIiLA0KICAgICAgICAgICAgICAgICAgIm51bWJlci1vZi1pbnRlcnZh
bHMiIDogMjQNCiAgICAgICAgICAgICAgICAgfSwNCiAgICAgICAgICAgICAgICAgeyJjb3N0LXR5
cGUtbmFtZXMiIDogInN0cmluZy1zZXJ2aWNlLXN0YXR1cyIsDQogICAgICAgICAgICAgICAgICAi
dGltZS1pbnRlcnZhbC1zaXplIiA6ICIzMCBtaW51dGUiLA0KICAgICAgICAgICAgICAgICAgIm51
bWJlci1vZi1pbnRlcnZhbHMiIDogNDgNCiAgICAgICAgICAgICAgICAgfQ0KICAgICAgICAgICAg
ICAgXSAvLyBlbmQgY2FsZW5kYXItYXR0cmlidXRlcw0KICAgICAgICAgICAgICAidXNlcyI6IFsg
Im15LWRlZmF1bHQtbmV0d29yay1tYXAiIF0NCiAgICAgICAgICAgICAgfQ0KfQ0KDQpIb3dldmVy
LCB0aGUgb2JqZWN0ICBDYWxlbmRhckF0dHJpYnV0ZXMgZGVmaW5lZCBpbiBTZWN0aW9uIDMuMSBp
cyBmb2xsb3dpbmcsIGl0IGRvZXMgbm90IHN1cHBvcnQgbXVsdGlwbGUgY29zdC10eXBlLW5hbWVz
IGluIGEgc2luZ2xlIENhbGVuZGFyQXR0cmlidXRlcyBjdXJyZW50bHkNCm9iamVjdHsNCiAgICAg
W0pTT05TdHJpbmcgICBjb3N0LXR5cGUtbmFtZTtdDQogICAgIEpTT05TdHJpbmcgICAgdGltZS1p
bnRlcnZhbC1zaXplOw0KICAgICBKU09OTnVtYmVyICAgIG51bWJlci1vZi1pbnRlcnZhbHM7DQog
fSBDYWxlbmRhckF0dHJpYnV0ZXM7DQpbU1IgICAgIF0gQWdyZWUsIHRoaXMgbWVtYmVyIHdpbGwg
YmUgbWFuZGF0b3J5IGFuZCBhbiA8MSoqTj4gYXJyYXkgdGhhbmtzIGZvciBwb2ludGluZyB0aGlz
DQoNCkFub3RoZXIgcG9pbnQgaXMgdGhhdCBpbiBTZWN0aW9uIDQuMi4xLCB0aGUgb2JqZWN0IFJl
cUVuZHBvaW50Q29zdE1hcCBpcyBleHRlbmRlZCBhcyBmb2xsb3dzIChhIG5ldyBmaWVsZCBjYWxl
bmRhcmVkIGlzIGFkZGVkKS4gSXQgZXh0ZW5kcyB0aGUgcXVlcnkgZm9ybWF0IG9mIGxlZ2FjeSBl
bmRwb2ludCBjb3N0IHF1ZXJ5LCB3ZSBtYXkgYWxzbyBuZWVkIHRvIGV4dGVuZCB0aGUgcXVlcnkg
Zm9ybWF0IG9mIG11bHRpLWNvc3QgYXdhcmUgcXVlcnkoYSBuZXcgZmllbGQg4oCcY2FsZW5kYXJl
ZOKAnSBhZGQgdG8gdGhlIHF1ZXJ5KS4NCm9iamVjdCB7DQogICAgIENvc3RUeXBlICAgICAgIGNv
c3QtdHlwZTsNCiAgICAgW0pTT05Cb29sZWFuICAgIGNhbGVuZGFyZWQ8MS4uKj47XQ0KICAgICBF
bmRwb2ludEZpbHRlciBlbmRwb2ludHM7DQogICB9IFJlcUVuZHBvaW50Q29zdE1hcDsNCiAgIG9i
amVjdCB7DQogICAgIFtUeXBlZEVuZHBvaW50QWRkciBzcmNzPDAuLio+O10NCiAgICAgW1R5cGVk
RW5kcG9pbnRBZGRyIGRzdHM8MC4uKj47XQ0KICAgfSBFbmRwb2ludEZpbHRlcjsNCltTUiAgICAg
XSBBZ3JlZSwgSeKAmWxsIGFkZCBzb21lIHRleHQgb24gTXVsdGktQ29zdCByZXF1ZXN0cw0KDQpU
aGF04oCZcyBteSBvcGluaW9ucyBhYm91dCB0aGUgZHJhZnQgY29zdC1jYWxlbmRhci4gV2lzaCB0
byBoZWFyIHlvdXIgaWRlYXMsIHRoYW5rcy4NCltTUiAgICAgXSBUaGFua3MNCg0KQmVzdCBSZWdh
cmRzLA0KRGF3bg0K

--_000_DB6PR0701MB2454A303AAC0459B781F9C2495D30DB6PR0701MB2454_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiSGVsdmV0aWNhIE5ldWUiOw0KCXBhbm9z
ZS0xOjAgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNv
Tm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJn
aW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGlt
ZXMgTmV3IFJvbWFuIixzZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxp
bmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHls
ZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmln
aHQ6MGNtOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBjbTsN
Cglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlm
O30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0K
Lk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXpl
OjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJ
bWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJ
e3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+
PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4
dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxh
eW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkZSIiBsaW5rPSJi
bHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxh
bmd1YWdlOkVOLVVTIj5IaSBEYXduLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVMiPlRoYW5rcyBhIGxvdCBmb3IgeW91ciByZXZpZXcgYW5kIGZlZWRiYWNrLg0KPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+UGxlYXNlIHNlZSBteSBhbnN3ZXJz
IGlubGluZSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5UaGFu
a3MsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+U2FiaW5lPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAx
LjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3Jk
ZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20g
MGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+IERh
d24gQ2hhbiBbbWFpbHRvOmRhd25fY2hlbl9mQGhvdG1haWwuY29tXQ0KPGJyPg0KPGI+U2VudDo8
L2I+IDIxIEp1bmUgMjAxNyAwNTo1ODxicj4NCjxiPlRvOjwvYj4gZHJhZnQtaWV0Zi1hbHRvLWNv
c3QtY2FsZW5kYXJAaWV0Zi5vcmc7IGFsdG9AaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4g
U29tZSBvcGluaW9ucyBhYm91dCBjb3N0IGNhbGVuZGFyPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtIZWx2ZXRpY2EgTmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij5IaSBhdXRob3Jz
IG9mIGFsdG8tY29zdC1jYWxlbmRhciBhbmQgYWxsLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtIZWx2ZXRpY2EgTmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij5BZnRlciBy
ZXZpZXdpbmcgdGhlIGRyYWZ0IGNvc3QgY2FsZW5kYXIsIEkgdGhpbmsgdGhlcmUgYXJlIHR3byBw
b2ludHMgdGhhdCBjb3VsZCBiZSBzcGVjaWZpZWQgbW9yZSBjbGVhcmx5IGluIHRoZSBjb3N0IGNh
bGVuZGFyIGRlc2lnbi48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
IE5ldWUmcXVvdDssc2VyaWY7Y29sb3I6IzQ1NDU0NSI+Rmlyc3QsIGluIFNlY3Rpb24gNC4xLjEs
IGZvciBhIG11bHRpLWNvc3QgYXdhcmUgY2xpZW50LCBpZiB0aGUgbnVtYmVyIG9mIHZhbHVlcyBv
ZiBmaWVsZCDigJxjYWxlbmRhcmVk4oCdIGlzIGxlc3MgdGhhbiB0aGUg4oCcY29zdC10eXBlLW5h
bWVz4oCdIHF1ZXJpZWQsIHRoZSBBTFRPIHNlcnZlciBtYXkgcmV0dXJuDQogYW4gRVJST1IuIDwv
c3Bhbj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhIE5ldWUmcXVvdDss
c2VyaWYiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxp
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPltTUiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyBdIFRoZSB0ZXh0IGNsZWFybHkgc2F5cyB0aGUgY2xpZW50IE1VU1QgYWRkIGFuIGFycmF5IG9m
IE4gYm9vbGVhbiB2YWx1ZXMgY29ycmVzcG9uZGluZyB0byB0aGUgTiBjb3N0IHR5cGVzIHJlcXVl
c3RlZC4gRG8geW91IG1lYW4gd2Ugc2hvdWxkIGFkZCBhDQogc2VudGVuY2Ugc2F5aW5nIHRoYXQg
aWYgdGhlIHNpemUgb2YgdGhpcyBhcnJheSBpcyBkaWZmZXJlbnQgZnJvbSBOIHRoZSBzZXJ2ZXIg
d2lsbCByZXR1cm4gYW4gZXJyb3I/PG86cD48L286cD48L3NwYW4+PC9pPjwvYj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPkFub3RoZXIgcHJv
YmxlbSByZWxhdGVkIHRvIHRoZSBmaWVsZCDigJxjYWxlbmRhcmVk4oCdIGlzIHRoYXQsIGlmIHRo
ZXJlIGlzIGEg4oCcZmFsc2XigJ0gaW4gZmllbGQg4oCcY2FsZW5kYXJlZOKAnWZvciBhIGNlcnRh
aW4gY29zdCB0eXBlIHdoaWxlIGNvc3QgdHlwZXMgYXJlIOKAnHRydWXigJ0oZm9yIGV4YW1wbGUs
DQogdGhlIGNsaWVudCB3YW50cyDigJxudW0tcm91dGluZ2Nvc3TigJ0gdG8gYmUgY2FsZW5kYXJl
ZCB3aGlsZSBkbyBub3Qgd2FudCDigJxudW0tbGF0ZW5jeeKAnSB0byBiZSBjYWxlbmRhcmVkKSwg
d2hlbiB3aWxsIHRoZSBjb3N0IHZhbHVlIG9mIOKAnG51bS1sYXRlbmN54oCdIGJlIHJldHVybmVk
Pw0KPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EgTmV1ZSZx
dW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij5XaWxsIGl0IGJlIHJldHVybmVkIHRvZ2V0aGVyIHdp
dGgg4oCcbnVtLXJvdXRpbmdjb3N04oCdIGFmdGVyIHNvbWUgdGltZSBpbnRlcnZhbHM/PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PGk+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZiI+W1NSJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IF0gVGhlIEFMVE8g
U2VydmVyIE1VU1QgcmV0dXJuIHNpbmdsZSB2YWx1ZXMgYXMgc3BlY2lmaWVkIGluIFJGQzcyODUg
Zm9yIHRob3NlIGNvc3QgdHlwZXMgZm9yIHdoaWNoIG5vIGNhbGVuZGFyIGlzIHJlcXVlc3RlZC4g
VGhpcyBpcyB3cml0dGVuIGluIHNlY3Rpb24NCiA0LjMgYnV0IHlvdSBhcmUgcmlnaHQsIGl0IHNo
b3VsZCBiZSBiZXR0ZXIgc3BlY2lmaWVkIGluIHNlY3Rpb25zIDQuMi4yIGFuZCA0LjEuMi4gVGhh
bmtzIGZvciBwb2ludGluZyB0aGlzLg0KPC9zcGFuPjwvaT48L2I+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtIZWx2ZXRpY2EgTmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhIE5ldWUmcXVvdDssc2VyaWY7Y29s
b3I6IzQ1NDU0NSI+U2Vjb25kLCB0aGUgZm9sbG93aW5nIGlzIHRoZSBleGFtcGxlIG9mIGhlIGNh
cGFiaWxpdHkgb2YgRmlsdGVyZWQgQ29zdCBNYXAgaW4gU2VjdGlvbiAzLjMuIEFzIHdlIGNhbiBz
ZWUsIHRoZSBjb3N0LXR5cGUg4oCcbnVtLXJvdXRpbmctY29zdOKAnSBhbmQg4oCcbnVtLXBhdGhi
YW5kd2lkdGjigJ0gc2hhcmUgdGhlDQogc2FtZSDigJx0aW1lLWludGVydmFsLXNpemXigJ0gYW5k
IOKAnG51bWJlci1vZi1pbnRlcnZhbHPigJ0sIHNvIHRoZXkgYXJlIGxpc3RlZCBpbiBvbmUg4oCc
Y2FsZW5kYXItYXR0cmlidXRlc+KAnS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
SGVsdmV0aWNhIE5ldWUmcXVvdDssc2VyaWY7Y29sb3I6IzQ1NDU0NSI+JnF1b3Q7Y2FwYWJpbGl0
aWVzJnF1b3Q7IDogezxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2Eg
TmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJnF1b3Q7Y29zdC1jb25zdHJhaW50cyZxdW90OyA6IHRy
dWUsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7
LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmcXVvdDtjb3N0LXR5cGUtbmFtZXMmcXVvdDsmbmJzcDsgOiBbICZxdW90
O251bS1yb3V0aW5nY29zdCZxdW90OywgJnF1b3Q7bnVtLXBhdGhiYW5kd2lkdGgmcXVvdDssPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlm
O2NvbG9yOiM0NTQ1NDUiPiZuYnNwOyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZxdW90O3N0cmluZy1zZXJ2aWNlLXN0
YXR1cyZxdW90OyBdLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2Eg
TmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij4mbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJnF1b3Q7Y2FsZW5kYXItYXR0cmlidXRlcyZxdW90OyA6
IFs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhIE5ldWUmcXVvdDss
c2VyaWY7Y29sb3I6IzQ1NDU0NSI+Jm5ic3A7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB7JnF1b3Q7Y29zdC10eXBlLW5hbWVzJnF1b3Q7IDog
WyAmcXVvdDtudW0tcm91dGluZ2Nvc3QmcXVvdDssICZxdW90O251bS1wYXRoYmFuZHdpZHRoJnF1
b3Q7IF0sPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1
b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZxdW90O3RpbWUtaW50ZXJ2YWwtc2l6ZSZx
dW90OyA6ICZxdW90OzEgaG91ciZxdW90Oyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7SGVsdmV0aWNhIE5ldWUmcXVvdDssc2VyaWY7Y29sb3I6IzQ1NDU0NSI+Jm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJnF1b3Q7
bnVtYmVyLW9mLWludGVydmFscyZxdW90OyA6IDI0PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPiZuYnNwOyZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfSw8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhIE5ldWUmcXVvdDssc2Vy
aWY7Y29sb3I6IzQ1NDU0NSI+Jm5ic3A7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB7JnF1b3Q7Y29zdC10eXBlLW5hbWVzJnF1b3Q7IDogJnF1
b3Q7c3RyaW5nLXNlcnZpY2Utc3RhdHVzJnF1b3Q7LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtIZWx2ZXRpY2EgTmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij4mbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
cXVvdDt0aW1lLWludGVydmFsLXNpemUmcXVvdDsgOiAmcXVvdDszMCBtaW51dGUmcXVvdDssPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlm
O2NvbG9yOiM0NTQ1NDUiPiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZxdW90O251bWJlci1vZi1pbnRlcnZhbHMmcXVvdDsgOiA0
ODxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EgTmV1ZSZxdW90Oyxz
ZXJpZjtjb2xvcjojNDU0NTQ1Ij4mbmJzcDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IH08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7SGVsdmV0aWNhIE5ldWUmcXVvdDssc2VyaWY7Y29sb3I6IzQ1NDU0NSI+Jm5ic3A7Jm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IF0gLy8gZW5kIGNhbGVu
ZGFyLWF0dHJpYnV0ZXM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNh
IE5ldWUmcXVvdDssc2VyaWY7Y29sb3I6IzQ1NDU0NSI+Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZxdW90O3VzZXMmcXVvdDs6IFsgJnF1b3Q7bXktZGVm
YXVsdC1uZXR3b3JrLW1hcCZxdW90OyBdPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPiZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyB9PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPn08
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhIE5ldWUmcXVvdDssc2Vy
aWY7Y29sb3I6IzQ1NDU0NSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPkhvd2V2ZXIsIHRoZSBv
YmplY3QmbmJzcDsgQ2FsZW5kYXJBdHRyaWJ1dGVzIGRlZmluZWQgaW4gU2VjdGlvbiAzLjEgaXMg
Zm9sbG93aW5nLCBpdCBkb2VzIG5vdCBzdXBwb3J0IG11bHRpcGxlIGNvc3QtdHlwZS1uYW1lcyBp
biBhIHNpbmdsZSBDYWxlbmRhckF0dHJpYnV0ZXMgY3VycmVudGx5PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUi
Pm9iamVjdHs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhIE5ldWUm
cXVvdDssc2VyaWY7Y29sb3I6IzQ1NDU0NSI+Jm5ic3A7Jm5ic3A7ICZuYnNwOyBbSlNPTlN0cmlu
ZyAmbmJzcDsgY29zdC10eXBlLW5hbWU7XTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtIZWx2ZXRpY2EgTmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij4mbmJzcDsmbmJzcDsg
Jm5ic3A7IEpTT05TdHJpbmcmbmJzcDsgJm5ic3A7IHRpbWUtaW50ZXJ2YWwtc2l6ZTs8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhIE5ldWUmcXVvdDssc2VyaWY7Y29s
b3I6IzQ1NDU0NSI+Jm5ic3A7Jm5ic3A7ICZuYnNwOyBKU09OTnVtYmVyJm5ic3A7ICZuYnNwOyBu
dW1iZXItb2YtaW50ZXJ2YWxzOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2
ZXRpY2EgTmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij4mbmJzcDt9IENhbGVuZGFyQXR0
cmlidXRlczs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48
aT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5bU1ImbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgXSBBZ3JlZSwgdGhpcyBtZW1iZXIgd2lsbCBiZSBtYW5kYXRvcnkgYW5kIGFuICZsdDsxKipO
Jmd0OyBhcnJheSB0aGFua3MgZm9yIHBvaW50aW5nIHRoaXMNCjwvc3Bhbj48L2k+PC9iPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhIE5ldWUmcXVvdDssc2VyaWY7Y29sb3I6IzQ1NDU0NSI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2
ZXRpY2EgTmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij5Bbm90aGVyIHBvaW50IGlzIHRo
YXQgaW4gU2VjdGlvbiA0LjIuMSwgdGhlIG9iamVjdCBSZXFFbmRwb2ludENvc3RNYXAgaXMgZXh0
ZW5kZWQgYXMgZm9sbG93cyAoYSBuZXcgZmllbGQgY2FsZW5kYXJlZCBpcyBhZGRlZCkuDQo8L3Nw
YW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNl
cmlmO2NvbG9yOiM0NTQ1NDUiPkl0IGV4dGVuZHMgdGhlIHF1ZXJ5IGZvcm1hdCBvZiBsZWdhY3kg
ZW5kcG9pbnQgY29zdCBxdWVyeSwgd2UgbWF5IGFsc28gbmVlZCB0byBleHRlbmQgdGhlIHF1ZXJ5
IGZvcm1hdCBvZiBtdWx0aS1jb3N0IGF3YXJlIHF1ZXJ5KGEgbmV3IGZpZWxkIOKAnGNhbGVuZGFy
ZWTigJ0gYWRkIHRvIHRoZSBxdWVyeSkuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPm9iamVjdCB7PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2Nv
bG9yOiM0NTQ1NDUiPiZuYnNwOyZuYnNwOyAmbmJzcDsgQ29zdFR5cGUgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgY29zdC10eXBlOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRp
Y2EgTmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij4mbmJzcDsmbmJzcDsgJm5ic3A7IFtK
U09OQm9vbGVhbiZuYnNwOyAmbmJzcDsgY2FsZW5kYXJlZCZsdDsxLi4qJmd0OztdPG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9y
OiM0NTQ1NDUiPiZuYnNwOyZuYnNwOyAmbmJzcDsgRW5kcG9pbnRGaWx0ZXIgZW5kcG9pbnRzOzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EgTmV1ZSZxdW90OyxzZXJp
Zjtjb2xvcjojNDU0NTQ1Ij4mbmJzcDsmbmJzcDsgfSBSZXFFbmRwb2ludENvc3RNYXA7PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2Nv
bG9yOiM0NTQ1NDUiPiZuYnNwOyZuYnNwOyBvYmplY3QgezxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTomcXVvdDtIZWx2ZXRpY2EgTmV1ZSZxdW90OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij4mbmJz
cDsmbmJzcDsgJm5ic3A7IFtUeXBlZEVuZHBvaW50QWRkciBzcmNzJmx0OzAuLiomZ3Q7O108bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhIE5ldWUmcXVvdDssc2VyaWY7
Y29sb3I6IzQ1NDU0NSI+Jm5ic3A7Jm5ic3A7ICZuYnNwOyBbVHlwZWRFbmRwb2ludEFkZHIgZHN0
cyZsdDswLi4qJmd0OztdPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGlj
YSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPiZuYnNwOyZuYnNwOyB9IEVuZHBvaW50
RmlsdGVyOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxp
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPltTUiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyBdIEFncmVlLCBJ4oCZbGwgYWRkIHNvbWUgdGV4dCBvbiBNdWx0aS1Db3N0IHJlcXVlc3RzPC9z
cGFuPjwvaT48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EgTmV1ZSZxdW90OyxzZXJp
Zjtjb2xvcjojNDU0NTQ1Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
SGVsdmV0aWNhIE5ldWUmcXVvdDssc2VyaWY7Y29sb3I6IzQ1NDU0NSI+VGhhdOKAmXMgbXkgb3Bp
bmlvbnMgYWJvdXQgdGhlIGRyYWZ0IGNvc3QtY2FsZW5kYXIuIFdpc2ggdG8gaGVhciB5b3VyIGlk
ZWFzLCB0aGFua3MuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGI+PGk+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmIj5bU1ImbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgXSBUaGFu
a3MNCjwvc3Bhbj48L2k+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EgTmV1ZSZxdW90
OyxzZXJpZjtjb2xvcjojNDU0NTQ1Ij5CZXN0IFJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0hlbHZldGljYSBOZXVlJnF1b3Q7LHNlcmlmO2NvbG9yOiM0NTQ1NDUiPkRh
d248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_DB6PR0701MB2454A303AAC0459B781F9C2495D30DB6PR0701MB2454_--


From nobody Fri Jun 30 10:59:40 2017
Return-Path: <sabine.randriamasy@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 36D0313147E; Fri, 30 Jun 2017 10:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 wJohTlbBzRKK; Fri, 30 Jun 2017 10:59:32 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0097.outbound.protection.outlook.com [104.47.2.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4C9B129B52; Fri, 30 Jun 2017 10:59:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=2GZdNQa2Kad5Oz/xnNZQChC7Xt0+zNFQ3ShPtxrwYrE=; b=RpTsFSvZwbQqhVca0yjgbjFTmmPffqkQvVoLLsh6LSI4VsYjHe8x5D2E4FuP6eg6mXXEFQH3oUDmj8W1qlzuBkrKjBM50qSNe1KkPvRZtFmKae2g0T9rVLce2H3qbmVxoTZvtqHgje3flLDZH3dx4eI4pyaBnrrK7kopv+UVtjU=
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) by DB6PR0701MB3031.eurprd07.prod.outlook.com (10.168.84.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.6; Fri, 30 Jun 2017 17:59:29 +0000
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com ([fe80::79f9:96c:a3c5:3ecc]) by DB6PR0701MB2454.eurprd07.prod.outlook.com ([fe80::79f9:96c:a3c5:3ecc%17]) with mapi id 15.01.1240.007; Fri, 30 Jun 2017 17:59:29 +0000
From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
To: "Li, Geng" <geng.li@yale.edu>, "alto@ietf.org" <alto@ietf.org>, "draft-ietf-alto-cost-calendar@ietf.org" <draft-ietf-alto-cost-calendar@ietf.org>
Thread-Topic: Review on draft-ietf-alto-cost-calendar-01 by Geng
Thread-Index: AQHS8HMuQLzTwfvpkkCJkJ4bp1yyraI9rbRw
Date: Fri, 30 Jun 2017 17:59:29 +0000
Message-ID: <DB6PR0701MB2454994C85386BAE960FDAB395D30@DB6PR0701MB2454.eurprd07.prod.outlook.com>
References: <CY4PR08MB3526BFB8A5CA44375C4FED8191D20@CY4PR08MB3526.namprd08.prod.outlook.com>
In-Reply-To: <CY4PR08MB3526BFB8A5CA44375C4FED8191D20@CY4PR08MB3526.namprd08.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: yale.edu; dkim=none (message not signed) header.d=none;yale.edu; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [135.245.212.17]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB6PR0701MB3031; 7:L1hWaXSCh0EMtiqQHhE2CvAPzJa9/tHJ3dDpJ8QWV5RC1tvQVRFX0Punsz+X2PU+CIepHp5iuBqtWqetKgoiYr44VlG4iSInWXBFs6jGX8RDwc1CLbE+hiXKoe7oGUMYY9+rPNI8VrQOSnLAJPR0amfzBBqhGb4leaHe1CC0sBzdDbF5t7tdpcaCqUXND/QK+LFn8LK0bZEMa9oLlauUhqV4MvN61FRQM0I9G73p3+paviPbeo1qO+XG4gFBIS7CRJbDpVpWuasfUlRs24k9N1ZNIYnoE2q4DMTvhRtPqa0vnyPvkwZjoY27hJ5G/M2rXvagLXcTSRlOrTRioHF0G+bA2OD/Ta5iUQhKsXtn3r6YK6+lyseYs52x6hcLJyAQHTSxZ8RYL3mTeU/kwIXXUYCxCujUFe38BrXkOGq3MqNITJAySpot1pzo4JgEWdhZzXQ+W39nFthAqJIgxu6c3NEbgJTXOD9gK0AbMkVP+FOAwkR0yGNFFuu2rFOeIDUBOhXUhr0+k3cnMVe5dvBv9Rw5qwfFl4V2LgkbPO6ly4fN3QQR4SHq+2Ui3Z5saxWF72IhsqKntNcObnMFR9A9OZZteh0eSANz8R0ojaVqMVI/u1RG7NwwlMdunLJf73igmf4tzKyLymvX3SyTRj3RuAbdau75mG3xZP2xaiY6kN+hhh15CIkeSsTG71PSjIjGWjNEIJTPzgJSfFCyVRvrWxwZwZS8XDx6c+E6gWSY45tr87ikHIXCta/TkPmCaCrMZXuOl9h4fqUBEuVEUfxd+ONMhz1sTC/lr+LLGO10N7c=
x-ms-office365-filtering-correlation-id: 0bee4a34-6c82-4f3c-d731-08d4bfe1c11d
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(48565401081)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:DB6PR0701MB3031; 
x-ms-traffictypediagnostic: DB6PR0701MB3031:
x-microsoft-antispam-prvs: <DB6PR0701MB30316F9591DADF77BFB6C90295D30@DB6PR0701MB3031.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(151999592597050)(158342451672863)(26388249023172)(236129657087228)(48057245064654)(148574349560750)(21748063052155)(92977632026198);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(3002001)(6055026)(6041248)(20161123564025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123562025)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB6PR0701MB3031; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB6PR0701MB3031; 
x-forefront-prvs: 0354B4BED2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39400400002)(39850400002)(39410400002)(39840400002)(39860400002)(229853002)(102836003)(3846002)(7736002)(2950100002)(6116002)(790700001)(2501003)(6506006)(86362001)(6436002)(66066001)(189998001)(8936002)(25786009)(478600001)(2201001)(76176999)(5660300001)(230783001)(54356999)(53546010)(7696004)(6306002)(54896002)(55016002)(3280700002)(2900100001)(9686003)(5250100002)(3660700001)(53936002)(74316002)(81166006)(14454004)(50986999)(8676002)(99286003)(38730400002)(2906002)(2171002)(6246003)(33656002)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB3031; H:DB6PR0701MB2454.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB6PR0701MB2454994C85386BAE960FDAB395D30DB6PR0701MB2454_"
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jun 2017 17:59:29.3337 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB3031
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/8bkjqVxvH47DT1MlVMIVxRp6Aqo>
Subject: Re: [alto] Review on draft-ietf-alto-cost-calendar-01 by Geng
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, 30 Jun 2017 17:59:35 -0000

--_000_DB6PR0701MB2454994C85386BAE960FDAB395D30DB6PR0701MB2454_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Geng,

Thanks a lot for your feedback,
Please see my responses inline,
Thanks,
Sabine


From: Li, Geng [mailto:geng.li@yale.edu]
Sent: 29 June 2017 03:01
To: alto@ietf.org; draft-ietf-alto-cost-calendar@ietf.org
Subject: Review on draft-ietf-alto-cost-calendar-01 by Geng


Dear authors,



Your work on cost calendar makes a lot of sense to me, and here are some co=
mments I have.



Issues:

1. In the 4th paragraph of section 1 (Page 4), here is supposed to introduc=
e the advantages of cost calendar. I would like to add another significant =
advantage which is the reduction of the frequent information exchange betwe=
en ALTO client and ALTO server. And I think it may be the salient benefit t=
hat leads to saving the network resources for ALTO protocol.

[SR     ]  this was meant in the first sentence of paragraph 5. I will try =
to clarify it.



2. In section 2.2.1, the word "time-sensitive" comes up several times, but =
what is the exact definition for "time-sensitive"? Maybe I'm wrong, but I r=
eckon it is used to describe the data for real-time service. I suggest the =
authors can give a definition and examples here, or provide the references =
where the word is interpreted.

[SR     ] Agree, "time varying" is more appropriate

3. I think maybe the authors missed a point which many audiences are concer=
ned about. When the network state is getting changed by e.g., link failures=
, node crashed, and if there is a conflict between the cost calendar that h=
as already been conveyed and the current new cost map, then how the client =
can be aware of it? The ALTO server needs to notify the clients before they=
 schedule data transfers according to the old cost calendar.

[SR     ] Agree, such a notification may be conveyed via incremental update=
s, see [draft-ietf-alto-incr-update-sse]



Typos:

1. In the first line of section 3.1, there is a redundant space before the =
comma.

2. At the end of the 3rd paragraph of section 3.1,  "ressources" =3D=3D> "r=
esources".

[SR     ] Thanks for catching those



Hope these are helpful.

[SR     ] They are, thanks a lot

Sabine



Best, Geng

Computer Science, Yale

--_000_DB6PR0701MB2454994C85386BAE960FDAB395D30DB6PR0701MB2454_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1493334029;
	mso-list-type:hybrid;
	mso-list-template-ids:2003630984 67895311 67895321 67895323 67895311 67895=
321 67895323 67895311 67895321 67895323;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US">Hi Geng,<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US"><o:p>&nbs=
p;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US">Thanks a =
lot for your feedback,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US">Please se=
e my responses inline,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US">Thanks,<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US">Sabine<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US"><o:p>&nbs=
p;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,sans-serif;mso-fareast-language:EN-US"><o:p>&nbs=
p;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang=3D"EN-=
US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> =
Li, Geng [mailto:geng.li@yale.edu]
<br>
<b>Sent:</b> 29 June 2017 03:01<br>
<b>To:</b> alto@ietf.org; draft-ietf-alto-cost-calendar@ietf.org<br>
<b>Subject:</b> Review on draft-ietf-alto-cost-calendar-01 by Geng<o:p></o:=
p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div id=3D"divtagdefaultwrapper">
<div>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">Dear authors,</span><span style=3D"font-size:14.0pt;color:=
black"><o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">&nbsp;</span><span style=3D"font-size:14.0pt;color:black">=
<o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">Your work on cost calendar makes a lot of sense to me, and=
 here are some comments I have.</span><span style=3D"font-size:14.0pt;color=
:black"><o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">&nbsp;</span><span style=3D"font-size:14.0pt;color:black">=
<o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">Issues:</span><span style=3D"font-size:14.0pt;color:black"=
><o:p></o:p></span></p>
<p style=3D"margin-left:5.25pt;text-align:justify"><span lang=3D"EN-US" sty=
le=3D"font-size:14.0pt;color:black">1.</span><span lang=3D"EN-US" style=3D"=
font-size:14.0pt">
<span style=3D"color:black">In the 4th paragraph of section 1 (Page 4), her=
e is supposed to introduce the advantages of cost calendar. I would like to=
 add another significant advantage which is the reduction of the frequent i=
nformation exchange between ALTO client
 and ALTO server. And I think it may be the salient benefit that leads to s=
aving the network resources for ALTO protocol.</span><o:p></o:p></span></p>
<p style=3D"text-align:justify"><b><i><span lang=3D"EN-US" style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">[SR&nbsp;&nbsp;&nbsp;=
&nbsp; ] &nbsp;this was meant in the first sentence of paragraph 5. I will =
try to clarify it.</span></i></b><span lang=3D"EN-US" style=3D"font-size:14=
.0pt">
</span><b><i><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&qu=
ot;Calibri&quot;,sans-serif"><o:p></o:p></span></i></b></p>
<p style=3D"margin-left:5.25pt;text-align:justify"><span lang=3D"EN-US" sty=
le=3D"font-size:14.0pt"><o:p>&nbsp;</o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">2. In section 2.2.1, the word &#8220;time-sensitive&#8221;=
 comes up several times, but what is the exact definition for &#8220;time-s=
ensitive&#8221;? Maybe I&#8217;m wrong, but I reckon it is used to describe
 the data for real-time service. I suggest the authors can give a definitio=
n and examples here, or provide the references where the word is interprete=
d.<o:p></o:p></span></p>
<p style=3D"text-align:justify"><b><i><span lang=3D"EN-US" style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">[SR&nbsp;&nbsp;&nbsp;=
&nbsp; ] Agree, &#8220;time varying&#8221; is more appropriate</span></i></=
b><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&=
quot;,sans-serif"><o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">3. I think maybe the authors missed a point which many aud=
iences are concerned about. When the network state is getting changed by e.=
g., link failures, node crashed, and if
 there is a conflict between the cost calendar that has already been convey=
ed and the current new cost map, then how the client can be aware of it? Th=
e ALTO server needs to notify the clients before they schedule data transfe=
rs according to the old cost calendar.<o:p></o:p></span></p>
<p style=3D"text-align:justify"><b><i><span lang=3D"EN-US" style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">[SR&nbsp;&nbsp;&nbsp;=
&nbsp; ] Agree, such a notification may be conveyed via incremental updates=
, see [draft-ietf-alto-incr-update-sse]</span></i></b><span lang=3D"EN-US" =
style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"><o:p>=
</o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">&nbsp;<o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">Typos:</span><span style=3D"font-size:14.0pt;color:black">=
<o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">1. In the first line of section 3.1, there is a redundant =
space before the comma.</span><span style=3D"font-size:14.0pt;color:black">=
<o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">2. At the end of the 3rd paragraph of section 3.1, &nbsp;<=
/span><span style=3D"font-size:14.0pt;font-family:SimSun;color:black">&#822=
0;</span><span lang=3D"EN-US" style=3D"font-size:14.0pt;color:black">ressou=
rces&#8221;
 =3D=3D&gt; &#8220;resources&#8221;.<o:p></o:p></span></p>
<p style=3D"text-align:justify"><b><i><span lang=3D"EN-US" style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">[SR&nbsp;&nbsp;&nbsp;=
&nbsp; ] Thanks for catching those</span></i></b><span lang=3D"EN-US" style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"><o:p></o:p=
></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">&nbsp;<o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">Hope these are helpful.<o:p></o:p></span></p>
<p style=3D"text-align:justify"><b><i><span lang=3D"EN-US" style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">[SR&nbsp;&nbsp;&nbsp;=
&nbsp; ] They are, thanks a lot<o:p></o:p></span></i></b></p>
<p style=3D"text-align:justify"><b><i><span lang=3D"EN-US" style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,sans-serif">Sabine</span></i></b>=
<span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,sans-serif"><o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">&nbsp;<o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">Best, Geng</span><span style=3D"font-size:14.0pt;color:bla=
ck"><o:p></o:p></span></p>
<p style=3D"text-align:justify"><span lang=3D"EN-US" style=3D"font-size:14.=
0pt;color:black">Computer Science, Yale</span><span style=3D"font-size:14.0=
pt;color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_DB6PR0701MB2454994C85386BAE960FDAB395D30DB6PR0701MB2454_--


From nobody Fri Jun 30 11:23:18 2017
Return-Path: <sabine.randriamasy@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 948D7131458; Fri, 30 Jun 2017 11:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 y6Lro3GDgtiI; Fri, 30 Jun 2017 11:23:14 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0100.outbound.protection.outlook.com [104.47.2.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC78E128BA2; Fri, 30 Jun 2017 11:23:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=V/dqfBhb+BLpdOE3h6tNg01OP1wOQzQOjOizIHv5C+o=; b=Lhh06fxARr5piUvtKkWoJG4dkTztkow8pZxnHYzmQjubbO2buhXTgqhnFMDDApQQh9uZqk8af6CSZBdv6g8JVX0JpTr6r1jsESSyUilqXAJEabRw2VhnR9sI5TjlHivTz3ZsM7608MB6jGh7xQG6GdAs8kbYgxjKN2D7jDiy3uI=
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) by DB6PR0701MB2887.eurprd07.prod.outlook.com (10.168.83.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.6; Fri, 30 Jun 2017 18:23:05 +0000
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com ([fe80::79f9:96c:a3c5:3ecc]) by DB6PR0701MB2454.eurprd07.prod.outlook.com ([fe80::79f9:96c:a3c5:3ecc%17]) with mapi id 15.01.1240.007; Fri, 30 Jun 2017 18:23:05 +0000
From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
To: Yichen Qian <92yichenqian@tongji.edu.cn>, IETF ALTO <alto@ietf.org>, "draft-ietf-alto-cost-calendar@ietf.org" <draft-ietf-alto-cost-calendar@ietf.org>
Thread-Topic: Review of draft-ietf-alto-cost-calendar-01
Thread-Index: AQHS8QDbe/YCvASDgUucG/XNiRsd5KI9s5Pw
Date: Fri, 30 Jun 2017 18:23:05 +0000
Message-ID: <DB6PR0701MB24546543D3C05E216F9532A395D30@DB6PR0701MB2454.eurprd07.prod.outlook.com>
References: <299945C8-58C4-4BEA-98B7-9187F0F263CC@tongji.edu.cn>
In-Reply-To: <299945C8-58C4-4BEA-98B7-9187F0F263CC@tongji.edu.cn>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: tongji.edu.cn; dkim=none (message not signed) header.d=none;tongji.edu.cn; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [135.245.212.17]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB6PR0701MB2887; 7:X66ivx09R1Q04/NtLMyhZRsHSzS/X/RNE9zqO/dMZx4aTKr/Jj1qNjJQuRFsE0tAQg3obbEUb5jBIV6WprE0GdMDpzAV04FVfHD+iQnLt4F5SMUZzs9T7N9NPJVifKoVPFFl524/Y3aM5WhkhWAN9eiILnxry1i40J/lVf1K6ZqkKDeCnaAfzLTHCDWTZGQRWRBtJF/FCoKIwofmSe3OkPwW9t391RAZqrApxEk5G88ereu1eTLZ0izupnMDednXeb/Qk3IaNajMddCgM8sqTKCXGiKnf+WgSoqjomC24kV3CvbG6cayVKox9vJm9vvOrMORLoL5ZrNKdfWsY29/neFv+J1fLcJpYfnuocq44lV1W9urNpJy6BAgQPRqWaoIWQbVNwEMZSUNS15p2v3Zmw+1txryPLuXKNafKAV6Myauz6A8rKz2waCFd1OVrAMKyEYWVnynPmZUJi6Y+ayMoPVzWRYPsRqYaXnzIATg0a8aUO66HP5IihvkY+M4CBP3SS7PhWRAJuYjsnuWOMvA27Nl733leceHQRoJXyE0edf6a8zWNI9ycWsW9kqnw0aYo1/G+fABEhDiBVZsIGj5EGizL4p5UT2S24UTZBa8qzPiLLeiwRgHjdwxZgLnsp+AP/yfqLrM/mP/BhvsVG1kuZyGA9fa9hIv2GJNsyQ7d1Earvi6OklF11uqhhI9foFcIzHpvdi2HX5GfqXhbr+yMTdqOfAbz6lsrIg3ZXIvDdbuP7bgdaqKb0k4tlekeIHbk2LVztswFYJk2Po4ukOX7yscjVZcq4A0n1ZkUtFAjwU=
x-ms-office365-filtering-correlation-id: 20f97d04-36e3-47b9-4bd6-08d4bfe50cf4
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(48565401081)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:DB6PR0701MB2887; 
x-ms-traffictypediagnostic: DB6PR0701MB2887:
x-microsoft-antispam-prvs: <DB6PR0701MB28870591B98140D7116D026995D30@DB6PR0701MB2887.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(236129657087228)(48057245064654)(92977632026198)(247924648384137);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(2017060910020)(5005006)(10201501046)(3002001)(93006095)(93001095)(100000703101)(100105400095)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123558100)(20161123560025)(20161123562025)(20161123555025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB6PR0701MB2887; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB6PR0701MB2887; 
x-forefront-prvs: 0354B4BED2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39400400002)(39850400002)(39860400002)(39410400002)(39840400002)(13464003)(3660700001)(5660300001)(7696004)(2900100001)(189998001)(33656002)(8936002)(2950100002)(66066001)(74316002)(54356999)(305945005)(50986999)(8676002)(76176999)(7736002)(81166006)(2171002)(6506006)(6116002)(6436002)(3846002)(53936002)(9686003)(2906002)(38730400002)(2501003)(6246003)(3280700002)(229853002)(99286003)(55016002)(102836003)(478600001)(5250100002)(230783001)(25786009)(86362001)(14454004)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB2887; H:DB6PR0701MB2454.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jun 2017 18:23:05.0585 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2887
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/tcuVSz5v7kdxC9s2iUNGL46mxhc>
Subject: Re: [alto] Review of draft-ietf-alto-cost-calendar-01
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, 30 Jun 2017 18:23:17 -0000

SGkgUWlhbiwNCg0KVGhhbmtzIGZvciB5b3VyIGZlZWRiYWNrLiBQbGVhc2Ugc2VlIG15IGFuc3dl
cnMgaW5saW5lDQpUaGFua3MsDQpTYWJpbmUNCg0KDQo+Pi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQo+PkZyb206IFlpY2hlbiBRaWFuIFttYWlsdG86OTJ5aWNoZW5xaWFuQHRvbmdqaS5lZHUu
Y25dDQo+PlNlbnQ6IDI5IEp1bmUgMjAxNyAxOTo1NQ0KPj5UbzogSUVURiBBTFRPIDxhbHRvQGll
dGYub3JnPjsgZHJhZnQtaWV0Zi1hbHRvLWNvc3QtY2FsZW5kYXJAaWV0Zi5vcmcNCj4+U3ViamVj
dDogUmV2aWV3IG9mIGRyYWZ0LWlldGYtYWx0by1jb3N0LWNhbGVuZGFyLTAxDQo+Pg0KPj5EZWFy
IGF1dGhvcnMsDQo+Pg0KPj5JIHRoaW5rIGl04oCZcyBxdWl0IHVzZWZ1bCB0byBwcm92aWRlIGNv
c3QgY2FsZW5kYXIgZm9yIHRoZSB1c2Vycy4gSGVyZeKAmXMgbXkNCj4+cmV2aWV3IG9mIHRoaXMg
ZHJhZnQuDQo+Pg0KPj4xLiBPbmUgY29uY2VybiBpcyB0aGF0IHRoZSBxdWVyeSByZXN1bHQgb2Yg
Q29zdCBDYWxlbmRhciBpcyBub3Qgb25seSByZWxhdGVkIHRvDQo+PnJlZ3VsYXIgZGF0YSBjaGFu
Z2VzLCBidXQgYWxzbyBjYW4gYmUgYWZmZWN0ZWQgYnkgc29tZSB1bmV4cGVjdGVkIHRvcG9sb2d5
DQo+PmNoYW5nZXMsIHNheSBsaW5rIGZhaWx1cmVzLiBTbyBzb21lIGNvc3QgaW4gQ29zdCBDYWxl
bmRhciBjYW4gYmUgYWJub3JtYWwgYW5kDQo+Pm1heSBtaXNsZWFkIHRoZSB1c2VyIHRvIGRvIHRo
ZSBpbmFwcHJvcHJpYXRlIGNob2ljZS4NCg0KW1NSICAgICBdIEluZGVlZCwgbGluayBhbmQgbmV0
d29yayBmYWlsdXJlcyBhcmUgYmUgZXNzZW5jZSBub3QgcHJlZGljYWJsZSBhbmQgQUxUTyBDbGll
bnRzIA0Kc2hvdWxkIGJlIG5vdGlmaWVkIGFzIHNvb24gYXMgcG9zc2libGUuIE9uZSBvcHRpb24g
YXMgSSBzdWdnZXN0ZWQgdG8gR2VuZyBpcyB0byBkZWZpbmUgYW4gYXBwcm9wcmlhdGUgDQpzZXJ2
aWNlIGluIGRyYWZ0LWlldGYtYWx0by1pbmNyLXVwZGF0ZS1zc2UtMDUNCj4+DQo+PjIuIEluIHRo
ZSBjdXJyZW50IGRlc2lnbiwgdGhlIEFMVE8gY2xpZW50IG9ubHkgY2hvb3NlcyBpZiBpdCBuZWVk
cyB0aGUgY2FsZW5kYXIuDQo+PklzIGl0IHBvc3NpYmxlIHRoYXQgdGhlIEFMVE8gc2VydmVyIGhh
cyBzZXZlcmFsIG9wdGlvbnMgb2YgZGlmZmVyZW50DQo+PmNvbWJpbmF0aW9ucyBvZiDigJx0aW1l
LWludGVydmFsLXNpemXigJ0gYW5kIOKAnG51bWJlci1vZiBpbnRlcnZhbHPigJ0gZm9yIEFMVE8N
Cj4+Y2xpZW50IHRvIGNob29zZSBmb3IgbW9yZSBmaW5lLWdyYWluZWQgQ29zdCBDYWxlbmRhcnM/
DQo+Pg0KW1NSICAgICBdIFRoaXMgbWF5IGluZGVlZCBiZSBhbiBvcHRpb24uIElmIHRoZSBTZXJ2
ZXIgY2FuIGFmZm9yZCBpdCBpbiB0ZXJtcyBvZiB3b3JrbG9hZCwgDQppdCBtYXkgcHJvcG9zZSBk
aWZmZXJlbnQgY2FsZW5kYXIgYXR0cmlidXRlcyBmb3IgYSBzYW1lIENvc3QgVHlwZS4gIA0KDQo+
Pk90aGVyIGRldGFpbGVkIG1vZGlmaWNhdGlvbjoNCj4+DQo+PkluIHRoZSAzcmQgcGFyYWdyYXBo
IG9mIHNlY3Rpb24gMi4yLCDigJxBIGNhbGVuZGFyIGFuZCBpdHMgY2FwYWJpbGl0aWVzIGFyZQ0K
Pj5hc3NvY2lhdGVkIHRvIGEgZ2l2ZW4gaW5mb3JtYXRpb24gcmVzb3VyY2XigJ0NCj4+LSBhc3Nv
Y2lhdGVkIHRvIC0+IGFzc29jaWF0ZWQgd2l0aA0KPj4NCj4+SW4gdGhlIDFzdCBwYXJhZ3JhcGgg
b2Ygc2VjdGlvbiAzLCDigJxBIGNhbGVuZGFyIGlzIGFzc29jaWF0ZWQgdG8gYW4gaW5mb3JtYXRp
b24NCj4+cmVzb3VyY2UgcmF0aGVyIHRoYW4gYSBjb3N0IHR5cGUu4oCdDQo+Pi0gYXNzb2NpYXRl
ZCB0byAtPiBhc3NvY2lhdGVkIHdpdGgNCj4+DQo+PkluIHRoZSAxc3QgcGFyYWdyYXBoIG9mIHNl
Y3Rpb24gMy4xLCDigJ1ieSBhbiBvYmplY3Qgb2YgdHlwZSAnQ2FsZW5kYXJBdHRyaWJ1dGVzJywN
Cj4+YXNzb2NpYXRlZCB0byB0aGlzIENvc3QgVHlwZSBhbmQgc3BlY2lmaWVkIGJlbG93LuKAnQ0K
Pj4tIGFzc29jaWF0ZWQgdG8gLT4gYXNzb2NpYXRlZCB3aXRoDQo+Pg0KPj5JbiB0aGUgM3JkIHBh
cmFncmFwaCBvZiBzZWN0aW9uIDMuMSwg4oCdb24gdGhpcyAiY29zdC10eXBlLW5hbWUiIGZvciB0
aGlzDQo+PnJlc3NvdXJjZSBlbnRyeS7igJ0NCj4+LSByZXNzb3VyY2UgLT4gcmVzb3VyY2UNCj4+
DQo+PkluIHRoZSAxc3QgcGFyYWdyYXBoIG9mIHNlY3Rpb24gNC4xLjMsIOKAnWFzIHNwZWNpZmll
ZCBpbiB0aGUgSVJEIHRvIHNoZWR1bGUgaXRzDQo+PmJ1bGsgZGF0YSB0cmFuc2ZlcnMgYXMgZGVz
Y3JpYmVkIGluIHRoZSB1c2UgY2FzZXMu4oCdDQo+Pi0gc2hlZHVsZSAtPiBzY2hlZHVsZQ0KPj4N
Cj4+SW4gc2VjdGlvbiA0LjIuMiwg4oCcaW5jbHVkZSB0aGUgc2FtZSBhZGRpZmlvbmFsIG1lbWJl
ciAiY2FsZW5kYXItcmVzcG9uc2UtDQo+PmF0dHJpYnV0ZXMiIGFzIOKApuKAnQ0KPj4tIGFkZGlm
aW9uYWwgLT5hZGRpdGlvbmFsDQo+Pg0KPj5JbiB0aGUgMXN0IHBhcmFncmFwaCBvZiBzZWN0aW9u
IDQuMi4zLCDigJxMZXQgdXMgYXNzdW1lIGFuIEFwcGxpY2F0aW9uIENsaWVudCBpcw0KPj5sb2Nh
dGVkIGluIGFuIGVuZCBzeXRlbSB3aXRoIGxpbWl0ZWQgcmVzb3VyY2VzIGFuZCDigKbigJ0NCj4+
LSBzeXRlbSAtPiBzeXN0ZW0NCj4+DQo+PkluIHRoZSAybmQgcGFyYWdyYXBoIG9mIHNlY3Rpb24g
NC4yLjMsIOKAnHRoZSAncm91dGluZ2Nvc3QnIGlzIGFzc3VtZWQgdG8gYmUgdGltZQ0KPj5zZW50
aXRpdmUgd2l0aCB2YWx1ZXMgcHJvdmlkZWQgYXMgQUxUTyBDYWxlbmRhcnMu4oCdDQo+Pi0gc2Vu
dGl0aXZlIC0+IHNlbnNpdGl2ZQ0KW1NSICAgICBdIHJlcGxhY2VkIGJ5IHRpbWUtdmFyeWluZw0K
Pj4NCj4+SW4gdGhlIDNyZCBwYXJhZ3JhcGggb2Ygc2VjdGlvbiA0LjIuMywgIlRoZSBBTFRPIENs
aWVudCBhc3NvY2lhdGVkIHRvIHRoZQ0KPj5BcHBsaWNhdGlvbiBDbGllbnQg4oCm4oCdDQo+Pi0g
YXNzb2NpYXRlZCB0byAtPiBhc3NvY2lhdGVkIHdpdGgNCj4+DQo+PkluIHRoZSA0dGggcGFyYWdy
YXBoIG9mIHNlY3Rpb24gNC4yLjMsIOKAnHRoZSBzb2xsaWNpdGVkIEFMVE8gU2VydmVyIGhhcyDi
gKbigJ0NCj4+LSBzb2xsaWNpdGVkIC0+IHNvbGljaXRlZA0KPj4NCj4+SW4gdGhlIDJuZCBwYXJh
Z3JhcGggb2Ygc2VjdGlvbiA0LjMsIOKAnEFuIEFMVE8gU2VydmVyIGFxdWlyaW5nIGNvc3QgdmFs
dWVzIGluDQo+PmxpbWl0ZWQgdGltZSBpbnRlcnZhbHMg4oCm4oCdDQo+Pi0gYXF1aXJpbmcgLT4g
YWNxdWlyaW5nDQpbU1IgICAgIF0gdGhpcyBzZW50ZW5jZSB3aWxsIGJlIHJlbW92ZWQgYW5kIHRo
ZSBwYXJhZ3JhcGggbW92ZWQgdG8gc2VjdGlvbiAyLjINCj4+DQo+PkluIHRoZSA2dGggcGFyYWdy
YXBoIG9mIHNlY3Rpb24gNS4xLCDigJxhIHNtYWxsIHRvcG9sb2d5IHdpdGggbG93IGRlbnNpdHkg
YW5kDQo+PmxvdyBjYXBhY2l0eSB0aGF0IGNhcnJpZXMgaW5wcmVkaWN0YWJsZeKAnQ0KPj4tIGlu
cHJlZGljdGFibGUgLT4gdW5wcmVkaWN0YWJsZQ0KPj4NCj4+SW4gdGhlIDNyZCBwYXJhZ3JhcGgg
b2Ygc2VjdGlvbiA1LjIsIOKAnHRoZSBpbnRlcmFjdGlvbiB3aXRoIEVuZHBvaW50cyBjYW4gYmUN
Cj4+b3JjaGVzdHJhdHJhdGVkIGFuZCBzY2hlZHVsZWQgYXQgdGhlIHRpbWUgc2xvdHMg4oCm4oCd
DQo+Pi0gb3JjaGVzdHJhdHJhdGVkIC0+IG9yY2hlc3RyYXRlZA0KPj4NCltTUiAgICAgXSBTZWN0
aW9uIDUgd2lsbCBiZSByZW1vdmVkDQoNCj4+VGhlIHN1YnRpdGxlIG9mIHNlY3Rpb24gNi4yLCDi
gJxJbmZvcm1hdGlvbiBmb3IgSUFOQSBvbiBwcm9wb3NlZCBFbmRwb2ludA0KPj5Qcm9wZWVyaWVz
4oCdDQo+Pi0gUHJvcGVlcmllcyAtPiBQcm9wZXJ0aWVzDQo+Pg0KW1NSICAgICBdIEdyZWF0IHRo
YW5rcyBmb3IgY2F0Y2hpbmcgYWxsIHRob3NlIG5pdHMgDQoNCj4+QmVzdCB3aXNoZXMsDQo+PkVh
c29uDQo=

