
From diego@tid.es  Tue Feb  5 06:42:54 2013
Return-Path: <diego@tid.es>
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 C2BA321F8972 for <alto@ietfa.amsl.com>; Tue,  5 Feb 2013 06:42:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.921
X-Spam-Level: 
X-Spam-Status: No, score=-5.921 tagged_above=-999 required=5 tests=[AWL=0.678,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GaggomvJRf-v for <alto@ietfa.amsl.com>; Tue,  5 Feb 2013 06:42:52 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 5616121F8962 for <alto@ietf.org>; Tue,  5 Feb 2013 06:42:51 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MHR00G9W4V7QI@tid.hi.inet> for alto@ietf.org; Tue, 05 Feb 2013 15:42:49 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 9E.72.02896.76A11115; Tue, 05 Feb 2013 15:42:47 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MHR00GB44VBQI@tid.hi.inet> for alto@ietf.org; Tue, 05 Feb 2013 15:42:47 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Tue, 05 Feb 2013 15:42:47 +0100
Date: Tue, 05 Feb 2013 14:42:47 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <CD2ED65D.2CC8B%w.roome@alcatel-lucent.com>
X-Originating-IP: [10.95.64.115]
To: Wendy Roome <w.roome@alcatel-lucent.com>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A0468D53592@EX10-MB2-MAD.hi.inet>
Content-id: <41D5598C2376C14CB2EC5958C02AE3AE@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, es-ES
Thread-topic: [alto] Unifying cost-mode and cost-type
Thread-index: AQHN/x3F29oSMrTFO0S6VfH6Nykxm5hrTx4A
X-AuditID: 0a5f4e69-b7f636d000000b50-a6-51111a67e199
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42Lhivcz1M2QEgw0aGnWtni4fS+rA6PHkiU/ mQIYo7hsUlJzMstSi/TtErgy5q2+yl4wQ6tiw/Q17A2MPZpdjJwcEgImEmdXL2KBsMUkLtxb zwZiCwlsY5ToPVYKYX9nlDi1tbyLkQvInskocXbafiaQBIuAqsSH+w/BbDYg+1Hzb3YQWxho 6PXbD1hBbE4BC4ntZ2ZDLVCQ+HPuMZgtIqAjsej8FTCbGah3z5yHYIt5Bbwlrt7azQgRN5N4 fLcXKi4o8WPyPaB6DqC4usSUKbkQJeISza03ocYoSkxb1ADWyiggK/Fu/nxWiFWmElc+XGGC sI0knh+azQRxjoDEkj3nmSFsUYmXj/+xQvxrLvHyzQH2CYwSs5BcMQvJFbMQrpiF5IpZSK5Y wMi6ilGsOKkoMz2jJDcxMyfdwEgvI1MvMy+1ZBMjJOIydzAu36lyiFGAg1GJh/fDD4FAIdbE suLK3EOMEhzMSiK85qKCgUK8KYmVValF+fFFpTmpxYcYmTg4pRoYrUL/n+M9Xiu0Ypeq9j9f q7n6typNZuw/5CiUWL24+0/mH8VH3d2Ss4rUVzySO/x3tZNXYm60ykmpCR6+0Z+YTYQmV9m/ Nf8dX2thvF/Et9BVadoi24W25ansIcLb32+93/qRv39HXMde3dl5sxkeLpv3apawzd3qzifL GDPZOTQ7cx8ftpNXYinOSDTUYi4qTgQAdpYOR5YCAAA=
References: <CD2ED65D.2CC8B%w.roome@alcatel-lucent.com>
Cc: "<alto@ietf.org>" <alto@ietf.org>
Subject: Re: [alto] Unifying cost-mode and cost-type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 05 Feb 2013 14:42:54 -0000

SGksDQoNCkkgdGhpbmsgeW91ciBwcm9wb3NhbCBvbiBhZGRpbmcgdGhpcyBtZXRhZGF0YSBvbiB3
aGF0IGFuIEFMVE8gc2VydmVyIHByb3ZpZGVzIG1ha2VzIGEgbG90IG9mIHNlbnNlLCBlc3BlY2lh
bGx5IGlmIHdlIHRoaW5rIGFib3V0IHRoZSBhZGRpdGlvbmFsIHVzYWdlcyBvZiBBTFRPIHRoYXQg
d2VyZSBvcmlnaW5hbGx5IGRpc2N1c3NlZCBpbiB0aGUgaTJycyBCb0YgaW4gUGFyaXMsIGFuZCB0
aGF0IEknZCBzYXkgaGF2ZSByYWlzZWQgc28gbXVjaCBleHBlY3RhdGlvbiBhbW9uZyB0aGUgU0RO
IGNvbW11bml0eSwgYW1vbmcgb3RoZXJzLg0KDQpUaGVyZWZvcmUsIEknZCBsaWtlIHZlcnkgbXVj
aCB0byBzZWUgdGhpcyBkaXNjdXNzaW9uIGhhcHBlbmluZyB3aXRoaW4gdGhlIEFMVE8gZ3JvdXAs
IG1vc3RseSBvbmNlIHdlIGhhdmUgYmVlbiBhYmxlIHRvIGNvbXBsZXRlIHRoZSBjdXJyZW50IHNl
dCBvZiBkb2N1bWVudHMgYW5kIHdlIGFyZSBpbiB0aGUgcG9zaXRpb24gb2YgcmUtY2hhcnRlcmlu
ZyB0aGUgZ3JvdXAgYWxvbmcgdGhlIGxpbmVzIGRpc2N1c3NlZCBpbiB0aGUgUGFyaXMgQm9GLg0K
DQpCZSBnb29kZSwNCg0KT24gMzAgSmFuIDIwMTMsIGF0IDIwOjEyICwgV2VuZHkgUm9vbWUgd3Jv
dGU6DQoNCj4gSSByZWFsaXplIGl0J3MgbGF0ZSB0byBtYWtlIGNoYW5nZXMsIGJ1dCBJIHJlYWxs
eSB0aGluayB1bmlmeWluZyB0eXBlICYNCj4gbW9kZSBtYWtlcyBhIGxvdCBvZiBzZW5zZS4gIEhl
cmUncyBteSBzdWdnZXN0aW9uOiBleHRlbmQgdGhlICJyZXNvdXJjZQ0KPiBkaXJlY3RvcnkiIHRv
IGluY2x1ZGUgYSBnZW5lcmFsaXplZCBkZXNjcmlwdGlvbiBvZiB0aGUgY29zdC10eXBlcyB0aGF0
IHRoZQ0KPiBzZXJ2ZXIgcHJvdmlkZXMuICBJIHdvbid0IHN1Z2dlc3QgYSBzeW50YXggLS0gdG9v
IGVhcmx5IGZvciB0aGF0ISEgLS0gYnV0DQo+IGhlcmUncyB3aGF0IHRoZSBkZXNjcmlwdGlvbiBz
aG91bGQgcHJvdmlkZSBmb3IgZWFjaCBkaXN0aW5jdCB0eXBlOg0KPg0KPiAqIFRoZSB0eXBlIG5h
bWUuICBUaGlzIGlzIHdoYXQgY2xpZW50cyBnaXZlIGluIHRoZSBjb3N0LXR5cGUgcGFyYW1ldGVy
Lg0KPg0KPiAqIFRoZSB2YWx1ZSB0eXBlLiAgIm51bWVyaWNhbCIgJiAic3RyaW5nIiBhcmUgb2J2
aW91cyBwb3NzaWJpbGl0aWVzLg0KPg0KPiAqIExpbmVhcjogYSBib29sZWFuIGZsYWcuIFRydWUg
bWVhbnMgdGhpcyBudW1lcmljIHZhbHVlIGlzIGxpbmVhci4NCj4gIEZhbHNlIG1lYW5zIHZhbHVl
cyBhcmUgbm90IGxpbmVhci4gVGhpcyB0YWtlcyB0aGUgcGxhY2Ugb2YNCj4gIHRoZSBvcmRpbmFs
L251bWVyaWNhbCBtb2RlLg0KPg0KPiAqIENhdGVnb3J5OiBXaGF0IHRoaXMgY29zdCBtZWFzdXJl
czogImRlbGF5IiwgImhvcHMiLCAiY29zdCIsICJvdGhlciIuDQo+ICBIZXJlICJjb3N0IiBtZWFu
cyBtb25leS4NCj4NCj4gKiBEZXNjcmlwdGlvbjogQW4gb3B0aW9uYWwgZnJlZS1mb3JtIGRlc2Ny
aXB0aW9uIG9mIHRoaXMgY29zdCB0eXBlLg0KPiAgRm9yIGh1bWFuIGNvbnN1bXB0aW9uLCB0byBi
ZSB1c2VkIHdoZW4gaW52ZXN0aWdhdGluZyBhIG5ldyBBTFRPIHNlcnZlci4NCj4NCj4gKiBVUkw6
IEFuIG9wdGlvbmFsIHVybCB3aXRoIGEgZGV0YWlsZWQgZGVzY3JpcHRpb24gb2YgdGhpcyBjb3N0
IHR5cGUuDQo+ICBGb3IgbW9yZSBpbnZvbHZlZCAiRGVzY3JpcHRpb25zIiwgb2YgY291cnNlLiBU
aGlzIGNhbiBiZSBpbg0KPiAgbXVsdGlwbGUgbGFuZ3VhZ2VzLCBvZiBjb3Vyc2UuDQo+DQo+IFll
cywgdGhlIGNoYW5nZSB3b3VsZCBiZSBwYWluZnVsLCBidXQgSSB0aGluayBpdCB3aWxsIHNpbXBs
aWZ5IHRoZQ0KPiBwcm90b2NvbCwgc2VydmVycyBhbmQgY2xpZW50cyAtLSBBTkQgaXQgd2lsbCBt
YWtlIGl0IGVhc2llciBmb3Igc2VydmVycyB0bw0KPiBhZGQgbmV3IGNvc3QgdHlwZXMuDQo+DQo+
IFRvIHNpbXBsaWZ5IGNsaWVudHMsIHdlIG1pZ2h0IHJlc2VydmUgYSBmZXcgdHlwZSBuYW1lcywg
c3VjaCBhcw0KPiAgIHJvdXRpbmdjb3N0LW51bWVyaWNhbA0KPiAgIHJvdXRpbmdjb3N0LW9yZGlu
YWwNCj4gICBob3Bjb3VudC1udW1lcmljYWwNCj4gICBob3Bjb3VudC1vcmRpbmFsDQo+IGFuZCBy
ZXF1aXJlIHRoZW0gdG8gaGF2ZSB0aGUgb2J2aW91cyBkZXNjcmlwdGlvbnMuDQo+DQo+ICAgICAg
IC0gV2VuZHkgUm9vbWUNCj4NCj4NCj4NCj4NCj4gT24gMDEvMjkvMjAxMyAxNTowMCwgImFsdG8t
cmVxdWVzdEBpZXRmLm9yZyIgPGFsdG8tcmVxdWVzdEBpZXRmLm9yZz4gd3JvdGU6DQo+DQo+PiBE
YXRlOiBNb24sIDI4IEphbiAyMDEzIDIzOjA4OjIzICswMDAwDQo+PiBGcm9tOiAiUmVpbmFsZG8g
UGVubm8gKHJlcGVubm8pIiA8cmVwZW5ub0BjaXNjby5jb20+DQo+PiBUbzogImFsdG9AaWV0Zi5v
cmciIDxhbHRvQGlldGYub3JnPg0KPj4gU3ViamVjdDogW2FsdG9dIEFMVE8gUHJvdG9jb2wgT3V0
c3RhbmRpbmcgSXNzdWUgSUk6IFVuaWZ5aW5nIGNvc3QtbW9kZQ0KPj4gICAgICBhbmQgY29zdC10
eXBlIHRvIGEgc2luZ2xlIHR5cGUNCj4+IE1lc3NhZ2UtSUQ6DQo+PiAgICAgIDw0NUE2OTdBOEZG
RDdDRjQ4QkNGMkJFN0UxMDZGMDYwNDA4RkY1MkVGQHhtYi1yY2QteDA0LmNpc2NvLmNvbT4NCj4+
IENvbnRlbnQtVHlwZTogdGV4dC9wbGFpbjsgY2hhcnNldD0idXMtYXNjaWkiDQo+Pg0KPj4gSGVs
bG8sDQo+Pg0KPj4gUGxlYXNlIHNlbmQgeW91ciBjb21tZW50cyB0byB0aGUgbGlzdCBpbiB0aGUg
bmV4dCAyIHdlZWtzLiBTaWxlbmNlIG1lYW5zDQo+PiB3ZSB3aWxsIGdvIHdpdGggdGhlIHByb3Bv
c2FsLg0KPj4NCj4+IERpc2N1c3Npb24gSUk6IFVuaWZ5aW5nIGNvc3QtbW9kZSBhbmQgY29zdC10
eXBlIHRvIGEgc2luZ2xlIHR5cGUNCj4+DQo+PiBlLmcuLCByb3V0aW5nY29zdC1udW0gYW5kIHJv
dXRpbmdjb3N0LW9yZA0KPj4NCj4+IEhhdmluZyBhIHNpbmdsZSB0eXBlIHNpbXBsZXMgdGhlIHBy
b3RvY29sIHNpbmNlIHRoZXJlIGlzIGp1c3Qgb25lDQo+PiBwYXJhbWV0ZXIgd2hlbiBpbmRpY2F0
aW5nIGNvc3QuIEJ1dCBpdCB3aWxsIGltcGFjdCBjdXJyZW50DQo+PiBpbXBsZW1lbnRhdGlvbnMg
YW5kIG1pZ2h0IGxvb3NlIGZsZXhpYmlsaXR5Lg0KPj4NCj4+IFByb3Bvc2FsOiBMZWF2ZSBpdCBh
cyBpcy4NCj4+DQo+PiBUaGFua3MsDQo+Pg0KPj4gUmVpbmFsZG8NCj4+DQo+DQo+DQo+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IGFsdG8gbWFpbGlu
ZyBsaXN0DQo+IGFsdG9AaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9hbHRvDQoNCg0KLS0NCiJFc3RhIHZleiBubyBmYWxsYXJlbW9zLCBEb2N0b3IgSW5m
aWVybm8iDQoNCkRyIERpZWdvIFIuIExvcGV6DQpUZWxlZm9uaWNhIEkrRA0KaHR0cDovL3Blb3Bs
ZS50aWQuZXMvZGllZ28ubG9wZXovDQoNCmUtbWFpbDogZGllZ29AdGlkLmVzDQpUZWw6ICAgICsz
NCA5MTMgMTI5IDA0MQ0KTW9iaWxlOiArMzQgNjgyIDA1MSAwOTENCi0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCg0KRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNpdmFtZW50ZSBhIHN1IGRlc3Rp
bmF0YXJpby4gUHVlZGUgY29uc3VsdGFyIG51ZXN0cmEgcG9sw610aWNhIGRlIGVudsOtbyB5IHJl
Y2VwY2nDs24gZGUgY29ycmVvIGVsZWN0csOzbmljbyBlbiBlbCBlbmxhY2Ugc2l0dWFkbyBtw6Fz
IGFiYWpvLg0KVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRk
cmVzc2VlLiBXZSBvbmx5IHNlbmQgYW5kIHJlY2VpdmUgZW1haWwgb24gdGhlIGJhc2lzIG9mIHRo
ZSB0ZXJtcyBzZXQgb3V0IGF0Og0KaHR0cDovL3d3dy50aWQuZXMvRVMvUEFHSU5BUy9kaXNjbGFp
bWVyLmFzcHgNCg==

From leeyoung@huawei.com  Tue Feb  5 14:17:27 2013
Return-Path: <leeyoung@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 DAC3121F847B for <alto@ietfa.amsl.com>; Tue,  5 Feb 2013 14:17:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6qtB+Uw-Czu3 for <alto@ietfa.amsl.com>; Tue,  5 Feb 2013 14:17:27 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 911BB21F846C for <alto@ietf.org>; Tue,  5 Feb 2013 14:17:26 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APL71865; Tue, 05 Feb 2013 22:17:25 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Feb 2013 22:16:27 +0000
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Feb 2013 22:17:25 +0000
Received: from dfweml511-mbs.china.huawei.com ([169.254.15.175]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.007; Tue, 5 Feb 2013 14:17:18 -0800
From: Leeyoung <leeyoung@huawei.com>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: charter extension to support i2aex proposal 
Thread-Index: Ac4D7o3Y7bYPZh0eQ9iDno+O6XmboA==
Date: Tue, 5 Feb 2013 22:17:17 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E17290FC244@dfweml511-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-hashedpuzzle: ACMP A+9z BqtJ CRv0 Cr7c DZBX Di1V FBLA FI7k GNqU Go/i HDFd Ij2r JCUG JIeT KHM1; 1; YQBsAHQAbwBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {893046D7-A32B-4AD7-9C11-64DFCE47F13E}; bABlAGUAeQBvAHUAbgBnAEAAaAB1AGEAdwBlAGkALgBjAG8AbQA=; Tue, 05 Feb 2013 22:17:15 GMT; YwBoAGEAcgB0AGUAcgAgAGUAeAB0AGUAbgBzAGkAbwBuACAAdABvACAAcwB1AHAAcABvAHIAdAAgAGkAMgBhAGUAeAAgAHAAcgBvAHAAbwBzAGEAbAA=
x-cr-puzzleid: {893046D7-A32B-4AD7-9C11-64DFCE47F13E}
x-originating-ip: [10.192.11.96]
Content-Type: multipart/alternative; boundary="_000_7AEB3D6833318045B4AE71C2C87E8E17290FC244dfweml511mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [alto] charter extension to support i2aex proposal
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 05 Feb 2013 22:17:28 -0000

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

Hello ALTO WG participants,

We have uploaded a couple of drafts.

http://datatracker.ietf.org/doc/draft-lee-alto-app-net-info-exchange/

http://datatracker.ietf.org/doc/draft-lee-alto-ext-dc-resource/

This is an follow-up effort to address the issues raised in the i2aex BOF. =
The first draft addresses the need to extend the current ALTO cost map to i=
nclude a graph type that depicts critical links and resource bottlenecks of=
 underlying network topology. The second draft addresses how to model data =
center resources using ALTO model. This draft addresses what abstraction is=
 needed in the context of data center selection problem.

In order to continue on with this work, we believe the current charter woul=
d need to be re-chartered in the spirit of i2aex.  It would be great to kno=
w if there is enough interest in this kind of work in ALTO WG.

Best Regards,
Young



--_000_7AEB3D6833318045B4AE71C2C87E8E17290FC244dfweml511mbschi_
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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Malgun Gothic";
	panose-1:2 11 5 3 2 0 0 2 0 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:85.05pt 1.0in 1.0in 1.0in;}
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"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hello ALTO WG participants,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We have uploaded a couple of drafts. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://datatracker.ietf.org/doc/draft-lee=
-alto-app-net-info-exchange/">http://datatracker.ietf.org/doc/draft-lee-alt=
o-app-net-info-exchange/</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://datatracker.ietf.org/doc/draft-lee=
-alto-ext-dc-resource/">http://datatracker.ietf.org/doc/draft-lee-alto-ext-=
dc-resource/</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is an follow-up effort to address the issues ra=
ised in the i2aex BOF. The first draft addresses the need to extend the cur=
rent ALTO cost map to include a graph type that depicts critical links and =
resource bottlenecks of underlying
 network topology. The second draft addresses how to model data center reso=
urces using ALTO model. This draft addresses what abstraction is needed in =
the context of data center selection problem.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In order to continue on with this work, we believe t=
he current charter would need to be re-chartered in the spirit of i2aex.&nb=
sp; It would be great to know if there is enough interest in this kind of w=
ork in ALTO WG.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Young<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7AEB3D6833318045B4AE71C2C87E8E17290FC244dfweml511mbschi_--

From Martin.Stiemerling@neclab.eu  Wed Feb  6 05:33:32 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
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 081A521F875F for <alto@ietfa.amsl.com>; Wed,  6 Feb 2013 05:33:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.465
X-Spam-Level: 
X-Spam-Status: No, score=-103.465 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TdfAKi2tqf1x for <alto@ietfa.amsl.com>; Wed,  6 Feb 2013 05:33:31 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4A421F85F3 for <alto@ietf.org>; Wed,  6 Feb 2013 05:33:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id BE64C1030D8; Wed,  6 Feb 2013 14:33:30 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mK-7uX4koNv8; Wed,  6 Feb 2013 14:33:30 +0100 (CET)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id A36641030D5; Wed,  6 Feb 2013 14:33:20 +0100 (CET)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 6 Feb 2013 14:33:20 +0100
Message-ID: <51125BA0.1010600@neclab.eu>
Date: Wed, 6 Feb 2013 14:33:20 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Leeyoung <leeyoung@huawei.com>, "alto@ietf.org" <alto@ietf.org>
References: <7AEB3D6833318045B4AE71C2C87E8E17290FC244@dfweml511-mbs.china.huawei.com>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E17290FC244@dfweml511-mbs.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Subject: Re: [alto] charter extension to support i2aex proposal
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Feb 2013 13:33:32 -0000

Hi all,

Just to make a point:

This WG is not allowed to discuss any re-chartering efforts until the 
ALTO protocol is in IESG evaluation.

There at least two outstanding questions on the ALTO protocol posted by 
Reinaldo that have not been addressed yet. And I do not have the feeling 
that there is sufficient energy in the group to answer the questions.

So, please get the ALTO protocol done and afterwards talk about any 
recharter.

Thanks,

   Martin

-- 
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe - Network Research Division NEC Europe Limited
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
Registered in England 283


On 02/05/2013 11:17 PM, Leeyoung wrote:
> Hello ALTO WG participants,
>
> We have uploaded a couple of drafts.
>
> http://datatracker.ietf.org/doc/draft-lee-alto-app-net-info-exchange/
>
> http://datatracker.ietf.org/doc/draft-lee-alto-ext-dc-resource/
>
> This is an follow-up effort to address the issues raised in the i2aex
> BOF. The first draft addresses the need to extend the current ALTO cost
> map to include a graph type that depicts critical links and resource
> bottlenecks of underlying network topology. The second draft addresses
> how to model data center resources using ALTO model. This draft
> addresses what abstraction is needed in the context of data center
> selection problem.
>
> In order to continue on with this work, we believe the current charter
> would need to be re-chartered in the spirit of i2aex.  It would be great
> to know if there is enough interest in this kind of work in ALTO WG.
>
> Best Regards,
>
> Young
>
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>


From leeyoung@huawei.com  Wed Feb  6 09:19:35 2013
Return-Path: <leeyoung@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 7CA3E21F8526 for <alto@ietfa.amsl.com>; Wed,  6 Feb 2013 09:19:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dKDrvjoEP14H for <alto@ietfa.amsl.com>; Wed,  6 Feb 2013 09:19:34 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6BBD621F861A for <alto@ietf.org>; Wed,  6 Feb 2013 09:19:23 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APM45640; Wed, 06 Feb 2013 17:19:22 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 6 Feb 2013 17:18:26 +0000
Received: from DFWEML408-HUB.china.huawei.com (10.193.5.134) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 6 Feb 2013 17:19:21 +0000
Received: from dfweml511-mbs.china.huawei.com ([169.254.15.175]) by dfweml408-hub.china.huawei.com ([10.193.5.134]) with mapi id 14.01.0323.007; Wed, 6 Feb 2013 09:19:18 -0800
From: Leeyoung <leeyoung@huawei.com>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] charter extension to support i2aex proposal
Thread-Index: AQHOBG6XMZB9+ODSOky6Yv8R/SkQnphtESJw
Date: Wed, 6 Feb 2013 17:19:17 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E17290FCA17@dfweml511-mbs.china.huawei.com>
References: <7AEB3D6833318045B4AE71C2C87E8E17290FC244@dfweml511-mbs.china.huawei.com> <51125BA0.1010600@neclab.eu>
In-Reply-To: <51125BA0.1010600@neclab.eu>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.96]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [alto] charter extension to support i2aex proposal
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Feb 2013 17:19:35 -0000

Martin,

Thanks for your feedback. When do you expect the ALTO protocol to move to t=
he IESG evaluation?

Regards,
Young
=20

-----Original Message-----
From: Martin Stiemerling [mailto:martin.stiemerling@neclab.eu]=20
Sent: Wednesday, February 06, 2013 7:33 AM
To: Leeyoung; alto@ietf.org
Subject: Re: [alto] charter extension to support i2aex proposal

Hi all,

Just to make a point:

This WG is not allowed to discuss any re-chartering efforts until the=20
ALTO protocol is in IESG evaluation.

There at least two outstanding questions on the ALTO protocol posted by=20
Reinaldo that have not been addressed yet. And I do not have the feeling=20
that there is sufficient energy in the group to answer the questions.

So, please get the ALTO protocol done and afterwards talk about any=20
recharter.

Thanks,

   Martin

--=20
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe - Network Research Division NEC Europe Limited
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
Registered in England 283


On 02/05/2013 11:17 PM, Leeyoung wrote:
> Hello ALTO WG participants,
>
> We have uploaded a couple of drafts.
>
> http://datatracker.ietf.org/doc/draft-lee-alto-app-net-info-exchange/
>
> http://datatracker.ietf.org/doc/draft-lee-alto-ext-dc-resource/
>
> This is an follow-up effort to address the issues raised in the i2aex
> BOF. The first draft addresses the need to extend the current ALTO cost
> map to include a graph type that depicts critical links and resource
> bottlenecks of underlying network topology. The second draft addresses
> how to model data center resources using ALTO model. This draft
> addresses what abstraction is needed in the context of data center
> selection problem.
>
> In order to continue on with this work, we believe the current charter
> would need to be re-chartered in the spirit of i2aex.  It would be great
> to know if there is enough interest in this kind of work in ALTO WG.
>
> Best Regards,
>
> Young
>
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>


From vkg@bell-labs.com  Wed Feb  6 11:09:21 2013
Return-Path: <vkg@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 EF75B21F89A3 for <alto@ietfa.amsl.com>; Wed,  6 Feb 2013 11:09:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EO5AJOp4zQl1 for <alto@ietfa.amsl.com>; Wed,  6 Feb 2013 11:09:20 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 2A2E621F8994 for <alto@ietf.org>; Wed,  6 Feb 2013 11:09:20 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r16J95IS026395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Wed, 6 Feb 2013 13:09:05 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r16J95aI002919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Wed, 6 Feb 2013 13:09:05 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r16J94bm024467 for <alto@ietf.org>; Wed, 6 Feb 2013 13:09:04 -0600 (CST)
Message-ID: <5112AA50.5010908@bell-labs.com>
Date: Wed, 06 Feb 2013 13:09:04 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: alto@ietf.org
References: <7AEB3D6833318045B4AE71C2C87E8E17290FC244@dfweml511-mbs.china.huawei.com> <51125BA0.1010600@neclab.eu> <7AEB3D6833318045B4AE71C2C87E8E17290FCA17@dfweml511-mbs.china.huawei.com>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E17290FCA17@dfweml511-mbs.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [alto] charter extension to support i2aex proposal
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 06 Feb 2013 19:09:21 -0000

On 02/06/2013 11:19 AM, Leeyoung wrote:
> Martin,
>
> Thanks for your feedback. When do you expect the ALTO protocol to
> move to the IESG evaluation?

Young: That depends on the WG as a whole.  We need to band together
and finish the open issues Reinaldo and Richard have posted on the list.

The sooner we get done, the better it would be to chart out next
steps.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From Martin.Stiemerling@neclab.eu  Thu Feb  7 03:19:20 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
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 D766421F863A for <alto@ietfa.amsl.com>; Thu,  7 Feb 2013 03:19:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.474
X-Spam-Level: 
X-Spam-Status: No, score=-103.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2tPNMXCu4K+z for <alto@ietfa.amsl.com>; Thu,  7 Feb 2013 03:19:20 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 37C1821F8635 for <alto@ietf.org>; Thu,  7 Feb 2013 03:19:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 919AC1030F0; Thu,  7 Feb 2013 12:19:19 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aoGy2TLGHjuK; Thu,  7 Feb 2013 12:19:19 +0100 (CET)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 785E31030ED; Thu,  7 Feb 2013 12:19:09 +0100 (CET)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 7 Feb 2013 12:18:48 +0100
Message-ID: <51138D98.9070802@neclab.eu>
Date: Thu, 7 Feb 2013 12:18:48 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Leeyoung <leeyoung@huawei.com>
References: <7AEB3D6833318045B4AE71C2C87E8E17290FC244@dfweml511-mbs.china.huawei.com> <51125BA0.1010600@neclab.eu> <7AEB3D6833318045B4AE71C2C87E8E17290FCA17@dfweml511-mbs.china.huawei.com>
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E17290FCA17@dfweml511-mbs.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] charter extension to support i2aex proposal
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 07 Feb 2013 11:19:21 -0000

Young,

On 02/06/2013 06:19 PM, Leeyoung wrote:
> Martin,
>
> Thanks for your feedback. When do you expect the ALTO protocol to
> move to the IESG evaluation?

As Vijay pointed out:
It primarily depends on the WG and the draft authors.

Once the draft has addressed all outstanding issues out of the AD 
review, it will go for IETF LC (which is 2 weeks) and enter the IESG 
evaluation afterwards.

   Martin

>
> Regards, Young
>
>
> -----Original Message----- From: Martin Stiemerling
> [mailto:martin.stiemerling@neclab.eu] Sent: Wednesday, February 06,
> 2013 7:33 AM To: Leeyoung; alto@ietf.org Subject: Re: [alto] charter
> extension to support i2aex proposal
>
> Hi all,
>
> Just to make a point:
>
> This WG is not allowed to discuss any re-chartering efforts until
> the ALTO protocol is in IESG evaluation.
>
> There at least two outstanding questions on the ALTO protocol posted
> by Reinaldo that have not been addressed yet. And I do not have the
> feeling that there is sufficient energy in the group to answer the
> questions.
>
> So, please get the ALTO protocol done and afterwards talk about any
> recharter.
>
> Thanks,
>
> Martin
>

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe - Network Research Division NEC Europe Limited
Registered Office: NEC House, 1 Victoria Road, London W3 6BL
Registered in England 283

From sabine.randriamasy@alcatel-lucent.com  Thu Feb  7 09:32:43 2013
Return-Path: <sabine.randriamasy@alcatel-lucent.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 EA99C21F8596 for <alto@ietfa.amsl.com>; Thu,  7 Feb 2013 09:32:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FjGzMqbc0qlD for <alto@ietfa.amsl.com>; Thu,  7 Feb 2013 09:32:43 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id A1F6321F854E for <alto@ietf.org>; Thu,  7 Feb 2013 09:32:42 -0800 (PST)
Received: from FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (FRMRSSXCHHUB04.dc-m.alcatel-lucent.com [135.120.45.64]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r17HW8At025565 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 7 Feb 2013 18:32:40 +0100
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) by FRMRSSXCHHUB04.dc-m.alcatel-lucent.com (135.120.45.64) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 7 Feb 2013 18:32:20 +0100
Received: from [172.27.204.27] (135.239.27.11) by FR712WXCHHUB03.zeu.alcatel-lucent.com (135.239.2.74) with Microsoft SMTP Server (TLS) id 14.2.247.3; Thu, 7 Feb 2013 18:32:19 +0100
Message-ID: <5113E51D.6020408@alcatel-lucent.com>
Date: Thu, 7 Feb 2013 18:32:13 +0100
From: Sabine Randriamasy <Sabine.Randriamasy@alcatel-lucent.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: "Diego R. Lopez" <diego@tid.es>
References: <CD2ED65D.2CC8B%w.roome@alcatel-lucent.com> <E6D8B95470ED0845B3376F61DCAB1A0468D53592@EX10-MB2-MAD.hi.inet>
In-Reply-To: <E6D8B95470ED0845B3376F61DCAB1A0468D53592@EX10-MB2-MAD.hi.inet>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [135.239.27.11]
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Cc: Wendy Roome <w.roome@alcatel-lucent.com>, "<alto@ietf.org>" <alto@ietf.org>
Subject: Re: [alto] Unifying cost-mode and cost-type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 07 Feb 2013 17:32:44 -0000

Hello,

I'd also go for unifying cost-type and cost-mode in one type name. One 
of the reasons is that it would spare the time of parsing ALTO requests 
and responses to detect incompatible cost types and modes or mismatched 
cost types and cost mode lists.
We need these explicit description attributes indicating how to use the 
values and value types covering all the JSON types.
The important thing is to keep the possiblity to extend the cost types 
and cost modes.

Cheers
Sabine

Diego R. Lopez a écrit :
> Hi,
>
> I think your proposal on adding this metadata on what an ALTO server provides makes a lot of sense, especially if we think about the additional usages of ALTO that were originally discussed in the i2rs BoF in Paris, and that I'd say have raised so much expectation among the SDN community, among others.
>
> Therefore, I'd like very much to see this discussion happening within the ALTO group, mostly once we have been able to complete the current set of documents and we are in the position of re-chartering the group along the lines discussed in the Paris BoF.
>
> Be goode,
>
> On 30 Jan 2013, at 20:12 , Wendy Roome wrote:
>
>   
>> I realize it's late to make changes, but I really think unifying type &
>> mode makes a lot of sense.  Here's my suggestion: extend the "resource
>> directory" to include a generalized description of the cost-types that the
>> server provides.  I won't suggest a syntax -- too early for that!! -- but
>> here's what the description should provide for each distinct type:
>>
>> * The type name.  This is what clients give in the cost-type parameter.
>>
>> * The value type.  "numerical" & "string" are obvious possibilities.
>>
>> * Linear: a boolean flag. True means this numeric value is linear.
>>  False means values are not linear. This takes the place of
>>  the ordinal/numerical mode.
>>
>> * Category: What this cost measures: "delay", "hops", "cost", "other".
>>  Here "cost" means money.
>>
>> * Description: An optional free-form description of this cost type.
>>  For human consumption, to be used when investigating a new ALTO server.
>>
>> * URL: An optional url with a detailed description of this cost type.
>>  For more involved "Descriptions", of course. This can be in
>>  multiple languages, of course.
>>
>> Yes, the change would be painful, but I think it will simplify the
>> protocol, servers and clients -- AND it will make it easier for servers to
>> add new cost types.
>>
>> To simplify clients, we might reserve a few type names, such as
>>   routingcost-numerical
>>   routingcost-ordinal
>>   hopcount-numerical
>>   hopcount-ordinal
>> and require them to have the obvious descriptions.
>>
>>       - Wendy Roome
>>
>>
>>
>>
>> On 01/29/2013 15:00, "alto-request@ietf.org" <alto-request@ietf.org> wrote:
>>
>>     
>>> Date: Mon, 28 Jan 2013 23:08:23 +0000
>>> From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
>>> To: "alto@ietf.org" <alto@ietf.org>
>>> Subject: [alto] ALTO Protocol Outstanding Issue II: Unifying cost-mode
>>>      and cost-type to a single type
>>> Message-ID:
>>>      <45A697A8FFD7CF48BCF2BE7E106F060408FF52EF@xmb-rcd-x04.cisco.com>
>>> Content-Type: text/plain; charset="us-ascii"
>>>
>>> Hello,
>>>
>>> Please send your comments to the list in the next 2 weeks. Silence means
>>> we will go with the proposal.
>>>
>>> Discussion II: Unifying cost-mode and cost-type to a single type
>>>
>>> e.g., routingcost-num and routingcost-ord
>>>
>>> Having a single type simples the protocol since there is just one
>>> parameter when indicating cost. But it will impact current
>>> implementations and might loose flexibility.
>>>
>>> Proposal: Leave it as is.
>>>
>>> Thanks,
>>>
>>> Reinaldo
>>>
>>>       
>> _______________________________________________
>> alto mailing list
>> alto@ietf.org
>> https://www.ietf.org/mailman/listinfo/alto
>>     
>
>
> --
> "Esta vez no fallaremos, Doctor Infierno"
>
> Dr Diego R. Lopez
> Telefonica I+D
> http://people.tid.es/diego.lopez/
>
> e-mail: diego@tid.es
> Tel:    +34 913 129 041
> Mobile: +34 682 051 091
> -----------------------------------------
>
>
> ________________________________
>
> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
> This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>   


From sebi@gw01.ehlo.wurstkaes.de  Mon Feb 11 06:54:09 2013
Return-Path: <sebi@gw01.ehlo.wurstkaes.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 7BC6E21F8984 for <alto@ietfa.amsl.com>; Mon, 11 Feb 2013 06:54:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UyOp9M1eW121 for <alto@ietfa.amsl.com>; Mon, 11 Feb 2013 06:54:08 -0800 (PST)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id 720D121F8950 for <alto@ietf.org>; Mon, 11 Feb 2013 06:54:07 -0800 (PST)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1U4ulg-0004Y2-5x for alto@ietf.org; Mon, 11 Feb 2013 15:54:04 +0100
Date: Mon, 11 Feb 2013 15:54:04 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: alto@ietf.org
Message-ID: <20130211145404.GY25725@gw01.ehlo.wurstkaes.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [alto] fwd: I-D Action: draft-kist-alto-3pdisc-02.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 11 Feb 2013 14:54:09 -0000

Dear ALTO WG members,

this is a significant change to the ALTO third-party discovery
algorithm, so please read.  As always, feedback is very welcome.

Thanks
Sebastian

----- Forwarded message from internet-drafts@ietf.org -----

Date: Mon, 11 Feb 2013 06:51:16 -0800
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-kist-alto-3pdisc-02.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title           : Third-Party ALTO Server Discovery (3pdisc)
	Author(s)       : Sebastian Kiesel
                          Kilian Krause
                          Martin Stiemerling
	Filename        : draft-kist-alto-3pdisc-02.txt
	Pages           : 14
	Date            : 2013-02-11

Abstract:
   The goal of Application-Layer Traffic Optimization (ALTO) is to
   provide guidance to applications that have to select one or several
   hosts from a set of candidates capable of providing a desired
   resource.  ALTO is realized by a client-server protocol.  Before an
   ALTO client can ask for guidance it needs to discover one or more
   ALTO servers that can provide suitable guidance.

   This document specifies a procedure for third-party ALTO server
   discovery, which can be used if the ALTO client is not co-located
   with the actual resource consumer, but instead embedded in a third
   party such as a peer-to-peer tracker.

   This algorithm takes a resource consumer's IP address as argument,
   performs several DNS lookups (for PTR, SOA, and U-NAPTR resource
   records), and produces URIs of ALTO servers that are able to give
   reasonable ALTO guidance to a resource consumer willing to
   communicate using this IP address.

   Starting with draft-kist-alto-3pdisc-02 the algorithm has
   significantly changed compared to previous versions of this document,
   including draft-kiesel-alto-3pdisc-* and
   draft-ietf-alto-server-discovery-*.  The new algorithm does not try
   "DNS tree climbing" and it does not neccessarily rely on PTR records,
   i.e., it can also produce results if no PTR records are populated in
   the DNS, for example when IPv6 privacy exensions are in use.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-kist-alto-3pdisc

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-kist-alto-3pdisc-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-kist-alto-3pdisc-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

----- End forwarded message -----

From w.roome@alcatel-lucent.com  Mon Feb 11 08:53:20 2013
Return-Path: <w.roome@alcatel-lucent.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 DE50521F87CD for <alto@ietfa.amsl.com>; Mon, 11 Feb 2013 08:53:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EMwDckhYYlh0 for <alto@ietfa.amsl.com>; Mon, 11 Feb 2013 08:53:10 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id E6E6821F8836 for <alto@ietf.org>; Mon, 11 Feb 2013 08:53:05 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r1BGr4nO002126 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Mon, 11 Feb 2013 10:53:05 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1BGr43T005693 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Mon, 11 Feb 2013 10:53:04 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1BGr2d0009841 for <alto@ietf.org>; Mon, 11 Feb 2013 10:53:03 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.0.121105
Date: Mon, 11 Feb 2013 11:53:03 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: <alto@ietf.org>
Message-ID: <CD3E8C1F.31AE6%w.roome@alcatel-lucent.com>
Thread-Topic: Should we allow relative URIs in resource directories?
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: [alto] Should we allow relative URIs in resource directories?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 11 Feb 2013 16:53:20 -0000

In general URIs can be relative as well as absolute. So if an ALTO
server's resource directory has the URI
"http://alto.example.com/directory", directory entries like
  { "uri" : "/networkmap", ....}
or
  { "uri" : "costmap/num/routingcost", ...}
should be legal and should resolve to "http://alto.example.com/networkmap"
and "http://alto.example.com/costmap/num/routingcost", respectively.

However, our examples only use absolute URIs. As far as I can tell, draft
13 doesn't say anything about relative URIs.

So I think we should either explicitly allow relative URIs -- and use them
in examples in the RFC and in the next interop -- or else forbid them.
That would affect Sections 6.7.2 & 6.7.3.

Comments?
	
 - Wendy Roome



From ben@niven-jenkins.co.uk  Tue Feb 12 06:33:25 2013
Return-Path: <ben@niven-jenkins.co.uk>
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 5810021F8DB2 for <alto@ietfa.amsl.com>; Tue, 12 Feb 2013 06:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CDdotiXspYxW for <alto@ietfa.amsl.com>; Tue, 12 Feb 2013 06:33:24 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5DCD821F8DAE for <alto@ietf.org>; Tue, 12 Feb 2013 06:33:24 -0800 (PST)
Received: from [77.241.234.205] (helo=[192.168.250.5]) by mail4.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1U5Gv3-0007Of-Ko; Tue, 12 Feb 2013 14:33:22 +0000
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <CD3E8C1F.31AE6%w.roome@alcatel-lucent.com>
Date: Tue, 12 Feb 2013 14:33:10 +0000
Content-Transfer-Encoding: 7bit
Message-Id: <0D1494C5-2154-43E0-886B-29DF8402B1D8@niven-jenkins.co.uk>
References: <CD3E8C1F.31AE6%w.roome@alcatel-lucent.com>
To: Wendy Roome <w.roome@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: alto@ietf.org
Subject: Re: [alto] Should we allow relative URIs in resource directories?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 12 Feb 2013 14:33:25 -0000

Wendy,

I see no reason to restrict to absolute URIs.

Currently section 6.7.2 of the ALTO protocol spec states:

   uri  A URI at which the ALTO Server provides one or more Information
      Resources, or an Information Resource Directory indicating
      additional Information Resources.

Would adding a reference to section 4.1 of RFC3986 be sufficient, e.g.

   uri  A URI reference (as per section 4.1 of [RFC3986] to one or more
      Information Resources, or an Information Resource Directory
      indicating additional Information Resources.


Ben

On 11 Feb 2013, at 16:53, Wendy Roome wrote:

> In general URIs can be relative as well as absolute. So if an ALTO
> server's resource directory has the URI
> "http://alto.example.com/directory", directory entries like
>  { "uri" : "/networkmap", ....}
> or
>  { "uri" : "costmap/num/routingcost", ...}
> should be legal and should resolve to "http://alto.example.com/networkmap"
> and "http://alto.example.com/costmap/num/routingcost", respectively.
> 
> However, our examples only use absolute URIs. As far as I can tell, draft
> 13 doesn't say anything about relative URIs.
> 
> So I think we should either explicitly allow relative URIs -- and use them
> in examples in the RFC and in the next interop -- or else forbid them.
> That would affect Sections 6.7.2 & 6.7.3.
> 
> Comments?
> 	
> - Wendy Roome
> 
> 
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From diego@tid.es  Tue Feb 12 07:44:51 2013
Return-Path: <diego@tid.es>
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 4F29F21F8D96 for <alto@ietfa.amsl.com>; Tue, 12 Feb 2013 07:44:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.168
X-Spam-Level: 
X-Spam-Status: No, score=-5.168 tagged_above=-999 required=5 tests=[AWL=-0.428, BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id il7kTsL4j4Rh for <alto@ietfa.amsl.com>; Tue, 12 Feb 2013 07:44:50 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 17B9421F8D8F for <alto@ietf.org>; Tue, 12 Feb 2013 07:44:50 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MI400EKQ6EO92@tid.hi.inet> for alto@ietf.org; Tue, 12 Feb 2013 16:44:48 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 00.35.02896.0736A115; Tue, 12 Feb 2013 16:44:48 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MI400EKL6EO92@tid.hi.inet> for alto@ietf.org; Tue, 12 Feb 2013 16:44:48 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by EX10-HTCAS6-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Tue, 12 Feb 2013 16:44:48 +0100
Date: Tue, 12 Feb 2013 15:44:48 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <0D1494C5-2154-43E0-886B-29DF8402B1D8@niven-jenkins.co.uk>
X-Originating-IP: [10.95.64.115]
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A0468D65E70@EX10-MB2-MAD.hi.inet>
Content-id: <F6277D9CC3E99247950F88C8E19ACEF0@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, es-ES
Thread-topic: [alto] Should we allow relative URIs in resource directories?
Thread-index: AQHOCHj/QcWtKg/in0idBm7aBT9bw5h2Og0AgAAUAoA=
X-AuditID: 0a5f4e69-b7f636d000000b50-fa-511a63704ebb
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42Lhivcz1C1Ilgo0OLbe0OLh9r2sDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKuLBxBWNBg2zFnfMTWBoYF8h0MXJySAiYSLQ+bmKDsMUkLtxb D2RzcQgJbGOU2Hb2ESOE851R4smjT6wQzkxGiT3HuhlBWlgEVCXOLjrJAmKzAdmPmn+zg9jC Al4S0w8uBLM5Bdwlbq+bDLVCQeLPucdA9RwcIgL6Eh3HikHCzAL+Ep9OTGUECfMKeEucmqUM ETaT2LVwFxOIzSsgKPFj8j2wTmYBdYkpU3IhSsQlmltvskDYihLTFjWAHcYoICvxbv58VhBb BGji8z0b2SFsK4mHtyayQBwjILFkz3lmCFtU4uXjf2D1QgIlEtcbbjJPYJSYheSKWUiumIVw xSwkV8xCcsUCRtZVjGLFSUWZ6RkluYmZOekGRnoZmXqZeaklmxghEZe5g3H5TpVDjAIcjEo8 vBE3RAKFWBPLiitzDzFKcDArifAeMpEKFOJNSaysSi3Kjy8qzUktPsTIxMEp1cB48Gnv3C8u 0S+2bwv0FT2sviT43KnUD9q+7x5oOEpOeSK+4JhC2s0DC6sWFe5uq9945kJs8cPNC+Ia297l +yqzixtPNf48dXm0KMP5f3IzapZmvTZfZTZxV6uY/7aMXTdy1cX0/Y4aRrv9FhJOvZTJ3btv J9/ETNluQa7M7vBXBhUWWzh695UosRRnJBpqMRcVJwIAXqt2QZYCAAA=
References: <CD3E8C1F.31AE6%w.roome@alcatel-lucent.com> <0D1494C5-2154-43E0-886B-29DF8402B1D8@niven-jenkins.co.uk>
Cc: Wendy Roome <w.roome@alcatel-lucent.com>, "<alto@ietf.org>" <alto@ietf.org>
Subject: Re: [alto] Should we allow relative URIs in resource directories?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 12 Feb 2013 15:44:51 -0000

SGksDQoNCkkgdGhpbmsgYWxsb3dpbmcgb25seSBhYnNvbHV0ZSBVUklzIHdvdWxkIHRyYW5zbGF0
ZSBpbnRvIHNpbXBsZXIgbWVjaGFuaXNtcyB0byBidWlsZCB0aGVtLCBhbmQgYmV0dGVyIHVuZGVy
c3RhbmRpbmcgYnkgaHVtYW4gcmVhZGVycyB0cnlpbmcgdG8gZGVidWcgYmFzZWQgb24gQUxUTyBv
dXRwdXRzLCBidXQgSSBhY2tub3dsZWRnZSB0aGVzZSBhcmUgbGltaXRlZCBhZHZhbnRhZ2VzIGlm
IHRoZXJlIGFyZSBhbnkgb3RoZXIgcmVhc29ucyBmb3IgYWxsb3dpbmcgcmVsYXRpdmUgVVJJcy4N
Cg0KQmUgZ29vZGUsDQoNCk9uIDEyIEZlYiAyMDEzLCBhdCAxNTozMyAsIEJlbiBOaXZlbi1KZW5r
aW5zIHdyb3RlOg0KDQo+IFdlbmR5LA0KPg0KPiBJIHNlZSBubyByZWFzb24gdG8gcmVzdHJpY3Qg
dG8gYWJzb2x1dGUgVVJJcy4NCj4NCj4gQ3VycmVudGx5IHNlY3Rpb24gNi43LjIgb2YgdGhlIEFM
VE8gcHJvdG9jb2wgc3BlYyBzdGF0ZXM6DQo+DQo+ICAgdXJpICBBIFVSSSBhdCB3aGljaCB0aGUg
QUxUTyBTZXJ2ZXIgcHJvdmlkZXMgb25lIG9yIG1vcmUgSW5mb3JtYXRpb24NCj4gICAgICBSZXNv
dXJjZXMsIG9yIGFuIEluZm9ybWF0aW9uIFJlc291cmNlIERpcmVjdG9yeSBpbmRpY2F0aW5nDQo+
ICAgICAgYWRkaXRpb25hbCBJbmZvcm1hdGlvbiBSZXNvdXJjZXMuDQo+DQo+IFdvdWxkIGFkZGlu
ZyBhIHJlZmVyZW5jZSB0byBzZWN0aW9uIDQuMSBvZiBSRkMzOTg2IGJlIHN1ZmZpY2llbnQsIGUu
Zy4NCj4NCj4gICB1cmkgIEEgVVJJIHJlZmVyZW5jZSAoYXMgcGVyIHNlY3Rpb24gNC4xIG9mIFtS
RkMzOTg2XSB0byBvbmUgb3IgbW9yZQ0KPiAgICAgIEluZm9ybWF0aW9uIFJlc291cmNlcywgb3Ig
YW4gSW5mb3JtYXRpb24gUmVzb3VyY2UgRGlyZWN0b3J5DQo+ICAgICAgaW5kaWNhdGluZyBhZGRp
dGlvbmFsIEluZm9ybWF0aW9uIFJlc291cmNlcy4NCj4NCj4NCj4gQmVuDQo+DQo+IE9uIDExIEZl
YiAyMDEzLCBhdCAxNjo1MywgV2VuZHkgUm9vbWUgd3JvdGU6DQo+DQo+PiBJbiBnZW5lcmFsIFVS
SXMgY2FuIGJlIHJlbGF0aXZlIGFzIHdlbGwgYXMgYWJzb2x1dGUuIFNvIGlmIGFuIEFMVE8NCj4+
IHNlcnZlcidzIHJlc291cmNlIGRpcmVjdG9yeSBoYXMgdGhlIFVSSQ0KPj4gImh0dHA6Ly9hbHRv
LmV4YW1wbGUuY29tL2RpcmVjdG9yeSIsIGRpcmVjdG9yeSBlbnRyaWVzIGxpa2UNCj4+IHsgInVy
aSIgOiAiL25ldHdvcmttYXAiLCAuLi4ufQ0KPj4gb3INCj4+IHsgInVyaSIgOiAiY29zdG1hcC9u
dW0vcm91dGluZ2Nvc3QiLCAuLi59DQo+PiBzaG91bGQgYmUgbGVnYWwgYW5kIHNob3VsZCByZXNv
bHZlIHRvICJodHRwOi8vYWx0by5leGFtcGxlLmNvbS9uZXR3b3JrbWFwIg0KPj4gYW5kICJodHRw
Oi8vYWx0by5leGFtcGxlLmNvbS9jb3N0bWFwL251bS9yb3V0aW5nY29zdCIsIHJlc3BlY3RpdmVs
eS4NCj4+DQo+PiBIb3dldmVyLCBvdXIgZXhhbXBsZXMgb25seSB1c2UgYWJzb2x1dGUgVVJJcy4g
QXMgZmFyIGFzIEkgY2FuIHRlbGwsIGRyYWZ0DQo+PiAxMyBkb2Vzbid0IHNheSBhbnl0aGluZyBh
Ym91dCByZWxhdGl2ZSBVUklzLg0KPj4NCj4+IFNvIEkgdGhpbmsgd2Ugc2hvdWxkIGVpdGhlciBl
eHBsaWNpdGx5IGFsbG93IHJlbGF0aXZlIFVSSXMgLS0gYW5kIHVzZSB0aGVtDQo+PiBpbiBleGFt
cGxlcyBpbiB0aGUgUkZDIGFuZCBpbiB0aGUgbmV4dCBpbnRlcm9wIC0tIG9yIGVsc2UgZm9yYmlk
IHRoZW0uDQo+PiBUaGF0IHdvdWxkIGFmZmVjdCBTZWN0aW9ucyA2LjcuMiAmIDYuNy4zLg0KPj4N
Cj4+IENvbW1lbnRzPw0KPj4NCj4+IC0gV2VuZHkgUm9vbWUNCj4+DQo+Pg0KPj4gX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+IGFsdG8gbWFpbGluZyBs
aXN0DQo+PiBhbHRvQGlldGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2FsdG8NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4gYWx0byBtYWlsaW5nIGxpc3QNCj4gYWx0b0BpZXRmLm9yZw0KPiBodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FsdG8NCg0KDQotLQ0KIkVzdGEgdmV6IG5v
IGZhbGxhcmVtb3MsIERvY3RvciBJbmZpZXJubyINCg0KRHIgRGllZ28gUi4gTG9wZXoNClRlbGVm
b25pY2EgSStEDQpodHRwOi8vcGVvcGxlLnRpZC5lcy9kaWVnby5sb3Blei8NCg0KZS1tYWlsOiBk
aWVnb0B0aWQuZXMNClRlbDogICAgKzM0IDkxMyAxMjkgMDQxDQpNb2JpbGU6ICszNCA2ODIgMDUx
IDA5MQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KDQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpFc3RlIG1lbnNhamUgc2UgZGlyaWdlIGV4
Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRhcmlvLiBQdWVkZSBjb25zdWx0YXIgbnVlc3RyYSBw
b2zDrXRpY2EgZGUgZW52w61vIHkgcmVjZXBjacOzbiBkZSBjb3JyZW8gZWxlY3Ryw7NuaWNvIGVu
IGVsIGVubGFjZSBzaXR1YWRvIG3DoXMgYWJham8uDQpUaGlzIG1lc3NhZ2UgaXMgaW50ZW5kZWQg
ZXhjbHVzaXZlbHkgZm9yIGl0cyBhZGRyZXNzZWUuIFdlIG9ubHkgc2VuZCBhbmQgcmVjZWl2ZSBl
bWFpbCBvbiB0aGUgYmFzaXMgb2YgdGhlIHRlcm1zIHNldCBvdXQgYXQ6DQpodHRwOi8vd3d3LnRp
ZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIuYXNweA0K

From sebi@gw01.ehlo.wurstkaes.de  Tue Feb 12 10:59:27 2013
Return-Path: <sebi@gw01.ehlo.wurstkaes.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 D1D1721F90CE for <alto@ietfa.amsl.com>; Tue, 12 Feb 2013 10:59:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U19JO6YOVTPB for <alto@ietfa.amsl.com>; Tue, 12 Feb 2013 10:59:27 -0800 (PST)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id 56D9721F90CD for <alto@ietf.org>; Tue, 12 Feb 2013 10:59:25 -0800 (PST)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1U5L4c-0004az-G3 for alto@ietf.org; Tue, 12 Feb 2013 19:59:22 +0100
Date: Tue, 12 Feb 2013 19:59:22 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: alto@ietf.org
Message-ID: <20130212185922.GA14781@gw01.ehlo.wurstkaes.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: [alto] fwd: I-D Action: draft-kiesel-alto-3pdisc-impl-00.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 12 Feb 2013 18:59:28 -0000

Dear ALTO WG members,

There is running code!  The primary goal is showing the feasibility of
implementing the 3pdisc algorithm, but the draft also illustrates the
NAPTR lookups used in draft-ietf-alto-server-discovery.

  -- Sebastian

----- Forwarded message from internet-drafts@ietf.org -----

Date: Tue, 12 Feb 2013 10:30:43 -0800
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-kiesel-alto-3pdisc-impl-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title           : Third-Party ALTO Server Discovery Prototype Implementation and Testbed
	Author(s)       : Sebastian Kiesel
	Filename        : draft-kiesel-alto-3pdisc-impl-00.txt
	Pages           : 14
	Date            : 2013-02-12

Abstract:
   This document contains a prototype implementation for the third-party
   ALTO server discovery (3pdisc) procedure specified in
   draft-kist-alto-3pdisc-02.txt [I-D.kist-alto-3pdisc].  The prototype
   implementation has been written in Perl and tested with the GNU/Linux
   operating system.

   A set of BIND 9 configuration files and DNS zone files is also
   included.  They can be used for setting up a small, self-contained
   testbed.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-kiesel-alto-3pdisc-impl

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-kiesel-alto-3pdisc-impl-00


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

----- End forwarded message -----

From Martin.Stiemerling@neclab.eu  Wed Feb 13 02:37:27 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
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 6531421F8821 for <alto@ietfa.amsl.com>; Wed, 13 Feb 2013 02:37:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.487
X-Spam-Level: 
X-Spam-Status: No, score=-103.487 tagged_above=-999 required=5 tests=[AWL=0.112, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id paJj6sZ1vkcb for <alto@ietfa.amsl.com>; Wed, 13 Feb 2013 02:37:27 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id CD72C21F87A4 for <alto@ietf.org>; Wed, 13 Feb 2013 02:37:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 3E1591031E5; Wed, 13 Feb 2013 11:37:26 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HaoXORIZSmr3; Wed, 13 Feb 2013 11:37:26 +0100 (CET)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id 2302D1031E4; Wed, 13 Feb 2013 11:37:16 +0100 (CET)
Received: from [10.1.99.64] (10.1.99.64) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 13 Feb 2013 11:36:35 +0100
Message-ID: <511B6CC6.7040406@neclab.eu>
Date: Wed, 13 Feb 2013 11:36:54 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
References: <5109510F.9060800@bell-labs.com>
In-Reply-To: <5109510F.9060800@bell-labs.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.99.64]
Cc: alto <alto@ietf.org>
Subject: Re: [alto] server-discovery-07: IPR and 2nd WGLC
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 13 Feb 2013 10:37:27 -0000

[writing as an individual]

Here is my take on this:
I cannot read the IPR itself, as I don't speak Chinese.
But given the licensing terms, I am Ok with progressing the draft as it is.

Thanks,

   Martin

On 01/30/2013 05:57 PM, Vijay K. Gurbani wrote:
> As co-chair ...
>
> Folks: An IPR notice [1] has been filed against
> draft-ietf-alto-server-discovery-07.
>
> Enrico and I would like to open up the draft for a second WGLC to allow
> the WG to raise any issues with respect to this IPR.
>
> The second WGLC will run from Wed, Jan 30 2013 to Wed, February 13,
> 2013.
>
> If you have any concerns with respect to the IPR, please raise them on
> the list.
>
> [1] http://www.ietf.org/mail-archive/web/alto/current/msg01664.html
>
> Thank you,
>
> - vijay

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From w.roome@alcatel-lucent.com  Wed Feb 13 06:38:55 2013
Return-Path: <w.roome@alcatel-lucent.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 9ACED21F8790 for <alto@ietfa.amsl.com>; Wed, 13 Feb 2013 06:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jr6jMbeuTZF0 for <alto@ietfa.amsl.com>; Wed, 13 Feb 2013 06:38:55 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE2A21F870E for <alto@ietf.org>; Wed, 13 Feb 2013 06:38:54 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r1DEcsxT007267 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Wed, 13 Feb 2013 08:38:54 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1DEcrKv022868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Wed, 13 Feb 2013 08:38:54 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1DEcqwe029404 for <alto@ietf.org>; Wed, 13 Feb 2013 08:38:53 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.0.121105
Date: Wed, 13 Feb 2013 09:38:52 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: <alto@ietf.org>
Message-ID: <CD410929.32200%w.roome@alcatel-lucent.com>
Thread-Topic: [alto] Should we allow relative URIs in resource directories?
In-Reply-To: <mailman.100.1360699231.7699.alto@ietf.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [alto] Should we allow relative URIs in resource directories?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 13 Feb 2013 14:38:55 -0000

RFC 3986 does define relative URIs, so technically that's sufficient. But
I think that's like a lawyer burying some critical information -- like
"double every amount that you owe us" -- in tiny type in a footnote.
Legal, but sleazy.

The problem is that software libraries with a simple connectToServer(uri)
function require an absolute uri. If the uri might be relative, the client
must first resolve the uri in the context of some absolute base uri. Most
libraries provide a function to do that, but it's easy to forget that step.

Case in point: My client, which passed all the interop tests, failed when
it contacted a server that returned relative URIs. (And yes, I've since
fixed my client.)

So if we want to allow relative URIs, we should be more explicit. At the
very least, add this sentence to the end of Ben's revised uri section:

    Relative URIs should be resolved using the URI of the Information
Resource Directory as the base URI.

Even better, use some relative URIs in the example.

On the other hand, if we want to forbid relative uris, we should instead
add:

    The URI must be absolute, not relative.

	- Wendy

>Date: Tue, 12 Feb 2013 14:33:10 +0000
>From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
>Subject: Re: [alto] Should we allow relative URIs in resource
>	directories?
>Message-ID: <0D1494C5-2154-43E0-886B-29DF8402B1D8@niven-jenkins.co.uk>
>
>Wendy,
>
>I see no reason to restrict to absolute URIs.
>
>Currently section 6.7.2 of the ALTO protocol spec states:
>
>   uri  A URI at which the ALTO Server provides one or more Information
>      Resources, or an Information Resource Directory indicating
>      additional Information Resources.
>
>Would adding a reference to section 4.1 of RFC3986 be sufficient, e.g.
>
>   uri  A URI reference (as per section 4.1 of [RFC3986] to one or more
>      Information Resources, or an Information Resource Directory
>      indicating additional Information Resources.
>
>
>Ben



From w.roome@alcatel-lucent.com  Wed Feb 13 06:52:13 2013
Return-Path: <w.roome@alcatel-lucent.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 54CDF21F877A for <alto@ietfa.amsl.com>; Wed, 13 Feb 2013 06:52:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6xVNYj47vp19 for <alto@ietfa.amsl.com>; Wed, 13 Feb 2013 06:52:12 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 0764C21F86F7 for <alto@ietf.org>; Wed, 13 Feb 2013 06:52:11 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r1DEq8a8022328 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Wed, 13 Feb 2013 08:52:08 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1DEq8Yw029160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Wed, 13 Feb 2013 08:52:08 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1DEq6Pm009447 for <alto@ietf.org>; Wed, 13 Feb 2013 08:52:07 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.0.121105
Date: Wed, 13 Feb 2013 09:52:05 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: <alto@ietf.org>
Message-ID: <CD410FCA.3223B%w.roome@alcatel-lucent.com>
Thread-Topic: [alto] Should we allow relative URIs in resource directories?
In-Reply-To: <mailman.100.1360699231.7699.alto@ietf.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [alto] Should we allow relative URIs in resource directories?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 13 Feb 2013 14:52:13 -0000

Here's my take on the tradeoffs.

Relative URIs simplify the ALTO server. Assuming the server is built on
top of an http handling package, like servlets, the server name and port
number are configured at the http handler level. The ALTO-specific server
code doesn't see, or otherwise need, that information. The server can
extract the server & port from the http handler, but it takes some effort.

On the other hand, relative URIs complicate clients, because the client
must resolve the relative URI in the context of the resource directory
URI. That isn't hard (most http client libraries have a resolve function),
but it is easy to forget. The client will work fine with ALTO servers that
return absolute URIs, but will fail the first time it connects to a server
that uses relative URIs.

It's another example of the Law of Conservation Of Difficulty. :-)

   - Wendy Roome

On 02/12/2013 15:00, "alto-request@ietf.org" <alto-request@ietf.org> wrote:

>Date: Tue, 12 Feb 2013 15:44:48 +0000
>From: "Diego R. Lopez" <diego@tid.es>
>Subject: Re: [alto] Should we allow relative URIs in resource
>	directories?
>Hi,
>
>I think allowing only absolute URIs would translate into simpler
>mechanisms to build them, and better understanding by human readers
>trying to debug based on ALTO outputs, but I acknowledge these are
>limited advantages if there are any other reasons for allowing relative
>URIs.



From ben@niven-jenkins.co.uk  Wed Feb 13 22:56:31 2013
Return-Path: <ben@niven-jenkins.co.uk>
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 D642F21F87C6 for <alto@ietfa.amsl.com>; Wed, 13 Feb 2013 22:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aMSR3EDoEI2L for <alto@ietfa.amsl.com>; Wed, 13 Feb 2013 22:56:30 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by ietfa.amsl.com (Postfix) with ESMTP id 53F7F21F8799 for <alto@ietf.org>; Wed, 13 Feb 2013 22:56:30 -0800 (PST)
Received: from cpc4-cmbg17-2-0-cust814.5-4.cable.virginmedia.com ([86.14.227.47] helo=[192.168.0.4]) by mail10.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1U5sk8-0002Ug-BJ; Thu, 14 Feb 2013 06:56:28 +0000
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <CD410929.32200%w.roome@alcatel-lucent.com>
Date: Thu, 14 Feb 2013 06:56:26 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <32175B8B-3F60-4DB9-AEC6-6C6D9EFE8F9C@niven-jenkins.co.uk>
References: <CD410929.32200%w.roome@alcatel-lucent.com>
To: Wendy Roome <w.roome@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1085)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: alto@ietf.org
Subject: Re: [alto] Should we allow relative URIs in resource directories?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 14 Feb 2013 06:56:32 -0000

Wendy,

On 13 Feb 2013, at 14:38, Wendy Roome wrote:

> RFC 3986 does define relative URIs, so technically that's sufficient. =
But
> I think that's like a lawyer burying some critical information -- like
> "double every amount that you owe us" -- in tiny type in a footnote.
> Legal, but sleazy.
>=20
> The problem is that software libraries with a simple =
connectToServer(uri)
> function require an absolute uri. If the uri might be relative, the =
client
> must first resolve the uri in the context of some absolute base uri. =
Most
> libraries provide a function to do that, but it's easy to forget that =
step.
>=20
> Case in point: My client, which passed all the interop tests, failed =
when
> it contacted a server that returned relative URIs. (And yes, I've =
since
> fixed my client.)
>=20
> So if we want to allow relative URIs, we should be more explicit. At =
the
> very least, add this sentence to the end of Ben's revised uri section:
>=20
>    Relative URIs should be resolved using the URI of the Information
> Resource Directory as the base URI.

Or a reference to section 5 of RFC 3986 rather than re-specifying its =
semantics.

Maybe something like:
   URIs can be relative and MUST be resolved according to section 5 of=20=

   [RFC3986].

Ben



From michael.scharf@alcatel-lucent.com  Thu Feb 14 04:01:05 2013
Return-Path: <michael.scharf@alcatel-lucent.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 B2E5521F85DA for <alto@ietfa.amsl.com>; Thu, 14 Feb 2013 04:01:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.162
X-Spam-Level: 
X-Spam-Status: No, score=-9.162 tagged_above=-999 required=5 tests=[AWL=0.488,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsHGaSvahJMD for <alto@ietfa.amsl.com>; Thu, 14 Feb 2013 04:01:05 -0800 (PST)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 673BF21F85DF for <alto@ietf.org>; Thu, 14 Feb 2013 04:01:04 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r1EBsLAK004147 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 14 Feb 2013 13:00:58 +0100
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Thu, 14 Feb 2013 13:00:11 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "alto@ietf.org" <alto@ietf.org>
Date: Thu, 14 Feb 2013 13:00:09 +0100
Thread-Topic: New ALTO draft: draft-scharf-alto-vpn-service-00
Thread-Index: Ac4Kp0dhvSPn0LQjSba0mrJ0Xd37BgAAK4OQ
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AA10D60F2@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.83
Cc: "Soprovich, Greg \(Greg\)" <greg.soprovich@alcatel-lucent.com>, "Hilt, Volker \(Volker\)" <volker.hilt@bell-labs.com>, "Gurbani, Vijay K \(Vijay\)" <vijay.gurbani@alcatel-lucent.com>
Subject: [alto] New ALTO draft: draft-scharf-alto-vpn-service-00
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 14 Feb 2013 12:01:05 -0000

Hi all,

This draft discusses the use of ALTO in VPNs, such as L3VPNs and L2VPNs.

The document includes several potential use cases, a list of (new) requirem=
ents that seem specific to VPNs, as well as a gap analysis when using the b=
ase ALTO protocol. This draft does not suggest a specific solution right no=
w. Our understanding is that it is important to first analyze what problems=
 have to be solved when ALTO shall be used in VPN environments.

Feedback would be highly welcome!

Thanks

Michael


-----Original Message-----
From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] =
On Behalf Of internet-drafts@ietf.org
Sent: Thursday, February 14, 2013 12:34 PM
To: i-d-announce@ietf.org
Subject: I-D Action: draft-scharf-alto-vpn-service-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


	Title           : The Virtual Private Network (VPN) Service in ALTO: Use C=
ases, Requirements and Extensions
	Author(s)       : Michael Scharf
                          Vijay K. Gurbani
                          Greg Soprovich
                          Volker Hilt
	Filename        : draft-scharf-alto-vpn-service-00.txt
	Pages           : 19
	Date            : 2013-02-14

Abstract:
   The Application-Layer Traffic Optimization (ALTO) protocol is
   designed to allow entities with knowledge about the network
   infrastructure to export such information to applications that need
   to choose one or more resources from a candidate set.  This document
   provides motivation for using ALTO in a Virtual Private Network (VPN)
   environment.  We discuss use cases, requirements, and possible
   extensions to the base ALTO protocol that will be needed to support
   VPN services.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-scharf-alto-vpn-service

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-scharf-alto-vpn-service-00


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ie=
tf.org/ietf/1shadow-sites.txt

From richard.alimi@gmail.com  Thu Feb 14 22:07:10 2013
Return-Path: <richard.alimi@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 8BB3921F8A49 for <alto@ietfa.amsl.com>; Thu, 14 Feb 2013 22:07:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNX76DX2yRUy for <alto@ietfa.amsl.com>; Thu, 14 Feb 2013 22:07:09 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 6125E21F8717 for <alto@ietf.org>; Thu, 14 Feb 2013 22:07:09 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id o1so712407wic.11 for <alto@ietf.org>; Thu, 14 Feb 2013 22:07:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=yHeFbYUC7jfgC4ojSRUZ1+ZwMqmAa9kdeg8byQShEP4=; b=NWmaU1mVQRO4A7hEPY8XgWJTwVeFQMz8S0tH+nTlRDdsj04cFaAbNiDey8SzzG2YOi 89Mp0kNx9vZy+B9SwPKLJ83Ti2Kqa+yjRg7cPbwB23Osqa/ISTBO7i4Ee9eqs+R98CaV wkpRl0hxqrAzDObSKuKWZS0bbJDcDwMbDaDHZn7Zce6ae5XYz1F/hHq6gwEPAK2VgejV ZhU4CkvoMjLRiJP7S4RQY4xYZ+Snw6ODiwXu2ib/65wZNzHWMC45kg1DzEsQL1GqV1nV 7yAha5VD5C78FAfIPpFeOMN3PPopcUMzk2uh88kXex6638ptpS8TnTEzWhk63QvyiHYq x8bQ==
X-Received: by 10.180.85.97 with SMTP id g1mr3729703wiz.29.1360908428463; Thu, 14 Feb 2013 22:07:08 -0800 (PST)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.58.209.169 with HTTP; Thu, 14 Feb 2013 22:06:48 -0800 (PST)
In-Reply-To: <32175B8B-3F60-4DB9-AEC6-6C6D9EFE8F9C@niven-jenkins.co.uk>
References: <CD410929.32200%w.roome@alcatel-lucent.com> <32175B8B-3F60-4DB9-AEC6-6C6D9EFE8F9C@niven-jenkins.co.uk>
From: Richard Alimi <rich@velvetsea.net>
Date: Thu, 14 Feb 2013 22:06:48 -0800
X-Google-Sender-Auth: t8QZrnAOxlaeuewJzLQobQl7r2w
Message-ID: <CA+cvDaZJvCwWzDZQx45-MCzpjMaczkbzR84dQM32-Eno8x5M-w@mail.gmail.com>
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Content-Type: multipart/alternative; boundary=f46d0444036c734e9704d5bd2f57
Cc: Wendy Roome <w.roome@alcatel-lucent.com>, "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Should we allow relative URIs in resource directories?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Feb 2013 06:07:10 -0000

--f46d0444036c734e9704d5bd2f57
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Feb 13, 2013 at 10:56 PM, Ben Niven-Jenkins <ben@niven-jenkins.co.uk
> wrote:

> Wendy,
>
> On 13 Feb 2013, at 14:38, Wendy Roome wrote:
>
> > RFC 3986 does define relative URIs, so technically that's sufficient. But
> > I think that's like a lawyer burying some critical information -- like
> > "double every amount that you owe us" -- in tiny type in a footnote.
> > Legal, but sleazy.
> >
> > The problem is that software libraries with a simple connectToServer(uri)
> > function require an absolute uri. If the uri might be relative, the
> client
> > must first resolve the uri in the context of some absolute base uri. Most
> > libraries provide a function to do that, but it's easy to forget that
> step.
> >
> > Case in point: My client, which passed all the interop tests, failed when
> > it contacted a server that returned relative URIs. (And yes, I've since
> > fixed my client.)
> >
> > So if we want to allow relative URIs, we should be more explicit. At the
> > very least, add this sentence to the end of Ben's revised uri section:
> >
> >    Relative URIs should be resolved using the URI of the Information
> > Resource Directory as the base URI.
>
> Or a reference to section 5 of RFC 3986 rather than re-specifying its
> semantics.
>
> Maybe something like:
>    URIs can be relative and MUST be resolved according to section 5 of
>    [RFC3986].
>

+1 for allowing relative URIs.  If there are no dissenting opinions, we'll
update the draft with Ben's proposed text.


>
> Ben
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

--f46d0444036c734e9704d5bd2f57
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Wed, Feb 13, 2013 at 10:56 PM, Ben Niven-Jenkins <span dir=3D"ltr">&lt;<=
a href=3D"mailto:ben@niven-jenkins.co.uk" target=3D"_blank">ben@niven-jenki=
ns.co.uk</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Wendy,<br>
<div class=3D"im"><br>
On 13 Feb 2013, at 14:38, Wendy Roome wrote:<br>
<br>
&gt; RFC 3986 does define relative URIs, so technically that&#39;s sufficie=
nt. But<br>
&gt; I think that&#39;s like a lawyer burying some critical information -- =
like<br>
&gt; &quot;double every amount that you owe us&quot; -- in tiny type in a f=
ootnote.<br>
&gt; Legal, but sleazy.<br>
&gt;<br>
&gt; The problem is that software libraries with a simple connectToServer(u=
ri)<br>
&gt; function require an absolute uri. If the uri might be relative, the cl=
ient<br>
&gt; must first resolve the uri in the context of some absolute base uri. M=
ost<br>
&gt; libraries provide a function to do that, but it&#39;s easy to forget t=
hat step.<br>
&gt;<br>
&gt; Case in point: My client, which passed all the interop tests, failed w=
hen<br>
&gt; it contacted a server that returned relative URIs. (And yes, I&#39;ve =
since<br>
&gt; fixed my client.)<br>
&gt;<br>
&gt; So if we want to allow relative URIs, we should be more explicit. At t=
he<br>
&gt; very least, add this sentence to the end of Ben&#39;s revised uri sect=
ion:<br>
&gt;<br>
&gt; =A0 =A0Relative URIs should be resolved using the URI of the Informati=
on<br>
&gt; Resource Directory as the base URI.<br>
<br>
</div>Or a reference to section 5 of RFC 3986 rather than re-specifying its=
 semantics.<br>
<br>
Maybe something like:<br>
=A0 =A0URIs can be relative and MUST be resolved according to section 5 of<=
br>
=A0 =A0[RFC3986].<br></blockquote><div><br></div><div style>+1 for allowing=
 relative URIs. =A0If there are no dissenting opinions, we&#39;ll update th=
e draft with Ben&#39;s proposed text.</div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">


<div class=3D"HOEnZb"><div class=3D"h5"><br>
Ben<br>
<br>
<br>
_______________________________________________<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" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</div></div></blockquote></div><br></div></div>

--f46d0444036c734e9704d5bd2f57--

From richard.alimi@gmail.com  Thu Feb 14 22:10:44 2013
Return-Path: <richard.alimi@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 7A04221F8746 for <alto@ietfa.amsl.com>; Thu, 14 Feb 2013 22:10:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KPxpOCQTXcbD for <alto@ietfa.amsl.com>; Thu, 14 Feb 2013 22:10:44 -0800 (PST)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 8E41221F85EB for <alto@ietf.org>; Thu, 14 Feb 2013 22:10:43 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id x10so2625915wey.3 for <alto@ietf.org>; Thu, 14 Feb 2013 22:10:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=tBTccuA931TcRdgU+uGTEW6prc+1PjeC8bONqK98UNg=; b=jjlWBUogEI+Mmjp8MMt3MDRVCLg686OvOAfVu15wdlCYzYef7CeORmOWzkiCngz+ae 1RYNf2UhJT+IbwUe9frzvwoNw7X+nVBNOOKT7VbHeLInpQ1shV5bESVcWHD5zHA8o/HC b2KByCrbqCWxgSIcq4YnPkll/AWeLE7pciykvzuFzrNTH3dZ84CR1WoCIO6q9ezSj0/M eYS02QBgJ5/0058bApFj6xHhrAJKQ71Q3PSjPdRQ52WJstkbLTNXuj0qhi6ezV6iZmdI KmUaW2mmzg2nbLWm9ZMR2yRewyQ474nB4vG9AIhcThXGFbQcFjewPark+B8pTiuad9ha uU6w==
X-Received: by 10.194.76.137 with SMTP id k9mr1955125wjw.29.1360908642399; Thu, 14 Feb 2013 22:10:42 -0800 (PST)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.180.85.170 with HTTP; Thu, 14 Feb 2013 22:10:22 -0800 (PST)
In-Reply-To: <CD2FE830.2D9E5%w.roome@alcatel-lucent.com>
References: <mailman.107.1359489625.24927.alto@ietf.org> <CD2FE830.2D9E5%w.roome@alcatel-lucent.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Thu, 14 Feb 2013 22:10:22 -0800
X-Google-Sender-Auth: 2WxrU74jE69MSJg_jxFtoejNj-w
Message-ID: <CA+cvDaZW-oRVgrcFbVf2LOD_R8rm79NsaDfjVmsBUSneGUse8g@mail.gmail.com>
To: Wendy Roome <w.roome@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=047d7bfceb1833b5b604d5bd3c16
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Issue I: Specify behavior of degenerated map filtering service
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Feb 2013 06:10:44 -0000

--047d7bfceb1833b5b604d5bd3c16
Content-Type: text/plain; charset=ISO-8859-1

Agreed.


On Thu, Jan 31, 2013 at 6:29 AM, Wendy Roome <w.roome@alcatel-lucent.com>wrote:

> I'm in favor of returning the complete map, rather than generating a error.
>
> Why?  Because errors are annoying to implement, and they're annoying to
> test in a bake-off. So whenever practical, I prefer to legislate errors
> out of existence by using reasonable defaults.
>
>         - Wendy Roome
>
>
> >Date: Mon, 28 Jan 2013 23:03:56 +0000
> >From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
> >To: "alto@ietf.org" <alto@ietf.org>
> >Subject: [alto] ALTO Protocol Outstanding Issue I: Specify behavior of
> >       degenerated map filtering service
> >Message-ID:
> >       <45A697A8FFD7CF48BCF2BE7E106F060408FF52D6@xmb-rcd-x04.cisco.com>
> >Content-Type: text/plain; charset="us-ascii"
> >
> >Discussion I:  Specify behaviors of degenerated map filtering service
> >
> >Do we enforce non-empty PID/AddressType? If protocol allows empty there
> >are two possible design choices: default to complete map or reporting an
> >Error
> >
> >Proposal going forward: Return complete Map.
> >
> >
> >Thanks,
> >
> >Reinaldo
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

--047d7bfceb1833b5b604d5bd3c16
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Agreed.</div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Thu, Jan 31, 2013 at 6:29 AM, Wendy Roome <span dir=3D"=
ltr">&lt;<a href=3D"mailto:w.roome@alcatel-lucent.com" target=3D"_blank">w.=
roome@alcatel-lucent.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I&#39;m in favor of returning the complete m=
ap, rather than generating a error.<br>
<br>
Why? =A0Because errors are annoying to implement, and they&#39;re annoying =
to<br>
test in a bake-off. So whenever practical, I prefer to legislate errors<br>
out of existence by using reasonable defaults.<br>
<br>
=A0 =A0 =A0 =A0 - Wendy Roome<br>
<br>
<br>
&gt;Date: Mon, 28 Jan 2013 23:03:56 +0000<br>
&gt;From: &quot;Reinaldo Penno (repenno)&quot; &lt;<a href=3D"mailto:repenn=
o@cisco.com">repenno@cisco.com</a>&gt;<br>
&gt;To: &quot;<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a>&quot; &lt;=
<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a>&gt;<br>
&gt;Subject: [alto] ALTO Protocol Outstanding Issue I: Specify behavior of<=
br>
&gt; =A0 =A0 =A0 degenerated map filtering service<br>
&gt;Message-ID:<br>
&gt; =A0 =A0 =A0 &lt;<a href=3D"mailto:45A697A8FFD7CF48BCF2BE7E106F060408FF=
52D6@xmb-rcd-x04.cisco.com">45A697A8FFD7CF48BCF2BE7E106F060408FF52D6@xmb-rc=
d-x04.cisco.com</a>&gt;<br>
&gt;Content-Type: text/plain; charset=3D&quot;us-ascii&quot;<br>
&gt;<br>
&gt;Discussion I: =A0Specify behaviors of degenerated map filtering service=
<br>
&gt;<br>
&gt;Do we enforce non-empty PID/AddressType? If protocol allows empty there=
<br>
&gt;are two possible design choices: default to complete map or reporting a=
n<br>
&gt;Error<br>
&gt;<br>
&gt;Proposal going forward: Return complete Map.<br>
&gt;<br>
&gt;<br>
&gt;Thanks,<br>
&gt;<br>
&gt;Reinaldo<br>
<br>
<br>
_______________________________________________<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" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</blockquote></div><br></div>

--047d7bfceb1833b5b604d5bd3c16--

From w.roome@alcatel-lucent.com  Fri Feb 15 06:18:51 2013
Return-Path: <w.roome@alcatel-lucent.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 3272821F8AA8 for <alto@ietfa.amsl.com>; Fri, 15 Feb 2013 06:18:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.901
X-Spam-Level: 
X-Spam-Status: No, score=-9.901 tagged_above=-999 required=5 tests=[AWL=-0.699, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kbTaspC33U+0 for <alto@ietfa.amsl.com>; Fri, 15 Feb 2013 06:18:50 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 9AEC721F8717 for <alto@ietf.org>; Fri, 15 Feb 2013 06:18:45 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r1FEIf3D013436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 15 Feb 2013 08:18:42 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1FEIeXK022697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Feb 2013 08:18:41 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1FEIard017028; Fri, 15 Feb 2013 08:18:38 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.1.130117
Date: Fri, 15 Feb 2013 09:18:41 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: Richard Alimi <rich@velvetsea.net>, Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Message-ID: <CD43AC8B.33C2D%w.roome@alcatel-lucent.com>
Thread-Topic: [alto] Should we allow relative URIs in resource directories?
In-Reply-To: <CA+cvDaZJvCwWzDZQx45-MCzpjMaczkbzR84dQM32-Eno8x5M-w@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3443764726_2632357"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Should we allow relative URIs in resource directories?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Feb 2013 14:18:51 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3443764726_2632357
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

To  reinforce that, how about using relative URIs in the 6.7.3 example?  Eg,
replace
        "uri" : "http://alto.example.com/networkmap",
with
        "uri" : "/networkmap",
etc.

- Wendy

From:  Richard Alimi <rich@velvetsea.net>
Date:  Fri, February 15, 2013 01:06
To:  Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
Cc:  Bill Roome <w.roome@alcatel-lucent.com>, "alto@ietf.org"
<alto@ietf.org>
Subject:  Re: [alto] Should we allow relative URIs in resource directories?


On Wed, Feb 13, 2013 at 10:56 PM, Ben Niven-Jenkins
<ben@niven-jenkins.co.uk> wrote:
> Wendy,
> 
> On 13 Feb 2013, at 14:38, Wendy Roome wrote:
> 
>> > RFC 3986 does define relative URIs, so technically that's sufficient. But
>> > I think that's like a lawyer burying some critical information -- like
>> > "double every amount that you owe us" -- in tiny type in a footnote.
>> > Legal, but sleazy.
>> >
>> > The problem is that software libraries with a simple connectToServer(uri)
>> > function require an absolute uri. If the uri might be relative, the client
>> > must first resolve the uri in the context of some absolute base uri. Most
>> > libraries provide a function to do that, but it's easy to forget that step.
>> >
>> > Case in point: My client, which passed all the interop tests, failed when
>> > it contacted a server that returned relative URIs. (And yes, I've since
>> > fixed my client.)
>> >
>> > So if we want to allow relative URIs, we should be more explicit. At the
>> > very least, add this sentence to the end of Ben's revised uri section:
>> >
>> >    Relative URIs should be resolved using the URI of the Information
>> > Resource Directory as the base URI.
> 
> Or a reference to section 5 of RFC 3986 rather than re-specifying its
> semantics.
> 
> Maybe something like:
>    URIs can be relative and MUST be resolved according to section 5 of
>    [RFC3986].

+1 for allowing relative URIs.  If there are no dissenting opinions, we'll
update the draft with Ben's proposed text.
 
> 
> Ben
> 
> 
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto




--B_3443764726_2632357
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>To &nbsp;reinforce that, how=
 about using relative URIs in the 6.7.3 example? &nbsp;Eg, replace</div><div=
>&nbsp; &nbsp; &nbsp; &nbsp; "uri" : "http://alto.example.com/networkmap",</=
div><div>with</div><div>&nbsp; &nbsp; &nbsp; &nbsp; "uri" : "/networkmap",</=
div><div>etc.</div><div><br></div><div><span class=3D"Apple-tab-span" style=3D"w=
hite-space:pre">	</span>- Wendy</div><div><br></div><span id=3D"OLK_SRC_BODY_S=
ECTION"><div style=3D"font-family:Calibri; font-size:11pt; text-align:left; co=
lor:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt sol=
id; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bo=
ld">From: </span> Richard Alimi &lt;<a href=3D"mailto:rich@velvetsea.net">rich=
@velvetsea.net</a>&gt;<br><span style=3D"font-weight:bold">Date: </span> Fri, =
February 15, 2013 01:06<br><span style=3D"font-weight:bold">To: </span> Ben Ni=
ven-Jenkins &lt;<a href=3D"mailto:ben@niven-jenkins.co.uk">ben@niven-jenkins.c=
o.uk</a>&gt;<br><span style=3D"font-weight:bold">Cc: </span> Bill Roome &lt;<a=
 href=3D"mailto:w.roome@alcatel-lucent.com">w.roome@alcatel-lucent.com</a>&gt;=
, "<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a>" &lt;<a href=3D"mailto:alt=
o@ietf.org">alto@ietf.org</a>&gt;<br><span style=3D"font-weight:bold">Subject:=
 </span> Re: [alto] Should we allow relative URIs in resource directories?<b=
r></div><div><br></div><div dir=3D"ltr"><br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote">On Wed, Feb 13, 2013 at 10:56 PM, Ben Niven-Jenkins <span di=
r=3D"ltr">&lt;<a href=3D"mailto:ben@niven-jenkins.co.uk" target=3D"_blank">ben@niv=
en-jenkins.co.uk</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Wendy,<b=
r><div class=3D"im"><br>
On 13 Feb 2013, at 14:38, Wendy Roome wrote:<br><br>
&gt; RFC 3986 does define relative URIs, so technically that's sufficient. =
But<br>
&gt; I think that's like a lawyer burying some critical information -- like=
<br>
&gt; "double every amount that you owe us" -- in tiny type in a footnote.<b=
r>
&gt; Legal, but sleazy.<br>
&gt;<br>
&gt; The problem is that software libraries with a simple connectToServer(u=
ri)<br>
&gt; function require an absolute uri. If the uri might be relative, the cl=
ient<br>
&gt; must first resolve the uri in the context of some absolute base uri. M=
ost<br>
&gt; libraries provide a function to do that, but it's easy to forget that =
step.<br>
&gt;<br>
&gt; Case in point: My client, which passed all the interop tests, failed w=
hen<br>
&gt; it contacted a server that returned relative URIs. (And yes, I've sinc=
e<br>
&gt; fixed my client.)<br>
&gt;<br>
&gt; So if we want to allow relative URIs, we should be more explicit. At t=
he<br>
&gt; very least, add this sentence to the end of Ben's revised uri section:=
<br>
&gt;<br>
&gt; &nbsp; &nbsp;Relative URIs should be resolved using the URI of the Inf=
ormation<br>
&gt; Resource Directory as the base URI.<br><br></div>Or a reference to sec=
tion 5 of RFC 3986 rather than re-specifying its semantics.<br><br>
Maybe something like:<br>
&nbsp; &nbsp;URIs can be relative and MUST be resolved according to section=
 5 of<br>
&nbsp; &nbsp;[RFC3986].<br></blockquote><div><br></div><div style=3D"">+1 for=
 allowing relative URIs. &nbsp;If there are no dissenting opinions, we'll up=
date the draft with Ben's proposed text.</div><div>&nbsp;</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;paddi=
ng-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><br>
Ben<br><br><br>
_______________________________________________<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" target=3D"_blank">https://w=
ww.ietf.org/mailman/listinfo/alto</a><br></div></div></blockquote></div><br>=
</div></div></span></body></html>

--B_3443764726_2632357--



From vkg@bell-labs.com  Fri Feb 15 06:49:44 2013
Return-Path: <vkg@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 8830A21F8AE6 for <alto@ietfa.amsl.com>; Fri, 15 Feb 2013 06:49:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BULnwJQlo3kO for <alto@ietfa.amsl.com>; Fri, 15 Feb 2013 06:49:42 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id E8C0321F8AB4 for <alto@ietf.org>; Fri, 15 Feb 2013 06:49:41 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r1FEnfnh005686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Fri, 15 Feb 2013 08:49:41 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1FEnehx004701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Fri, 15 Feb 2013 08:49:40 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1FEneO4005177 for <alto@ietf.org>; Fri, 15 Feb 2013 08:49:40 -0600 (CST)
Message-ID: <511E4B94.2050804@bell-labs.com>
Date: Fri, 15 Feb 2013 08:52:04 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: alto@ietf.org
References: <CD410929.32200%w.roome@alcatel-lucent.com> <32175B8B-3F60-4DB9-AEC6-6C6D9EFE8F9C@niven-jenkins.co.uk> <CA+cvDaZJvCwWzDZQx45-MCzpjMaczkbzR84dQM32-Eno8x5M-w@mail.gmail.com>
In-Reply-To: <CA+cvDaZJvCwWzDZQx45-MCzpjMaczkbzR84dQM32-Eno8x5M-w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [alto] Should we allow relative URIs in resource directories?
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Feb 2013 14:49:44 -0000

[As individual contributor]

On 02/15/2013 12:06 AM, Richard Alimi wrote:
> +1 for allowing relative URIs.  If there are no dissenting opinions,
> we'll update the draft with Ben's proposed text.

Richard: That is fine.  Originally I was going to state that we adopt
absolute URIs, but I must admit that this was driven by expediency
of us adopting *a* position instead of greeting the issue with silence
on the list.

Wendy has outlined the pros and cons of absolute versus relative URIs,
and yes it is a bit of pain to handle relative URIs,  But as long as we
have a position well spelled out in the document, adhering to it is a
matter of minor implementation complexity.  Let's go for what you
suggest above.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From w.roome@alcatel-lucent.com  Fri Feb 15 12:23:38 2013
Return-Path: <w.roome@alcatel-lucent.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 5F91D21F8652 for <alto@ietfa.amsl.com>; Fri, 15 Feb 2013 12:23:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.462
X-Spam-Level: 
X-Spam-Status: No, score=-10.462 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, MIME_BASE64_BLANKS=0.041, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id imj51gqHxJu2 for <alto@ietfa.amsl.com>; Fri, 15 Feb 2013 12:23:32 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 9992721F8644 for <alto@ietf.org>; Fri, 15 Feb 2013 12:23:32 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r1FKNVMR015568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Fri, 15 Feb 2013 14:23:31 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1FKNUlN017746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Fri, 15 Feb 2013 14:23:31 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1FKNSFg027455 for <alto@ietf.org>; Fri, 15 Feb 2013 14:23:28 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.1.130117
Date: Fri, 15 Feb 2013 15:23:33 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: <alto@ietf.org>
Message-ID: <CD43C00C.33E4A%w.roome@alcatel-lucent.com>
Thread-Topic: Discussion II: Unifying cost-mode and cost-type to a single type
In-Reply-To: <mailman.107.1359489625.24927.alto@ietf.org>
Mime-version: 1.0
Content-type: multipart/mixed; boundary="B_3443786615_3929526"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 15 Feb 2013 20:23:38 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3443786615_3929526
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

To return to this issue, I suggest we unify them, so that we have Cost
Types -- period. The "Mode" becomes a property of the Cost Type. So if a
server provides numerical & ordinal routingcosts, it provides *two*
separate Cost Types, say "routingcost" and "routingcost-ord".

I believe the result will simplify both clients and servers, and make it
easier for servers to introduce additional cost types.

My suggestion is to extend the Information Resource Directory with a list
of definitions for each Cost Type the server supports. Each Cost Type
definition would give the name of the Cost Type, the mode, and other
attributes. Currently the Information Resource Directory is a dictionary
with one item, "resources". So I propose adding a second item named
"cost-types," whose value is a list of cost-type definitions, as in

  "cost-types" : [
    {
      "name" : "routingcost",
      "value" : "number",
      "mode" : "numerical",
      "measures" : "delay",
      "description" : "Standard routing cost",
    }, { 
      "name" : "hopcount",
      "value" : "number",
      "mode" : "numerical",
      "measures" : "hops",
      "description" : "Simple hop count",
    }, {
      "name" : "routingcost-ord",
      "value" : "number",
      "mode" : "ordinal",
      "measures" : "delay",
      "description" : "Ordinal routing cost",
    }
  ]

Then pretty much delete every reference to a field named "cost-mode".



To get the ball rolling, I've attached proposed replacements for

	Section 5.1. Cost Attributes
	Section 6.7.2. Encoding	Section 6.7.3. Example

If those don't survive the list server, let me know and I'll put them up
on a web server.

If y'all like this idea, I'd be happy to help with the editing.

	- Wendy Roome
 

>Date: Mon, 28 Jan 2013 23:08:23 +0000
>From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
>Subject: [alto] ALTO Protocol Outstanding Issue II: Unifying cost-mode
>	and cost-type to a single type
>
>Discussion II: Unifying cost-mode and cost-type to a single type
>
>e.g., routingcost-num and routingcost-ord
>
>Having a single type simples the protocol since there is just one
>parameter when indicating cost. But it will impact current
>implementations and might loose flexibility.
>
>Proposal: Leave it as is.
>
>Thanks,
>
>Reinaldo


--B_3443786615_3929526
Content-type: text/plain; name="sect-5-1.txt";
 x-mac-creator="522A6368";
 x-mac-type="54455854"
Content-disposition: attachment;
	filename="sect-5-1.txt"
Content-transfer-encoding: base64


NS4xLiBDb3N0IEF0dHJpYnV0ZXMKCkFuIEFMVE8gc2VydmVyIHByb3ZpZGVzIG9uZSBvciBt
b3JlIGRpc3RpbmN0IENvc3QgVHlwZXMuIEVhY2ggQ29zdCBUeXBlCmhhcyBhdHRyaWJ1dGVz
LCBpbmNsdWRpbmcgYnV0IG5vdCBsaW1pdGVkIHRvOgoKKiBOYW1lOiBhIG5hbWUgdXNlZCB0
byBpZGVudGlmeSB0aGUgQ29zdCBUeXBlOwoqIFZhbHVlOiB0aGUgSlNPTiB0eXBlIG9mIHRo
ZSB2YWx1ZS4KKiBNZWFzdXJlczogd2hhdCBxdWFudGl0eSB0aGlzIENvc3QgVHlwZSBtZWFz
dXJlczsKKiBNb2RlOiBpZGVudGlmaWVzIGhvdyB0aGUgY29zdHMgc2hvdWxkIGJlIGludGVy
cHJldGVkLgoKQ2VydGFpbiBxdWVyaWVzIGZvciBDb3N0IE1hcHMgYWxsb3cgdGhlIEFMVE8g
Q2xpZW50IHRvIHNlbGVjdCB0aGUKZGVzaXJlZCBDb3N0IFR5cGUuCgo1LjEuMSBOYW1lCgpU
aGUgTmFtZSBhdHRyaWJ1dGUgaXMgYSBzdHJpbmcgdXNlZCB0byBpZGVudGlmeSBhIENvc3Qg
VHlwZSBpbiByZXF1ZXN0CmFuZCByZXNwb25zZSBtZXNzYWdlcy4KCjUuMS4yIFZhbHVlCgpU
aGUgVmFsdWUgYXR0cmlidXRlIGlzIHRoZSBKU09OIHR5cGUgZm9yIHZhbHVlcyBvZiB0aGlz
IENvc3QgVHlwZS4KQ3VycmVudGx5IG9ubHkgZmxvYXRpbmctcG9pbnQgIm51bWJlciIgdmFs
dWVzIGFyZSByZWNvZ25pemVkLiBFeHRlbnNpb25zCm1heSBhbGxvdyBhZGRpdGlvbmFsIHR5
cGVzLgoKNS4xLjMgTWVhc3VyZXMKClRoZSBNZWFzdXJlcyBhdHRyaWJ1dGUgaW5kaWNhdGVz
IG9mIHRoZSB1bmRlcmx5aW5nIHByb3BlcnR5IGZyb20gd2hpY2gKdGhpcyBDb3N0IFR5cGUg
aXMgZGVyaXZlZC4gRm9yIGV4YW1wbGUsIGFuIEFMVE8gU2VydmVyIGNvdWxkIGRlZmluZQpj
b3N0cyByZXByZXNlbnRpbmcgYWlyLW1pbGVzLCBob3AtY291bnRzLCBkZWxheXMsIGdlbmVy
aWMgcm91dGluZyBjb3N0cywKb3IgZXZlbiBtb25ldGFyeSBleHBlbnNlcy4KCjUuMS40LiBN
b2RlCgpUaGUgTW9kZSBhdHRyaWJ1dGUgaW5kaWNhdGVzIGhvdyBjb3N0cyBzaG91bGQgYmUg
aW50ZXJwcmV0ZWQuClNwZWNpZmljYWxseSwgdGhlIE1vZGUgYXR0cmlidXRlIGluZGljYXRl
cyB3aGV0aGVyIHJldHVybmVkIGNvc3RzIHNob3VsZApiZSBpbnRlcnByZXRlZCBhcyBudW1l
cmljYWwgdmFsdWVzIG9yIG9yZGluYWwgcmFua2luZ3MuCgpJdCBpcyBpbXBvcnRhbnQgdG8g
Y29tbXVuaWNhdGUgc3VjaCBpbmZvcm1hdGlvbiB0byBBTFRPIENsaWVudHMsIGFzCmNlcnRh
aW4gb3BlcmF0aW9ucyBtYXkgbm90IGJlIHZhbGlkIG9uIGNlcnRhaW4gY29zdHMgcmV0dXJu
ZWQgYnkgYW4gQUxUTwpTZXJ2ZXIuIEZvciBleGFtcGxlLCBpdCBpcyBwb3NzaWJsZSBmb3Ig
YW4gQUxUTyBTZXJ2ZXIgdG8gcmV0dXJuIGEgc2V0Cm9mIElQIGFkZHJlc3NlcyB3aXRoIGNv
c3RzIGluZGljYXRpbmcgYSByYW5raW5nIG9mIHRoZSBJUCBhZGRyZXNzZXMuCkFyaXRobWV0
aWMgb3BlcmF0aW9ucyB0aGF0IHdvdWxkIG1ha2Ugc2Vuc2UgZm9yIG51bWVyaWNhbCB2YWx1
ZXMsIGRvIG5vdAptYWtlIHNlbnNlIGZvciBvcmRpbmFsIHJhbmtpbmdzLiBBTFRPIENsaWVu
dHMgbWF5IGhhbmRsZSBzdWNoIGNvc3RzCmRpZmZlcmVudGx5LgoKQUxUTyBDbGllbnRzIFNI
T1VMRCBiZSBjb2duaXphbnQgb2Ygb3BlcmF0aW9ucyB3aGVuIGEgZGVzaXJlZCBjb3N0IG1v
ZGUKaXMgbm90IHN1cHBvcnRlZC4gRm9yIGV4YW1wbGUsIGFuIEFMVE8gQ2xpZW50IGRlc2ly
aW5nIG51bWVyaWNhbCBjb3N0cwptYXkgYWRqdXN0IGJlaGF2aW9yIGlmIG9ubHkgdGhlIG9y
ZGluYWwgQ29zdCBNb2RlIGlzIGF2YWlsYWJsZS4KQWx0ZXJuYXRpdmVseSwgYW4gQUxUTyBD
bGllbnQgZGVzaXJpbmcgb3JkaW5hbCBjb3N0cyBtYXkgY29uc3RydWN0Cm9yZGluYWwgY29z
dHMgZ2l2ZW4gbnVtZXJpY2FsIHZhbHVlcyBpZiBvbmx5IHRoZSBudW1lcmljYWwgQ29zdCBN
b2RlIGlzCmF2YWlsYWJsZS4KCjUuMS40LjEuIENvc3QgTW9kZTogbnVtZXJpY2FsCgpUaGlz
IG1vZGUgaW5kaWNhdGVzIHRoYXQgaXQgaXMgc2FmZSB0byBwZXJmb3JtIG51bWVyaWNhbCBv
cGVyYXRpb25zCihlLmcuIG5vcm1hbGl6YXRpb24gb3IgY29tcHV0aW5nIHJhdGlvcyBmb3Ig
d2VpZ2h0ZWQgbG9hZC1iYWxhbmNpbmcpIG9uCnRoZSByZXR1cm5lZCBjb3N0cy4gVGhlIHZh
bHVlcyBhcmUgZmxvYXRpbmctcG9pbnQgbnVtYmVycy4KCjUuMS40LjIuIENvc3QgTW9kZTog
b3JkaW5hbAoKVGhpcyBtb2RlIGluZGljYXRlcyB0aGF0IHRoZSBjb3N0cyB2YWx1ZXMgaW4g
YSBDb3N0IE1hcCBhcmUgYSByYW5raW5nCihyZWxhdGl2ZSB0byBhbGwgb3RoZXIgdmFsdWVz
IGluIHRoZSBDb3N0IE1hcCksIHdpdGggbG93ZXIgdmFsdWVzCmluZGljYXRpbmcgYSBoaWdo
ZXIgcHJlZmVyZW5jZS4gVGhlIHZhbHVlcyBhcmUgbm9uLW5lZ2F0aXZlIGludGVnZXJzLgpP
cmRpbmFsIGNvc3QgdmFsdWVzIGluIGEgQ29zdCBNYXAgbmVlZCBub3QgYmUgdW5pcXVlIG5v
ciBjb250aWd1b3VzLiBJbgpwYXJ0aWN1bGFyLCBpdCBpcyBwb3NzaWJsZSB0aGF0IHR3byBl
bnRyaWVzIGluIGEgbWFwIGhhdmUgYW4gaWRlbnRpY2FsCnJhbmsgKG9yZGluYWwgY29zdCB2
YWx1ZSkuIFRoaXMgZG9jdW1lbnQgZG9lcyBub3Qgc3BlY2lmeSBhbnkgYmVoYXZpb3IKYnkg
YW4gQUxUTyBDbGllbnQgaW4gdGhpcyBjYXNlOyBhbiBBTFRPIENsaWVudCBtYXkgZGVjaWRl
IHRvIGJyZWFrIHRpZXMKYnkgcmFuZG9tIHNlbGVjdGlvbiwgb3RoZXIgYXBwbGljYXRpb24g
a25vd2xlZGdlLCBvciBzb21lIG90aGVyIG1lYW5zLgoKSXQgaXMgaW1wb3J0YW50IHRvIG5v
dGUgdGhhdCB0aGUgdmFsdWVzIGluIHRoZSBDb3N0IE1hcCBwcm92aWRlZCB3aXRoCnRoZSBv
cmRpbmFsIENvc3QgTW9kZSBhcmUgbm90IG5lY2Vzc2FyaWx5IHRoZSBhY3R1YWwgY29zdCBr
bm93biB0byB0aGUKQUxUTyBTZXJ2ZXIuCgo1LjEuNSBQcmVkZWZpbmVkIENvc3QgVHlwZXMK
CjUuMS41LjEgQ29zdCBUeXBlOiByb3V0aW5nY29zdAoKQW4gQUxUTyBTZXJ2ZXIgTVVTVCBk
ZWZpbmUgYSBDb3N0IFR5cGUgbmFtZWQgJ3JvdXRpbmdjb3N0Jy4gVGhpcyBDb3N0ClR5cGUg
Y29udmV5cyBhIGdlbmVyaWMgbWVhc3VyZSBmb3IgdGhlIGNvc3Qgb2Ygcm91dGluZyB0cmFm
ZmljIGZyb20gYQpzb3VyY2UgdG8gYSBkZXN0aW5hdGlvbi4gTG93ZXIgdmFsdWVzIGluZGlj
YXRlIGEgaGlnaGVyIHByZWZlcmVuY2UgZm9yCnRyYWZmaWMgdG8gYmUgc2VudCBmcm9tIGEg
c291cmNlIHRvIGEgZGVzdGluYXRpb24uCgpOb3RlIHRoYXQgYW4gSVNQIG1heSBpbnRlcm5h
bGx5IGNvbXB1dGUgcm91dGluZyBjb3N0IHVzaW5nIGFueSBtZXRob2QgaXQKY2hvb3NlcyAo
ZS5nLiwgYWlyLW1pbGVzIG9yIGhvcC1jb3VudCkgYXMgbG9uZyBhcyBpdCBjb25mb3JtcyB0
byB0aGVzZQpzZW1hbnRpY3MuCgpUaGUgTW9kZSBmb3IgJ3JvdXRpbmdjb3N0JyBtYXkgYmUg
J251bWVyaWNhbCcgb3IgJ29yZGluYWwnLCBhdCB0aGUKc2VydmVyJ3MgZGlzY3JldGlvbi4K
CkFuIEFMVE8gU2VydmVyIE1VU1Qgc3VwcG9ydCBhdCBsZWFzdCBvbmUgb2Yg4oCZbnVtZXJp
Y2Fs4oCZIGFuZCDigJlvcmRpbmFs4oCZCmNvc3RzLiBBTFRPIENsaWVudHMgU0hPVUxEIGJl
IGNvZ25pemFudCBvZiBvcGVyYXRpb25zIHdoZW4gYSBkZXNpcmVkCmNvc3QgbW9kZSBpcyBu
b3Qgc3VwcG9ydGVkLiBGb3IgZXhhbXBsZSwgYW4gQUxUTyBDbGllbnQgZGVzaXJpbmcKbnVt
ZXJpY2FsIGNvc3RzIG1heSBhZGp1c3QgYmVoYXZpb3IgaWYgb25seSB0aGUgb3JkaW5hbCBD
b3N0IE1vZGUgaXMKYXZhaWxhYmxlLiBBbHRlcm5hdGl2ZWx5LCBhbiBBTFRPIENsaWVudCBk
ZXNpcmluZyBvcmRpbmFsIGNvc3RzIG1heQpjb25zdHJ1Y3Qgb3JkaW5hbCBjb3N0cyBnaXZl
biBudW1lcmljYWwgdmFsdWVzIGlmIG9ubHkgdGhlIG51bWVyaWNhbApDb3N0IE1vZGUgaXMg
YXZhaWxhYmxlLgoKNS4xLjUuMiBDb3N0IFR5cGU6IGhvcGNvdW50CgpBbiBBTFRPIFNlcnZl
ciBNQVkgZGVmaW5lIGEgQ29zdCBUeXBlIG5hbWVkICdob3Bjb3VudCcuIElmIHNvLCB0aGF0
IENvc3QKVHlwZSBNVVNUIGJlIGJhc2VkIG9uIHRoZSBudW1iZXIgb2YgaG9wcy4KClRoZSBN
b2RlIGZvciAnaG9wY291bnQnIG1heSBiZSAnbnVtZXJpY2FsJyBvciAnb3JkaW5hbCcsIGF0
IHRoZSBzZXJ2ZXIncwpkaXNjcmV0aW9uLgo=
--B_3443786615_3929526
Content-type: text/plain; name="sect-6-7-2.txt";
 x-mac-creator="522A6368";
 x-mac-type="54455854"
Content-disposition: attachment;
	filename="sect-6-7-2.txt"
Content-transfer-encoding: base64


Ni43LjIuIEVuY29kaW5nCgpBbiBJbmZvcm1hdGlvbiBSZXNvdXJjZSBEaXJlY3RvcnkgaXMg
YSBKU09OIG9iamVjdCBvZiB0eXBlCkluZm9SZXNvdXJjZURpcmVjdG9yeToKCiAgb2JqZWN0
IHsKICAgIC4uLgogIH0gQ2FwYWJpbGl0aWVzOwoKICBvYmplY3QgewogICAgSlNPTlN0cmlu
ZyB1cmk7CiAgICBKU09OU3RyaW5nIG1lZGlhLXR5cGVzPDEuLio+OwogICAgSlNPTlN0cmlu
ZyBhY2NlcHRzPDAuLio+OyAgICAgICBbT1BUSU9OQUxdCiAgICBDYXBhYmlsaXRpZXMgY2Fw
YWJpbGl0aWVzOyAgICAgIFtPUFRJT05BTF0KICB9IFJlc291cmNlRW50cnk7CiAgCiAgb2Jq
ZWN0IHsKICAgIEpTT05TdHJpbmcgbmFtZTsKICAgIEpTT05TdHJpbmcgbWVhc3VyZXM7CiAg
ICBKU09OU3RyaW5nIHZhbHVlOyAgICAgICAgICAgICAgIFtPUFRJT05BTF0KICAgIEpTT05T
dHJpbmcgbW9kZTsgICAgICAgICAgICAgICAgW09QVElPTkFMXQogICAgSlNPTlN0cmluZyBk
ZXNjcmlwdGlvbjsgICAgICAgICBbT1BUSU9OQUxdCiAgICBKU09OU3RyaW5nIHVyaTsgICAg
ICAgICAgICAgICAgIFtPUFRJT05BTF0KICB9IENvc3RUeXBlRW50cnk7CiAgCiAgb2JqZWN0
IHsKICAgIFJlc291cmNlRW50cnkgcmVzb3VyY2VzPDAuLio+OwogICAgQ29zdFR5cGVFbnRy
eSBjb3N0LXR5cGVzPDAuLio+OwogIH0gSW5mb1Jlc291cmNlRGlyZWN0b3J5OwogIAp3aGVy
ZSB0aGUgInJlc291cmNlcyIgYW5kICJjb3N0LXR5cGVzIiBhcnJheXMgaW5kaWNhdGUgYSBs
aXN0IG9mCkluZm9ybWF0aW9uIFJlc291cmNlcyBhbmQgQ29zdCBUeXBlcyBwcm92aWRlZCBi
eSBhbiBBTFRPIFNlcnZlci4gTm90ZQp0aGF0IHRoZSBsaXN0IG9mIGF2YWlsYWJsZSByZXNv
dXJjZXMgaXMgZW5jbG9zZWQgaW4gYSBKU09OIG9iamVjdCBmb3IKZXh0ZW5zaWJpbGl0eTsg
ZnV0dXJlIHByb3RvY29sIHZlcnNpb25zIG1heSBzcGVjaWZ5IGFkZGl0aW9uYWwgbWVtYmVy
cwppbiB0aGUgSW5mb1Jlc291cmNlRGlyZWN0b3J5IG9iamVjdC4KCkFueSBVUkkgZW5kcG9p
bnQgaW5kaWNhdGVkIGluIGFuIEluZm9ybWF0aW9uIFJlc291cmNlIERpcmVjdG9yeSBNQVkK
cHJvdmlkZSBhIHJlc3BvbnNlIHRvIGFuIE9QVElPTlMgcmVxdWVzdCB0aGF0IGlzIGluIHRo
ZSBmb3JtYXQgb2YgYW4KSW5mb3JtYXRpb24gUmVzb3VyY2UgRGlyZWN0b3J5IHJlc3BvbnNl
LiBUaGlzIHByb3ZpZGVzIEFMVE8gQ2xpZW50cyBhCm1lYW5zIHRvIGRpc2NvdmVyIHJlc291
cmNlcyBhbmQgY2FwYWJpbGl0aWVzIG9mZmVyZWQgYnkgdGhhdCBVUkkKZW5kcG9pbnQuIEFM
VE8gU2VydmVycyB0aGF0IHJlcGx5IHdpdGggYW4gSFRUUCAzMDAgc3RhdHVzIGNvZGUKKCJN
dWx0aXBsZSBDaG9pY2VzIikgU0hPVUxEIHVzZSB0aGUgSW5mb3JtYXRpb24gUmVzb3VyY2Ug
RGlyZWN0b3J5CmZvcm1hdCBpbiB0aGUgcmVwbHkuCgpFYWNoIFJlc291cmNlRW50cnkgaW4g
dGhlIGRpcmVjdG9yeSBzcGVjaWZpZXM6CgogIHVyaSAgIEEgVVJJIGF0IHdoaWNoIHRoZSBB
TFRPIFNlcnZlciBwcm92aWRlcyBvbmUgb3IgbW9yZSBJbmZvcm1hdGlvbgogICAgUmVzb3Vy
Y2VzLCBvciBhbiBJbmZvcm1hdGlvbiBSZXNvdXJjZSBEaXJlY3RvcnkgaW5kaWNhdGluZwog
ICAgYWRkaXRpb25hbCBJbmZvcm1hdGlvbiBSZXNvdXJjZXMuIFVSSXMgY2FuIGJlIHJlbGF0
aXZlIGFuZCBNVVNUIGJlCiAgICByZXNvbHZlZCBhY2NvcmRpbmcgdG8gc2VjdGlvbiA1IG9m
IFtSRkMzOTg2XSwgdXNpbmcgdGhlIFVSSSBvZiB0aGUKICAgIFJlc291cmNlIERpcmVjdG9y
eSBhcyB0aGUgYmFzZSBVUkkuCgogIG1lZGlhLXR5cGVzICAgVGhlIGxpc3Qgb2YgYWxsIG1l
ZGlhIHR5cGVzIG9mIEluZm9ybWF0aW9uIFJlc291cmNlcyAoc2VlCiAgICBTZWN0aW9uIDYu
NC4zKSBhdmFpbGFibGUgdmlhIEdFVCBvciBQT1NUIHJlcXVlc3RzIHRvIHRoZSBjb3JyZXNw
b25kaW5nCiAgICBVUkkgb3IgVVJJcyBkaXNjb3ZlcmFibGUgdmlhIHRoZSBVUkkuCiAgICAK
ICBhY2NlcHRzICAgVGhlIGxpc3Qgb2YgYWxsIG1lZGlhIHR5cGVzIG9mIGlucHV0IHBhcmFt
ZXRlcnMgKHNlZSBTZWN0aW9uCiAgICA2LjQuMikgYWNjZXB0ZWQgYnkgUE9TVCByZXF1ZXN0
cyB0byB0aGUgY29ycmVzcG9uZGluZyBVUkkgb3IgVVJJcwogICAgZGlzY292ZXJhYmxlIHZp
YSB0aGUgVVJJLiBJZiB0aGlzIG1lbWJlciBpcyBub3QgcHJlc2VudCwgaXQgTVVTVCBiZQog
ICAgYXNzdW1lZCB0byBiZSBhbiBlbXB0eSBhcnJheS4KICAgIAogIGNhcGFiaWxpdGllcyAg
IEEgSlNPTiBPYmplY3QgZW51bWVyYXRpbmcgY2FwYWJpbGl0aWVzIG9mIGFuIEFMVE8KICAg
IFNlcnZlciBpbiBwcm92aWRpbmcgdGhlIEluZm9ybWF0aW9uIFJlc291cmNlIGF0IHRoZSBj
b3JyZXNwb25kaW5nCiAgICBVUkkgYW5kIEluZm9ybWF0aW9uIFJlc291cmNlcyBkaXNjb3Zl
cmFibGUgdmlhIHRoZSBVUkkuIElmIHRoaXMKICAgIG1lbWJlciBpcyBub3QgcHJlc2VudCwg
aXQgTVVTVCBiZSBhc3N1bWVkIHRvIGJlIGFuIGVtcHR5IG9iamVjdC4gSWYKICAgIGEgY2Fw
YWJpbGl0eSBmb3Igb25lIG9mIHRoZSBvZmZlcmVkIEluZm9ybWF0aW9uIFJlc291cmNlcyBp
cyBub3QKICAgIGV4cGxpY2l0bHkgbGlzdGVkIGhlcmUsIGFuIEFMVE8gQ2xpZW50IG1heSBl
aXRoZXIgaXNzdWUgYW4gT1BUSU9OUwogICAgSFRUUCByZXF1ZXN0IHRvIHRoZSBjb3JyZXNw
b25kaW5nIFVSSSB0byBkZXRlcm1pbmUgaWYgdGhlIGNhcGFiaWxpdHkKICAgIGlzIHN1cHBv
cnRlZCwgb3IgYXNzdW1lIGl0cyBkZWZhdWx0IHZhbHVlIGRvY3VtZW50ZWQgaW4gdGhpcwog
ICAgc3BlY2lmaWNhdGlvbiBvciBhbiBleHRlbnNpb24gZG9jdW1lbnQgZGVzY3JpYmluZyB0
aGUgY2FwYWJpbGl0eS4gSWYKICAgIGFuIGVudHJ5IGhhcyBhbiBlbXB0eSBsaXN0IGZvciAi
YWNjZXB0cyIsIHRoZW4gdGhlIGNvcnJlc3BvbmRpbmcgVVJJCiAgICBNVVNUIHN1cHBvcnQg
R0VUIHJlcXVlc3RzLiBJZiBhbiBlbnRyeSBoYXMgYSBub24tZW1wdHkgbGlzdCBmb3IKICAg
ICJhY2NlcHRzIiwgdGhlbiB0aGUgY29ycmVzcG9uZGluZyBVUkkgTVVTVCBzdXBwb3J0IFBP
U1QgcmVxdWVzdHMuIElmCiAgICBhbiBBTFRPIFNlcnZlciB3aXNoZXMgdG8gc3VwcG9ydCBi
b3RoIEdFVCBhbmQgUE9TVCBvbiBhIHNpbmdsZSBVUkksCiAgICBpdCBNVVNUIHNwZWNpZnkg
dHdvIGVudHJpZXMgaW4gdGhlIEluZm9ybWF0aW9uIFJlc291cmNlIERpcmVjdG9yeS4KICAK
VGhlIEFMVE8gU2VydmVyIE1VU1QgZGVmaW5lIGEgQ29zdFR5cGVFbnRyeSBmb3IgZXZlcnkg
Y29zdCB0eXBlIHRoYXQgaXMKc3VwcG9ydHMuIEFuIEFMVE8gU2VydmVyIE1BWSBkZWZpbmUg
Q29zdCBUeXBlcyB3aGljaCBpdCBkb2VzIG5vdApjdXJyZW50bHkgc3VwcG9ydC4gRWFjaCBD
b3N0VHlwZUVudHJ5IGluIHRoZSBkaXJlY3Rvcnkgc3BlY2lmaWVzOgoKICBuYW1lICBUaGUg
bmFtZSBvZiB0aGlzIENvc3QgVHlwZS4KICAKICBtZWFzdXJlcyAgV2hhdCB0aGlzIENvc3Qg
VHlwZSBtZWFzdXJlcy4gVmFsdWVzIGFyZSAiZGVsYXkiLCAiaG9wcyIsCiAgICAiZGlzdGFu
Y2UiLCAibW9uZXkiLCBhbmQgIm90aGVyLiIgRnV0dXJlIHZlcnNpb25zIG9mIHRoZSBwcm90
b2NvbCwKICAgIG9yIGV4dGVuc2lvbnMsIG1heSBkZWZpbmUgYWRkaXRpb25hbCBjaG9pY2Vz
LgogICAgCiAgdmFsdWUgIFRoZSBKU09OIHR5cGUgb2YgdGhlIHZhbHVlcyBmb3IgdGhpcyBD
b3N0IFR5cGUuICBDdXJyZW50bHkgdGhlCiAgICBvbmx5IGNob2ljZSBpcyAibnVtYmVyIiwg
Zm9yIGEgSlNPTiBudW1iZXIuIFRoaXMgYXR0cmlidXRlIGlzCiAgICBvcHRpb25hbDsgdGhl
IGRlZmF1bHQgaXMgIm51bWJlci4iIEZ1dHVyZSB2ZXJzaW9ucyBvZiB0aGUgcHJvdG9jb2ws
CiAgICBvciBleHRlbnNpb25zLCBtYXkgZGVmaW5lIGFkZGl0aW9uYWwgY2hvaWNlcy4KICAg
IAogIG1vZGUgIFRoZSBjb3N0IG1vZGUgIm51bWVyaWNhbCIgb3IgIm9yZGluYWwuIiBUaGUg
ZGVmYXVsdCBpcwogICAgIm51bWVyaWNhbC4iCiAgICAKICBkZXNjcmlwdGlvbiAgQSBmcmVl
LWZvcm0gZGVzY3JpcHRpb24gb2YgdGhlIENvc3QgVHlwZS4gImRlc2NyaXB0aW9uIgogICAg
aXMgb3B0aW9uYWwsIGJ1dCBpdCBpcyByZWNvbW1lbmRlZCB0aGF0IGFuIEFMVE8gU2VydmVy
IHByb3ZpZGUKICAgIGVpdGhlciAiZGVzY3JpcHRpb24iIG9yICJ1cmkuIgogIAogIHVyaSAg
VGhlIFVSSSBvZiBhIGRldGFpbGVkLCBhbmQgcG9zc2libHkgbXVsdGktbGluZ3VhbCwgZGVz
Y3JpcHRpb24KICAgIG9mIHRoaXMgY29zdCB0eXBlLiAidXJpIiBpcyBvcHRpb25hbCwgYnV0
IGl0IGlzIHJlY29tbWVuZGVkIHRoYXQgYW4KICAgIEFMVE8gU2VydmVyIHByb3ZpZGUgZWl0
aGVyICJ1cmkiIG9yICJkZXNjcmlwdGlvbi4iCgpGdXR1cmUgdmVyc2lvbnMgb2YgdGhlIHBy
b3RvY29sLCBvciBleHRlbnNpb25zLCBtYXkgZGVmaW5lIGFkZGl0aW9uYWwKaXRlbXMuCg==
--B_3443786615_3929526
Content-type: text/plain; name="sect-6-7-3.txt";
 x-mac-creator="522A6368";
 x-mac-type="54455854"
Content-disposition: attachment;
	filename="sect-6-7-3.txt"
Content-transfer-encoding: base64


Ni43LjMuIEV4YW1wbGUKClRoZSBmb2xsb3dpbmcgaXMgYW4gZXhhbXBsZSBJbmZvcm1hdGlv
biBSZXNvdXJjZSBEaXJlY3RvcnkgcmV0dXJuZWQgYnkKYW4gQUxUTyBTZXJ2ZXIuIFRoZSBz
ZXJ2ZXIgc3VwcG9ydHMgdGhyZWUgQ29zdCBUeXBlczogdGhlIHJlcXVpcmVkIHR5cGUKInJv
dXRpbmdjb3N0IiwgYSAiaG9wY291bnQiIGNvc3QsIGFuZCBhbiBvcmRpbmFsIHJvdXRpbmcg
Y29zdCBjYWxsZWQKInJvdXRpbmdjb3N0LW9yZC4iIFRoZSBzZXJ2ZXIgZG9lcyBub3QgcHJv
dmlkZSBhIG9yZGluYWwgdmVyc2lvbiBvZiBob3AKY291bnQuCgpJbiB0aGlzIGV4YW1wbGUs
IHRoZSBBTFRPIFNlcnZlciBwcm92aWRlcyBhZGRpdGlvbmFsIE5ldHdvcmsgYW5kIENvc3QK
TWFwcyB2aWEgYSBzZXBhcmF0ZSBzdWJkb21haW4sICJjdXN0b20uYWx0by5leGFtcGxlLmNv
bSIuIFRoZSBtYXBzCmF2YWlsYWJsZSB2aWEgdGhpcyBzdWJkb21haW4gYXJlIEZpbHRlcmVk
IE5ldHdvcmsgYW5kIENvc3QgTWFwcyBhcyB3ZWxsCmFzIGEgcHJlLWdlbmVyYXRlZCBtYXAg
Zm9yIHRoZSBvcmRpbmFsICJyb3V0aW5nY29zdC1vcmQiIENvc3QgVHlwZS4KCkFuIEFMVE8g
Q2xpZW50IGNhbiBkaXNjb3ZlciB0aGUgbWFwcyBhdmFpbGFibGUgYnkKImN1c3RvbS5hbHRv
LmV4YW1wbGUuY29tIiBieSBzdWNjZXNzZnVsbHkgcGVyZm9ybWluZyBhbiBPUFRJT05TIHJl
cXVlc3QKdG8gImh0dHA6Ly9jdXN0b20uYWx0by5leGFtcGxlLmNvbS9tYXBzIi4KCkluIHRo
aXMgZXhhbXBsZSwgdGhlIEFMVE8gc2VydmVyIHByb3ZpZGVzIHRoZSBFbmRwb2ludCBDb3N0
IFNlcnZpY2UgZm9yCmFsbCB0aHJlZSBDb3N0IFR5cGVzLgoKICBHRVQgL2RpcmVjdG9yeSBI
VFRQLzEuMQogIEhvc3Q6IGFsdG8uZXhhbXBsZS5jb20KICBBY2NlcHQ6IGFwcGxpY2F0aW9u
L2FsdG8tZGlyZWN0b3J5K2pzb24sYXBwbGljYXRpb24vYWx0by1lcnJvcitqc29uCgogIEhU
VFAvMS4xIDIwMCBPSwogIENvbnRlbnQtTGVuZ3RoOiAtLS0tCiAgQ29udGVudC1UeXBlOiBh
cHBsaWNhdGlvbi9hbHRvLWRpcmVjdG9yeStqc29uCiAgCiAgewogICAgInJlc291cmNlcyIg
OiBbCiAgICAgIHsKICAgICAgICAidXJpIiA6ICIvbmV0d29ya21hcCIsCiAgICAgICAgIm1l
ZGlhLXR5cGVzIiA6IFsgImFwcGxpY2F0aW9uL2FsdG8tbmV0d29ya21hcCtqc29uIiBdCiAg
ICAgIH0sIHsKICAgICAgICAidXJpIiA6ICIvY29zdG1hcC9udW0vcm91dGluZ2Nvc3QiLAog
ICAgICAgICJtZWRpYS10eXBlcyIgOiBbICJhcHBsaWNhdGlvbi9hbHRvLWNvc3RtYXAranNv
biIgXSwKICAgICAgICAiY2FwYWJpbGl0aWVzIiA6IHsKICAgICAgICAgICJjb3N0LXR5cGVz
IiA6IFsgInJvdXRpbmdjb3N0IiBdCiAgICAgICAgfQogICAgICB9LCB7CiAgICAgICAgInVy
aSIgOiAiL2Nvc3RtYXAvbnVtL2hvcGNvdW50IiwKICAgICAgICAibWVkaWEtdHlwZXMiIDog
WyAiYXBwbGljYXRpb24vYWx0by1jb3N0bWFwK2pzb24iIF0sCiAgICAgICAgImNhcGFiaWxp
dGllcyIgOiB7CiAgICAgICAgICAiY29zdC10eXBlcyIgOiBbICJob3Bjb3VudCIgXQogICAg
ICAgIH0KICAgICAgfSwgewogICAgICAgICJ1cmkiIDogImh0dHA6Ly9jdXN0b20uYWx0by5l
eGFtcGxlLmNvbS9tYXBzIiwKICAgICAgICAibWVkaWEtdHlwZXMiIDogWwogICAgICAgICAg
ImFwcGxpY2F0aW9uL2FsdG8tbmV0d29ya21hcCtqc29uIiwKICAgICAgICAgICJhcHBsaWNh
dGlvbi9hbHRvLWNvc3RtYXAranNvbiIKICAgICAgICBdLAogICAgICAgICJhY2NlcHRzIiA6
IFsKICAgICAgICAgICJhcHBsaWNhdGlvbi9hbHRvLW5ldHdvcmttYXBmaWx0ZXIranNvbiIs
CiAgICAgICAgICAiYXBwbGljYXRpb24vYWx0by1jb3N0bWFwZmlsdGVyK2pzb24iCiAgICAg
ICAgXQogICAgICB9LCB7CiAgICAgICAgInVyaSIgOiAiL2VuZHBvaW50cHJvcC9sb29rdXAi
LAogICAgICAgICJtZWRpYS10eXBlcyIgOiBbICJhcHBsaWNhdGlvbi9hbHRvLWVuZHBvaW50
cHJvcCtqc29uIiBdLAogICAgICAgICJhY2NlcHRzIiA6IFsgImFwcGxpY2F0aW9uL2FsdG8t
ZW5kcG9pbnRwcm9wcGFyYW1zK2pzb24iIF0sCiAgICAgICAgImNhcGFiaWxpdGllcyIgOiB7
CiAgICAgICAgICAicHJvcC10eXBlcyIgOiBbICJwaWQiIF0KICAgICAgICB9CiAgICAgIH0s
IHsKICAgICAgICAidXJpIiA6ICIvZW5kcG9pbnRjb3N0L2xvb2t1cCIsCiAgICAgICAgIm1l
ZGlhLXR5cGVzIiA6IFsgImFwcGxpY2F0aW9uL2FsdG8tZW5kcG9pbnRjb3N0K2pzb24iIF0s
CiAgICAgICAgImFjY2VwdHMiIDogWyAiYXBwbGljYXRpb24vYWx0by1lbmRwb2ludGNvc3Rw
YXJhbXMranNvbiIgXSwKICAgICAgICAiY2FwYWJpbGl0aWVzIiA6IHsKICAgICAgICAgICJj
b3N0LWNvbnN0cmFpbnRzIiA6IHRydWUsCiAgICAgICAgICAiY29zdC10eXBlcyIgOiBbICJy
b3V0aW5nY29zdCIsICJob3Bjb3VudCIsICJyb3V0aW5nY29zdC1vcmQiIF0KICAgICAgICB9
CiAgICAgIH0KICAgIF0sCiAgICAiY29zdC10eXBlcyIgOiBbCiAgICAgIHsKICAgICAgICAg
Im5hbWUiIDogInJvdXRpbmdjb3N0IiwKICAgICAgICAgInZhbHVlIiA6ICJudW1iZXIiLAog
ICAgICAgICAibW9kZSIgOiAibnVtZXJpY2FsIiwKICAgICAgICAgIm1lYXN1cmVzIiA6ICJk
ZWxheSIsCiAgICAgICAgICJkZXNjcmlwdGlvbiIgOiAiU3RhbmRhcmQgcm91dGluZyBjb3N0
IiwKICAgICAgfSwgewogICAgICAgICAibmFtZSIgOiAiaG9wY291bnQiLAogICAgICAgICAi
dmFsdWUiIDogIm51bWJlciIsCiAgICAgICAgICJtb2RlIiA6ICJudW1lcmljYWwiLAogICAg
ICAgICAibWVhc3VyZXMiIDogImhvcHMiLAogICAgICAgICAiZGVzY3JpcHRpb24iIDogIlN0
YW5kYXJkIGhvcCBjb3VudCIsCiAgICAgIH0sIHsKICAgICAgICAgIm5hbWUiIDogInJvdXRp
bmdjb3N0LW9yZCIsCiAgICAgICAgICJ2YWx1ZSIgOiAibnVtYmVyIiwKICAgICAgICAgIm1v
ZGUiIDogIm9yZGluYWwiLAogICAgICAgICAibWVhc3VyZXMiIDogImRlbGF5IiwKICAgICAg
ICAgImRlc2NyaXB0aW9uIiA6ICJPcmRpbmFsIHJvdXRpbmcgY29zdCIsCiAgICAgIH0KICAg
IF0KICB9CiAgCiAgCiAgT1BUSU9OUyAvbWFwcyBIVFRQLzEuMQogIEhvc3Q6IGN1c3RvbS5h
bHRvLmV4YW1wbGUuY29tCiAgQWNjZXB0OiBhcHBsaWNhdGlvbi9hbHRvLWRpcmVjdG9yeStq
c29uLGFwcGxpY2F0aW9uL2FsdG8tZXJyb3IranNvbgogIAogIEhUVFAvMS4xIDIwMCBPSwog
IENvbnRlbnQtTGVuZ3RoOiAtLS0tCiAgQ29udGVudC1UeXBlOiBhcHBsaWNhdGlvbi9hbHRv
LWRpcmVjdG9yeStqc29uCiAgewogICAgInJlc291cmNlcyIgOiBbCiAgICAgIHsKICAgICAg
ICAidXJpIiA6ICIvbmV0d29ya21hcC9maWx0ZXJlZCIsCiAgICAgICAgIm1lZGlhLXR5cGVz
IiA6IFsgImFwcGxpY2F0aW9uL2FsdG8tbmV0d29ya21hcCtqc29uIiBdLAogICAgICAgICJh
Y2NlcHRzIiA6IFsgImFwcGxpY2F0aW9uL2FsdG8tbmV0d29ya21hcGZpbHRlcitqc29uIiBd
CiAgICAgIH0sIHsKICAgICAgICAidXJpIiA6ICIvY29zdG1hcC9maWx0ZXJlZCIsCiAgICAg
ICAgIm1lZGlhLXR5cGVzIiA6IFsgImFwcGxpY2F0aW9uL2FsdG8tY29zdG1hcCtqc29uIiBd
LAogICAgICAgICJhY2NlcHRzIiA6IFsgImFwcGxpY2F0aW9uL2FsdG8tY29zdG1hcGZpbHRl
citqc29uIiBdLAogICAgICAgICJjYXBhYmlsaXRpZXMiIDogewogICAgICAgICAgImNvc3Qt
Y29uc3RyYWludHMiIDogdHJ1ZSwKICAgICAgICAgICJjb3N0LXR5cGVzIiA6IFsgInJvdXRp
bmdjb3N0IiwgImhvcGNvdW50IiwgInJvdXRpbmdjb3N0LW9yZCIgXQogICAgICAgIH0KICAg
ICAgfSwgewogICAgICAgICJ1cmkiIDogIi9vcmQvcm91dGluZ2Nvc3QiLAogICAgICAgICJt
ZWRpYS10eXBlcyIgOiBbICJhcHBsaWNhdGlvbi9hbHRvLWNvc3RtYXAranNvbiIgXSwKICAg
ICAgICAiY2FwYWJpbGl0aWVzIiA6IHsKICAgICAgICAgICJjb3N0LXR5cGVzIiA6IFsgInJv
dXRpbmdjb3N0LW9yZCIgXQogICAgICAgIH0KICAgICAgfQogICAgXSwKICAgICJjb3N0LXR5
cGVzIiA6IFsKICAgICAgewogICAgICAgICAibmFtZSIgOiAicm91dGluZ2Nvc3QiLAogICAg
ICAgICAidmFsdWUiIDogIm51bWJlciIsCiAgICAgICAgICJtb2RlIiA6ICJudW1lcmljYWwi
LAogICAgICAgICAibWVhc3VyZXMiIDogImRlbGF5IiwKICAgICAgICAgImRlc2NyaXB0aW9u
IiA6ICJTdGFuZGFyZCByb3V0aW5nIGNvc3QiLAogICAgICB9LCB7CiAgICAgICAgICJuYW1l
IiA6ICJob3Bjb3VudCIsCiAgICAgICAgICJ2YWx1ZSIgOiAibnVtYmVyIiwKICAgICAgICAg
Im1vZGUiIDogIm51bWVyaWNhbCIsCiAgICAgICAgICJtZWFzdXJlcyIgOiAiaG9wcyIsCiAg
ICAgICAgICJkZXNjcmlwdGlvbiIgOiAiU3RhbmRhcmQgaG9wIGNvdW50IiwKICAgICAgfSwg
ewogICAgICAgICAibmFtZSIgOiAicm91dGluZ2Nvc3Qtb3JkIiwKICAgICAgICAgInZhbHVl
IiA6ICJudW1iZXIiLAogICAgICAgICAibW9kZSIgOiAib3JkaW5hbCIsCiAgICAgICAgICJt
ZWFzdXJlcyIgOiAiZGVsYXkiLAogICAgICAgICAiZGVzY3JpcHRpb24iIDogIk9yZGluYWwg
cm91dGluZyBjb3N0IiwKICAgICAgfQogICAgXQogIH0K
--B_3443786615_3929526--



From diego@tid.es  Sat Feb 16 07:00:35 2013
Return-Path: <diego@tid.es>
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 B4E6921F856F for <alto@ietfa.amsl.com>; Sat, 16 Feb 2013 07:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.036
X-Spam-Level: 
X-Spam-Status: No, score=-6.036 tagged_above=-999 required=5 tests=[AWL=0.563,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YS+py1Bj0zWu for <alto@ietfa.amsl.com>; Sat, 16 Feb 2013 07:00:31 -0800 (PST)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id E381721F8C32 for <alto@ietf.org>; Sat, 16 Feb 2013 07:00:30 -0800 (PST)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MIB0020SJ0RRF@tid.hi.inet> for alto@ietf.org; Sat, 16 Feb 2013 16:00:29 +0100 (MET)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id DE.59.01293.D0F9F115; Sat, 16 Feb 2013 16:00:29 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MIB002B9J0TRM@tid.hi.inet> for alto@ietf.org; Sat, 16 Feb 2013 16:00:29 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.165]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0328.009; Sat, 16 Feb 2013 16:00:29 +0100
Date: Sat, 16 Feb 2013 15:00:28 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <CD43C00C.33E4A%w.roome@alcatel-lucent.com>
X-Originating-IP: [10.95.64.115]
To: Wendy Roome <w.roome@alcatel-lucent.com>
Message-id: <E6D8B95470ED0845B3376F61DCAB1A0468D6E39F@EX10-MB2-MAD.hi.inet>
Content-id: <C11E229A8C8AB640AB2AD353F671F303@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, es-ES
Thread-topic: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
Thread-index: AQHOC7pbaas+VaakYU6b+5aCaxR5kph8VJ8A
X-AuditID: 0a5f4068-b7f006d00000050d-9e-511f9f0dba31
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphkeLIzCtJLcpLzFFi42Lhinfg0uWdLx9o0NYnZ/Fw+15WB0aPJUt+ MgUwRnHZpKTmZJalFunbJXBlrD3YxFqwSL1i4tZ29gbGBWpdjJwcEgImEpv+n2KEsMUkLtxb z9bFyMUhJLCBUWLOv81QzndGiV8PrrNCODMZJb5OfcMM0sIioCoxe9cfVhCbDch+1PybHcQW FgiTWLe6F8zmFLCQOHfwLhPECgWJP+ces4DYIgI6EovOXwGzmYF698x5yAZi8wp4S1zbupMN Im4mcejWE0aIuKDEj8n3gOo5gOLqElOm5EKUiEs0t96EGqMoMW1RA1g5o4CsxLv581lBykUE wiW+zsuF2Gok8e/Fc6hrBCSW7DnPDGGLSrx8/A/sEyEBc4kjp16zT2CUmIXkiFlIjpiFcMQs JEfMQnLEAkbWVYxixUlFmekZJbmJmTnpBoZ6GZl6mXmpJZsYITGXsYNx+U6VQ4wCHIxKPLwG 6tKBQqyJZcWVuYcYJTiYlUR4JSbKBwrxpiRWVqUW5ccXleakFh9iZOLglGpglLiqViEr23d6 8ea8UqNbZ+damLAoqGwOmJF7YELUWf11wSb/lJ7USW7X6dCNZFLNFL3SFCDZHGH2yXm7CveT m99O/Z9WtuP8LBPh2pTGjIgtdcxr1Gf6LX8SdzfDbdtCnuINrx+aiJl6r5gvcclwGfOv4xGr m1++kS+tD+k8fZ/T8WHv5RU7lFiKMxINtZiLihMBHEGExZcCAAA=
References: <CD43C00C.33E4A%w.roome@alcatel-lucent.com>
Cc: "<alto@ietf.org>" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a	single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2013 15:00:35 -0000

SGksDQoNCkFzIHNhaWQgc29tZSB0aW1lIGFnbywgSSBkbyBzdXBwb3J0IHRoZSBpZGVhLiBJdCBp
cyBtdWNoIGJldHRlciBzdHJ1Y3R1cmVkIGFuZCBzaW1wbGlmaWVzIHByb2Nlc3NpbmcgKGF0IGJv
dGggc2lkZXMsIEknZCBzYXkpIEFuZCBpdCBwb3NzZXNlcyBhIHRhc3RlIGNsb3NlIHRvIHRoZSBn
b29kLW9sZSBNSU1FIHR5cGVzIEkgY2Fubm90IGF2b2l1ZCB0byBhcHByZWNpYXRlLg0KDQpXaWxs
IGdvIHRocm91Z2ggdGhlIGRldGFpbGVkIHRleHQgbGF0ZXIgYW5kIHByb3ZpZGUgY29tbWVudHMg
KGlmIGFueSkgYnV0IGxldCdzIGdldCB0aGUgYmFsbCByb2xsaW5nIQ0KDQpCZSBnb29kZSwNCg0K
T24gMTUgRmViIDIwMTMsIGF0IDIxOjIzICwgV2VuZHkgUm9vbWUgd3JvdGU6DQoNCj4gVG8gcmV0
dXJuIHRvIHRoaXMgaXNzdWUsIEkgc3VnZ2VzdCB3ZSB1bmlmeSB0aGVtLCBzbyB0aGF0IHdlIGhh
dmUgQ29zdA0KPiBUeXBlcyAtLSBwZXJpb2QuIFRoZSAiTW9kZSIgYmVjb21lcyBhIHByb3BlcnR5
IG9mIHRoZSBDb3N0IFR5cGUuIFNvIGlmIGENCj4gc2VydmVyIHByb3ZpZGVzIG51bWVyaWNhbCAm
IG9yZGluYWwgcm91dGluZ2Nvc3RzLCBpdCBwcm92aWRlcyAqdHdvKg0KPiBzZXBhcmF0ZSBDb3N0
IFR5cGVzLCBzYXkgInJvdXRpbmdjb3N0IiBhbmQgInJvdXRpbmdjb3N0LW9yZCIuDQo+DQo+IEkg
YmVsaWV2ZSB0aGUgcmVzdWx0IHdpbGwgc2ltcGxpZnkgYm90aCBjbGllbnRzIGFuZCBzZXJ2ZXJz
LCBhbmQgbWFrZSBpdA0KPiBlYXNpZXIgZm9yIHNlcnZlcnMgdG8gaW50cm9kdWNlIGFkZGl0aW9u
YWwgY29zdCB0eXBlcy4NCj4NCj4gTXkgc3VnZ2VzdGlvbiBpcyB0byBleHRlbmQgdGhlIEluZm9y
bWF0aW9uIFJlc291cmNlIERpcmVjdG9yeSB3aXRoIGEgbGlzdA0KPiBvZiBkZWZpbml0aW9ucyBm
b3IgZWFjaCBDb3N0IFR5cGUgdGhlIHNlcnZlciBzdXBwb3J0cy4gRWFjaCBDb3N0IFR5cGUNCj4g
ZGVmaW5pdGlvbiB3b3VsZCBnaXZlIHRoZSBuYW1lIG9mIHRoZSBDb3N0IFR5cGUsIHRoZSBtb2Rl
LCBhbmQgb3RoZXINCj4gYXR0cmlidXRlcy4gQ3VycmVudGx5IHRoZSBJbmZvcm1hdGlvbiBSZXNv
dXJjZSBEaXJlY3RvcnkgaXMgYSBkaWN0aW9uYXJ5DQo+IHdpdGggb25lIGl0ZW0sICJyZXNvdXJj
ZXMiLiBTbyBJIHByb3Bvc2UgYWRkaW5nIGEgc2Vjb25kIGl0ZW0gbmFtZWQNCj4gImNvc3QtdHlw
ZXMsIiB3aG9zZSB2YWx1ZSBpcyBhIGxpc3Qgb2YgY29zdC10eXBlIGRlZmluaXRpb25zLCBhcyBp
bg0KPg0KPiAgImNvc3QtdHlwZXMiIDogWw0KPiAgICB7DQo+ICAgICAgIm5hbWUiIDogInJvdXRp
bmdjb3N0IiwNCj4gICAgICAidmFsdWUiIDogIm51bWJlciIsDQo+ICAgICAgIm1vZGUiIDogIm51
bWVyaWNhbCIsDQo+ICAgICAgIm1lYXN1cmVzIiA6ICJkZWxheSIsDQo+ICAgICAgImRlc2NyaXB0
aW9uIiA6ICJTdGFuZGFyZCByb3V0aW5nIGNvc3QiLA0KPiAgICB9LCB7DQo+ICAgICAgIm5hbWUi
IDogImhvcGNvdW50IiwNCj4gICAgICAidmFsdWUiIDogIm51bWJlciIsDQo+ICAgICAgIm1vZGUi
IDogIm51bWVyaWNhbCIsDQo+ICAgICAgIm1lYXN1cmVzIiA6ICJob3BzIiwNCj4gICAgICAiZGVz
Y3JpcHRpb24iIDogIlNpbXBsZSBob3AgY291bnQiLA0KPiAgICB9LCB7DQo+ICAgICAgIm5hbWUi
IDogInJvdXRpbmdjb3N0LW9yZCIsDQo+ICAgICAgInZhbHVlIiA6ICJudW1iZXIiLA0KPiAgICAg
ICJtb2RlIiA6ICJvcmRpbmFsIiwNCj4gICAgICAibWVhc3VyZXMiIDogImRlbGF5IiwNCj4gICAg
ICAiZGVzY3JpcHRpb24iIDogIk9yZGluYWwgcm91dGluZyBjb3N0IiwNCj4gICAgfQ0KPiAgXQ0K
Pg0KPiBUaGVuIHByZXR0eSBtdWNoIGRlbGV0ZSBldmVyeSByZWZlcmVuY2UgdG8gYSBmaWVsZCBu
YW1lZCAiY29zdC1tb2RlIi4NCj4NCj4NCj4NCj4gVG8gZ2V0IHRoZSBiYWxsIHJvbGxpbmcsIEkn
dmUgYXR0YWNoZWQgcHJvcG9zZWQgcmVwbGFjZW1lbnRzIGZvcg0KPg0KPiAgICAgICBTZWN0aW9u
IDUuMS4gQ29zdCBBdHRyaWJ1dGVzDQo+ICAgICAgIFNlY3Rpb24gNi43LjIuIEVuY29kaW5nIFNl
Y3Rpb24gNi43LjMuIEV4YW1wbGUNCj4NCj4gSWYgdGhvc2UgZG9uJ3Qgc3Vydml2ZSB0aGUgbGlz
dCBzZXJ2ZXIsIGxldCBtZSBrbm93IGFuZCBJJ2xsIHB1dCB0aGVtIHVwDQo+IG9uIGEgd2ViIHNl
cnZlci4NCj4NCj4gSWYgeSdhbGwgbGlrZSB0aGlzIGlkZWEsIEknZCBiZSBoYXBweSB0byBoZWxw
IHdpdGggdGhlIGVkaXRpbmcuDQo+DQo+ICAgICAgIC0gV2VuZHkgUm9vbWUNCj4NCj4NCj4+IERh
dGU6IE1vbiwgMjggSmFuIDIwMTMgMjM6MDg6MjMgKzAwMDANCj4+IEZyb206ICJSZWluYWxkbyBQ
ZW5ubyAocmVwZW5ubykiIDxyZXBlbm5vQGNpc2NvLmNvbT4NCj4+IFN1YmplY3Q6IFthbHRvXSBB
TFRPIFByb3RvY29sIE91dHN0YW5kaW5nIElzc3VlIElJOiBVbmlmeWluZyBjb3N0LW1vZGUNCj4+
ICAgICAgYW5kIGNvc3QtdHlwZSB0byBhIHNpbmdsZSB0eXBlDQo+Pg0KPj4gRGlzY3Vzc2lvbiBJ
STogVW5pZnlpbmcgY29zdC1tb2RlIGFuZCBjb3N0LXR5cGUgdG8gYSBzaW5nbGUgdHlwZQ0KPj4N
Cj4+IGUuZy4sIHJvdXRpbmdjb3N0LW51bSBhbmQgcm91dGluZ2Nvc3Qtb3JkDQo+Pg0KPj4gSGF2
aW5nIGEgc2luZ2xlIHR5cGUgc2ltcGxlcyB0aGUgcHJvdG9jb2wgc2luY2UgdGhlcmUgaXMganVz
dCBvbmUNCj4+IHBhcmFtZXRlciB3aGVuIGluZGljYXRpbmcgY29zdC4gQnV0IGl0IHdpbGwgaW1w
YWN0IGN1cnJlbnQNCj4+IGltcGxlbWVudGF0aW9ucyBhbmQgbWlnaHQgbG9vc2UgZmxleGliaWxp
dHkuDQo+Pg0KPj4gUHJvcG9zYWw6IExlYXZlIGl0IGFzIGlzLg0KPj4NCj4+IFRoYW5rcywNCj4+
DQo+PiBSZWluYWxkbw0KPg0KPiA8c2VjdC01LTEudHh0PjxzZWN0LTYtNy0yLnR4dD48c2VjdC02
LTctMy50eHQ+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj4gYWx0byBtYWlsaW5nIGxpc3QNCj4gYWx0b0BpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FsdG8NCg0KDQotLQ0KIkVzdGEgdmV6IG5vIGZhbGxhcmVt
b3MsIERvY3RvciBJbmZpZXJubyINCg0KRHIgRGllZ28gUi4gTG9wZXoNClRlbGVmb25pY2EgSStE
DQpodHRwOi8vcGVvcGxlLnRpZC5lcy9kaWVnby5sb3Blei8NCg0KZS1tYWlsOiBkaWVnb0B0aWQu
ZXMNClRlbDogICAgKzM0IDkxMyAxMjkgMDQxDQpNb2JpbGU6ICszNCA2ODIgMDUxIDA5MQ0KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KDQpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KDQpFc3RlIG1lbnNhamUgc2UgZGlyaWdlIGV4Y2x1c2l2YW1l
bnRlIGEgc3UgZGVzdGluYXRhcmlvLiBQdWVkZSBjb25zdWx0YXIgbnVlc3RyYSBwb2zDrXRpY2Eg
ZGUgZW52w61vIHkgcmVjZXBjacOzbiBkZSBjb3JyZW8gZWxlY3Ryw7NuaWNvIGVuIGVsIGVubGFj
ZSBzaXR1YWRvIG3DoXMgYWJham8uDQpUaGlzIG1lc3NhZ2UgaXMgaW50ZW5kZWQgZXhjbHVzaXZl
bHkgZm9yIGl0cyBhZGRyZXNzZWUuIFdlIG9ubHkgc2VuZCBhbmQgcmVjZWl2ZSBlbWFpbCBvbiB0
aGUgYmFzaXMgb2YgdGhlIHRlcm1zIHNldCBvdXQgYXQ6DQpodHRwOi8vd3d3LnRpZC5lcy9FUy9Q
QUdJTkFTL2Rpc2NsYWltZXIuYXNweA0K

From enrico.marocco@telecomitalia.it  Mon Feb 18 06:28:11 2013
Return-Path: <enrico.marocco@telecomitalia.it>
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 D1C9121F8A4F for <alto@ietfa.amsl.com>; Mon, 18 Feb 2013 06:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.719
X-Spam-Level: 
X-Spam-Status: No, score=-101.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BNEDmtDyBthg for <alto@ietfa.amsl.com>; Mon, 18 Feb 2013 06:28:11 -0800 (PST)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id A897121F8971 for <alto@ietf.org>; Mon, 18 Feb 2013 06:28:10 -0800 (PST)
Received: from grfhub703rm001.griffon.local (10.19.3.10) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 18 Feb 2013 15:28:09 +0100
Received: from MacLab.local (10.229.8.19) by smtp.telecomitalia.it (10.19.9.236) with Microsoft SMTP Server (TLS) id 8.3.297.1; Mon, 18 Feb 2013 15:28:09 +0100
Message-ID: <51223A78.9070503@telecomitalia.it>
Date: Mon, 18 Feb 2013 15:28:08 +0100
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010200050004010801050507"
X-TI-Disclaimer: Disclaimer1
Subject: [alto]  Agenda requests for IETF 86
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 18 Feb 2013 14:28:12 -0000

--------------ms010200050004010801050507
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

if you have any requests for agenda slots at the next IETF meeting,
please send them to Vijay and me by Monday, February 25. As usual,
priority will be given to charter items, and to topics that have been
already presented and discussed on the list.

--=20
Ciao,
Enrico






--------------ms010200050004010801050507
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINdzCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIHOzCCBiOgAwIBAgIDBKfoMA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTIwODA3MDkxNTQz
WhcNMTMwODA4MDczMzM3WjB1MRkwFwYDVQQNExBvWkNPVnNYc09NME9mcExwMSgwJgYDVQQD
DB9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MS4wLAYJKoZIhvcNAQkBFh9lbnJp
Y28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEAshI2shfUZ7P5RVcP04fJ4OfYmK/RUyokJpuJE4KaSOLArtpNtlYo6MtXfmZzA8y/
5HChSAmPvqUwhMMYh1LurWbOdX4uKXO1gsFrPOtxTa6qin6lXaJ3bo2pKnkN9mQkjvm0E23r
rrT3MC6h6UfyFAcvs01+yq9wVuxxRdC4LZTGAbXGkE34GQAnBy9eqvJ+m351hPaaVw9u8CWN
uyv9YKLXpicS/q8j2EOpFBCkZVp0E8fViSXViGtuhfbW6R+TjTXJZN06DEqb/vpRSWkvBDf0
UqDFrgmlmSnXJ/xpaygAJcHyE5qjRXkIV7adTkg9Z/Z2lJXvtDUdHbNBiYcVOwIDAQABo4ID
ujCCA7YwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBT1YgWCbkVCN8iNgS49Fh9R2ZC8wTAfBgNVHSMEGDAWgBRTcu2S
nODaywFcfH6WNU7y1LhRgjAqBgNVHREEIzAhgR9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRh
bGlhLml0MIICIQYDVR0gBIICGDCCAhQwggIQBgsrBgEEAYG1NwECAjCCAf8wLgYIKwYBBQUH
AgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgfcGCCsGAQUFBwICMIHq
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRp
ZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24g
cmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkg
Zm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcg
cGFydHkgb2JsaWdhdGlvbnMuMIGcBggrBgEFBQcCAjCBjzAnFiBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eTADAgECGmRMaWFiaWxpdHkgYW5kIHdhcnJhbnRpZXMgYXJlIGxp
bWl0ZWQhIFNlZSBzZWN0aW9uICJMZWdhbCBhbmQgTGltaXRhdGlvbnMiIG9mIHRoZSBTdGFy
dENvbSBDQSBwb2xpY3kuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wu
Y29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6
Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2
aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0
MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOC
AQEAIn8FoRaqvQzo8aGNi4EbPhIMX8aPIMhX3L/N+8sMyFe3cpSyjij47DW1K330zDJnoyZs
kuI10EzfK0wwY+D2qMQPGAmPDkix5t2dYQj6DKh1yBlBwAf7c65Ty1kpgtdymSptDJKVZcK6
R2CJ91oRBCZIObcWrG/0FZIr55+InAYyLDrlk34MwBmINhBZ4oRJdrzG6OC7cK4vG1ZWrAFE
GHVwx1uG2NXRUXQTH9DGYcwwfPo4uinFCwHZAJ2Il/J0Mqui5x+N/7p+WUlGRyb67qxg7ect
f2095+YDnbqIKIz7fGzw8XTwpjYbvWZplkG93qRXr8MRD9ukgxpxpHG2dTGCA90wggPZAgEB
MIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwSn6DAJBgUrDgMCGgUA
oIICHTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzAyMTgx
NDI4MDhaMCMGCSqGSIb3DQEJBDEWBBSIyfWbdLb9Bwvt3vZ8t+bQwWjwKzBsBgkqhkiG9w0B
CQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEE
AYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9T
dGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBKfoMIGn
BgsqhkiG9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2
BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENB
AgMEp+gwDQYJKoZIhvcNAQEBBQAEggEAaIGTA+1Y6/cOZX21LIj5uoJUSYqTo+iyBmxZKaBr
XGh70E+hVH0oqDVVvZN8VjuATMeZT/+ep/D691i9ZDRwCiTVCfQhlOv2N3gS6rYl/uc0U413
SkoWaUuJS1RddS3lHdv8NQGNaBCw0yNST5yYny8ccJ1T9+bUB6/w57ePv3nIb1vx5KCUcJ5K
Mb4+iWxPMNGrOQY69Y+xAPvgCN/SdgtN82wskCKvlKsmVOuqPkSRZ2WcoU2bcJQ8uPclL4A8
6uwA2Bhy+HtXqxacHGJ3kN4eJkNo6dLYlckIxIE0u98vzUfxqS54jnmU40yrZdxyGlBxpGG6
vekVzlUGJUnXJQAAAAAAAA==
--------------ms010200050004010801050507--

From haibin.song@huawei.com  Mon Feb 18 19:17:32 2013
Return-Path: <haibin.song@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 A0FD621E804B for <alto@ietfa.amsl.com>; Mon, 18 Feb 2013 19:17:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ELdQaf-X8Rvv for <alto@ietfa.amsl.com>; Mon, 18 Feb 2013 19:17:32 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF4F21E80B9 for <alto@ietf.org>; Mon, 18 Feb 2013 19:17:19 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOO77114; Tue, 19 Feb 2013 03:17:18 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 19 Feb 2013 03:16:47 +0000
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 19 Feb 2013 11:17:17 +0800
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.101]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.01.0323.007; Tue, 19 Feb 2013 11:17:13 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: alto <alto@ietf.org>
Thread-Topic: new individual document notification
Thread-Index: Ac4OT5xZs3E+i3HCTuCPKCWp97Tbfg==
Date: Tue, 19 Feb 2013 03:17:13 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F245B383C@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.75]
Content-Type: multipart/alternative; boundary="_000_E33E01DFD5BEA24B9F3F18671078951F245B383Cnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: [alto] new individual document notification
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2013 03:17:32 -0000

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

Hi all,

We have submitted a new individual document.
http://tools.ietf.org/html/draft-song-alto-i2rs-00

Which is aimed to focus on gathering infrastructure information for ALTO se=
rvice. I think it could be called the south bound interface for ALTO. This =
document is also related to i2rs wg. Anybody who has the same interest to c=
ontribute is welcome to join us, we plan to give an update by next Monday.

Regards!
-Haibin


--_000_E33E01DFD5BEA24B9F3F18671078951F245B383Cnkgeml501mbschi_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" 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 12 (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;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-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;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@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" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi all,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We have submitted a new individ=
ual document.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><a href=3D"http://tools.ietf.or=
g/html/draft-song-alto-i2rs-00">http://tools.ietf.org/html/draft-song-alto-=
i2rs-00</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Which is aimed to focus on gath=
ering infrastructure information for ALTO service. I think it could be call=
ed the south bound interface for ALTO. This document is also related to i2r=
s wg. Anybody who has the same interest
 to contribute is welcome to join us, we plan to give an update by next Mon=
day.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards!<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">-Haibin<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_E33E01DFD5BEA24B9F3F18671078951F245B383Cnkgeml501mbschi_--

From Jan.Seedorf@neclab.eu  Tue Feb 19 02:35:42 2013
Return-Path: <Jan.Seedorf@neclab.eu>
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 AA79B21F8CC8 for <alto@ietfa.amsl.com>; Tue, 19 Feb 2013 02:35:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.479
X-Spam-Level: 
X-Spam-Status: No, score=-103.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tTnaeWi5ryO1 for <alto@ietfa.amsl.com>; Tue, 19 Feb 2013 02:35:42 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id CE03821F8CC7 for <alto@ietf.org>; Tue, 19 Feb 2013 02:35:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 3DF361032CC for <alto@ietf.org>; Tue, 19 Feb 2013 11:35:41 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iOjqaiu10l9e for <alto@ietf.org>; Tue, 19 Feb 2013 11:35:41 +0100 (CET)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 1B5091032CB for <alto@ietf.org>; Tue, 19 Feb 2013 11:35:36 +0100 (CET)
Received: from PALLENE.office.hd ([169.254.1.80]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Tue, 19 Feb 2013 11:35:35 +0100
From: Jan Seedorf <Jan.Seedorf@neclab.eu>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: New Draft "ALTO for LMAP"
Thread-Index: Ac4Oi6mcJ/Qe+4WcQQ6yrXjfzkiEXAAASSZA
Date: Tue, 19 Feb 2013 10:35:23 +0000
Message-ID: <2779C9F0771F974CAD742BAE6D9904FE5544C8B2@PALLENE.office.hd>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.2.227]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [alto] New Draft "ALTO for LMAP"
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2013 10:35:43 -0000

RGVhciBhbGwsDQoNCldlIGhhdmUgc3VibWl0dGVkIGEgZHJhZnQgdGhhdCBvdXRsaW5lcyBob3cg
QUxUTyBjb3VsZCBiZSB1c2VkIHRvIGV4cG9ydC9leHBsb2l0IExNQVAgbWVhc3VyZW1lbnQgcmVz
dWx0cy4gQ29tbWVudHMgYXJlIHZlcnkgd2VsY29tZS4NCg0KCS0gSmFuDQoNCi0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcgW21haWx0bzpp
bnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KU2VudDogTW9uZGF5LCBGZWJydWFyeSAxOCwgMjAx
MyAzOjU1IFBNDQpUbzogZW5yaWNvLm1hcm9jY29AdGVsZWNvbWl0YWxpYS5pdA0KQ2M6IHZrZ0Bi
ZWxsLWxhYnMuY29tOyBKYW4gU2VlZG9yZg0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90aWZpY2F0
aW9uIGZvciBkcmFmdC1zZWVkb3JmLWxtYXAtYWx0by0wMC50eHQNCg0KDQpBIG5ldyB2ZXJzaW9u
IG9mIEktRCwgZHJhZnQtc2VlZG9yZi1sbWFwLWFsdG8tMDAudHh0DQpoYXMgYmVlbiBzdWNjZXNz
ZnVsbHkgc3VibWl0dGVkIGJ5IEVucmljbyBNYXJvY2NvIGFuZCBwb3N0ZWQgdG8gdGhlDQpJRVRG
IHJlcG9zaXRvcnkuDQoNCkZpbGVuYW1lOgkgZHJhZnQtc2VlZG9yZi1sbWFwLWFsdG8NClJldmlz
aW9uOgkgMDANClRpdGxlOgkJIEFMVE8gZm9yIExNQVANCkNyZWF0aW9uIGRhdGU6CSAyMDEzLTAy
LTE4DQpHcm91cDoJCSBJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCk51bWJlciBvZiBwYWdlczogMTIN
ClVSTDogICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh
ZnQtc2VlZG9yZi1sbWFwLWFsdG8tMDAudHh0DQpTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtc2VlZG9yZi1sbWFwLWFsdG8NCkh0bWxpemVkOiAg
ICAgICAgaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtc2VlZG9yZi1sbWFwLWFsdG8t
MDANCg0KDQpBYnN0cmFjdDoNCiAgIEluIHRoZSBjb250ZXh0IG9mIExhcmdlLVNjYWxlIE1lYXN1
cmVtZW50IG9mIEJyb2FkYmFuZCBQZXJmb3JtYW5jZQ0KICAgKExNQVApLCBtZWFzdXJtZW50IHJl
c3VsdHMgYXJlIGN1cnJlbnRseSBtYWRlIGF2YWlsYWJsZSB0byB0aGUgcHVibGljDQogICBlaXRo
ZXIgYXQgdGhlIGZpbmVzdCBncmFudWxhcml0eSBsZXZlbCAoZS5nLiBhcyBhIGxpc3Qgb2YgcmVz
dWx0cyBvZg0KICAgYWxsIGluZGl2aWR1YWwgdGVzdHMpLCBvciBpbiBhIHZlcnkgaGlnaCBsZXZl
bCBodW1hbi1yZWFkYWJsZSBmb3JtYXQNCiAgIChlLmcuIGFzIFBERiByZXBvcnRzKS4NCg0KICAg
VGhpcyBkb2N1bWVudCBhcmd1ZXMgdGhhdCB0aGVyZSBpcyBhIG5lZWQgZm9yIGFuIGludGVybWVk
aWF0ZSB3YXkgdG8NCiAgIHByb3ZpZGUgYWNjZXNzIHRvIGxhcmdlLXNjYWxlIG5ldHdvcmsgbWVh
c3VyZW1lbnQgcmVzdWx0cywgZmxleGlibGUNCiAgIGVub3VnaCB0byBlbmFibGUgcXVlcnlpbmcg
b2Ygc3BlY2lmaWMgYW5kIHBvc3NpYmx5IGFnZ3JlZ2F0ZWQgZGF0YS4NCiAgIFRoZSBBcHBsaWNh
dGlvbi1MYXllciBUcmFmZmljIE9wdGltaXphdGlvbiAoQUxUTykgUHJvdG9jb2wsIGRlZmluZWQN
CiAgIHdpdGggdGhlIGdvYWwgdG8gcHJvdmlkZSBhcHBsaWNhdGlvbnMgd2l0aCBuZXR3b3JrIGlu
Zm9ybWF0aW9uLCBzZWVtcw0KICAgYSBnb29kIGNhbmRpZGF0ZSB0byBmdWxmaWxsIHN1Y2ggYSBy
b2xlLg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgDQoNCg0KVGhlIElFVEYgU2VjcmV0YXJp
YXQNCg0K

From richard.alimi@gmail.com  Tue Feb 19 14:52:27 2013
Return-Path: <richard.alimi@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 53A8C21E803C for <alto@ietfa.amsl.com>; Tue, 19 Feb 2013 14:52:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZKCifSTeeKQO for <alto@ietfa.amsl.com>; Tue, 19 Feb 2013 14:52:21 -0800 (PST)
Received: from mail-vc0-f171.google.com (mail-vc0-f171.google.com [209.85.220.171]) by ietfa.amsl.com (Postfix) with ESMTP id 1B4B921F8788 for <alto@ietf.org>; Tue, 19 Feb 2013 14:52:16 -0800 (PST)
Received: by mail-vc0-f171.google.com with SMTP id p1so4725174vcq.30 for <alto@ietf.org>; Tue, 19 Feb 2013 14:52:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=baAnWS4jU3Z2GUn3kbY/OS/pEEqPqcFnIH8z03lCxL4=; b=fXK+FCk3b2jhR2UG5PrPnDcxzg3mxWzg9DNlPOJHCB/F3W/5APGwlctWgBvJOXjZ5r v23ibpnxsQm++2y7xZmi1J1KDqr2IutlREzjtd523CdNYgOl/enmubh2gzk4nl7+U3Oa HXgoeSlzin7pOhVB05vmKsSRwJTlQxENfx+iCtP0jx4w17rI0MeNJUOMyflnKiMfKCS6 2DcBOUH+yELGqMyfcJv67zLyI9h8fCz1qnOJGk16rdVyvFVba8cVAK8i6YlQhwHFntN5 8KMfDzeOHQf9yD5sBJPzEJ+epC4GCIzka6eCt+FVwM4DPP9iVAccAehB9q5Q4zp5X+M5 kI4Q==
X-Received: by 10.52.73.73 with SMTP id j9mr19912901vdv.124.1361314335436; Tue, 19 Feb 2013 14:52:15 -0800 (PST)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.58.209.169 with HTTP; Tue, 19 Feb 2013 14:51:55 -0800 (PST)
In-Reply-To: <CD43C00C.33E4A%w.roome@alcatel-lucent.com>
References: <mailman.107.1359489625.24927.alto@ietf.org> <CD43C00C.33E4A%w.roome@alcatel-lucent.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Tue, 19 Feb 2013 14:51:55 -0800
X-Google-Sender-Auth: WJ-Tpgik9hoFW-Nu6wC1tOfFi68
Message-ID: <CA+cvDaa_di9L3wnOHzcCURtuFmckogVjbLc7hodLOep9_Ykwnw@mail.gmail.com>
To: Wendy Roome <w.roome@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=bcaec501c5bc64307004d61bb118
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2013 22:52:27 -0000

--bcaec501c5bc64307004d61bb118
Content-Type: text/plain; charset=ISO-8859-1

This was supposed to go out last night, but evidently the "Reply All"
button was a bit too elusive....

On Fri, Feb 15, 2013 at 12:23 PM, Wendy Roome <w.roome@alcatel-lucent.com>wrote:

> To return to this issue, I suggest we unify them, so that we have Cost
> Types -- period. The "Mode" becomes a property of the Cost Type. So if a
> server provides numerical & ordinal routingcosts, it provides *two*
> separate Cost Types, say "routingcost" and "routingcost-ord".
>
> I believe the result will simplify both clients and servers, and make it
> easier for servers to introduce additional cost types.
>

I believe that having them separate is a bit more 'normalized' of a form
and has some important benefits. That is, one just has to define what
'hopcount' means once, and then a server can expose that metric in
different forms.  By creating a single opaque identifier, one now has to
register 'hopcount' for each and every "mode" that comes along.  This also
makes it more difficult for a client to understand that if it wants a
particular cost type (but can handle different forms), it has to know
beforehand the exact set of identifiers under which it can find all of the
forms.

For example, consider the following:
(1) Person A registers cost type 'some-new-type' and describes it with
numerical costs
(2) Person B comes along and wants ordinal costs 'with 'some-new-type'.
Person B then has to go through the registration process to create
'some-new-type-ord'.  [ A side point - do we care about the registry
staying clean? Do we have rules on how to construct appropriate cost type
identifiers so they convey whether they are ordinal or numerical? ]
(3) At some point down the line, the Reincarnated ALTO Working Group
decides to add a new 'mode' of cost, such as an array of costs that
indicates the cost's historical value over the past week.
(4) Person C looks at the registry and figures out that they want
'some-new-type' to be available in this new mode. Person C then has to go
and register 'some-new-type-historical' before it can be used. [ And this
is going to happen for each cost type. ]

In short, I think the registry for cost types is going to get messy and
it's going to make it more difficult for a client to say "I want the
hopcount costs but I don't care whether the server gives me the actual
costs, or is just going to rank them".

All that said, I understand this has been brought up in the past and there
are some things that it simplifies (which have been discussed in an earlier
thread) and if there is good consensus for doing this in the working group,
then we can certainly adopt the changes.

Thanks,
Rich


>
> My suggestion is to extend the Information Resource Directory with a list
> of definitions for each Cost Type the server supports. Each Cost Type
> definition would give the name of the Cost Type, the mode, and other
> attributes. Currently the Information Resource Directory is a dictionary
> with one item, "resources". So I propose adding a second item named
> "cost-types," whose value is a list of cost-type definitions, as in
>
>   "cost-types" : [
>     {
>       "name" : "routingcost",
>       "value" : "number",
>       "mode" : "numerical",
>       "measures" : "delay",
>       "description" : "Standard routing cost",
>     }, {
>       "name" : "hopcount",
>       "value" : "number",
>       "mode" : "numerical",
>       "measures" : "hops",
>       "description" : "Simple hop count",
>     }, {
>       "name" : "routingcost-ord",
>       "value" : "number",
>       "mode" : "ordinal",
>       "measures" : "delay",
>       "description" : "Ordinal routing cost",
>     }
>   ]
>
> Then pretty much delete every reference to a field named "cost-mode".
>
>
>
> To get the ball rolling, I've attached proposed replacements for
>
>         Section 5.1. Cost Attributes
>         Section 6.7.2. Encoding Section 6.7.3. Example
>
> If those don't survive the list server, let me know and I'll put them up
> on a web server.
>
> If y'all like this idea, I'd be happy to help with the editing.
>
>         - Wendy Roome
>
>
> >Date: Mon, 28 Jan 2013 23:08:23 +0000
> >From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
> >Subject: [alto] ALTO Protocol Outstanding Issue II: Unifying cost-mode
> >       and cost-type to a single type
> >
> >Discussion II: Unifying cost-mode and cost-type to a single type
> >
> >e.g., routingcost-num and routingcost-ord
> >
> >Having a single type simples the protocol since there is just one
> >parameter when indicating cost. But it will impact current
> >implementations and might loose flexibility.
> >
> >Proposal: Leave it as is.
> >
> >Thanks,
> >
> >Reinaldo
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>

--bcaec501c5bc64307004d61bb118
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div style>This was supposed to go out last night, but evi=
dently the &quot;Reply All&quot; button was a bit too elusive....</div><br>=
<div class=3D"gmail_extra"><div class=3D"gmail_quote">On Fri, Feb 15, 2013 =
at 12:23 PM, Wendy Roome <span dir=3D"ltr">&lt;<a href=3D"mailto:w.roome@al=
catel-lucent.com" target=3D"_blank">w.roome@alcatel-lucent.com</a>&gt;</spa=
n> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">To return to this issue, I suggest we unify them, so that =
we have Cost<br>


Types -- period. The &quot;Mode&quot; becomes a property of the Cost Type. =
So if a<br>
server provides numerical &amp; ordinal routingcosts, it provides *two*<br>
separate Cost Types, say &quot;routingcost&quot; and &quot;routingcost-ord&=
quot;.<br>
<br>
I believe the result will simplify both clients and servers, and make it<br=
>
easier for servers to introduce additional cost types.<br></blockquote><div=
><br></div><div><div style=3D"font-family:arial,sans-serif;font-size:13px">=
I believe that having them separate is a bit more &#39;normalized&#39; of a=
 form and has some important benefits. That is, one just has to define what=
 &#39;hopcount&#39; means once, and then a server can expose that metric in=
 different forms. =A0By creating a single opaque identifier, one now has to=
 register &#39;hopcount&#39; for each and every &quot;mode&quot; that comes=
 along. =A0This also makes it more difficult for a client to understand tha=
t if it wants a particular cost type (but can handle different forms), it h=
as to know beforehand the exact set of identifiers under which it can find =
all of the forms.</div>

<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">For example, consider =
the following:</div><div style=3D"font-family:arial,sans-serif;font-size:13=
px">

(1) Person A registers cost type &#39;some-new-type&#39; and describes it w=
ith numerical costs</div><div style=3D"font-family:arial,sans-serif;font-si=
ze:13px">(2) Person B comes along and wants ordinal costs &#39;with &#39;so=
me-new-type&#39;. Person B then has to go through the registration process =
to create &#39;some-new-type-ord&#39;. =A0[ A side point - do we care about=
 the registry staying clean? Do we have rules on how to construct appropria=
te cost type identifiers so they convey whether they are ordinal or numeric=
al? ]</div>

<div style=3D"font-family:arial,sans-serif;font-size:13px">(3) At some poin=
t down the line, the Reincarnated ALTO Working Group decides to add a new &=
#39;mode&#39; of cost, such as an array of costs that indicates the cost&#3=
9;s historical value over the past week.</div>

<div style=3D"font-family:arial,sans-serif;font-size:13px">(4) Person C loo=
ks at the registry and figures out that they want &#39;some-new-type&#39; t=
o be available in this new mode. Person C then has to go and register &#39;=
some-new-type-historical&#39; before it can be used. [ And this is going to=
 happen for each cost type. ]</div>

<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">In short, I think the =
registry for cost types is going to get messy and it&#39;s going to make it=
 more difficult for a client to say &quot;I want the hopcount costs but I d=
on&#39;t care whether the server gives me the actual costs, or is just goin=
g to rank them&quot;.</div>

<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">All that said, I under=
stand this has been brought up in the past and there are some things that i=
t simplifies (which have been discussed in an earlier thread) and if there =
is good consensus for doing this in the working group, then we can certainl=
y adopt the changes.</div>

</div><div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div>=
<div style=3D"font-family:arial,sans-serif;font-size:13px">Thanks,</div><di=
v style=3D"font-family:arial,sans-serif;font-size:13px">Rich</div><div>=A0<=
/div>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
My suggestion is to extend the Information Resource Directory with a list<b=
r>
of definitions for each Cost Type the server supports. Each Cost Type<br>
definition would give the name of the Cost Type, the mode, and other<br>
attributes. Currently the Information Resource Directory is a dictionary<br=
>
with one item, &quot;resources&quot;. So I propose adding a second item nam=
ed<br>
&quot;cost-types,&quot; whose value is a list of cost-type definitions, as =
in<br>
<br>
=A0 &quot;cost-types&quot; : [<br>
=A0 =A0 {<br>
=A0 =A0 =A0 &quot;name&quot; : &quot;routingcost&quot;,<br>
=A0 =A0 =A0 &quot;value&quot; : &quot;number&quot;,<br>
=A0 =A0 =A0 &quot;mode&quot; : &quot;numerical&quot;,<br>
=A0 =A0 =A0 &quot;measures&quot; : &quot;delay&quot;,<br>
=A0 =A0 =A0 &quot;description&quot; : &quot;Standard routing cost&quot;,<br=
>
=A0 =A0 }, {<br>
=A0 =A0 =A0 &quot;name&quot; : &quot;hopcount&quot;,<br>
=A0 =A0 =A0 &quot;value&quot; : &quot;number&quot;,<br>
=A0 =A0 =A0 &quot;mode&quot; : &quot;numerical&quot;,<br>
=A0 =A0 =A0 &quot;measures&quot; : &quot;hops&quot;,<br>
=A0 =A0 =A0 &quot;description&quot; : &quot;Simple hop count&quot;,<br>
=A0 =A0 }, {<br>
=A0 =A0 =A0 &quot;name&quot; : &quot;routingcost-ord&quot;,<br>
=A0 =A0 =A0 &quot;value&quot; : &quot;number&quot;,<br>
=A0 =A0 =A0 &quot;mode&quot; : &quot;ordinal&quot;,<br>
=A0 =A0 =A0 &quot;measures&quot; : &quot;delay&quot;,<br>
=A0 =A0 =A0 &quot;description&quot; : &quot;Ordinal routing cost&quot;,<br>
=A0 =A0 }<br>
=A0 ]<br>
<br>
Then pretty much delete every reference to a field named &quot;cost-mode&qu=
ot;.<br>
<br>
<br>
<br>
To get the ball rolling, I&#39;ve attached proposed replacements for<br>
<br>
=A0 =A0 =A0 =A0 Section 5.1. Cost Attributes<br>
=A0 =A0 =A0 =A0 Section 6.7.2. Encoding Section 6.7.3. Example<br>
<br>
If those don&#39;t survive the list server, let me know and I&#39;ll put th=
em up<br>
on a web server.<br>
<br>
If y&#39;all like this idea, I&#39;d be happy to help with the editing.<br>
<br>
=A0 =A0 =A0 =A0 - Wendy Roome<br>
<br>
<br>
&gt;Date: Mon, 28 Jan 2013 23:08:23 +0000<br>
&gt;From: &quot;Reinaldo Penno (repenno)&quot; &lt;<a href=3D"mailto:repenn=
o@cisco.com">repenno@cisco.com</a>&gt;<br>
&gt;Subject: [alto] ALTO Protocol Outstanding Issue II: Unifying cost-mode<=
br>
&gt; =A0 =A0 =A0 and cost-type to a single type<br>
&gt;<br>
&gt;Discussion II: Unifying cost-mode and cost-type to a single type<br>
&gt;<br>
&gt;e.g., routingcost-num and routingcost-ord<br>
&gt;<br>
&gt;Having a single type simples the protocol since there is just one<br>
&gt;parameter when indicating cost. But it will impact current<br>
&gt;implementations and might loose flexibility.<br>
&gt;<br>
&gt;Proposal: Leave it as is.<br>
&gt;<br>
&gt;Thanks,<br>
&gt;<br>
&gt;Reinaldo<br>
<br>
<br>_______________________________________________<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" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
<br></blockquote></div><br></div></div>

--bcaec501c5bc64307004d61bb118--

From enrico.marocco@telecomitalia.it  Wed Feb 20 01:02:33 2013
Return-Path: <enrico.marocco@telecomitalia.it>
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 EE2EC21F8797 for <alto@ietfa.amsl.com>; Wed, 20 Feb 2013 01:02:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.719
X-Spam-Level: 
X-Spam-Status: No, score=-101.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uH0unD5loj92 for <alto@ietfa.amsl.com>; Wed, 20 Feb 2013 01:02:33 -0800 (PST)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id E240221F8780 for <alto@ietf.org>; Wed, 20 Feb 2013 01:02:32 -0800 (PST)
Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 20 Feb 2013 10:02:32 +0100
Received: from MacLab.local (163.162.180.246) by smtp.telecomitalia.it (10.19.9.235) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 20 Feb 2013 10:02:31 +0100
Message-ID: <51249127.1020309@telecomitalia.it>
Date: Wed, 20 Feb 2013 10:02:31 +0100
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: <alto@ietf.org>
References: <E33E01DFD5BEA24B9F3F18671078951F245B383C@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <E33E01DFD5BEA24B9F3F18671078951F245B383C@nkgeml501-mbs.china.huawei.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020401050909000804090103"
X-TI-Disclaimer: Disclaimer1
Subject: Re: [alto] new individual document notification
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2013 09:02:34 -0000

--------------ms020401050909000804090103
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I believe this effort is very useful. The i2rs WG is in fact considering
the ALTO protocol as a candidate for some of the use cases they are
focusing on (see e.g.
http://tools.ietf.org/html/draft-amante-i2rs-topology-use-cases-00#sectio=
n-4.3).
The more information ALTO experts can provide to help them make an
informed decision, the better. I would encourage anyone who have been
involved in the development of the ALTO protocol to coordinate with
Haibin and Young, and help people outside the WG understand whether the
work done here could be a good match for their needs.

Enrico

On 2/19/13 4:17 AM, Songhaibin (A) wrote:
> Hi all,
>=20
> =20
>=20
> We have submitted a new individual document.
>=20
> http://tools.ietf.org/html/draft-song-alto-i2rs-00
>=20
> =20
>=20
> Which is aimed to focus on gathering infrastructure information for ALT=
O
> service. I think it could be called the south bound interface for ALTO.=

> This document is also related to i2rs wg. Anybody who has the same
> interest to contribute is welcome to join us, we plan to give an update=

> by next Monday.
>=20
> =20
>=20
> Regards!
>=20
> -Haibin
>=20
> =20
>=20



--------------ms020401050909000804090103
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINdzCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIHOzCCBiOgAwIBAgIDBKfoMA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTIwODA3MDkxNTQz
WhcNMTMwODA4MDczMzM3WjB1MRkwFwYDVQQNExBvWkNPVnNYc09NME9mcExwMSgwJgYDVQQD
DB9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MS4wLAYJKoZIhvcNAQkBFh9lbnJp
Y28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEAshI2shfUZ7P5RVcP04fJ4OfYmK/RUyokJpuJE4KaSOLArtpNtlYo6MtXfmZzA8y/
5HChSAmPvqUwhMMYh1LurWbOdX4uKXO1gsFrPOtxTa6qin6lXaJ3bo2pKnkN9mQkjvm0E23r
rrT3MC6h6UfyFAcvs01+yq9wVuxxRdC4LZTGAbXGkE34GQAnBy9eqvJ+m351hPaaVw9u8CWN
uyv9YKLXpicS/q8j2EOpFBCkZVp0E8fViSXViGtuhfbW6R+TjTXJZN06DEqb/vpRSWkvBDf0
UqDFrgmlmSnXJ/xpaygAJcHyE5qjRXkIV7adTkg9Z/Z2lJXvtDUdHbNBiYcVOwIDAQABo4ID
ujCCA7YwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBT1YgWCbkVCN8iNgS49Fh9R2ZC8wTAfBgNVHSMEGDAWgBRTcu2S
nODaywFcfH6WNU7y1LhRgjAqBgNVHREEIzAhgR9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRh
bGlhLml0MIICIQYDVR0gBIICGDCCAhQwggIQBgsrBgEEAYG1NwECAjCCAf8wLgYIKwYBBQUH
AgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgfcGCCsGAQUFBwICMIHq
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRp
ZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24g
cmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkg
Zm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcg
cGFydHkgb2JsaWdhdGlvbnMuMIGcBggrBgEFBQcCAjCBjzAnFiBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eTADAgECGmRMaWFiaWxpdHkgYW5kIHdhcnJhbnRpZXMgYXJlIGxp
bWl0ZWQhIFNlZSBzZWN0aW9uICJMZWdhbCBhbmQgTGltaXRhdGlvbnMiIG9mIHRoZSBTdGFy
dENvbSBDQSBwb2xpY3kuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wu
Y29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6
Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2
aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0
MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOC
AQEAIn8FoRaqvQzo8aGNi4EbPhIMX8aPIMhX3L/N+8sMyFe3cpSyjij47DW1K330zDJnoyZs
kuI10EzfK0wwY+D2qMQPGAmPDkix5t2dYQj6DKh1yBlBwAf7c65Ty1kpgtdymSptDJKVZcK6
R2CJ91oRBCZIObcWrG/0FZIr55+InAYyLDrlk34MwBmINhBZ4oRJdrzG6OC7cK4vG1ZWrAFE
GHVwx1uG2NXRUXQTH9DGYcwwfPo4uinFCwHZAJ2Il/J0Mqui5x+N/7p+WUlGRyb67qxg7ect
f2095+YDnbqIKIz7fGzw8XTwpjYbvWZplkG93qRXr8MRD9ukgxpxpHG2dTGCA90wggPZAgEB
MIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwSn6DAJBgUrDgMCGgUA
oIICHTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzAyMjAw
OTAyMzFaMCMGCSqGSIb3DQEJBDEWBBQo5SdR2NLwT8d9ZqZF/QOrlVgwnjBsBgkqhkiG9w0B
CQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEE
AYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9T
dGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBKfoMIGn
BgsqhkiG9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2
BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENB
AgMEp+gwDQYJKoZIhvcNAQEBBQAEggEAbFsZD7Fc1lFBn47+zSG4MvM+5pVaUFmdg60veVn9
yGaDyS8Gwa2NSMXQqM5/A1IS3E6pr9jMstb/8W+qt2Zv3trULN4ynASWHINtCIxlgjVwgxgl
HbNqLllhuzxf/+Z0UOOiiibI651UFG/fMCE+IZwBZ9heBL7nco30uYP0TgTAWvl6FIGWUNCl
4KQu0U0dInZ3oVVnEPks95K5q2LxVghtSsTrwGx8Ty/pS7Rvbln9Hx98wTGpz4FqL8AO5AKe
GElChQmfy7meMdkW1Ag67dOrQshR9awIgGCp9KRCxq4dkwYhE7fGargNboSkdLuX1qS7524x
BQGp2O2h44Qg0QAAAAAAAA==
--------------ms020401050909000804090103--

From w.roome@alcatel-lucent.com  Wed Feb 20 06:49:25 2013
Return-Path: <w.roome@alcatel-lucent.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 3BC2821F8810 for <alto@ietfa.amsl.com>; Wed, 20 Feb 2013 06:49:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.798
X-Spam-Level: 
X-Spam-Status: No, score=-9.798 tagged_above=-999 required=5 tests=[AWL=-0.596, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TXKKhTl0MC0W for <alto@ietfa.amsl.com>; Wed, 20 Feb 2013 06:49:21 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 6906921F87F9 for <alto@ietf.org>; Wed, 20 Feb 2013 06:49:21 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r1KEnKoY008725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 20 Feb 2013 08:49:20 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1KEnJZ2018661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 20 Feb 2013 08:49:20 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1KEnHkL020399; Wed, 20 Feb 2013 08:49:18 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.1.130117
Date: Wed, 20 Feb 2013 09:49:17 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: Richard Alimi <rich@velvetsea.net>
Message-ID: <CD4A40E9.351C9%w.roome@alcatel-lucent.com>
Thread-Topic: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
In-Reply-To: <CA+cvDaa_di9L3wnOHzcCURtuFmckogVjbLc7hodLOep9_Ykwnw@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3444198560_15647451"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2013 14:49:25 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3444198560_15647451
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

I respectfully disagree.

1. Why do we have "ordinal" mode at all?  I was told it was because ISPs
were afraid that providing accurate hopcount & delay information would
reveal too much of the internal structure of their network. "Ordinal" mode
allows an ISP to obfuscate the details, but still provides what most client=
s
need -- a rank ordering.

Given that, why would a production ALTO server (as opposed to a research
testbed) provide both "numerical" and "ordinal" modes for the same cost
type? I'd think the server would provide numerical if it's not afraid to
give away that much detail. Otherwise it would provide only offer ordinal.

On top of that, if you think about it, if a server maintains numerical cost
values, and a client asks for that cost-type in "ordinal" mode, the server
can just return the numerical values.

So I don't think it will be difficult for a server to maintain both modes
for the same cost type, if only because there's no reason for a server to d=
o
that.

2. Why would a client ever want ordinal cost values? The only reason I can
think of is if the client could rely on "1" being the lowest cost. But that
doesn't work, because ordinal values can be anything -- they do not have to
be 1, 2, 3, 4, =8A.

So I don't see clients as needing ordinal mode at all. It's just there to
warn clients that this cost isn't linear.

In fact, I'm tempted to suggest that we replace the idea of a "mode"
attribute with a simple binary attribute called "linear." For a linear cost=
,
40 is twice as high as 20, and 21 is only slightly higher than 20. For a
non-linear cost, 40 is higher than 21, and 21 is higher than 20, but we
don't know by how much.

3. Your last point is about registering cost types. Yes, my proposal would
make it harder to register new cost types with the IANA.

But I'll turn that around. Why do we need a central registry for cost types
at all? Why does the IANA need to control them? Sorry if I'm stepping on
someone's favorite idea here, but to me, a central registry seems totally
unnecessary. Worse than that, it's harmful: it will stifle innovation, by
making it much harder to create and experiment with new cost types.

Yes, that means that two independently implemented ALTO servers can each
define a new cost type named "myExtendedCost", with completely different
semantics. So what? What's the problem with that? Clients will know that
"myExtendedCost" is only meaningful within the context of a specific ALTO
server.

Note that the cost type extension I proposed takes over the descriptive
features of the IANA registry, in that it provides all the information abou=
t
this new cost type that a potential client needs to know. It doesn't allow
the IANA to manage and control new cost types. But I think that's a good
thing!

So in short, I suggest dropping the central "cost type registry"
requirements completely (Section 9.2). Instead, the ALTO server provides a
description of its cost types in its resource directory. ALTO servers are
free to invent new cost types, to differentiate themselves and provide
additional value.

- Wendy Roome

From:  Richard Alimi <rich@velvetsea.net>
Date:  Tue, February 19, 2013 17:51
Subject:  Re: [alto] Discussion II: Unifying cost-mode and cost-type to a
single type

On Fri, Feb 15, 2013 at 12:23 PM, Wendy Roome <w.roome@alcatel-lucent.com>
wrote:
> To return to this issue, I suggest we unify them, so that we have Cost
> Types -- period. The "Mode" becomes a property of the Cost Type. So if a
> server provides numerical & ordinal routingcosts, it provides *two*
> separate Cost Types, say "routingcost" and "routingcost-ord".
>=20
> I believe the result will simplify both clients and servers, and make it
> easier for servers to introduce additional cost types.

I believe that having them separate is a bit more 'normalized' of a form an=
d
has some important benefits. That is, one just has to define what 'hopcount=
'
means once, and then a server can expose that metric in different forms.  B=
y
creating a single opaque identifier, one now has to register 'hopcount' for
each and every "mode" that comes along.  This also makes it more difficult
for a client to understand that if it wants a particular cost type (but can
handle different forms), it has to know beforehand the exact set of
identifiers under which it can find all of the forms.

For example, consider the following:
(1) Person A registers cost type 'some-new-type' and describes it with
numerical costs
(2) Person B comes along and wants ordinal costs 'with 'some-new-type'.
Person B then has to go through the registration process to create
'some-new-type-ord'.  [ A side point - do we care about the registry stayin=
g
clean? Do we have rules on how to construct appropriate cost type
identifiers so they convey whether they are ordinal or numerical? ]
(3) At some point down the line, the Reincarnated ALTO Working Group decide=
s
to add a new 'mode' of cost, such as an array of costs that indicates the
cost's historical value over the past week.
(4) Person C looks at the registry and figures out that they want
'some-new-type' to be available in this new mode. Person C then has to go
and register 'some-new-type-historical' before it can be used. [ And this i=
s
going to happen for each cost type. ]

In short, I think the registry for cost types is going to get messy and it'=
s
going to make it more difficult for a client to say "I want the hopcount
costs but I don't care whether the server gives me the actual costs, or is
just going to rank them".

All that said, I understand this has been brought up in the past and there
are some things that it simplifies (which have been discussed in an earlier
thread) and if there is good consensus for doing this in the working group,
then we can certainly adopt the changes.

Thanks,
Rich




--B_3444198560_15647451
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>I respectfully disagree.</di=
v><div><br></div><div>1. Why do we have "ordinal" mode at all? &nbsp;I was t=
old it was because ISPs were afraid that providing accurate hopcount &amp; d=
elay information would reveal too much of the internal structure of their ne=
twork. "Ordinal" mode allows an ISP to obfuscate the details, but still prov=
ides what most clients need -- a rank ordering.</div><div><br></div><div>Giv=
en that, why would a production ALTO server (as opposed to a research testbe=
d) provide both "numerical" and "ordinal" modes for the same cost type? I'd =
think the server would provide numerical if it's not afraid to give away tha=
t much detail. Otherwise it would provide only offer ordinal.</div><div><br>=
</div><div>On top of that, if you think about it, if a server maintains nume=
rical cost values, and a client asks for that cost-type in "ordinal" mode, t=
he server can just return the numerical values.</div><div><br></div><div>So =
I don't think it will be difficult for a server to maintain both modes for t=
he same cost type, if only because there's no reason for a server to do that=
.</div><div><br></div><div>2. Why would a client ever want ordinal cost valu=
es? The only reason I can think of is if the client could rely on "1" being =
the lowest cost. But that doesn't work, because ordinal values can be anythi=
ng -- they do&nbsp;<b>not</b> have to be 1, 2, 3, 4, &#8230;.</div><div><br>=
</div><div>So I don't see clients as needing ordinal mode at all. It's just =
there to warn clients that this cost isn't linear.</div><div><br></div><div>=
In fact, I'm tempted to suggest that we replace the idea of a "mode" attribu=
te with a simple binary attribute called "linear." For a linear cost, 40 is =
twice as high as 20, and 21 is only slightly higher than 20. For a non-linea=
r cost, 40 is higher than 21, and 21 is higher than 20, but we don't know by=
 how much.</div><div><br></div><div>3. Your last point is about registering =
cost types. Yes, my proposal would make it harder to register new cost types=
 with the IANA.</div><div><br></div><div>But I'll turn that around. Why do w=
e need a central registry for cost types at all? Why does the IANA need to c=
ontrol them? Sorry if I'm stepping on someone's favorite idea here, but to m=
e, a central registry seems totally unnecessary. Worse than that, it's harmf=
ul: it will stifle innovation, by making it much harder to create and experi=
ment with new cost types.</div><div><br></div><div>Yes, that means that two =
independently implemented ALTO servers can each define a new cost type named=
 "myExtendedCost", with completely different semantics. So what? What's the =
problem with that? Clients will know that "myExtendedCost" is only meaningfu=
l within the context of a specific ALTO server.</div><div><br></div><div><di=
v>Note that the cost type extension I proposed takes over the descriptive fe=
atures of the IANA registry, in that it provides all the information about t=
his new cost type that a potential client needs to know. It doesn't allow th=
e IANA to manage and control new cost types. But I think that's a good thing=
!</div></div><div><br></div><div>So in short, I suggest dropping the central=
 "cost type registry" requirements completely (Section 9.2). Instead, the AL=
TO server provides a description of its cost types in its resource directory=
. ALTO servers are free to invent new cost types, to differentiate themselve=
s and provide additional value.</div><div><br></div><div><span class=3D"Apple-=
tab-span" style=3D"white-space:pre">	</span>- Wendy Roome</div><div><br></div>=
<span id=3D"OLK_SRC_BODY_SECTION"><div style=3D"font-family:Calibri; font-size:1=
1pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: =
medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BOR=
DER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><sp=
an style=3D"font-weight:bold">From: </span> Richard Alimi &lt;<a href=3D"mailto:=
rich@velvetsea.net">rich@velvetsea.net</a>&gt;<br><span style=3D"font-weight:b=
old">Date: </span> Tue, February 19, 2013 17:51<br><span style=3D"font-weight:=
bold">Subject: </span> Re: [alto] Discussion II: Unifying cost-mode and cost=
-type to a single type<br></div><div><br></div><span class=3D"Apple-style-span=
" style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: Calibr=
i; font-style: normal; font-variant: normal; font-weight: normal; letter-spa=
cing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; tex=
t-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-sp=
acing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-=
spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-ad=
just: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">On Fri, Feb=
 15, 2013 at 12:23 PM, Wendy Roome<span class=3D"Apple-converted-space">&nbsp;=
</span><span dir=3D"ltr">&lt;<a href=3D"mailto:w.roome@alcatel-lucent.com" targe=
t=3D"_blank">w.roome@alcatel-lucent.com</a>&gt;</span><span class=3D"Apple-conve=
rted-space">&nbsp;</span>wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; bo=
rder-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-sty=
le: solid; padding-left: 1ex; ">To return to this issue, I suggest we unify =
them, so that we have Cost<br>Types -- period. The "Mode" becomes a property=
 of the Cost Type. So if a<br>server provides numerical &amp; ordinal routin=
gcosts, it provides *two*<br>separate Cost Types, say "routingcost" and "rou=
tingcost-ord".<br><br>I believe the result will simplify both clients and se=
rvers, and make it<br>easier for servers to introduce additional cost types.=
<br></blockquote><div><br></div><div><div style=3D"font-family: arial, sans-se=
rif; font-size: 13px; ">I believe that having them separate is a bit more 'n=
ormalized' of a form and has some important benefits. That is, one just has =
to define what 'hopcount' means once, and then a server can expose that metr=
ic in different forms. &nbsp;By creating a single opaque identifier, one now=
 has to register 'hopcount' for each and every "mode" that comes along. &nbs=
p;This also makes it more difficult for a client to understand that if it wa=
nts a particular cost type (but can handle different forms), it has to know =
beforehand the exact set of identifiers under which it can find all of the f=
orms.</div><div style=3D"font-family: arial, sans-serif; font-size: 13px; "><b=
r></div><div style=3D"font-family: arial, sans-serif; font-size: 13px; ">For e=
xample, consider the following:</div><div style=3D"font-family: arial, sans-se=
rif; font-size: 13px; ">(1) Person A registers cost type 'some-new-type' and=
 describes it with numerical costs</div><div style=3D"font-family: arial, sans=
-serif; font-size: 13px; ">(2) Person B comes along and wants ordinal costs =
'with 'some-new-type'. Person B then has to go through the registration proc=
ess to create 'some-new-type-ord'. &nbsp;[ A side point - do we care about t=
he registry staying clean? Do we have rules on how to construct appropriate =
cost type identifiers so they convey whether they are ordinal or numerical? =
]</div><div style=3D"font-family: arial, sans-serif; font-size: 13px; ">(3) At=
 some point down the line, the Reincarnated ALTO Working Group decides to ad=
d a new 'mode' of cost, such as an array of costs that indicates the cost's =
historical value over the past week.</div><div style=3D"font-family: arial, sa=
ns-serif; font-size: 13px; ">(4) Person C looks at the registry and figures =
out that they want 'some-new-type' to be available in this new mode. Person =
C then has to go and register 'some-new-type-historical' before it can be us=
ed. [ And this is going to happen for each cost type. ]</div><div style=3D"fon=
t-family: arial, sans-serif; font-size: 13px; "><br></div><div style=3D"font-f=
amily: arial, sans-serif; font-size: 13px; ">In short, I think the registry =
for cost types is going to get messy and it's going to make it more difficul=
t for a client to say "I want the hopcount costs but I don't care whether th=
e server gives me the actual costs, or is just going to rank them".</div><di=
v style=3D"font-family: arial, sans-serif; font-size: 13px; "><br></div><div s=
tyle=3D"font-family: arial, sans-serif; font-size: 13px; ">All that said, I un=
derstand this has been brought up in the past and there are some things that=
 it simplifies (which have been discussed in an earlier thread) and if there=
 is good consensus for doing this in the working group, then we can certainl=
y adopt the changes.</div></div><div style=3D"font-family: arial, sans-serif; =
font-size: 13px; "><br></div><div style=3D"font-family: arial, sans-serif; fon=
t-size: 13px; ">Thanks,</div><div style=3D"font-family: arial, sans-serif; fon=
t-size: 13px; ">Rich</div></span><br class=3D"Apple-interchange-newline"></spa=
n></body></html>

--B_3444198560_15647451--



From w.roome@alcatel-lucent.com  Wed Feb 20 07:58:14 2013
Return-Path: <w.roome@alcatel-lucent.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 16EAA21F8698 for <alto@ietfa.amsl.com>; Wed, 20 Feb 2013 07:58:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.422
X-Spam-Level: 
X-Spam-Status: No, score=-10.422 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z+v-5u2weQw1 for <alto@ietfa.amsl.com>; Wed, 20 Feb 2013 07:58:13 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 7F46121F85D9 for <alto@ietf.org>; Wed, 20 Feb 2013 07:58:13 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id r1KFwBOQ013786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Wed, 20 Feb 2013 09:58:11 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1KFwAJJ026053 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Wed, 20 Feb 2013 09:58:11 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1KFw8Qc017752 for <alto@ietf.org>; Wed, 20 Feb 2013 09:58:09 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.1.130117
Date: Wed, 20 Feb 2013 10:58:09 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: "alto@ietf.org" <alto@ietf.org>
Message-ID: <CD4A5CC1.3541C%w.roome@alcatel-lucent.com>
Thread-Topic: Discussion II: Unifying cost-mode and cost-type to a single type
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2013 15:58:14 -0000

I'd like to propose a radical change to "cost mode". But first, I make the
following assertion:

"Ordinal" mode exists to allow ALTO servers to hide the details of their
network. For a client, "ordinal" mode has no advantage over "numerical"
mode; clients will never explicitly request an "ordinal" mode cost.
"Ordinal" mode benefits servers, not clients.

If you accept that, then I claim there's no reason for an ALTO server to
provide both "ordinal" and "numerical" values for the same cost type. If
the server wants to hide the network details, it will only provide an
"ordinal" cost. If the server doesn't mind exposing the details, it will
provide a "numerical" cost.

So I suggest the logical conclusion is that we drop "mode" as we've been
using it. Instead, a cost type has a binary-valued "linear" attribute
("true" => "numerical", "false" => "ordinal"). The ALTO server decides
whether a cost type is linear, and declares it in the resource directory.
The client lives with that decision; the client cannot chose to get an
ordinal cost.

In other words, I think we've over-engineered the concept of "cost mode",
and we should simply it.

	- Wendy Roome



From Martin.Stiemerling@neclab.eu  Thu Feb 21 03:36:23 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
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 73B6921F8AD8 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 03:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.489
X-Spam-Level: 
X-Spam-Status: No, score=-103.489 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZfFkdhEyK7N for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 03:36:23 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB3821F8CED for <alto@ietf.org>; Thu, 21 Feb 2013 03:36:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id D7385103379 for <alto@ietf.org>; Thu, 21 Feb 2013 12:36:16 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kNiyswU7tTqX for <alto@ietf.org>; Thu, 21 Feb 2013 12:36:16 +0100 (CET)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id BF777103378 for <alto@ietf.org>; Thu, 21 Feb 2013 12:36:11 +0100 (CET)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 21 Feb 2013 12:36:11 +0100
Message-ID: <512606AB.4020502@neclab.eu>
Date: Thu, 21 Feb 2013 12:36:11 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: <alto@ietf.org>
References: <45A697A8FFD7CF48BCF2BE7E106F060408FF52D6@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F060408FF52D6@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Subject: Re: [alto] ALTO Protocol Outstanding Issue I: Specify behavior of degenerated map filtering service
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 11:36:23 -0000

[writing without my AD hat on]

Hi all,

I'm sort of disappointed that actually nobody has any input to this and
the other open issue of the ALTO protocol.

Anyhow, here is my take:

On 01/29/2013 12:03 AM, Reinaldo Penno (repenno) wrote:
> Hello,
>
> This is the first of four outstanding issues related to the ALTO
> protocol. They were presented and discussed in the last IETF.
>
> For each outstanding issue I will send a separate email and a
> proposal to move forward. Please send your comments to the list in
> the next 2 weeks. Silence means we will go with the proposal.
>
> Discussion I:  Specify behaviors of degenerated map filtering
> service
>
> Do we enforce non-empty PID/AddressType? If protocol allows empty
> there are two possible design choices: default to complete map or
> reporting an Error
>
> Proposal going forward: Return complete Map.

I'm fine with that, but it should noted in the operational section that 
an empty PID can result in a full map to be returned.

   Martin

>
>
> Thanks,
>
> Reinaldo
>
>
> _______________________________________________ alto mailing list
> alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
>

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From Martin.Stiemerling@neclab.eu  Thu Feb 21 03:37:03 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
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 AB88721F8860 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 03:37:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.491
X-Spam-Level: 
X-Spam-Status: No, score=-103.491 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lD6hzAjWgiHb for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 03:37:03 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2539B21F8916 for <alto@ietf.org>; Thu, 21 Feb 2013 03:37:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 8EA1E103379 for <alto@ietf.org>; Thu, 21 Feb 2013 12:37:02 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2HBViRwfxLXH for <alto@ietf.org>; Thu, 21 Feb 2013 12:37:02 +0100 (CET)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 76F01103378 for <alto@ietf.org>; Thu, 21 Feb 2013 12:36:57 +0100 (CET)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 21 Feb 2013 12:36:57 +0100
Message-ID: <512606D9.4000702@neclab.eu>
Date: Thu, 21 Feb 2013 12:36:57 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: <alto@ietf.org>
References: <45A697A8FFD7CF48BCF2BE7E106F060408FF52EF@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F060408FF52EF@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Subject: Re: [alto] ALTO Protocol Outstanding Issue II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 11:37:03 -0000

[writing without my AD hat on]

Hi all,


On 01/29/2013 12:08 AM, Reinaldo Penno (repenno) wrote:
> Hello,
>
> Please send your comments to the list in the next 2 weeks. Silence
> means we will go with the proposal.
>
> Discussion II: Unifying cost-mode and cost-type to a single type
>
> e.g., routingcost-num and routingcost-ord
>
> Having a single type simples the protocol since there is just one
> parameter when indicating cost. But it will impact current
> implementations and might loose flexibility.
>
> Proposal: Leave it as is.

wfm.

>
> Thanks,
>
> Reinaldo
>
>
>
> _______________________________________________ alto mailing list
> alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
>

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From Martin.Stiemerling@neclab.eu  Thu Feb 21 03:43:11 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
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 69AF221F8DA2 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 03:43:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.492
X-Spam-Level: 
X-Spam-Status: No, score=-103.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yu1jwUOLnlp2 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 03:43:08 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id C47BE21F8920 for <alto@ietf.org>; Thu, 21 Feb 2013 03:43:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 3985E10337A for <alto@ietf.org>; Thu, 21 Feb 2013 12:43:07 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lYcqdGGBgIaP for <alto@ietf.org>; Thu, 21 Feb 2013 12:43:07 +0100 (CET)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 1F9B6103379 for <alto@ietf.org>; Thu, 21 Feb 2013 12:43:02 +0100 (CET)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 21 Feb 2013 12:43:02 +0100
Message-ID: <51260845.1000909@neclab.eu>
Date: Thu, 21 Feb 2013 12:43:01 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Subject: [alto] New ALTO use cases & the upcoming IETF meeting
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 11:43:11 -0000

Hi all,

I have seen a number of new ALTO drafts for LMAP, I2RS, etc and also the 
wish to discuss a rechartering of the ALTO WG.

I still do not see the WG to be ready for any rechartering discussion, 
as we should first finish up our current chartered items.

However, I can see the utility to discuss new ideas on what to do with 
ALTO, but outside the ALTO session at the upcoming IETF meeting in Orlando.

My proposal would be to do a side meeting, i.e., we meet sometimes in 
the evening over a drink and discuss the new drafts/use cases and how to 
progress ALTO.

But, do not rely on my to organize such a side meeting, i.e., somebody 
else should take the stab in organizing this.

   Martin

-- 
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From vkg@bell-labs.com  Thu Feb 21 05:40:23 2013
Return-Path: <vkg@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 B1BB421F8E27 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 05:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X5cPp8OaSXqk for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 05:40:22 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id B777D21F8DE7 for <alto@ietf.org>; Thu, 21 Feb 2013 05:40:22 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r1LDeK8O013927 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Thu, 21 Feb 2013 07:40:21 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1LDeKsN021733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Thu, 21 Feb 2013 07:40:20 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1LDeJ9K015877 for <alto@ietf.org>; Thu, 21 Feb 2013 07:40:20 -0600 (CST)
Message-ID: <51262458.8030102@bell-labs.com>
Date: Thu, 21 Feb 2013 07:42:48 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: alto <alto@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: [alto] server-discovery-07: Requesting publication
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 13:40:23 -0000

As co-chair ...

Folks: Pursuant to the email of Jan 30, 2013 [1], the second WGLC
against server-discovery for soliciting input regarding the IPR is now
closed.

Barring any further questions (and if there are, please post), Enrico
and I will go ahead and prepare for requesting publication of the draft.

[1] http://www.ietf.org/mail-archive/web/alto/current/msg01667.html

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From repenno@cisco.com  Thu Feb 21 06:16:39 2013
Return-Path: <repenno@cisco.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 97A0021F8CA7 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 06:16:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bIfNiOFhYqrq for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 06:16:38 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id D059321F8C83 for <alto@ietf.org>; Thu, 21 Feb 2013 06:16:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1282; q=dns/txt; s=iport; t=1361456199; x=1362665799; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=GOO+NzrXTKR0ZVzddUcNAaCIqUVrkd7za6ZXV6A75sU=; b=F1r6RWry6qGQqFz8DpSYg9sDAPdsEyfWdobOV8pKKXfECMDjFztatCE8 moLXO/ylDohPYwPwFHxuJvRY3WwO1/8gJZzkoeA1mkU7p/0mTGMb8GXgt RXoerXAhcB5lbDKJz0ErO1GZg4O9RENYUhiSUBTawBD+LxyG4QOCbM03Z c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EABEsJlGtJV2Y/2dsb2JhbABFwHSBBhZzgiEBBAEBATc0HQEIIhQ3CyUCBAESCIgKDL8aBI1HBIESOIJfYQOnEIMHgWk+
X-IronPort-AV: E=Sophos;i="4.84,709,1355097600"; d="scan'208";a="179415708"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 21 Feb 2013 14:16:31 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r1LEGVJj004332 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Feb 2013 14:16:31 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Thu, 21 Feb 2013 08:16:31 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] New ALTO use cases & the upcoming IETF meeting
Thread-Index: AQHOECikiNGqKZkSE0uR4z0mROaak5iEjggA
Date: Thu, 21 Feb 2013 14:16:30 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040900FF2D@xmb-rcd-x04.cisco.com>
In-Reply-To: <51260845.1000909@neclab.eu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.21.123.210]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BE8FAA43F1CD6A4CA981E00A1D6E5DF4@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [alto] New ALTO use cases & the upcoming IETF meeting
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 14:16:39 -0000

Thanks Martin,

We will try to organize a side meeting.

regards,

Reinaldo

On 2/21/13 8:43 AM, "Martin Stiemerling" <martin.stiemerling@neclab.eu>
wrote:

>Hi all,
>
>I have seen a number of new ALTO drafts for LMAP, I2RS, etc and also the
>wish to discuss a rechartering of the ALTO WG.
>
>I still do not see the WG to be ready for any rechartering discussion,
>as we should first finish up our current chartered items.
>
>However, I can see the utility to discuss new ideas on what to do with
>ALTO, but outside the ALTO session at the upcoming IETF meeting in
>Orlando.
>
>My proposal would be to do a side meeting, i.e., we meet sometimes in
>the evening over a drink and discuss the new drafts/use cases and how to
>progress ALTO.
>
>But, do not rely on my to organize such a side meeting, i.e., somebody
>else should take the stab in organizing this.
>
>   Martin
>
>--=20
>IETF Transport Area Director
>
>martin.stiemerling@neclab.eu
>
>NEC Laboratories Europe
>NEC Europe Limited
>Registered Office:
>Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
>Registered in England 2832014
>_______________________________________________
>alto mailing list
>alto@ietf.org
>https://www.ietf.org/mailman/listinfo/alto


From repenno@cisco.com  Thu Feb 21 08:00:41 2013
Return-Path: <repenno@cisco.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 D18D021F8E9F for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 08:00:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6IpXVpYMQ7N for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 08:00:33 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id DFA0C21F876E for <alto@ietf.org>; Thu, 21 Feb 2013 08:00:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19838; q=dns/txt; s=iport; t=1361462433; x=1362672033; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=gkZUA0ep3RlUkYCbXLA28oQ4MGlBtthYwnyM3VvADvQ=; b=Ne0dXcNylTAwV7bf8K6OtwO8wny4CCqyE7iq+1FaYe3qZElLLOrors9t /6CXQ5RBVrC10mXwrpDv05sXvSvOsTBVyV1UVPeVOyiPPy0UVfimuos50 JS2xLGRqTQ9JjOMbRaVyNPKYYENGqEEiIg1ArP8n+NhUKVzvrjroTDwMA A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAFZEJlGtJXHB/2dsb2JhbABFgkO+OIEFFnOCHwEBAQQBAQFrCxIBCA4DAwECCx0uCxQJCAIEAQ0FCIgKDL8NBI5dIAYHBAYBBoJZYQOnFIMHgic
X-IronPort-AV: E=Sophos;i="4.84,710,1355097600";  d="scan'208,217";a="179677665"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-6.cisco.com with ESMTP; 21 Feb 2013 16:00:31 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r1LG0VsG014081 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Feb 2013 16:00:31 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Thu, 21 Feb 2013 10:00:30 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Wendy Roome <w.roome@alcatel-lucent.com>, Richard Alimi <rich@velvetsea.net>
Thread-Topic: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
Thread-Index: AQHODvPTVY+ntXZyY0eKp/DUkgLdjpiDOZeAgAFz7YA=
Date: Thu, 21 Feb 2013 16:00:30 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F060409010027@xmb-rcd-x04.cisco.com>
In-Reply-To: <CD4A40E9.351C9%w.roome@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.21.123.210]
Content-Type: multipart/alternative; boundary="_000_45A697A8FFD7CF48BCF2BE7E106F060409010027xmbrcdx04ciscoc_"
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 16:00:41 -0000

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

Hello,

Some comments inline...

From: Wendy Roome <w.roome@alcatel-lucent.com<mailto:w.roome@alcatel-lucent=
.com>>
Date: Wed, 20 Feb 2013 09:49:17 -0500
To: Richard Alimi <rich@velvetsea.net<mailto:rich@velvetsea.net>>
Cc: "alto@ietf.org<mailto:alto@ietf.org>" <alto@ietf.org<mailto:alto@ietf.o=
rg>>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a si=
ngle type

I respectfully disagree.

1. Why do we have "ordinal" mode at all?  I was told it was because ISPs we=
re afraid that providing accurate hopcount & delay information would reveal=
 too much of the internal structure of their network. "Ordinal" mode allows=
 an ISP to obfuscate the details, but still provides what most clients need=
 -- a rank ordering.

Given that, why would a production ALTO server (as opposed to a research te=
stbed) provide both "numerical" and "ordinal" modes for the same cost type?=
 I'd think the server would provide numerical if it's not afraid to give aw=
ay that much detail. Otherwise it would provide only offer ordinal.

On top of that, if you think about it, if a server maintains numerical cost=
 values, and a client asks for that cost-type in "ordinal" mode, the server=
 can just return the numerical values.

So I don't think it will be difficult for a server to maintain both modes f=
or the same cost type, if only because there's no reason for a server to do=
 that.

2. Why would a client ever want ordinal cost values? The only reason I can =
think of is if the client could rely on "1" being the lowest cost. But that=
 doesn't work, because ordinal values can be anything -- they do not have t=
o be 1, 2, 3, 4, =85.

So I don't see clients as needing ordinal mode at all. It's just there to w=
arn clients that this cost isn't linear.

In fact, I'm tempted to suggest that we replace the idea of a "mode" attrib=
ute with a simple binary attribute called "linear." For a linear cost, 40 i=
s twice as high as 20, and 21 is only slightly higher than 20. For a non-li=
near cost, 40 is higher than 21, and 21 is higher than 20, but we don't kno=
w by how much.

3. Your last point is about registering cost types. Yes, my proposal would =
make it harder to register new cost types with the IANA.

But I'll turn that around. Why do we need a central registry for cost types=
 at all? Why does the IANA need to control them? Sorry if I'm stepping on s=
omeone's favorite idea here, but to me, a central registry seems totally un=
necessary. Worse than that, it's harmful: it will stifle innovation, by mak=
ing it much harder to create and experiment with new cost types.

[RP] You can always define a new cost type and experiment with it. IANA reg=
istered means standardization and interop are required.

Yes, that means that two independently implemented ALTO servers can each de=
fine a new cost type named "myExtendedCost", with completely different sema=
ntics. So what? What's the problem with that? Clients will know that "myExt=
endedCost" is only meaningful within the context of a specific ALTO server.

Note that the cost type extension I proposed takes over the descriptive fea=
tures of the IANA registry, in that it provides all the information about t=
his new cost type that a potential client needs to know. It doesn't allow t=
he IANA to manage and control new cost types. But I think that's a good thi=
ng!

So in short, I suggest dropping the central "cost type registry" requiremen=
ts completely (Section 9.2). Instead, the ALTO server provides a descriptio=
n of its cost types in its resource directory. ALTO servers are free to inv=
ent new cost types, to differentiate themselves and provide additional valu=
e.

[RP] ALTO servers can already do that today.  IANA registration does not pr=
eclude any of that, and as you say, within a domain you can define whatever=
 cost mode you want. This is not new, IANA registers a few modes/message ty=
pes/etc and reserves some for private use.


- Wendy Roome

From: Richard Alimi <rich@velvetsea.net<mailto:rich@velvetsea.net>>
Date: Tue, February 19, 2013 17:51
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a si=
ngle type

On Fri, Feb 15, 2013 at 12:23 PM, Wendy Roome <w.roome@alcatel-lucent.com<m=
ailto:w.roome@alcatel-lucent.com>> wrote:
To return to this issue, I suggest we unify them, so that we have Cost
Types -- period. The "Mode" becomes a property of the Cost Type. So if a
server provides numerical & ordinal routingcosts, it provides *two*
separate Cost Types, say "routingcost" and "routingcost-ord".

I believe the result will simplify both clients and servers, and make it
easier for servers to introduce additional cost types.

I believe that having them separate is a bit more 'normalized' of a form an=
d has some important benefits. That is, one just has to define what 'hopcou=
nt' means once, and then a server can expose that metric in different forms=
.  By creating a single opaque identifier, one now has to register 'hopcoun=
t' for each and every "mode" that comes along.  This also makes it more dif=
ficult for a client to understand that if it wants a particular cost type (=
but can handle different forms), it has to know beforehand the exact set of=
 identifiers under which it can find all of the forms.

For example, consider the following:
(1) Person A registers cost type 'some-new-type' and describes it with nume=
rical costs
(2) Person B comes along and wants ordinal costs 'with 'some-new-type'. Per=
son B then has to go through the registration process to create 'some-new-t=
ype-ord'.  [ A side point - do we care about the registry staying clean? Do=
 we have rules on how to construct appropriate cost type identifiers so the=
y convey whether they are ordinal or numerical? ]
(3) At some point down the line, the Reincarnated ALTO Working Group decide=
s to add a new 'mode' of cost, such as an array of costs that indicates the=
 cost's historical value over the past week.
(4) Person C looks at the registry and figures out that they want 'some-new=
-type' to be available in this new mode. Person C then has to go and regist=
er 'some-new-type-historical' before it can be used. [ And this is going to=
 happen for each cost type. ]

In short, I think the registry for cost types is going to get messy and it'=
s going to make it more difficult for a client to say "I want the hopcount =
costs but I don't care whether the server gives me the actual costs, or is =
just going to rank them".

All that said, I understand this has been brought up in the past and there =
are some things that it simplifies (which have been discussed in an earlier=
 thread) and if there is good consensus for doing this in the working group=
, then we can certainly adopt the changes.

Thanks,
Rich

_______________________________________________ alto mailing list alto@ietf=
.org<mailto:alto@ietf.org> https://www.ietf.org/mailman/listinfo/alto

--_000_45A697A8FFD7CF48BCF2BE7E106F060409010027xmbrcdx04ciscoc_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <9BC6AAC4BD52D1499DA709F9004FD2F4@cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Hello,</div>
<div><br>
</div>
<div>Some comments inline...</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Wendy Roome &lt;<a href=3D"ma=
ilto:w.roome@alcatel-lucent.com">w.roome@alcatel-lucent.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wed, 20 Feb 2013 09:49:17 -05=
00<br>
<span style=3D"font-weight:bold">To: </span>Richard Alimi &lt;<a href=3D"ma=
ilto:rich@velvetsea.net">rich@velvetsea.net</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:alto@ie=
tf.org">alto@ietf.org</a>&quot; &lt;<a href=3D"mailto:alto@ietf.org">alto@i=
etf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [alto] Discussion II: =
Unifying cost-mode and cost-type to a single type<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif; ">
<div>I respectfully disagree.</div>
<div><br>
</div>
<div>1. Why do we have &quot;ordinal&quot; mode at all? &nbsp;I was told it=
 was because ISPs were afraid that providing accurate hopcount &amp; delay =
information would reveal too much of the internal structure of their networ=
k. &quot;Ordinal&quot; mode allows an ISP to obfuscate the details,
 but still provides what most clients need -- a rank ordering.</div>
<div><br>
</div>
<div>Given that, why would a production ALTO server (as opposed to a resear=
ch testbed) provide both &quot;numerical&quot; and &quot;ordinal&quot; mode=
s for the same cost type? I'd think the server would provide numerical if i=
t's not afraid to give away that much detail. Otherwise
 it would provide only offer ordinal.</div>
<div><br>
</div>
<div>On top of that, if you think about it, if a server maintains numerical=
 cost values, and a client asks for that cost-type in &quot;ordinal&quot; m=
ode, the server can just return the numerical values.</div>
<div><br>
</div>
<div>So I don't think it will be difficult for a server to maintain both mo=
des for the same cost type, if only because there's no reason for a server =
to do that.</div>
<div><br>
</div>
<div>2. Why would a client ever want ordinal cost values? The only reason I=
 can think of is if the client could rely on &quot;1&quot; being the lowest=
 cost. But that doesn't work, because ordinal values can be anything -- the=
y do&nbsp;<b>not</b> have to be 1, 2, 3, 4, =85.</div>
<div><br>
</div>
<div>So I don't see clients as needing ordinal mode at all. It's just there=
 to warn clients that this cost isn't linear.</div>
<div><br>
</div>
<div>In fact, I'm tempted to suggest that we replace the idea of a &quot;mo=
de&quot; attribute with a simple binary attribute called &quot;linear.&quot=
; For a linear cost, 40 is twice as high as 20, and 21 is only slightly hig=
her than 20. For a non-linear cost, 40 is higher than
 21, and 21 is higher than 20, but we don't know by how much.</div>
<div><br>
</div>
<div>3. Your last point is about registering cost types. Yes, my proposal w=
ould make it harder to register new cost types with the IANA.</div>
<div><br>
</div>
<div>But I'll turn that around. Why do we need a central registry for cost =
types at all? Why does the IANA need to control them? Sorry if I'm stepping=
 on someone's favorite idea here, but to me, a central registry seems total=
ly unnecessary. Worse than that,
 it's harmful: it will stifle innovation, by making it much harder to creat=
e and experiment with new cost types.</div>
</div>
</div>
</span>
<div><br>
</div>
<div>[RP] You can always define a new cost type and experiment with it. IAN=
A registered means standardization and interop are required.</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif; ">
<div><br>
</div>
<div>Yes, that means that two independently implemented ALTO servers can ea=
ch define a new cost type named &quot;myExtendedCost&quot;, with completely=
 different semantics. So what? What's the problem with that? Clients will k=
now that &quot;myExtendedCost&quot; is only meaningful
 within the context of a specific ALTO server.</div>
<div><br>
</div>
<div>
<div>Note that the cost type extension I proposed takes over the descriptiv=
e features of the IANA registry, in that it provides all the information ab=
out this new cost type that a potential client needs to know. It doesn't al=
low the IANA to manage and control
 new cost types. But I think that's a good thing!</div>
</div>
<div><br>
</div>
<div>So in short, I suggest dropping the central &quot;cost type registry&q=
uot; requirements completely (Section 9.2). Instead, the ALTO server provid=
es a description of its cost types in its resource directory. ALTO servers =
are free to invent new cost types, to differentiate
 themselves and provide additional value.</div>
</div>
</div>
</span>
<div><br>
</div>
<div>[RP] ALTO servers can already do that today. &nbsp;IANA registration d=
oes not preclude any of that, and as you say, within a domain you can defin=
e whatever cost mode you want. This is not new, IANA registers a few modes/=
message types/etc and reserves some for
 private use. &nbsp;&nbsp;</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif; ">
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>- Wend=
y Roome</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Richard Alimi &lt;<a href=3D"=
mailto:rich@velvetsea.net">rich@velvetsea.net</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tue, February 19, 2013 17:51<=
br>
<span style=3D"font-weight:bold">Subject: </span>Re: [alto] Discussion II: =
Unifying cost-mode and cost-type to a single type<br>
</div>
<div><br>
</div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; color:=
 rgb(0, 0, 0); font-family: Calibri; font-style: normal; font-variant: norm=
al; font-weight: normal; letter-spacing: normal; line-height: normal; orpha=
ns: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; wh=
ite-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-=
spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decoration=
s-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-widt=
h: 0px; font-size: medium; ">On
 Fri, Feb 15, 2013 at 12:23 PM, Wendy Roome<span class=3D"Apple-converted-s=
pace">&nbsp;</span><span dir=3D"ltr">&lt;<a href=3D"mailto:w.roome@alcatel-=
lucent.com" target=3D"_blank">w.roome@alcatel-lucent.com</a>&gt;</span><spa=
n class=3D"Apple-converted-space">&nbsp;</span>wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0=
px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-=
left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex=
; ">
To return to this issue, I suggest we unify them, so that we have Cost<br>
Types -- period. The &quot;Mode&quot; becomes a property of the Cost Type. =
So if a<br>
server provides numerical &amp; ordinal routingcosts, it provides *two*<br>
separate Cost Types, say &quot;routingcost&quot; and &quot;routingcost-ord&=
quot;.<br>
<br>
I believe the result will simplify both clients and servers, and make it<br=
>
easier for servers to introduce additional cost types.<br>
</blockquote>
<div><br>
</div>
<div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; ">I believe =
that having them separate is a bit more 'normalized' of a form and has some=
 important benefits. That is, one just has to define what 'hopcount' means =
once, and then a server can expose
 that metric in different forms. &nbsp;By creating a single opaque identifi=
er, one now has to register 'hopcount' for each and every &quot;mode&quot; =
that comes along. &nbsp;This also makes it more difficult for a client to u=
nderstand that if it wants a particular cost type (but
 can handle different forms), it has to know beforehand the exact set of id=
entifiers under which it can find all of the forms.</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; "><br>
</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; ">For exampl=
e, consider the following:</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; ">(1) Person=
 A registers cost type 'some-new-type' and describes it with numerical cost=
s</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; ">(2) Person=
 B comes along and wants ordinal costs 'with 'some-new-type'. Person B then=
 has to go through the registration process to create 'some-new-type-ord'. =
&nbsp;[ A side point - do we care about
 the registry staying clean? Do we have rules on how to construct appropria=
te cost type identifiers so they convey whether they are ordinal or numeric=
al? ]</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; ">(3) At som=
e point down the line, the Reincarnated ALTO Working Group decides to add a=
 new 'mode' of cost, such as an array of costs that indicates the cost's hi=
storical value over the past week.</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; ">(4) Person=
 C looks at the registry and figures out that they want 'some-new-type' to =
be available in this new mode. Person C then has to go and register 'some-n=
ew-type-historical' before it can
 be used. [ And this is going to happen for each cost type. ]</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; "><br>
</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; ">In short, =
I think the registry for cost types is going to get messy and it's going to=
 make it more difficult for a client to say &quot;I want the hopcount costs=
 but I don't care whether the server gives
 me the actual costs, or is just going to rank them&quot;.</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; "><br>
</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; ">All that s=
aid, I understand this has been brought up in the past and there are some t=
hings that it simplifies (which have been discussed in an earlier thread) a=
nd if there is good consensus for
 doing this in the working group, then we can certainly adopt the changes.<=
/div>
</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; "><br>
</div>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; ">Thanks,</d=
iv>
<div style=3D"font-family: arial, sans-serif; font-size: 13px; ">Rich</div>
</span><br class=3D"Apple-interchange-newline">
</span></div>
</div>
_______________________________________________ alto mailing list <a href=
=3D"mailto:alto@ietf.org">
alto@ietf.org</a> <a href=3D"https://www.ietf.org/mailman/listinfo/alto">ht=
tps://www.ietf.org/mailman/listinfo/alto</a>
</span>
</body>
</html>

--_000_45A697A8FFD7CF48BCF2BE7E106F060409010027xmbrcdx04ciscoc_--

From leeyoung@huawei.com  Thu Feb 21 08:14:14 2013
Return-Path: <leeyoung@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 C760921F8E54 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 08:14:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gEn-7GhqyB6V for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 08:14:14 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8C37F21F8DAE for <alto@ietf.org>; Thu, 21 Feb 2013 08:14:13 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APY18958; Thu, 21 Feb 2013 16:14:12 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 21 Feb 2013 16:13:33 +0000
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 21 Feb 2013 16:14:12 +0000
Received: from dfweml511-mbs.china.huawei.com ([169.254.15.175]) by dfweml404-hub.china.huawei.com ([10.193.5.203]) with mapi id 14.01.0323.007; Thu, 21 Feb 2013 08:14:06 -0800
From: Leeyoung <leeyoung@huawei.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, Martin Stiemerling <martin.stiemerling@neclab.eu>
Thread-Topic: [alto] New ALTO use cases & the upcoming IETF meeting
Thread-Index: AQHOECinm7C2AVtBUEKuLYy9ZUxBv5iE4eEA//+Y3OA=
Date: Thu, 21 Feb 2013 16:14:05 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1729100475@dfweml511-mbs.china.huawei.com>
References: <51260845.1000909@neclab.eu> <45A697A8FFD7CF48BCF2BE7E106F06040900FF2D@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F06040900FF2D@xmb-rcd-x04.cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.179]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] New ALTO use cases & the upcoming IETF meeting
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 16:14:14 -0000

Hi Reinaldo,

I'd like to help this effort in any ways possible.

Thanks.
Young

-----Original Message-----
From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of Rei=
naldo Penno (repenno)
Sent: Thursday, February 21, 2013 8:17 AM
To: Martin Stiemerling; alto@ietf.org
Subject: Re: [alto] New ALTO use cases & the upcoming IETF meeting

Thanks Martin,

We will try to organize a side meeting.

regards,

Reinaldo

On 2/21/13 8:43 AM, "Martin Stiemerling" <martin.stiemerling@neclab.eu>
wrote:

>Hi all,
>
>I have seen a number of new ALTO drafts for LMAP, I2RS, etc and also the
>wish to discuss a rechartering of the ALTO WG.
>
>I still do not see the WG to be ready for any rechartering discussion,
>as we should first finish up our current chartered items.
>
>However, I can see the utility to discuss new ideas on what to do with
>ALTO, but outside the ALTO session at the upcoming IETF meeting in
>Orlando.
>
>My proposal would be to do a side meeting, i.e., we meet sometimes in
>the evening over a drink and discuss the new drafts/use cases and how to
>progress ALTO.
>
>But, do not rely on my to organize such a side meeting, i.e., somebody
>else should take the stab in organizing this.
>
>   Martin
>
>--=20
>IETF Transport Area Director
>
>martin.stiemerling@neclab.eu
>
>NEC Laboratories Europe
>NEC Europe Limited
>Registered Office:
>Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
>Registered in England 2832014
>_______________________________________________
>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

From w.roome@alcatel-lucent.com  Thu Feb 21 08:32:16 2013
Return-Path: <w.roome@alcatel-lucent.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 242A921F8CA7 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 08:32:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.743
X-Spam-Level: 
X-Spam-Status: No, score=-9.743 tagged_above=-999 required=5 tests=[AWL=-0.541, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1BQcPs+6NNOW for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 08:32:12 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id E626821F886A for <alto@ietf.org>; Thu, 21 Feb 2013 08:32:07 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r1LGW3IP014223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Thu, 21 Feb 2013 10:32:03 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1LGW2Mq010344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Thu, 21 Feb 2013 10:32:03 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1LGVxfM019280 for <alto@ietf.org>; Thu, 21 Feb 2013 10:32:00 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.1.130117
Date: Thu, 21 Feb 2013 11:32:03 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: <alto@ietf.org>
Message-ID: <CD4BB26C.35D3F%w.roome@alcatel-lucent.com>
Thread-Topic: [alto] Discussion II: Unifying cost-mode and cost-type to  a single type
In-Reply-To: <mailman.7015.1361462443.3383.alto@ietf.org>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3444291125_17847201"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 16:32:16 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3444291125_17847201
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Reinaldo,

I don't think the current ALTO draft is that permissive. Section 6.6.5 (Cos=
t
Types) seems to require that a server register any cost type that doesn't
start with "exp:":

> Identifiers prefixed with =B9priv:=B9 are reserved for Private Use
> [RFC5226]. Identifiers prefixed with =B9exp:=B9 are reserved for
> Experimental use. All other identifiers appearing in an HTTP request
> or response with an =B9application/alto-*=B9 media type MUST be
> registered in the ALTO Cost Types registry Section 9.2.
>=20
Also, although we've registered "routingcost" with IANA, I don't consider
that cost type is "interoperable." To me, "interoperable" means that
"routingcost" values would be comparable between servers, so that a cost of
(say) 40 means the same on all ALTO servers. That's clearly not the case.
Nor should it be!

Perhaps I'm missing the point, but as long as an ALTO server has a standard
way to describe its cost types, I don=B9t see any advantage to registering
ALTO cost types with the IANA.

- Wendy


> Date: Thu, 21 Feb 2013 16:00:30 +0000
> From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
>=20
> Hello,
>=20
> Some comments inline...
>=20
> From: Wendy Roome
> <w.roome@alcatel-lucent.com<mailto:w.roome@alcatel-lucent.com>>
> Date: Wed, 20 Feb 2013 09:49:17 -0500
>=20
> ....
>=20
> 3. Your last point is about registering cost types. Yes, my proposal woul=
d
> make it harder to register new cost types with the IANA.
>=20
> But I'll turn that around. Why do we need a central registry for cost typ=
es at
> all? Why does the IANA need to control them? Sorry if I'm stepping on
> someone's favorite idea here, but to me, a central registry seems totally
> unnecessary. Worse than that, it's harmful: it will stifle innovation, by
> making it much harder to create and experiment with new cost types.
>=20
> [RP] You can always define a new cost type and experiment with it. IANA
> registered means standardization and interop are required.
>=20
> Yes, that means that two independently implemented ALTO servers can each
> define a new cost type named "myExtendedCost", with completely different
> semantics. So what? What's the problem with that? Clients will know that
> "myExtendedCost" is only meaningful within the context of a specific ALTO
> server.
>=20
> Note that the cost type extension I proposed takes over the descriptive
> features of the IANA registry, in that it provides all the information ab=
out
> this new cost type that a potential client needs to know. It doesn't allo=
w the
> IANA to manage and control new cost types. But I think that's a good thin=
g!
>=20
> So in short, I suggest dropping the central "cost type registry" requirem=
ents
> completely (Section 9.2). Instead, the ALTO server provides a description=
 of
> its cost types in its resource directory. ALTO servers are free to invent=
 new
> cost types, to differentiate themselves and provide additional value.
>=20
> [RP] ALTO servers can already do that today.  IANA registration does not
> preclude any of that, and as you say, within a domain you can define what=
ever
> cost mode you want. This is not new, IANA registers a few modes/message
> types/etc and reserves some for private use.
>=20
>=20



--B_3444291125_17847201
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>Reinaldo,</div><div><br></di=
v><div>I don't think the current ALTO draft is that permissive. Section 6.6.=
5 (Cost Types) seems to require that a server register any cost type that do=
esn't start with "exp:":</div><div><br></div><div><blockquote style=3D"margin:=
0 0 0 40px; border:none; padding:0px;"><div>Identifiers prefixed with &#8217=
;priv:&#8217; are reserved for Private Use</div><div>[RFC5226]. Identifiers =
prefixed with &#8217;exp:&#8217; are reserved for</div><div>Experimental use=
. All other identifiers appearing in an HTTP request</div><div>or response w=
ith an &#8217;application/alto-*&#8217; media type MUST be</div><div>registe=
red in the ALTO Cost Types registry Section 9.2.</div><div><br></div></block=
quote></div><div>Also, although we've registered "routingcost" with IANA, I =
don't consider that cost type is "interoperable." To me, "interoperable" mea=
ns that "routingcost" values would be comparable between servers, so that a =
cost of (say) 40 means the same on all ALTO servers. That's clearly not the =
case. Nor should it be!</div><div><br></div><div>Perhaps I'm missing the poi=
nt, but as long as an ALTO server has a standard way to describe its cost ty=
pes, I don&#8217;t see any advantage to registering ALTO cost types with the=
 IANA.</div><div><br></div><div><span class=3D"Apple-tab-span" style=3D"white-sp=
ace:pre">	</span>- Wendy</div><div><br></div><div><br></div><blockquote id=3D"=
MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT: #b5c4df 5 solid; PAD=
DING:0 0 0 5; MARGIN:0 0 0 5;"><div>Date: Thu, 21 Feb 2013 16:00:30 +0000</d=
iv><div>From: "Reinaldo Penno (repenno)" &lt;<a href=3D"mailto:repenno@cisco.c=
om">repenno@cisco.com</a>&gt;</div><div><br></div><div>Hello,</div><div><br>=
</div><div>Some comments inline...</div><div><br></div><div>From: Wendy Room=
e &lt;<a href=3D"mailto:w.roome@alcatel-lucent.com">w.roome@alcatel-lucent.com=
</a>&lt;<a href=3D"mailto:w.roome@alcatel-lucent.com&gt;">mailto:w.roome@alcat=
el-lucent.com&gt;</a>&gt;</div><div>Date: Wed, 20 Feb 2013 09:49:17 -0500</d=
iv><div><br></div><div>....</div><div><br></div><div>3. Your last point is a=
bout registering cost types. Yes, my proposal would make it harder to regist=
er new cost types with the IANA.</div><div><br></div><div>But I'll turn that=
 around. Why do we need a central registry for cost types at all? Why does t=
he IANA need to control them? Sorry if I'm stepping on someone's favorite id=
ea here, but to me, a central registry seems totally unnecessary. Worse than=
 that, it's harmful: it will stifle innovation, by making it much harder to =
create and experiment with new cost types.</div><div><br></div><div>[RP] You=
 can always define a new cost type and experiment with it. IANA registered m=
eans standardization and interop are required.</div><div><br></div><div>Yes,=
 that means that two independently implemented ALTO servers can each define =
a new cost type named "myExtendedCost", with completely different semantics.=
 So what? What's the problem with that? Clients will know that "myExtendedCo=
st" is only meaningful within the context of a specific ALTO server.</div><d=
iv><br></div><div>Note that the cost type extension I proposed takes over th=
e descriptive features of the IANA registry, in that it provides all the inf=
ormation about this new cost type that a potential client needs to know. It =
doesn't allow the IANA to manage and control new cost types. But I think tha=
t's a good thing!</div><div><br></div><div>So in short, I suggest dropping t=
he central "cost type registry" requirements completely (Section 9.2). Inste=
ad, the ALTO server provides a description of its cost types in its resource=
 directory. ALTO servers are free to invent new cost types, to differentiate=
 themselves and provide additional value.</div><div><br></div><div>[RP] ALTO=
 servers can already do that today.&nbsp;&nbsp;IANA registration does not pr=
eclude any of that, and as you say, within a domain you can define whatever =
cost mode you want. This is not new, IANA registers a few modes/message type=
s/etc and reserves some for private use.</div><div><br></div><div><br></div>=
</blockquote></body></html>

--B_3444291125_17847201--



From repenno@cisco.com  Thu Feb 21 09:16:42 2013
Return-Path: <repenno@cisco.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 84B6E21F8EF9 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 09:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2GwKm9Jh+Jnu for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 09:16:41 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id D525721F8EF4 for <alto@ietf.org>; Thu, 21 Feb 2013 09:16:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10555; q=dns/txt; s=iport; t=1361467000; x=1362676600; h=from:to:subject:date:message-id:in-reply-to:mime-version; bh=jNiXWFsq35EmmoWgrxp0ECYfWA1zYRvm7KfmydTA1Mk=; b=alJWKEPpIEJV4xgZyaO6ODKrn/B/0u6kTipEZaVMUlkrlbT7jSfBXgnZ O5BcCeiQEuDr8yK7cydfvwCu5g6UGlEDm/o7/CANXEJZcoyl+CT7q7Yi6 0ohTYOssbJqOOZqx8Ds0WljL+zI7Wn9AkgOymiLp56sbE2R9rge4LFyOQ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFADZWJlGtJXG9/2dsb2JhbABFgkO+OYEEFnOCHwEBAQQBAQFrHQEIDgMDAQILHS4LFAkIAgQBEgiICgy/DASOXSAGBwsGgllhA6cUgweCJw
X-IronPort-AV: E=Sophos;i="4.84,710,1355097600";  d="scan'208,217";a="179685456"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-2.cisco.com with ESMTP; 21 Feb 2013 17:16:36 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id r1LHGZrE010672 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Feb 2013 17:16:35 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.02.0318.004; Thu, 21 Feb 2013 11:16:35 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Wendy Roome <w.roome@alcatel-lucent.com>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
Thread-Index: AQHOEFD6VY+ntXZyY0eKp/DUkgLdjpiEwAyA
Date: Thu, 21 Feb 2013 17:16:34 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F06040901008C@xmb-rcd-x04.cisco.com>
In-Reply-To: <CD4BB26C.35D3F%w.roome@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.21.123.210]
Content-Type: multipart/alternative; boundary="_000_45A697A8FFD7CF48BCF2BE7E106F06040901008Cxmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 17:16:43 -0000

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

This is what you need. A private cost you can use within your ALTO servers =
and domain.

"Identifiers prefixed with =92priv:=92 are reserved for Private Use"



From: Wendy Roome <w.roome@alcatel-lucent.com<mailto:w.roome@alcatel-lucent=
.com>>
Date: Thu, 21 Feb 2013 11:32:03 -0500
To: <alto@ietf.org<mailto:alto@ietf.org>>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a si=
ngle type

Reinaldo,

I don't think the current ALTO draft is that permissive. Section 6.6.5 (Cos=
t Types) seems to require that a server register any cost type that doesn't=
 start with "exp:":

Identifiers prefixed with =92priv:=92 are reserved for Private Use
[RFC5226]. Identifiers prefixed with =92exp:=92 are reserved for
Experimental use. All other identifiers appearing in an HTTP request
or response with an =92application/alto-*=92 media type MUST be
registered in the ALTO Cost Types registry Section 9.2.

Also, although we've registered "routingcost" with IANA, I don't consider t=
hat cost type is "interoperable." To me, "interoperable" means that "routin=
gcost" values would be comparable between servers, so that a cost of (say) =
40 means the same on all ALTO servers. That's clearly not the case. Nor sho=
uld it be!

Perhaps I'm missing the point, but as long as an ALTO server has a standard=
 way to describe its cost types, I don=92t see any advantage to registering=
 ALTO cost types with the IANA.

- Wendy


Date: Thu, 21 Feb 2013 16:00:30 +0000
From: "Reinaldo Penno (repenno)" <repenno@cisco.com<mailto:repenno@cisco.co=
m>>

Hello,

Some comments inline...

From: Wendy Roome <w.roome@alcatel-lucent.com<mailto:w.roome@alcatel-lucent=
.com><mailto:w.roome@alcatel-lucent.com>>
Date: Wed, 20 Feb 2013 09:49:17 -0500

....

3. Your last point is about registering cost types. Yes, my proposal would =
make it harder to register new cost types with the IANA.

But I'll turn that around. Why do we need a central registry for cost types=
 at all? Why does the IANA need to control them? Sorry if I'm stepping on s=
omeone's favorite idea here, but to me, a central registry seems totally un=
necessary. Worse than that, it's harmful: it will stifle innovation, by mak=
ing it much harder to create and experiment with new cost types.

[RP] You can always define a new cost type and experiment with it. IANA reg=
istered means standardization and interop are required.

Yes, that means that two independently implemented ALTO servers can each de=
fine a new cost type named "myExtendedCost", with completely different sema=
ntics. So what? What's the problem with that? Clients will know that "myExt=
endedCost" is only meaningful within the context of a specific ALTO server.

Note that the cost type extension I proposed takes over the descriptive fea=
tures of the IANA registry, in that it provides all the information about t=
his new cost type that a potential client needs to know. It doesn't allow t=
he IANA to manage and control new cost types. But I think that's a good thi=
ng!

So in short, I suggest dropping the central "cost type registry" requiremen=
ts completely (Section 9.2). Instead, the ALTO server provides a descriptio=
n of its cost types in its resource directory. ALTO servers are free to inv=
ent new cost types, to differentiate themselves and provide additional valu=
e.

[RP] ALTO servers can already do that today.  IANA registration does not pr=
eclude any of that, and as you say, within a domain you can define whatever=
 cost mode you want. This is not new, IANA registers a few modes/message ty=
pes/etc and reserves some for private use.


_______________________________________________ alto mailing list alto@ietf=
.org<mailto:alto@ietf.org> https://www.ietf.org/mailman/listinfo/alto

--_000_45A697A8FFD7CF48BCF2BE7E106F06040901008Cxmbrcdx04ciscoc_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <C1C0ED5FE0FD8C4EA9B855CF83470F95@cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>This is what you need. A private cost you can use within your ALTO ser=
vers and domain.</div>
<div><br>
</div>
<div>&quot;Identifiers prefixed with =92priv:=92 are reserved for Private U=
se&quot;</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Wendy Roome &lt;<a href=3D"ma=
ilto:w.roome@alcatel-lucent.com">w.roome@alcatel-lucent.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Thu, 21 Feb 2013 11:32:03 -05=
00<br>
<span style=3D"font-weight:bold">To: </span>&lt;<a href=3D"mailto:alto@ietf=
.org">alto@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [alto] Discussion II: =
Unifying cost-mode and cost-type to a single type<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif; ">
<div>Reinaldo,</div>
<div><br>
</div>
<div>I don't think the current ALTO draft is that permissive. Section 6.6.5=
 (Cost Types) seems to require that a server register any cost type that do=
esn't start with &quot;exp:&quot;:</div>
<div><br>
</div>
<div>
<blockquote style=3D"margin:0 0 0 40px; border:none; padding:0px;">
<div>Identifiers prefixed with =92priv:=92 are reserved for Private Use</di=
v>
<div>[RFC5226]. Identifiers prefixed with =92exp:=92 are reserved for</div>
<div>Experimental use. All other identifiers appearing in an HTTP request</=
div>
<div>or response with an =92application/alto-*=92 media type MUST be</div>
<div>registered in the ALTO Cost Types registry Section 9.2.</div>
<div><br>
</div>
</blockquote>
</div>
<div>Also, although we've registered &quot;routingcost&quot; with IANA, I d=
on't consider that cost type is &quot;interoperable.&quot; To me, &quot;int=
eroperable&quot; means that &quot;routingcost&quot; values would be compara=
ble between servers, so that a cost of (say) 40 means the same on all ALTO
 servers. That's clearly not the case. Nor should it be!</div>
<div><br>
</div>
<div>Perhaps I'm missing the point, but as long as an ALTO server has a sta=
ndard way to describe its cost types, I don=92t see any advantage to regist=
ering ALTO cost types with the IANA.</div>
<div><br>
</div>
<div><span class=3D"Apple-tab-span" style=3D"white-space:pre"></span>- Wend=
y</div>
<div><br>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>Date: Thu, 21 Feb 2013 16:00:30 &#43;0000</div>
<div>From: &quot;Reinaldo Penno (repenno)&quot; &lt;<a href=3D"mailto:repen=
no@cisco.com">repenno@cisco.com</a>&gt;</div>
<div><br>
</div>
<div>Hello,</div>
<div><br>
</div>
<div>Some comments inline...</div>
<div><br>
</div>
<div>From: Wendy Roome &lt;<a href=3D"mailto:w.roome@alcatel-lucent.com">w.=
roome@alcatel-lucent.com</a>&lt;<a href=3D"mailto:w.roome@alcatel-lucent.co=
m&gt;">mailto:w.roome@alcatel-lucent.com&gt;</a>&gt;</div>
<div>Date: Wed, 20 Feb 2013 09:49:17 -0500</div>
<div><br>
</div>
<div>....</div>
<div><br>
</div>
<div>3. Your last point is about registering cost types. Yes, my proposal w=
ould make it harder to register new cost types with the IANA.</div>
<div><br>
</div>
<div>But I'll turn that around. Why do we need a central registry for cost =
types at all? Why does the IANA need to control them? Sorry if I'm stepping=
 on someone's favorite idea here, but to me, a central registry seems total=
ly unnecessary. Worse than that,
 it's harmful: it will stifle innovation, by making it much harder to creat=
e and experiment with new cost types.</div>
<div><br>
</div>
<div>[RP] You can always define a new cost type and experiment with it. IAN=
A registered means standardization and interop are required.</div>
<div><br>
</div>
<div>Yes, that means that two independently implemented ALTO servers can ea=
ch define a new cost type named &quot;myExtendedCost&quot;, with completely=
 different semantics. So what? What's the problem with that? Clients will k=
now that &quot;myExtendedCost&quot; is only meaningful
 within the context of a specific ALTO server.</div>
<div><br>
</div>
<div>Note that the cost type extension I proposed takes over the descriptiv=
e features of the IANA registry, in that it provides all the information ab=
out this new cost type that a potential client needs to know. It doesn't al=
low the IANA to manage and control
 new cost types. But I think that's a good thing!</div>
<div><br>
</div>
<div>So in short, I suggest dropping the central &quot;cost type registry&q=
uot; requirements completely (Section 9.2). Instead, the ALTO server provid=
es a description of its cost types in its resource directory. ALTO servers =
are free to invent new cost types, to differentiate
 themselves and provide additional value.</div>
<div><br>
</div>
<div>[RP] ALTO servers can already do that today.&nbsp;&nbsp;IANA registrat=
ion does not preclude any of that, and as you say, within a domain you can =
define whatever cost mode you want. This is not new, IANA registers a few m=
odes/message types/etc and reserves some for
 private use.</div>
<div><br>
</div>
<div><br>
</div>
</blockquote>
</div>
</div>
_______________________________________________ alto mailing list <a href=
=3D"mailto:alto@ietf.org">
alto@ietf.org</a> <a href=3D"https://www.ietf.org/mailman/listinfo/alto">ht=
tps://www.ietf.org/mailman/listinfo/alto</a>
</span>
</body>
</html>

--_000_45A697A8FFD7CF48BCF2BE7E106F06040901008Cxmbrcdx04ciscoc_--

From yang.r.yang@gmail.com  Thu Feb 21 09:51:52 2013
Return-Path: <yang.r.yang@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 CE51421F8EC3 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 09:51:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dAA3a40gaGVH for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 09:51:36 -0800 (PST)
Received: from mail-ve0-f177.google.com (mail-ve0-f177.google.com [209.85.128.177]) by ietfa.amsl.com (Postfix) with ESMTP id 892E521F8EE8 for <alto@ietf.org>; Thu, 21 Feb 2013 09:51:35 -0800 (PST)
Received: by mail-ve0-f177.google.com with SMTP id m1so8202612ves.36 for <alto@ietf.org>; Thu, 21 Feb 2013 09:51:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4mdZ8JFqmPilZ6f3TH2ioO8apm2SniLRewxTN+NPU6c=; b=MajiZ/0Ys8zRw6JZh1UYSPfx9Ught24ur4407GrOVbZdXYwsQutMOQlPH7oAfgfkKh 4jpxLWk5dh22PGNs84xy/SFIzv1LJumUFCpR4wamyTJThc8nxWa6SdeBoai1K7H7YDEC Ui5yqv1Cwn+sl24/swjomFTil6Qw3DUFmScvTDktoe7V22JtMGnjuDGSBfSHqLz7hXmC Ife3RpC0qn6cE2C2EAVEL6VzFY6rgZMk0Ik8l9aKmFRRtAWIct+pUcNqluf63iv4O8+m gwQ4dfX4PYsfpNP5ALbIxMkZfI3ttqF604PEV2yiu33q8Bz1kOZXDqx43+Ikpq7XHRoR tBcA==
MIME-Version: 1.0
X-Received: by 10.220.208.137 with SMTP id gc9mr27326545vcb.51.1361469094993;  Thu, 21 Feb 2013 09:51:34 -0800 (PST)
Sender: yang.r.yang@gmail.com
Received: by 10.58.231.98 with HTTP; Thu, 21 Feb 2013 09:51:34 -0800 (PST)
In-Reply-To: <7AEB3D6833318045B4AE71C2C87E8E1729100475@dfweml511-mbs.china.huawei.com>
References: <51260845.1000909@neclab.eu> <45A697A8FFD7CF48BCF2BE7E106F06040900FF2D@xmb-rcd-x04.cisco.com> <7AEB3D6833318045B4AE71C2C87E8E1729100475@dfweml511-mbs.china.huawei.com>
Date: Thu, 21 Feb 2013 12:51:34 -0500
X-Google-Sender-Auth: WibOdqpVYLOlhIknSYgQrENXJGY
Message-ID: <CANUuoLo3TM-jFV6aTMfBvgsR75QsEBcq6bDP8uzDoBFL1z1-QA@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: Leeyoung <leeyoung@huawei.com>
Content-Type: multipart/alternative; boundary=bcaec54fb0fcc7da8e04d63fb97f
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] New ALTO use cases & the upcoming IETF meeting
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 17:51:53 -0000

--bcaec54fb0fcc7da8e04d63fb97f
Content-Type: text/plain; charset=ISO-8859-1

Dear all,

It is a good idea to run a side meeting! Do we use this mailing list to
coordinate or use private email messages?

Thanks.

Richard

On Thu, Feb 21, 2013 at 11:14 AM, Leeyoung <leeyoung@huawei.com> wrote:

> Hi Reinaldo,
>
> I'd like to help this effort in any ways possible.
>
> Thanks.
> Young
>
> -----Original Message-----
> From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of
> Reinaldo Penno (repenno)
> Sent: Thursday, February 21, 2013 8:17 AM
> To: Martin Stiemerling; alto@ietf.org
> Subject: Re: [alto] New ALTO use cases & the upcoming IETF meeting
>
> Thanks Martin,
>
> We will try to organize a side meeting.
>
> regards,
>
> Reinaldo
>
> On 2/21/13 8:43 AM, "Martin Stiemerling" <martin.stiemerling@neclab.eu>
> wrote:
>
> >Hi all,
> >
> >I have seen a number of new ALTO drafts for LMAP, I2RS, etc and also the
> >wish to discuss a rechartering of the ALTO WG.
> >
> >I still do not see the WG to be ready for any rechartering discussion,
> >as we should first finish up our current chartered items.
> >
> >However, I can see the utility to discuss new ideas on what to do with
> >ALTO, but outside the ALTO session at the upcoming IETF meeting in
> >Orlando.
> >
> >My proposal would be to do a side meeting, i.e., we meet sometimes in
> >the evening over a drink and discuss the new drafts/use cases and how to
> >progress ALTO.
> >
> >But, do not rely on my to organize such a side meeting, i.e., somebody
> >else should take the stab in organizing this.
> >
> >   Martin
> >
> >--
> >IETF Transport Area Director
> >
> >martin.stiemerling@neclab.eu
> >
> >NEC Laboratories Europe
> >NEC Europe Limited
> >Registered Office:
> >Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
> >Registered in England 2832014
> >_______________________________________________
> >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
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

--bcaec54fb0fcc7da8e04d63fb97f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear all,<div><br></div><div>It is a good idea to run a side meeting! Do we=
 use this mailing list to coordinate or use private email messages?</div><d=
iv><br></div><div>Thanks.</div><div><br></div><div>Richard<br><br><div clas=
s=3D"gmail_quote">
On Thu, Feb 21, 2013 at 11:14 AM, Leeyoung <span dir=3D"ltr">&lt;<a href=3D=
"mailto:leeyoung@huawei.com" target=3D"_blank">leeyoung@huawei.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Reinaldo,<br>
<br>
I&#39;d like to help this effort in any ways possible.<br>
<br>
Thanks.<br>
Young<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
-----Original Message-----<br>
From: <a href=3D"mailto:alto-bounces@ietf.org">alto-bounces@ietf.org</a> [m=
ailto:<a href=3D"mailto:alto-bounces@ietf.org">alto-bounces@ietf.org</a>] O=
n Behalf Of Reinaldo Penno (repenno)<br>
Sent: Thursday, February 21, 2013 8:17 AM<br>
To: Martin Stiemerling; <a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><=
br>
Subject: Re: [alto] New ALTO use cases &amp; the upcoming IETF meeting<br>
<br>
Thanks Martin,<br>
<br>
We will try to organize a side meeting.<br>
<br>
regards,<br>
<br>
Reinaldo<br>
<br>
On 2/21/13 8:43 AM, &quot;Martin Stiemerling&quot; &lt;<a href=3D"mailto:ma=
rtin.stiemerling@neclab.eu">martin.stiemerling@neclab.eu</a>&gt;<br>
wrote:<br>
<br>
&gt;Hi all,<br>
&gt;<br>
&gt;I have seen a number of new ALTO drafts for LMAP, I2RS, etc and also th=
e<br>
&gt;wish to discuss a rechartering of the ALTO WG.<br>
&gt;<br>
&gt;I still do not see the WG to be ready for any rechartering discussion,<=
br>
&gt;as we should first finish up our current chartered items.<br>
&gt;<br>
&gt;However, I can see the utility to discuss new ideas on what to do with<=
br>
&gt;ALTO, but outside the ALTO session at the upcoming IETF meeting in<br>
&gt;Orlando.<br>
&gt;<br>
&gt;My proposal would be to do a side meeting, i.e., we meet sometimes in<b=
r>
&gt;the evening over a drink and discuss the new drafts/use cases and how t=
o<br>
&gt;progress ALTO.<br>
&gt;<br>
&gt;But, do not rely on my to organize such a side meeting, i.e., somebody<=
br>
&gt;else should take the stab in organizing this.<br>
&gt;<br>
&gt; =A0 Martin<br>
&gt;<br>
&gt;--<br>
&gt;IETF Transport Area Director<br>
&gt;<br>
&gt;<a href=3D"mailto:martin.stiemerling@neclab.eu">martin.stiemerling@necl=
ab.eu</a><br>
&gt;<br>
&gt;NEC Laboratories Europe<br>
&gt;NEC Europe Limited<br>
&gt;Registered Office:<br>
&gt;Athene, Odyssey Business Park, West End =A0Road, London, HA4 6QE, GB<br=
>
&gt;Registered in England 2832014<br>
&gt;_______________________________________________<br>
&gt;alto mailing list<br>
&gt;<a href=3D"mailto:alto@ietf.org">alto@ietf.org</a><br>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/alto" target=3D"_blank=
">https://www.ietf.org/mailman/listinfo/alto</a><br>
<br>
_______________________________________________<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" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
_______________________________________________<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" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
</div></div></blockquote></div><br></div>

--bcaec54fb0fcc7da8e04d63fb97f--

From vkg@bell-labs.com  Thu Feb 21 09:56:04 2013
Return-Path: <vkg@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 D443A21F8F35 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 09:56:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-JuuFRcuEoJ for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 09:56:00 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 3516821F8EED for <alto@ietf.org>; Thu, 21 Feb 2013 09:56:00 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id r1LHtxjr006104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <alto@ietf.org>; Thu, 21 Feb 2013 11:55:59 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1LHtwJ5030817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <alto@ietf.org>; Thu, 21 Feb 2013 11:55:59 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1LHtwYJ011240 for <alto@ietf.org>; Thu, 21 Feb 2013 11:55:58 -0600 (CST)
Message-ID: <51266043.4010902@bell-labs.com>
Date: Thu, 21 Feb 2013 11:58:27 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130110 Thunderbird/17.0.2
MIME-Version: 1.0
To: alto@ietf.org
References: <51260845.1000909@neclab.eu> <45A697A8FFD7CF48BCF2BE7E106F06040900FF2D@xmb-rcd-x04.cisco.com> <7AEB3D6833318045B4AE71C2C87E8E1729100475@dfweml511-mbs.china.huawei.com> <CANUuoLo3TM-jFV6aTMfBvgsR75QsEBcq6bDP8uzDoBFL1z1-QA@mail.gmail.com>
In-Reply-To: <CANUuoLo3TM-jFV6aTMfBvgsR75QsEBcq6bDP8uzDoBFL1z1-QA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: Re: [alto] New ALTO use cases & the upcoming IETF meeting
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 17:56:05 -0000

On 02/21/2013 11:51 AM, Y. Richard Yang wrote:
> Dear all,
>
> It is a good idea to run a side meeting! Do we use this mailing list to
> coordinate or use private email messages?

Richard: I suspect that the best thing to do would be you or Reinaldo
(or whoever volunteers to organize) to use the list to solicit private
emails to gather the folks who are interested.  Then use the list to
disseminate information on where you plan to meet, etc.

That seem to have worked effectively in the past.

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From yang.r.yang@gmail.com  Thu Feb 21 10:04:30 2013
Return-Path: <yang.r.yang@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 C080121F8F10 for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 10:04:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.143
X-Spam-Level: 
X-Spam-Status: No, score=-2.143 tagged_above=-999 required=5 tests=[AWL=-0.833, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hf3CrH9X4M8P for <alto@ietfa.amsl.com>; Thu, 21 Feb 2013 10:04:29 -0800 (PST)
Received: from mail-vb0-f42.google.com (mail-vb0-f42.google.com [209.85.212.42]) by ietfa.amsl.com (Postfix) with ESMTP id C4DF321F8EDC for <alto@ietf.org>; Thu, 21 Feb 2013 10:04:23 -0800 (PST)
Received: by mail-vb0-f42.google.com with SMTP id ff1so2838004vbb.29 for <alto@ietf.org>; Thu, 21 Feb 2013 10:04:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=M/iRqIIJQ134Fhla+iLmEp7qHW0FV/IUD8iX8oyjQBg=; b=JtihfZPQTD5zITmbnQZXDsI02xQ4eYEp/JEzkrkLi43tR8Tn+UTIwJaEK7Ag5fsJYs rNs9A/wu+lQwLdEbrK0hJlPsOi88IiPoY66GUnMVaQM3GbNDNPdR5DBj16cqRzKwPGjw vXwK2Q6Js8D+L1ZzW8cOuqRs7dm63ZXHQLpBo1OAxFtX38cAzQNfCv28SjvQI95yD8NX Md5wU5rLimJSf92aNLu074MeazfkBFwN3SE8qfqlKUe+MgyCvQNUO8TXwByXRsILHAVy ZAIoLkr9dGuZz14Bak0If+QaaWjBZx2FcDVII4IfVOm9zHs19xvY6Yv39E6NOz2O89K6 x7Vg==
MIME-Version: 1.0
X-Received: by 10.220.116.5 with SMTP id k5mr32495860vcq.55.1361469863143; Thu, 21 Feb 2013 10:04:23 -0800 (PST)
Sender: yang.r.yang@gmail.com
Received: by 10.58.231.98 with HTTP; Thu, 21 Feb 2013 10:04:23 -0800 (PST)
In-Reply-To: <51266043.4010902@bell-labs.com>
References: <51260845.1000909@neclab.eu> <45A697A8FFD7CF48BCF2BE7E106F06040900FF2D@xmb-rcd-x04.cisco.com> <7AEB3D6833318045B4AE71C2C87E8E1729100475@dfweml511-mbs.china.huawei.com> <CANUuoLo3TM-jFV6aTMfBvgsR75QsEBcq6bDP8uzDoBFL1z1-QA@mail.gmail.com> <51266043.4010902@bell-labs.com>
Date: Thu, 21 Feb 2013 13:04:23 -0500
X-Google-Sender-Auth: LPAwUZEKTFRPwxNNQdOrO8F9F78
Message-ID: <CANUuoLp+kHNbroHi7uFe9OmNeJN=ewg=SkJb0naAf0E89k7WFg@mail.gmail.com>
From: "Y. Richard Yang" <yry@cs.yale.edu>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>
Content-Type: multipart/alternative; boundary=f46d0438946390e5f604d63fe7e0
Cc: Hao Yin <h-yin@mail.tsinghua.edu.cn>, alto@ietf.org
Subject: Re: [alto] New ALTO use cases & the upcoming IETF meeting
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 21 Feb 2013 18:04:30 -0000

--f46d0438946390e5f604d63fe7e0
Content-Type: text/plain; charset=ISO-8859-1

Hi Vijay,

Good idea.

To all folks: if you are interested, could you please send private emails
to Reinaldo, I, Young and (Jan, whom I assume will be interested given the
LMAP doc) so that we can get the preparation started? Given that it is a
side meeting, we can be slightly more off the charter and then it is best
that we produce some concrete results back to ALTO.

Thanks!

Richard

On Thu, Feb 21, 2013 at 12:58 PM, Vijay K. Gurbani <vkg@bell-labs.com>wrote:

> On 02/21/2013 11:51 AM, Y. Richard Yang wrote:
>
>> Dear all,
>>
>> It is a good idea to run a side meeting! Do we use this mailing list to
>> coordinate or use private email messages?
>>
>
> Richard: I suspect that the best thing to do would be you or Reinaldo
> (or whoever volunteers to organize) to use the list to solicit private
> emails to gather the folks who are interested.  Then use the list to
> disseminate information on where you plan to meet, etc.
>
> That seem to have worked effectively in the past.
>
> Thanks,
>
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.**com<vijay.gurbani@alcatel-lucent.com>
> Web:   http://ect.bell-labs.com/who/**vkg/<http://ect.bell-labs.com/who/vkg/>
>
> ______________________________**_________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/**listinfo/alto<https://www.ietf.org/mailman/listinfo/alto>
>

--f46d0438946390e5f604d63fe7e0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Vijay,<div><br></div><div>Good idea. <br><br>To all folks: if you are in=
terested, could you please send private emails to Reinaldo, I, Young and (J=
an, whom I assume will be interested given the LMAP doc) so that we can get=
 the preparation started? Given that it is a side meeting, we can be slight=
ly more off the charter and then it is best that we produce some concrete r=
esults back to ALTO.</div>
<div><br></div><div>Thanks!</div><div><br></div><div>Richard<br><br><div cl=
ass=3D"gmail_quote">On Thu, Feb 21, 2013 at 12:58 PM, Vijay K. Gurbani <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:vkg@bell-labs.com" target=3D"_blank">vk=
g@bell-labs.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 02/21/2013 11:51 AM, Y.=
 Richard Yang wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Dear all,<br>
<br>
It is a good idea to run a side meeting! Do we use this mailing list to<br>
coordinate or use private email messages?<br>
</blockquote>
<br></div>
Richard: I suspect that the best thing to do would be you or Reinaldo<br>
(or whoever volunteers to organize) to use the list to solicit private<br>
emails to gather the folks who are interested. =A0Then use the list to<br>
disseminate information on where you plan to meet, etc.<br>
<br>
That seem to have worked effectively in the past.<br>
<br>
Thanks,<br>
<br>
- vijay<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- <br>
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent<br>
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)<br>
Email: vkg@{<a href=3D"http://bell-labs.com" target=3D"_blank">bell-labs.co=
m</a>,<a href=3D"http://acm.org" target=3D"_blank">acm.org</a>} / <a href=
=3D"mailto:vijay.gurbani@alcatel-lucent.com" target=3D"_blank">vijay.gurban=
i@alcatel-lucent.<u></u>com</a><br>

Web: =A0 <a href=3D"http://ect.bell-labs.com/who/vkg/" target=3D"_blank">ht=
tp://ect.bell-labs.com/who/<u></u>vkg/</a></font></span><div class=3D"HOEnZ=
b"><div class=3D"h5"><br>
______________________________<u></u>_________________<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" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/alto</a><br>
</div></div></blockquote></div><br></div>

--f46d0438946390e5f604d63fe7e0--

From w.roome@alcatel-lucent.com  Fri Feb 22 09:51:09 2013
Return-Path: <w.roome@alcatel-lucent.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 3686521F886A for <alto@ietfa.amsl.com>; Fri, 22 Feb 2013 09:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.689
X-Spam-Level: 
X-Spam-Status: No, score=-9.689 tagged_above=-999 required=5 tests=[AWL=-0.487, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a8C9RmhESGGh for <alto@ietfa.amsl.com>; Fri, 22 Feb 2013 09:51:06 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id B6F1121F8853 for <alto@ietf.org>; Fri, 22 Feb 2013 09:51:04 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r1MHp3iD000186 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 22 Feb 2013 11:51:03 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1MHp2RR016103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 22 Feb 2013 11:51:03 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1MHp1pD020940; Fri, 22 Feb 2013 11:51:01 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.1.130117
Date: Fri, 22 Feb 2013 12:50:59 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, "alto@ietf.org" <alto@ietf.org>
Message-ID: <CD4D112F.36160%w.roome@alcatel-lucent.com>
Thread-Topic: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F06040901008C@xmb-rcd-x04.cisco.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3444382261_18923091"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 22 Feb 2013 17:51:09 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3444382261_18923091
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Okay, I can avoid the IANA registration requirements by using "priv:" or
"exp:" for custom Cost Types.

But that doesn't answer the question of *why* we should register Cost Types=
.
What's the advantage? How does that benefit us? That's a serious question.
To me, registration looks like an annoyance without any redeeming benefit.

I realize that the goal might have been to make costs interoperable, but I
don't think registration accomplishes that. Take "routingcost". I believe
all the IANA registration says is that "routingcost is a non-negative
number, and lower is better". I don't think that's enough. To make
routingcost interoperable, I'd like to know what "40" means. Better yet, I
think "interoperable" would mean that I could compare routingcost values
between different ALTO servers, so 40 on one server means roughly the same
as 40 on another server.

That's clearly not true.

Here's a sample use-case. I want to select a host for new VM. The VM manage=
r
gives me the CPU load (0.0 to 1.0) for several hosts. I then ask an ALTO
server for the routingcosts between my client and each of those hosts. I ru=
n
a function to blend the alto cost and the cpu load into an overall cost,
using the appropriate weighting and scaling factors, and I select the host
with the lowest overall cost.

So how do I determine those scaling factors? The IANA registry doesn't help=
.
I have to talk to the folks who provide that ALTO server, or else just look
at the values it returns. If I switch to a different ALTO server, I'll have
to start over again.

To me, that is not "interoperable". To me, "interoperable" would mean that =
I
could determine the scaling factors just from the central registry, and use
the same factors with any ALTO server.

As it stands now, "routingcost" values are only meaningful in the context o=
f
a specific ALTO server. So even though "routingcost" is registered, it's
still a custom cost that varies widely from server to server. So what's the
benefit to registration?

Sorry to be a pest, but it seems that a while back, someone just declared,
"Well, of course we should to register cost types!" Since then we've all
accepted that on blind faith. All I'm asking is for is why registration
helps.

- Wendy Roome


From:  "Reinaldo Penno (repenno)" <repenno@cisco.com>
Date:  Thu, February 21, 2013 12:16
To:  Bill Roome <w.roome@alcatel-lucent.com>, "alto@ietf.org"
<alto@ietf.org>
Subject:  Re: [alto] Discussion II: Unifying cost-mode and cost-type to a
single type

This is what you need. A private cost you can use within your ALTO servers
and domain.

"Identifiers prefixed with =B9priv:=B9 are reserved for Private Use"




--B_3444382261_18923091
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>Okay, I can avoid the IANA r=
egistration requirements by using "priv:" or "exp:" for custom Cost Types.</=
div><div><br></div><div>But that doesn't answer the question of *why* we sho=
uld register Cost Types. What's the advantage? How does that benefit us? Tha=
t's a serious question. To me, registration looks like an annoyance without =
any redeeming benefit.</div><div><br></div><div>I realize that the goal migh=
t have been to make costs interoperable, but I don't think registration acco=
mplishes that. Take "routingcost". I believe all the IANA registration says =
is that "routingcost is a non-negative number, and lower is better". I don't=
 think that's enough. To make routingcost interoperable, I'd like to know wh=
at "40" means. Better yet, I think "interoperable" would mean that I could c=
ompare routingcost values between different ALTO servers, so 40 on one serve=
r means roughly the same as 40 on another server.</div><div><br></div><div>T=
hat's clearly not true.</div><div><br></div><div>Here's a sample use-case. I=
 want to select a host for new VM. The VM manager gives me the CPU load (0.0=
 to 1.0) for several hosts. I then ask an ALTO server for the routingcosts b=
etween my client and each of those hosts. I run a function to blend the alto=
 cost and the cpu load into an overall cost, using the appropriate weighting=
 and scaling factors, and I select the host with the lowest overall cost.</d=
iv><div><br></div><div>So how do I determine those scaling factors? The IANA=
 registry doesn't help. I have to talk to the folks who provide that ALTO se=
rver, or else just look at the values it returns. If I switch to a different=
 ALTO server, I'll have to start over again.</div><div><br></div><div>To me,=
 that is not "interoperable". To me, "interoperable" would mean that I could=
 determine the scaling factors just from the central registry, and use the s=
ame factors with any ALTO server.</div><div><br></div><div>As it stands now,=
 "routingcost" values are only meaningful in the context of a specific ALTO =
server. So even though "routingcost" is registered, it's still a custom cost=
 that varies widely from server to server. So what's the benefit to registra=
tion?</div><div><br></div><div>Sorry to be a pest, but it seems that a while=
 back, someone just declared, "Well, of course we should to register cost ty=
pes!" Since then we've all accepted that on blind faith. All I'm asking is f=
or is why registration helps.</div><div><br></div><div><span class=3D"Apple-ta=
b-span" style=3D"white-space:pre">	</span>- Wendy Roome</div><div><br></div><d=
iv><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div style=3D"font-family:Calibri=
; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; =
BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RI=
GHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-=
TOP: 3pt"><span style=3D"font-weight:bold">From: </span> "Reinaldo Penno (repe=
nno)" &lt;<a href=3D"mailto:repenno@cisco.com">repenno@cisco.com</a>&gt;<br><s=
pan style=3D"font-weight:bold">Date: </span> Thu, February 21, 2013 12:16<br><=
span style=3D"font-weight:bold">To: </span> Bill Roome &lt;<a href=3D"mailto:w.r=
oome@alcatel-lucent.com">w.roome@alcatel-lucent.com</a>&gt;, "<a href=3D"mailt=
o:alto@ietf.org">alto@ietf.org</a>" &lt;<a href=3D"mailto:alto@ietf.org">alto@=
ietf.org</a>&gt;<br><span style=3D"font-weight:bold">Subject: </span> Re: [alt=
o] Discussion II: Unifying cost-mode and cost-type to a single type<br></div=
><div><br></div><span class=3D"Apple-style-span" style=3D"border-collapse: separ=
ate; color: rgb(0, 0, 0); font-family: Calibri; font-style: normal; font-var=
iant: normal; font-weight: normal; letter-spacing: normal; line-height: norm=
al; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-deco=
rations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke=
-width: 0px; font-size: medium; "><span class=3D"Apple-style-span" style=3D"font=
-size: 14px; font-family: Calibri, sans-serif; "><div>This is what you need.=
 A private cost you can use within your ALTO servers and domain.</div><div><=
br></div><div>"Identifiers prefixed with &#8217;priv:&#8217; are reserved fo=
r Private Use"</div></span></span><br class=3D"Apple-interchange-newline"></sp=
an></body></html>

--B_3444382261_18923091--



From sebi@gw01.ehlo.wurstkaes.de  Sat Feb 23 08:24:13 2013
Return-Path: <sebi@gw01.ehlo.wurstkaes.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 F222321F8FD5 for <alto@ietfa.amsl.com>; Sat, 23 Feb 2013 08:24:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OcDW2yACh+ty for <alto@ietfa.amsl.com>; Sat, 23 Feb 2013 08:24:12 -0800 (PST)
Received: from gw01.ehlo.wurstkaes.de (gw01.ehlo.wurstkaes.de [IPv6:2a02:a00:e000:116::41]) by ietfa.amsl.com (Postfix) with ESMTP id D52C521F8FAE for <alto@ietf.org>; Sat, 23 Feb 2013 08:24:11 -0800 (PST)
Received: from sebi by gw01.ehlo.wurstkaes.de with local (Exim 4.72) (envelope-from <sebi@gw01.ehlo.wurstkaes.de>) id 1U9HtG-0007zr-Me; Sat, 23 Feb 2013 17:23:58 +0100
Date: Sat, 23 Feb 2013 17:23:58 +0100
From: Sebastian Kiesel <ietf-alto@skiesel.de>
To: Wendy Roome <w.roome@alcatel-lucent.com>
Message-ID: <20130223162358.GH9265@gw01.ehlo.wurstkaes.de>
References: <45A697A8FFD7CF48BCF2BE7E106F06040901008C@xmb-rcd-x04.cisco.com> <CD4D112F.36160%w.roome@alcatel-lucent.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CD4D112F.36160%w.roome@alcatel-lucent.com>
Accept-Languages: en, de
Organization: my personal mail account
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: alto@ietf.org
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2013 16:24:13 -0000

Hi,

your observations regarding the "routing cost" cost type are right - we
cannot say more than "lower ist better" and there is no way to compare
values retrieved from different ALTO servers. This was a conscious
decision for the default cost type.  Personally, I would have preferred
to call the default cost type "relative preference" in order to 1) show
that this is indeed a relative measure, 2) remove the ambiguity whether
cost is to be understood in the sense of routing protocols as opposed to
monetary cost for sending traffic over specific links, and 3) explicitly
allow the ALTO server operator to express preferences based on
completely different issues than "cost".


On the other hand, there are many other cost types (or "rating
criteria", as the ALTO requirements document RFC 6708 calls them), where
an exact specification how to compute and how to encode them makes
sense, e.g.:

- draft-scharf-alto-vpn-service-00  talks about publishing the
  geographical location of a data center using ALTO. How excatly
  do we encode longitude/latitude?   This might fit into two lines
  of text directly in the IANA registry.

- Hop count, defined as the one-way TTL decrease you will observe 
  in the IP packet header when sending packets to the target host
  -> a well defined measure that can be compared among servers

- Weighted path length, maybe something like 

path_length := 
    2 * (Number of traversed  10 Gbps links in the access networks)
  + 4 * (Number of traversed   1 Gbps links in the access networks)
 + 19 * (Number of traversed 100 Mbps links in the access networks)
 + 100 *(Number of traversed  10 Mbps links in the access networks)
 + 30 * (Number of traversed Autonomous Systems between the access n.w's)

  This is for illustration only - the weights in each line probably need
  tweaking.  Such a rather long definition probably needs an own
  specification document before registering.
  
- For a longer list of other criteria we discussed long time ago see 
  section 5 of http://tools.ietf.org/id/draft-ietf-alto-reqs-06.txt



So for me the conclusion is: the fact that we cannot compare our
default cost type "routing cost" between different ALTO servers does
not contradict the need to establish a registry for registering and
defining more complex cost types, which may or may not have clear
scaling factors or units of measurement.

Thanks
Sebastian






On Fri, Feb 22, 2013 at 12:50:59PM -0500, Wendy Roome wrote:
> Okay, I can avoid the IANA registration requirements by using "priv:" or
> "exp:" for custom Cost Types.
> 
> But that doesn't answer the question of *why* we should register Cost Types.
> What's the advantage? How does that benefit us? That's a serious question.
> To me, registration looks like an annoyance without any redeeming benefit.
> 
> I realize that the goal might have been to make costs interoperable, but I
> don't think registration accomplishes that. Take "routingcost". I believe
> all the IANA registration says is that "routingcost is a non-negative
> number, and lower is better". I don't think that's enough. To make
> routingcost interoperable, I'd like to know what "40" means. Better yet, I
> think "interoperable" would mean that I could compare routingcost values
> between different ALTO servers, so 40 on one server means roughly the same
> as 40 on another server.
> 
> That's clearly not true.
> 
> Here's a sample use-case. I want to select a host for new VM. The VM manager
> gives me the CPU load (0.0 to 1.0) for several hosts. I then ask an ALTO
> server for the routingcosts between my client and each of those hosts. I run
> a function to blend the alto cost and the cpu load into an overall cost,
> using the appropriate weighting and scaling factors, and I select the host
> with the lowest overall cost.
> 
> So how do I determine those scaling factors? The IANA registry doesn't help.
> I have to talk to the folks who provide that ALTO server, or else just look
> at the values it returns. If I switch to a different ALTO server, I'll have
> to start over again.
> 
> To me, that is not "interoperable". To me, "interoperable" would mean that I
> could determine the scaling factors just from the central registry, and use
> the same factors with any ALTO server.
> 
> As it stands now, "routingcost" values are only meaningful in the context of
> a specific ALTO server. So even though "routingcost" is registered, it's
> still a custom cost that varies widely from server to server. So what's the
> benefit to registration?
> 
> Sorry to be a pest, but it seems that a while back, someone just declared,
> "Well, of course we should to register cost types!" Since then we've all
> accepted that on blind faith. All I'm asking is for is why registration
> helps.
> 
> - Wendy Roome
> 
> 
> From:  "Reinaldo Penno (repenno)" <repenno@cisco.com>
> Date:  Thu, February 21, 2013 12:16
> To:  Bill Roome <w.roome@alcatel-lucent.com>, "alto@ietf.org"
> <alto@ietf.org>
> Subject:  Re: [alto] Discussion II: Unifying cost-mode and cost-type to a
> single type
> 
> This is what you need. A private cost you can use within your ALTO servers
> and domain.
> 
> "Identifiers prefixed with ¹priv:¹ are reserved for Private Use"
> 
> 
> 

> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto


From michael.scharf@alcatel-lucent.com  Sat Feb 23 12:43:30 2013
Return-Path: <michael.scharf@alcatel-lucent.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 047A521F8E69 for <alto@ietfa.amsl.com>; Sat, 23 Feb 2013 12:43:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.467
X-Spam-Level: 
X-Spam-Status: No, score=-9.467 tagged_above=-999 required=5 tests=[AWL=0.782,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yew-e+g3xyWq for <alto@ietfa.amsl.com>; Sat, 23 Feb 2013 12:43:29 -0800 (PST)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3C26321F8E2C for <alto@ietf.org>; Sat, 23 Feb 2013 12:43:28 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r1NKhQOL026671 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sat, 23 Feb 2013 21:43:26 +0100
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Sat, 23 Feb 2013 21:43:26 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>, "Roome, W D" <w.roome@alcatel-lucent.com>
Date: Sat, 23 Feb 2013 21:43:23 +0100
Thread-Topic: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
Thread-Index: Ac4R4kDTVDRLGqG/TmeqZAwW3AnqZQAIeWXQ
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AA10D624B@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <45A697A8FFD7CF48BCF2BE7E106F06040901008C@xmb-rcd-x04.cisco.com> <CD4D112F.36160%w.roome@alcatel-lucent.com> <20130223162358.GH9265@gw01.ehlo.wurstkaes.de>
In-Reply-To: <20130223162358.GH9265@gw01.ehlo.wurstkaes.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2013 20:43:30 -0000

> On the other hand, there are many other cost types (or=20
> "rating criteria", as the ALTO requirements document RFC 6708=20
> calls them), where an exact specification how to compute and=20
> how to encode them makes sense, e.g.:
>=20
> - draft-scharf-alto-vpn-service-00  talks about publishing the
>   geographical location of a data center using ALTO. How excatly
>   do we encode longitude/latitude?   This might fit into two lines
>   of text directly in the IANA registry.

For what it is worth (slightly off-topic in this thread): Approximate geogr=
aphic location is already explicitly mentioned in the ALTO charter ("Initia=
lly the WG will consider: IP ranges to prefer and to avoid, ranked lists of=
 the peers requested by the client, information about topological proximity=
 and approximate geographic locations.").

IMHO, regarding geographical locations, draft-scharf-alto-vpn-service-00 ju=
st suggests something that the charter already mentions.

Michael


From richard.alimi@gmail.com  Sun Feb 24 22:12:45 2013
Return-Path: <richard.alimi@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 DFC9B21F8777 for <alto@ietfa.amsl.com>; Sun, 24 Feb 2013 22:12:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AhFG3UtGShNu for <alto@ietfa.amsl.com>; Sun, 24 Feb 2013 22:12:44 -0800 (PST)
Received: from mail-ve0-f169.google.com (mail-ve0-f169.google.com [209.85.128.169]) by ietfa.amsl.com (Postfix) with ESMTP id 34A8C21F874A for <alto@ietf.org>; Sun, 24 Feb 2013 22:12:44 -0800 (PST)
Received: by mail-ve0-f169.google.com with SMTP id 15so1906604vea.14 for <alto@ietf.org>; Sun, 24 Feb 2013 22:12:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=1gy7W8D2vaInZq8ZkZhOjId0yOQBmrzHKm1KqSTIQuQ=; b=h0uhLLWllNBAAFThSL6p30ZG1URGkhmaov0tClHGRvPqoKRlUebawP/O19G1n8bvZ2 H1TMkfNwRwShRhykqXftzQQ63SEk96K1KyFnZca4buMvxuke5jPpowPH2iUI911xB0ud a5G6WJ9z0/BUb5wdLj2mApkntRa9DPzhCMnP8NASKtzfO2xasPFuQ3uIHEnwozK5TFXH 5R0d0466c8m2a1iLil/MQUVeZjvToTbPmoQLRbN2lCzMsPWmsAtFfRx1t3APZFB2IUwQ VrXkcdRnldyNkHe66x++rCTybv/3ACU+3nv1p7JZ6Z8an9KCX1Y89PllKdweFwB+nlAn vzYA==
X-Received: by 10.220.218.195 with SMTP id hr3mr9150845vcb.70.1361772763635; Sun, 24 Feb 2013 22:12:43 -0800 (PST)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.58.209.169 with HTTP; Sun, 24 Feb 2013 22:12:22 -0800 (PST)
In-Reply-To: <CD4A40E9.351C9%w.roome@alcatel-lucent.com>
References: <CA+cvDaa_di9L3wnOHzcCURtuFmckogVjbLc7hodLOep9_Ykwnw@mail.gmail.com> <CD4A40E9.351C9%w.roome@alcatel-lucent.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 24 Feb 2013 22:12:22 -0800
X-Google-Sender-Auth: d30GggvGZVEmiYkSCwEq6Sex3EI
Message-ID: <CA+cvDabAFXtZFEcE+jTgyHPjpcHWYj_sA6cit4WL=0H6YYnQpQ@mail.gmail.com>
To: Wendy Roome <w.roome@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=14dae9cfcdcad7616a04d6866dbb
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2013 06:12:46 -0000

--14dae9cfcdcad7616a04d6866dbb
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 20, 2013 at 6:49 AM, Wendy Roome <w.roome@alcatel-lucent.com>wr=
ote:

> I respectfully disagree.
>
> 1. Why do we have "ordinal" mode at all?  I was told it was because ISPs
> were afraid that providing accurate hopcount & delay information would
> reveal too much of the internal structure of their network. "Ordinal" mod=
e
> allows an ISP to obfuscate the details, but still provides what most
> clients need -- a rank ordering.
>

> Given that, why would a production ALTO server (as opposed to a research
> testbed) provide both "numerical" and "ordinal" modes for the same cost
> type? I'd think the server would provide numerical if it's not afraid to
> give away that much detail. Otherwise it would provide only offer ordinal=
.
>
> On top of that, if you think about it, if a server maintains numerical
> cost values, and a client asks for that cost-type in "ordinal" mode, the
> server can just return the numerical values.
>

Yep. The idea was to make it easy for servers.


>
> So I don't think it will be difficult for a server to maintain both modes
> for the same cost type, if only because there's no reason for a server to
> do that.
>
> 2. Why would a client ever want ordinal cost values? The only reason I ca=
n
> think of is if the client could rely on "1" being the lowest cost. But th=
at
> doesn't work, because ordinal values can be anything -- they do *not*have=
 to be 1, 2, 3, 4, =85.
>
> So I don't see clients as needing ordinal mode at all. It's just there to
> warn clients that this cost isn't linear.
>

Clients needed to know the difference between when the servers were
providing ordinal values or numerical values. For example, the P4P approach
does not apply to ordinal values.


> In fact, I'm tempted to suggest that we replace the idea of a "mode"
> attribute with a simple binary attribute called "linear." For a linear
> cost, 40 is twice as high as 20, and 21 is only slightly higher than 20.
> For a non-linear cost, 40 is higher than 21, and 21 is higher than 20, bu=
t
> we don't know by how much.
>

If the intent is to rename it, then I think it's a mistake to collapse it
to a boolean value.  Then, that removes flexibility for extensions. For
example, what if someone wanted to add a mode that wasn't represented by a
single number, but rather a key/value map (such as some statistical
information about a measurement).  Having an identifier instead of a
boolean value gives more flexibility for extensions.


>
> 3. Your last point is about registering cost types. Yes, my proposal woul=
d
> make it harder to register new cost types with the IANA.
>
> But I'll turn that around. Why do we need a central registry for cost
> types at all? Why does the IANA need to control them? Sorry if I'm steppi=
ng
> on someone's favorite idea here, but to me, a central registry seems
> totally unnecessary. Worse than that, it's harmful: it will stifle
> innovation, by making it much harder to create and experiment with new co=
st
> types.
>
> Yes, that means that two independently implemented ALTO servers can each
> define a new cost type named "myExtendedCost", with completely different
> semantics. So what? What's the problem with that? Clients will know that
> "myExtendedCost" is only meaningful within the context of a specific ALTO
> server.
>
> Note that the cost type extension I proposed takes over the descriptive
> features of the IANA registry, in that it provides all the information
> about this new cost type that a potential client needs to know. It doesn'=
t
> allow the IANA to manage and control new cost types. But I think that's a
> good thing!
>
> So in short, I suggest dropping the central "cost type registry"
> requirements completely (Section 9.2). Instead, the ALTO server provides =
a
> description of its cost types in its resource directory. ALTO servers are
> free to invent new cost types, to differentiate themselves and provide
> additional value.
>

I think the other replies here have sufficiently backed up the need for a
registry, and addressed the desire to have your own custom type without the
need to register it.  Right?

At this point, would it be useful to have some guidance from the WG chairs
about what exactly should be considered in this thread?  I get the feeling
like we are straying a long way from the initial question (should we
combine cost mode and cost type to a single identifier), and discussing
large changes that would have been (I think) better brought up during WGLC.
 If the WG believes that we should go back and discuss these, that's fine -
I'd just like some clarity on what exactly the open issues with the draft
are.

Thanks,
Rich


> - Wendy Roome
>
> From: Richard Alimi <rich@velvetsea.net>
> Date: Tue, February 19, 2013 17:51
> Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a
> single type
>
> On Fri, Feb 15, 2013 at 12:23 PM, Wendy Roome <w.roome@alcatel-lucent.com=
>
>  wrote:
>
>> To return to this issue, I suggest we unify them, so that we have Cost
>> Types -- period. The "Mode" becomes a property of the Cost Type. So if a
>> server provides numerical & ordinal routingcosts, it provides *two*
>> separate Cost Types, say "routingcost" and "routingcost-ord".
>>
>> I believe the result will simplify both clients and servers, and make it
>> easier for servers to introduce additional cost types.
>>
>
> I believe that having them separate is a bit more 'normalized' of a form
> and has some important benefits. That is, one just has to define what
> 'hopcount' means once, and then a server can expose that metric in
> different forms.  By creating a single opaque identifier, one now has to
> register 'hopcount' for each and every "mode" that comes along.  This als=
o
> makes it more difficult for a client to understand that if it wants a
> particular cost type (but can handle different forms), it has to know
> beforehand the exact set of identifiers under which it can find all of th=
e
> forms.
>
> For example, consider the following:
> (1) Person A registers cost type 'some-new-type' and describes it with
> numerical costs
> (2) Person B comes along and wants ordinal costs 'with 'some-new-type'.
> Person B then has to go through the registration process to create
> 'some-new-type-ord'.  [ A side point - do we care about the registry
> staying clean? Do we have rules on how to construct appropriate cost type
> identifiers so they convey whether they are ordinal or numerical? ]
> (3) At some point down the line, the Reincarnated ALTO Working Group
> decides to add a new 'mode' of cost, such as an array of costs that
> indicates the cost's historical value over the past week.
> (4) Person C looks at the registry and figures out that they want
> 'some-new-type' to be available in this new mode. Person C then has to go
> and register 'some-new-type-historical' before it can be used. [ And this
> is going to happen for each cost type. ]
>
> In short, I think the registry for cost types is going to get messy and
> it's going to make it more difficult for a client to say "I want the
> hopcount costs but I don't care whether the server gives me the actual
> costs, or is just going to rank them".
>
> All that said, I understand this has been brought up in the past and ther=
e
> are some things that it simplifies (which have been discussed in an earli=
er
> thread) and if there is good consensus for doing this in the working grou=
p,
> then we can certainly adopt the changes.
>
> Thanks,
> Rich
>
>

--14dae9cfcdcad7616a04d6866dbb
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Feb 20, 2013 at 6:49 AM, Wendy Roome <span dir=3D"=
ltr">&lt;<a href=3D"mailto:w.roome@alcatel-lucent.com" target=3D"_blank">w.=
roome@alcatel-lucent.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra=
"><div class=3D"gmail_quote">


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"font-size:14px;font-family:Cal=
ibri,sans-serif;word-wrap:break-word"><div>I respectfully disagree.</div><d=
iv>


<br></div><div>1. Why do we have &quot;ordinal&quot; mode at all? =A0I was =
told it was because ISPs were afraid that providing accurate hopcount &amp;=
 delay information would reveal too much of the internal structure of their=
 network. &quot;Ordinal&quot; mode allows an ISP to obfuscate the details, =
but still provides what most clients need -- a rank ordering.<span style=3D=
"font-family:arial;font-size:small">=A0</span></div>


</div></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"font-size:1=
4px;font-family:Calibri,sans-serif;word-wrap:break-word"><div><br></div><di=
v>


Given that, why would a production ALTO server (as opposed to a research te=
stbed) provide both &quot;numerical&quot; and &quot;ordinal&quot; modes for=
 the same cost type? I&#39;d think the server would provide numerical if it=
&#39;s not afraid to give away that much detail. Otherwise it would provide=
 only offer ordinal.</div>


<div><br></div><div>On top of that, if you think about it, if a server main=
tains numerical cost values, and a client asks for that cost-type in &quot;=
ordinal&quot; mode, the server can just return the numerical values.</div>


</div></blockquote><div><br></div><div>Yep. The idea was to make it easy fo=
r servers.</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"=
font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">


<div><br></div><div>So I don&#39;t think it will be difficult for a server =
to maintain both modes for the same cost type, if only because there&#39;s =
no reason for a server to do that.</div><div><br></div><div>2. Why would a =
client ever want ordinal cost values? The only reason I can think of is if =
the client could rely on &quot;1&quot; being the lowest cost. But that does=
n&#39;t work, because ordinal values can be anything -- they do=A0<b>not</b=
> have to be 1, 2, 3, 4, =85.</div>


<div><br></div><div>So I don&#39;t see clients as needing ordinal mode at a=
ll. It&#39;s just there to warn clients that this cost isn&#39;t linear.</d=
iv></div></blockquote><div><br></div><div>Clients needed to know the differ=
ence between when the servers were providing ordinal values or numerical va=
lues. For example, the P4P approach does not apply to ordinal values.</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 style=3D"font-size:14px;=
font-family:Calibri,sans-serif;word-wrap:break-word"><div><br></div><div>In=
 fact, I&#39;m tempted to suggest that we replace the idea of a &quot;mode&=
quot; attribute with a simple binary attribute called &quot;linear.&quot; F=
or a linear cost, 40 is twice as high as 20, and 21 is only slightly higher=
 than 20. For a non-linear cost, 40 is higher than 21, and 21 is higher tha=
n 20, but we don&#39;t know by how much.</div>


</div></blockquote><div><br></div><div>If the intent is to rename it, then =
I think it&#39;s a mistake to collapse it to a boolean value. =A0Then, that=
 removes flexibility for extensions. For example, what if someone wanted to=
 add a mode that wasn&#39;t represented by a single number, but rather a ke=
y/value map (such as some statistical information about a measurement). =A0=
Having an identifier instead of a boolean value gives more flexibility for =
extensions.</div>


<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div style=3D"font-size:14px;f=
ont-family:Calibri,sans-serif;word-wrap:break-word"><div><br></div><div>3. =
Your last point is about registering cost types. Yes, my proposal would mak=
e it harder to register new cost types with the IANA.</div>


<div><br></div><div>But I&#39;ll turn that around. Why do we need a central=
 registry for cost types at all? Why does the IANA need to control them? So=
rry if I&#39;m stepping on someone&#39;s favorite idea here, but to me, a c=
entral registry seems totally unnecessary. Worse than that, it&#39;s harmfu=
l: it will stifle innovation, by making it much harder to create and experi=
ment with new cost types.</div>


<div><br></div><div>Yes, that means that two independently implemented ALTO=
 servers can each define a new cost type named &quot;myExtendedCost&quot;, =
with completely different semantics. So what? What&#39;s the problem with t=
hat? Clients will know that &quot;myExtendedCost&quot; is only meaningful w=
ithin the context of a specific ALTO server.</div>


<div><br></div><div><div>Note that the cost type extension I proposed takes=
 over the descriptive features of the IANA registry, in that it provides al=
l the information about this new cost type that a potential client needs to=
 know. It doesn&#39;t allow the IANA to manage and control new cost types. =
But I think that&#39;s a good thing!</div>


</div><div><br></div><div>So in short, I suggest dropping the central &quot=
;cost type registry&quot; requirements completely (Section 9.2). Instead, t=
he ALTO server provides a description of its cost types in its resource dir=
ectory. ALTO servers are free to invent new cost types, to differentiate th=
emselves and provide additional value.</div>


</div></blockquote><div><br></div><div>I think the other replies here have =
sufficiently backed up the need for a registry, and addressed the desire to=
 have your own custom type without the need to register it. =A0Right?</div>


<div><br></div><div>At this point, would it be useful to have some guidance=
 from the WG chairs about what exactly should be considered in this thread?=
 =A0I get the feeling like we are straying a long way from the initial ques=
tion (should we combine cost mode and cost type to a single identifier), an=
d discussing large changes that would have been (I think) better brought up=
 during WGLC. =A0If the WG believes that we should go back and discuss thes=
e, that&#39;s fine - I&#39;d just like some clarity on what exactly the ope=
n issues with the draft are.</div>


<div><br></div><div>Thanks,</div><div>Rich</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 style=3D"font-size:14px;font-family:Calibri,sans-se=
rif;word-wrap:break-word">


<div><br></div><div><span style=3D"white-space:pre-wrap">	</span>- Wendy Ro=
ome</div><div><br></div><span><div style=3D"border-right:medium none;paddin=
g-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:11pt=
;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df 1pt solid=
;padding-bottom:0in;border-left:medium none">


<span style=3D"font-weight:bold">From: </span> Richard Alimi &lt;<a href=3D=
"mailto:rich@velvetsea.net" target=3D"_blank">rich@velvetsea.net</a>&gt;<br=
><span style=3D"font-weight:bold">Date: </span> Tue, February 19, 2013 17:5=
1<br>


<span style=3D"font-weight:bold">Subject: </span> Re: [alto] Discussion II:=
 Unifying cost-mode and cost-type to a single type<br></div><div><div><br><=
/div><span style=3D"text-indent:0px;letter-spacing:normal;font-variant:norm=
al;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height=
:normal;border-collapse:separate;text-transform:none;font-size:medium;white=
-space:normal;font-family:Calibri;word-spacing:0px">On Fri, Feb 15, 2013 at=
 12:23 PM, Wendy Roome<span>=A0</span><span dir=3D"ltr">&lt;<a href=3D"mail=
to:w.roome@alcatel-lucent.com" target=3D"_blank">w.roome@alcatel-lucent.com=
</a>&gt;</span><span>=A0</span>wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin-top:0px;margin-right:0px;=
margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color=
:rgb(204,204,204);border-left-style:solid;padding-left:1ex">To return to th=
is issue, I suggest we unify them, so that we have Cost<br>


Types -- period. The &quot;Mode&quot; becomes a property of the Cost Type. =
So if a<br>server provides numerical &amp; ordinal routingcosts, it provide=
s *two*<br>separate Cost Types, say &quot;routingcost&quot; and &quot;routi=
ngcost-ord&quot;.<br>


<br>I believe the result will simplify both clients and servers, and make i=
t<br>easier for servers to introduce additional cost types.<br></blockquote=
><div><br></div><div><div style=3D"font-family:arial,sans-serif;font-size:1=
3px">


I believe that having them separate is a bit more &#39;normalized&#39; of a=
 form and has some important benefits. That is, one just has to define what=
 &#39;hopcount&#39; means once, and then a server can expose that metric in=
 different forms. =A0By creating a single opaque identifier, one now has to=
 register &#39;hopcount&#39; for each and every &quot;mode&quot; that comes=
 along. =A0This also makes it more difficult for a client to understand tha=
t if it wants a particular cost type (but can handle different forms), it h=
as to know beforehand the exact set of identifiers under which it can find =
all of the forms.</div>


<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">For example, consider =
the following:</div><div style=3D"font-family:arial,sans-serif;font-size:13=
px">


(1) Person A registers cost type &#39;some-new-type&#39; and describes it w=
ith numerical costs</div><div style=3D"font-family:arial,sans-serif;font-si=
ze:13px">(2) Person B comes along and wants ordinal costs &#39;with &#39;so=
me-new-type&#39;. Person B then has to go through the registration process =
to create &#39;some-new-type-ord&#39;. =A0[ A side point - do we care about=
 the registry staying clean? Do we have rules on how to construct appropria=
te cost type identifiers so they convey whether they are ordinal or numeric=
al? ]</div>


<div style=3D"font-family:arial,sans-serif;font-size:13px">(3) At some poin=
t down the line, the Reincarnated ALTO Working Group decides to add a new &=
#39;mode&#39; of cost, such as an array of costs that indicates the cost&#3=
9;s historical value over the past week.</div>


<div style=3D"font-family:arial,sans-serif;font-size:13px">(4) Person C loo=
ks at the registry and figures out that they want &#39;some-new-type&#39; t=
o be available in this new mode. Person C then has to go and register &#39;=
some-new-type-historical&#39; before it can be used. [ And this is going to=
 happen for each cost type. ]</div>


<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">In short, I think the =
registry for cost types is going to get messy and it&#39;s going to make it=
 more difficult for a client to say &quot;I want the hopcount costs but I d=
on&#39;t care whether the server gives me the actual costs, or is just goin=
g to rank them&quot;.</div>


<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">All that said, I under=
stand this has been brought up in the past and there are some things that i=
t simplifies (which have been discussed in an earlier thread) and if there =
is good consensus for doing this in the working group, then we can certainl=
y adopt the changes.</div>


</div><div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div>=
<div style=3D"font-family:arial,sans-serif;font-size:13px">Thanks,</div><di=
v style=3D"font-family:arial,sans-serif;font-size:13px">Rich</div></span><b=
r>


</div></span></div>
</blockquote></div><br></div></div>

--14dae9cfcdcad7616a04d6866dbb--

From richard.alimi@gmail.com  Sun Feb 24 22:18:28 2013
Return-Path: <richard.alimi@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 A5FAD21F91A7 for <alto@ietfa.amsl.com>; Sun, 24 Feb 2013 22:18:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4nOonIstqVk5 for <alto@ietfa.amsl.com>; Sun, 24 Feb 2013 22:18:27 -0800 (PST)
Received: from mail-vb0-f48.google.com (mail-vb0-f48.google.com [209.85.212.48]) by ietfa.amsl.com (Postfix) with ESMTP id D935321F9061 for <alto@ietf.org>; Sun, 24 Feb 2013 22:18:25 -0800 (PST)
Received: by mail-vb0-f48.google.com with SMTP id fc21so1502912vbb.35 for <alto@ietf.org>; Sun, 24 Feb 2013 22:18:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=A6OBtu2ZeY3NWew82Oa2WQSwEx1AOTzVia4pkPdFYL0=; b=NWYwoYywFRdlDf7MSuavtTDZcrbD+bcg+qFs1qd9mYzd6JVjJ81BPt5bnaDsB0/jy3 EVmQBPu48NQF45P+rz2WoyFiUkocheyaPJeJ1c/T0AyQ+Cq+K65p8JM5wN9HfwfCKo2P ufVorHPh0MFrGGjkcBirG/+j4bzHL4WHP1FsPl7qoHjKoRwdtx6Vm8NGtnffj3meYGyp QxctMqmBjxqnB8JpVRHC3Glu61zG7mGtJihmz20hYVjjpgGohCeyFugzV+lbEhVhHqOT BXqji5lcABam+BkhF6j5qpww/KHvC2DB6F2flRXmRf1HP3dp0dGWTj77O1PBqnShAtJF uvEQ==
X-Received: by 10.52.70.228 with SMTP id p4mr7981416vdu.89.1361773105190; Sun, 24 Feb 2013 22:18:25 -0800 (PST)
MIME-Version: 1.0
Sender: richard.alimi@gmail.com
Received: by 10.58.209.169 with HTTP; Sun, 24 Feb 2013 22:18:05 -0800 (PST)
In-Reply-To: <CD4D112F.36160%w.roome@alcatel-lucent.com>
References: <45A697A8FFD7CF48BCF2BE7E106F06040901008C@xmb-rcd-x04.cisco.com> <CD4D112F.36160%w.roome@alcatel-lucent.com>
From: Richard Alimi <rich@velvetsea.net>
Date: Sun, 24 Feb 2013 22:18:05 -0800
X-Google-Sender-Auth: jA6bIByeRHteCdPJjV_a8d0ID9o
Message-ID: <CA+cvDaY3boyjY-DuB2_E9ZOE9qz8vwVT0kTL-MYEqkGEF1+5PA@mail.gmail.com>
To: Wendy Roome <w.roome@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=20cf307f335233166a04d68682ff
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2013 06:18:28 -0000

--20cf307f335233166a04d68682ff
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 22, 2013 at 9:50 AM, Wendy Roome <w.roome@alcatel-lucent.com>wr=
ote:

> Okay, I can avoid the IANA registration requirements by using "priv:" or
> "exp:" for custom Cost Types.
>
> But that doesn't answer the question of *why* we should register Cost
> Types. What's the advantage? How does that benefit us? That's a serious
> question. To me, registration looks like an annoyance without any redeemi=
ng
> benefit.
>
> I realize that the goal might have been to make costs interoperable, but =
I
> don't think registration accomplishes that. Take "routingcost". I believe
> all the IANA registration says is that "routingcost is a non-negative
> number, and lower is better". I don't think that's enough. To make
> routingcost interoperable, I'd like to know what "40" means. Better yet, =
I
> think "interoperable" would mean that I could compare routingcost values
> between different ALTO servers, so 40 on one server means roughly the sam=
e
> as 40 on another server.
>
> That's clearly not true.
>
> Here's a sample use-case. I want to select a host for new VM. The VM
> manager gives me the CPU load (0.0 to 1.0) for several hosts. I then ask =
an
> ALTO server for the routingcosts between my client and each of those host=
s.
> I run a function to blend the alto cost and the cpu load into an overall
> cost, using the appropriate weighting and scaling factors, and I select t=
he
> host with the lowest overall cost.
>
> So how do I determine those scaling factors? The IANA registry doesn't
> help. I have to talk to the folks who provide that ALTO server, or else
> just look at the values it returns. If I switch to a different ALTO serve=
r,
> I'll have to start over again.
>
> To me, that is not "interoperable". To me, "interoperable" would mean tha=
t
> I could determine the scaling factors just from the central registry, and
> use the same factors with any ALTO server.
>
> As it stands now, "routingcost" values are only meaningful in the context
> of a specific ALTO server. So even though "routingcost" is registered, it=
's
> still a custom cost that varies widely from server to server. So what's t=
he
> benefit to registration?
>

Some context here: routingcost was intended to be a generic numerical value
that was roughly correlated with the 'goodness' of the source/destination
pair, but we intentionally stayed away from a rigorous definition.  The
belief was that this gives service providers a way to expose a cost that
has benefits to clients without explicitly communicating the basis for that
cost. The P4P approach and its field trials were a good example that even
this can have solid benefits in the real world; we asked multiple service
providers to devise costs but did not give any guidance on how to choose
them.

All that said, I think the other replies here have shown the desire and use
cases for additional cost types that have more formal definitions.

Thanks,
Rich


>
> Sorry to be a pest, but it seems that a while back, someone just declared=
,
> "Well, of course we should to register cost types!" Since then we've all
> accepted that on blind faith. All I'm asking is for is why registration
> helps.
>
> - Wendy Roome
>
>
> From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
> Date: Thu, February 21, 2013 12:16
> To: Bill Roome <w.roome@alcatel-lucent.com>, "alto@ietf.org" <
> alto@ietf.org>
>
> Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a
> single type
>
> This is what you need. A private cost you can use within your ALTO server=
s
> and domain.
>
> "Identifiers prefixed with =92priv:=92 are reserved for Private Use"
>
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>

--20cf307f335233166a04d68682ff
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><div class=3D"gmail_quote">=
On Fri, Feb 22, 2013 at 9:50 AM, Wendy Roome <span dir=3D"ltr">&lt;<a href=
=3D"mailto:w.roome@alcatel-lucent.com" target=3D"_blank">w.roome@alcatel-lu=
cent.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"font-size:14px;font-family:Cal=
ibri,sans-serif;word-wrap:break-word"><div>Okay, I can avoid the IANA regis=
tration requirements by using &quot;priv:&quot; or &quot;exp:&quot; for cus=
tom Cost Types.</div>

<div><br></div><div>But that doesn&#39;t answer the question of *why* we sh=
ould register Cost Types. What&#39;s the advantage? How does that benefit u=
s? That&#39;s a serious question. To me, registration looks like an annoyan=
ce without any redeeming benefit.</div>

<div><br></div><div>I realize that the goal might have been to make costs i=
nteroperable, but I don&#39;t think registration accomplishes that. Take &q=
uot;routingcost&quot;. I believe all the IANA registration says is that &qu=
ot;routingcost is a non-negative number, and lower is better&quot;. I don&#=
39;t think that&#39;s enough. To make routingcost interoperable, I&#39;d li=
ke to know what &quot;40&quot; means. Better yet, I think &quot;interoperab=
le&quot; would mean that I could compare routingcost values between differe=
nt ALTO servers, so 40 on one server means roughly the same as 40 on anothe=
r server.</div>

<div><br></div><div>That&#39;s clearly not true.</div><div><br></div><div>H=
ere&#39;s a sample use-case. I want to select a host for new VM. The VM man=
ager gives me the CPU load (0.0 to 1.0) for several hosts. I then ask an AL=
TO server for the routingcosts between my client and each of those hosts. I=
 run a function to blend the alto cost and the cpu load into an overall cos=
t, using the appropriate weighting and scaling factors, and I select the ho=
st with the lowest overall cost.</div>

<div><br></div><div>So how do I determine those scaling factors? The IANA r=
egistry doesn&#39;t help. I have to talk to the folks who provide that ALTO=
 server, or else just look at the values it returns. If I switch to a diffe=
rent ALTO server, I&#39;ll have to start over again.</div>

<div><br></div><div>To me, that is not &quot;interoperable&quot;. To me, &q=
uot;interoperable&quot; would mean that I could determine the scaling facto=
rs just from the central registry, and use the same factors with any ALTO s=
erver.</div>

<div><br></div><div>As it stands now, &quot;routingcost&quot; values are on=
ly meaningful in the context of a specific ALTO server. So even though &quo=
t;routingcost&quot; is registered, it&#39;s still a custom cost that varies=
 widely from server to server. So what&#39;s the benefit to registration?</=
div>

</div></blockquote><div><br></div><div style>Some context here: routingcost=
 was intended to be a generic numerical value that was roughly correlated w=
ith the &#39;goodness&#39; of the source/destination pair, but we intention=
ally stayed away from a=A0rigorous=A0definition. =A0The belief was that thi=
s gives service providers a way to expose a cost that has benefits to clien=
ts without explicitly communicating the basis for that cost. The P4P approa=
ch and its field trials were a good example that even this can have solid b=
enefits in the real world; we asked multiple service providers to devise co=
sts but did not give any guidance on how to choose them.</div>

<div style><br></div><div style>All that said, I think the other replies he=
re have shown the desire and use cases for additional cost types that have =
more formal definitions.</div><div style><br></div><div style>Thanks,</div>

<div style>Rich</div><div>=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div sty=
le=3D"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><=
div>
<br>
</div><div>Sorry to be a pest, but it seems that a while back, someone just=
 declared, &quot;Well, of course we should to register cost types!&quot; Si=
nce then we&#39;ve all accepted that on blind faith. All I&#39;m asking is =
for is why registration helps.</div>

<div><br></div><div><span style=3D"white-space:pre-wrap">	</span>- Wendy Ro=
ome</div><div><br></div><div><br></div><span><div style=3D"border-right:med=
ium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left=
;font-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b=
5c4df 1pt solid;padding-bottom:0in;border-left:medium none">

<div class=3D"im"><span style=3D"font-weight:bold">From: </span> &quot;Rein=
aldo Penno (repenno)&quot; &lt;<a href=3D"mailto:repenno@cisco.com" target=
=3D"_blank">repenno@cisco.com</a>&gt;<br></div><span style=3D"font-weight:b=
old">Date: </span> Thu, February 21, 2013 12:16<br>

<span style=3D"font-weight:bold">To: </span> Bill Roome &lt;<a href=3D"mail=
to:w.roome@alcatel-lucent.com" target=3D"_blank">w.roome@alcatel-lucent.com=
</a>&gt;, &quot;<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto@iet=
f.org</a>&quot; &lt;<a href=3D"mailto:alto@ietf.org" target=3D"_blank">alto=
@ietf.org</a>&gt;<div class=3D"im">

<br><span style=3D"font-weight:bold">Subject: </span> Re: [alto] Discussion=
 II: Unifying cost-mode and cost-type to a single type<br></div></div><div =
class=3D"im"><div><br></div><span style=3D"text-indent:0px;letter-spacing:n=
ormal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-we=
ight:normal;line-height:normal;border-collapse:separate;text-transform:none=
;font-size:medium;white-space:normal;font-family:Calibri;word-spacing:0px">=
<span style=3D"font-size:14px;font-family:Calibri,sans-serif"><div>

This is what you need. A private cost you can use within your ALTO servers =
and domain.</div><div><br></div><div>&quot;Identifiers prefixed with =92pri=
v:=92 are reserved for Private Use&quot;</div></span></span><br></div></spa=
n></div>


<br>_______________________________________________<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" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/alto</a><br>
<br></blockquote></div><br></div></div>

--20cf307f335233166a04d68682ff--

From internet-drafts@ietf.org  Mon Feb 25 01:26:34 2013
Return-Path: <internet-drafts@ietf.org>
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 0BC8E21F9231; Mon, 25 Feb 2013 01:26:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.476
X-Spam-Level: 
X-Spam-Status: No, score=-102.476 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hlvlxn6031Z0; Mon, 25 Feb 2013 01:26:33 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 819EA21F9254; Mon, 25 Feb 2013 01:26:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130225092633.1510.3938.idtracker@ietfa.amsl.com>
Date: Mon, 25 Feb 2013 01:26:33 -0800
Cc: alto@ietf.org
Subject: [alto] I-D Action: draft-ietf-alto-deployments-06.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2013 09:26:34 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Application-Layer Traffic Optimization Wo=
rking Group of the IETF.

	Title           : ALTO Deployment Considerations
	Author(s)       : Martin Stiemerling
                          Sebastian Kiesel
                          Stefano Previdi
	Filename        : draft-ietf-alto-deployments-06.txt
	Pages           : 46
	Date            : 2013-02-25

Abstract:
   Many Internet applications are used to access resources, such as
   pieces of information or server processes, which are available in
   several equivalent replicas on different hosts.  This includes, but
   is not limited to, peer-to-peer file sharing applications.  The goal
   of Application-Layer Traffic Optimization (ALTO) is to provide
   guidance to these applications, which have to select one or several
   hosts from a set of candidates, that are able to provide a desired
   resource.  The protocol is under specification in the ALTO working
   group.  This memo discusses deployment related issues of ALTO for
   peer-to-peer and CDNs, some preliminary security considerations, and
   also initial guidance for application designers using ALTO.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-deployments

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-alto-deployments-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-alto-deployments-06


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From Martin.Stiemerling@neclab.eu  Mon Feb 25 01:27:52 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
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 8D61721F90A7 for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 01:27:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.497
X-Spam-Level: 
X-Spam-Status: No, score=-103.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uzgr+pzpUaTx for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 01:27:52 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id A02A321F9061 for <alto@ietf.org>; Mon, 25 Feb 2013 01:27:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 0E22C103413; Mon, 25 Feb 2013 10:27:51 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JZL2K8gNf9p6; Mon, 25 Feb 2013 10:27:50 +0100 (CET)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id E0F0410340F; Mon, 25 Feb 2013 10:27:35 +0100 (CET)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 25 Feb 2013 10:27:35 +0100
Message-ID: <512B2E87.1060704@neclab.eu>
Date: Mon, 25 Feb 2013 10:27:35 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Y. Richard Yang" <yry@cs.yale.edu>
References: <51260845.1000909@neclab.eu> <45A697A8FFD7CF48BCF2BE7E106F06040900FF2D@xmb-rcd-x04.cisco.com> <7AEB3D6833318045B4AE71C2C87E8E1729100475@dfweml511-mbs.china.huawei.com> <CANUuoLo3TM-jFV6aTMfBvgsR75QsEBcq6bDP8uzDoBFL1z1-QA@mail.gmail.com>
In-Reply-To: <CANUuoLo3TM-jFV6aTMfBvgsR75QsEBcq6bDP8uzDoBFL1z1-QA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] New ALTO use cases & the upcoming IETF meeting
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2013 09:27:52 -0000

On 02/21/2013 06:51 PM, Y. Richard Yang wrote:
> Dear all,
>
> It is a good idea to run a side meeting! Do we use this mailing list
> to coordinate or use private email messages?

I would announce the meeting to this list here and also ask people if 
they are interested.

Thanks,

   Martin

>
> Thanks.
>
> Richard
>
> On Thu, Feb 21, 2013 at 11:14 AM, Leeyoung <leeyoung@huawei.com
> <mailto:leeyoung@huawei.com>> wrote:
>
> Hi Reinaldo,
>
> I'd like to help this effort in any ways possible.
>
> Thanks. Young
>
> -----Original Message----- From: alto-bounces@ietf.org
> <mailto:alto-bounces@ietf.org> [mailto:alto-bounces@ietf.org
> <mailto:alto-bounces@ietf.org>] On Behalf Of Reinaldo Penno
> (repenno) Sent: Thursday, February 21, 2013 8:17 AM To: Martin
> Stiemerling; alto@ietf.org <mailto:alto@ietf.org> Subject: Re: [alto]
> New ALTO use cases & the upcoming IETF meeting
>
> Thanks Martin,
>
> We will try to organize a side meeting.
>
> regards,
>
> Reinaldo
>
> On 2/21/13 8:43 AM, "Martin Stiemerling"
> <martin.stiemerling@neclab.eu <mailto:martin.stiemerling@neclab.eu>>
> wrote:
>
>> Hi all,
>>
>> I have seen a number of new ALTO drafts for LMAP, I2RS, etc and
> also the
>> wish to discuss a rechartering of the ALTO WG.
>>
>> I still do not see the WG to be ready for any rechartering
>> discussion, as we should first finish up our current chartered
>> items.
>>
>> However, I can see the utility to discuss new ideas on what to do
>> with ALTO, but outside the ALTO session at the upcoming IETF
>> meeting in Orlando.
>>
>> My proposal would be to do a side meeting, i.e., we meet sometimes
>> in the evening over a drink and discuss the new drafts/use cases
>> and
> how to
>> progress ALTO.
>>
>> But, do not rely on my to organize such a side meeting, i.e.,
>> somebody else should take the stab in organizing this.
>>
>> Martin
>>
>> -- IETF Transport Area Director
>>
>> martin.stiemerling@neclab.eu <mailto:martin.stiemerling@neclab.eu>
>>
>> NEC Laboratories Europe NEC Europe Limited Registered Office:
>> Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
>> Registered in England 2832014
>> _______________________________________________ alto mailing list
>> alto@ietf.org <mailto:alto@ietf.org>
>> https://www.ietf.org/mailman/listinfo/alto
>
> _______________________________________________ alto mailing list
> alto@ietf.org <mailto:alto@ietf.org>
> https://www.ietf.org/mailman/listinfo/alto
> _______________________________________________ alto mailing list
> alto@ietf.org <mailto:alto@ietf.org>
> https://www.ietf.org/mailman/listinfo/alto
>
>
>
>
> _______________________________________________ alto mailing list
> alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
>

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From Martin.Stiemerling@neclab.eu  Mon Feb 25 01:28:58 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
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 4428021F9272 for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 01:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.498
X-Spam-Level: 
X-Spam-Status: No, score=-103.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OOLMGQxI0uJP for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 01:28:57 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF6721F9271 for <alto@ietf.org>; Mon, 25 Feb 2013 01:28:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id D88D5103410 for <alto@ietf.org>; Mon, 25 Feb 2013 10:28:56 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tV--zwDtfJFv for <alto@ietf.org>; Mon, 25 Feb 2013 10:28:56 +0100 (CET)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id BFD1F10340F for <alto@ietf.org>; Mon, 25 Feb 2013 10:28:51 +0100 (CET)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 25 Feb 2013 10:28:51 +0100
Message-ID: <512B2ED3.30501@neclab.eu>
Date: Mon, 25 Feb 2013 10:28:51 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: <alto@ietf.org>
References: <20130225092633.1510.3938.idtracker@ietfa.amsl.com>
In-Reply-To: <20130225092633.1510.3938.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Subject: Re: [alto] I-D Action: draft-ietf-alto-deployments-06.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2013 09:28:58 -0000

Hi all,

This update is just a maintenance update of the draft, as it did expire 
in the past.

However, the authors need some reviews to gather feedback about the 
draft, especially also in the light of the ALTO protocol draft using the 
deployment considerations as reference to some operational aspects.

   Martin

On 02/25/2013 10:26 AM, internet-drafts@ietf.org wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the Application-Layer Traffic Optimization Working Group of the IETF.
>
> 	Title           : ALTO Deployment Considerations
> 	Author(s)       : Martin Stiemerling
>                            Sebastian Kiesel
>                            Stefano Previdi
> 	Filename        : draft-ietf-alto-deployments-06.txt
> 	Pages           : 46
> 	Date            : 2013-02-25
>
> Abstract:
>     Many Internet applications are used to access resources, such as
>     pieces of information or server processes, which are available in
>     several equivalent replicas on different hosts.  This includes, but
>     is not limited to, peer-to-peer file sharing applications.  The goal
>     of Application-Layer Traffic Optimization (ALTO) is to provide
>     guidance to these applications, which have to select one or several
>     hosts from a set of candidates, that are able to provide a desired
>     resource.  The protocol is under specification in the ALTO working
>     group.  This memo discusses deployment related issues of ALTO for
>     peer-to-peer and CDNs, some preliminary security considerations, and
>     also initial guidance for application designers using ALTO.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-alto-deployments
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-alto-deployments-06
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-alto-deployments-06
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From w.roome@alcatel-lucent.com  Mon Feb 25 07:30:17 2013
Return-Path: <w.roome@alcatel-lucent.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 4815321F9472 for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 07:30:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.645
X-Spam-Level: 
X-Spam-Status: No, score=-9.645 tagged_above=-999 required=5 tests=[AWL=-0.443, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c30WsgYeEsTK for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 07:30:14 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by ietfa.amsl.com (Postfix) with ESMTP id 3883721F88A2 for <alto@ietf.org>; Mon, 25 Feb 2013 07:30:14 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id r1PFU8t5011997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 25 Feb 2013 09:30:08 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id r1PFU7Fo002159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Feb 2013 09:30:08 -0600
Received: from [135.222.152.198] (wdr-i7mbp.mh.lucent.com [135.222.152.198]) by umail.lucent.com (8.13.8/TPES) with ESMTP id r1PFU37X026275; Mon, 25 Feb 2013 09:30:06 -0600 (CST)
User-Agent: Microsoft-MacOutlook/14.3.1.130117
Date: Mon, 25 Feb 2013 10:30:04 -0500
From: Wendy Roome <w.roome@alcatel-lucent.com>
To: Richard Alimi <rich@velvetsea.net>
Message-ID: <CD50DEFD.36F30%w.roome@alcatel-lucent.com>
Thread-Topic: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
In-Reply-To: <CA+cvDabAFXtZFEcE+jTgyHPjpcHWYj_sA6cit4WL=0H6YYnQpQ@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3444633009_25398655"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2013 15:30:17 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3444633009_25398655
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

I agree the client needs to know the mode for a cost type. To use an old
analogy, an "ordinal" cost type is like the warning "Drawing Not To Scale."

But I think the real question is whether "modes" are orthogonal to "cost
types." We've been assuming they are -- we've been assuming any "cost type"
can be presented in any "mode," and that clients would want to select the
mode independently of the cost type.

I don't think that's true. Consider the two modes we have now -- numerical
and ordinal. For costs based on delay or distance, yes, those are orthogona=
l
-- we can easy transform numerical costs into ordinal costs. But consider a
hopcount cost. The numerical version is already an ordinal, more or less.
Sure, we can disguise the hopcounts by transforming them, but that just
turns an "ordinal" hopcount cost into a general distance-based cost. Why
bother?

And "ordinal" mode is meaningless for the string-valued cost types that hav=
e
been proposed in extensions.

On top of that, if modes really are orthogonal -- if the various modes are
mathematical transforms of an underlying "numerical" cost -- why can't the
client do those transforms?  Take "ordinal" mode. It only takes a few lines
of code to convert an arbitrary set of values into the ordinals 1, 2, 3,
etc. If a client wants to rank-order the costs, a client can easily do that=
.

So I claim that "mode" is really a property of "cost type" -- they should b=
e
unified, not orthogonal. The client must be aware of the mode, because it's
part of the semantics of the cost type. But a client doesn't need to reques=
t
"mode" independently of "cost type." If a client wants a "mode" that is a
simple transform of a cost type, the client should do the transform, and
offload the work from the server to the client. And if we define a mode tha=
t
isn't a simple transform, then it's inherently part of the definition of th=
e
cost type.

So what would that mean for the protocol?   In the resource directory entry
for a uri, the server would give the cost-type, but not cost-mode. In a
filtered cost-map request, the client would specify cost-type, but not
cost-mode.  And if you accept my suggestion of a "cost-types" list in the
resource directory, the entry for each type would include some sort of
"mode" attribute.

- Wendy Roome


From:  Richard Alimi <rich@velvetsea.net>
Date:  Mon, February 25, 2013 01:12
Subject:  Re: [alto] Discussion II: Unifying cost-mode and cost-type to a
single type
>=20
> 2. Why would a client ever want ordinal cost values? The only reason I ca=
n
> think of is if the client could rely on "1" being the lowest cost. But th=
at
> doesn't work, because ordinal values can be anything -- they do not have =
to be
> 1, 2, 3, 4, =8A.
>=20
> So I don't see clients as needing ordinal mode at all. It's just there to=
 warn
> clients that this cost isn't linear.

Clients needed to know the difference between when the servers were
providing ordinal values or numerical values. For example, the P4P approach
does not apply to ordinal values.

>=20
> In fact, I'm tempted to suggest that we replace the idea of a "mode" attr=
ibute
> with a simple binary attribute called "linear." For a linear cost, 40 is =
twice
> as high as 20, and 21 is only slightly higher than 20. For a non-linear c=
ost,
> 40 is higher than 21, and 21 is higher than 20, but we don't know by how =
much.

If the intent is to rename it, then I think it's a mistake to collapse it t=
o
a boolean value.  Then, that removes flexibility for extensions. For
example, what if someone wanted to add a mode that wasn't represented by a
single number, but rather a key/value map (such as some statistical
information about a measurement).  Having an identifier instead of a boolea=
n
value gives more flexibility for extensions.



--B_3444633009_25398655
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>I agree the client needs to =
know the mode for a cost type. To use an old analogy, an "ordinal" cost type=
 is like the warning "Drawing Not To Scale."</div><div><br></div><div>But I =
think the real question is whether "modes" are orthogonal to "cost types." W=
e've been assuming they are -- we've been assuming any "cost type" can be pr=
esented in any "mode," and that clients would want to select the mode indepe=
ndently of the cost type.</div><div><br></div><div>I don't think that's true=
. Consider the two modes we have now -- numerical and ordinal. For costs bas=
ed on delay or distance, yes, those are orthogonal -- we can easy transform =
numerical costs into ordinal costs. But consider a hopcount cost. The numeri=
cal version is already an ordinal, more or less. Sure, we can disguise the h=
opcounts by transforming them, but that just turns an "ordinal" hopcount cos=
t into a general distance-based cost. Why bother?</div><div><br></div><div>A=
nd "ordinal" mode is meaningless for the string-valued cost types that have =
been proposed in extensions.</div><div><br></div><div>On top of that, if mod=
es really are orthogonal -- if the various modes are mathematical transforms=
 of an underlying "numerical" cost -- why can't the client do those transfor=
ms? &nbsp;Take "ordinal" mode. It only takes a few lines of code to convert =
an arbitrary set of values into the ordinals 1, 2, 3, etc. If a client wants=
 to rank-order the costs, a client can easily do that.</div><div><br></div><=
div>So I claim that "mode" is really a property of "cost type" -- they shoul=
d be unified, not orthogonal. The client must be aware of the mode, because =
it's part of the semantics of the cost type. But a client doesn't need to re=
quest "mode" independently of "cost type." If a client wants a "mode" that i=
s a simple transform of a cost type, the client should do the transform, and=
 offload the work from the server to the client. And if we define a mode tha=
t isn't a simple transform, then it's inherently part of the definition of t=
he cost type.</div><div><br></div><div>So what would that mean for the proto=
col? &nbsp; In the resource directory entry for a uri, the server would give=
 the cost-type, but not cost-mode.&nbsp;In a filtered cost-map request, the =
client would specify cost-type, but not cost-mode.&nbsp;&nbsp;And if you acc=
ept my suggestion of a "cost-types" list in the resource directory, the entr=
y for each type would include some sort of "mode" attribute.</div><div><br><=
/div><div><span class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>- Wen=
dy Roome</div><div><br></div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION">=
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:blac=
k; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in=
; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORD=
ER-RIGHT: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">From=
: </span> Richard Alimi &lt;<a href=3D"mailto:rich@velvetsea.net">rich@velvets=
ea.net</a>&gt;<br><span style=3D"font-weight:bold">Date: </span> Mon, February=
 25, 2013 01:12<br><span style=3D"font-weight:bold">Subject: </span> Re: [alto=
] Discussion II: Unifying cost-mode and cost-type to a single type<br></div>=
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; color: rgb(=
0, 0, 0); font-family: Calibri; font-style: normal; font-variant: normal; fo=
nt-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-spac=
e: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effec=
t: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; fon=
t-size: medium; "><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; ma=
rgin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: =
1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; paddin=
g-left: 1ex; "><div style=3D"font-size: 14px; font-family: Calibri, sans-serif=
; word-wrap: break-word; "><div><br class=3D"Apple-interchange-newline">2. Why=
 would a client ever want ordinal cost values? The only reason I can think o=
f is if the client could rely on "1" being the lowest cost. But that doesn't=
 work, because ordinal values can be anything -- they do&nbsp;<b>not</b><spa=
n class=3D"Apple-converted-space">&nbsp;</span>have to be 1, 2, 3, 4, &#8230;.=
</div><div><br></div><div>So I don't see clients as needing ordinal mode at =
all. It's just there to warn clients that this cost isn't linear.</div></div=
></blockquote><div><br></div><div>Clients needed to know the difference betw=
een when the servers were providing ordinal values or numerical values. For =
example, the P4P approach does not apply to ordinal values.</div><div><br></=
div><blockquote class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0p=
x; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-le=
ft-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; "=
><div style=3D"font-size: 14px; font-family: Calibri, sans-serif; word-wrap: b=
reak-word; "><div><br></div><div>In fact, I'm tempted to suggest that we rep=
lace the idea of a "mode" attribute with a simple binary attribute called "l=
inear." For a linear cost, 40 is twice as high as 20, and 21 is only slightl=
y higher than 20. For a non-linear cost, 40 is higher than 21, and 21 is hig=
her than 20, but we don't know by how much.</div></div></blockquote><div><br=
></div><div>If the intent is to rename it, then I think it's a mistake to co=
llapse it to a boolean value. &nbsp;Then, that removes flexibility for exten=
sions. For example, what if someone wanted to add a mode that wasn't represe=
nted by a single number, but rather a key/value map (such as some statistica=
l information about a measurement). &nbsp;Having an identifier instead of a =
boolean value gives more flexibility for extensions.</div></span></span></bo=
dy></html>

--B_3444633009_25398655--



From repenno@cisco.com  Mon Feb 25 08:51:19 2013
Return-Path: <repenno@cisco.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 1DD8321F94F7 for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 08:51:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.723
X-Spam-Level: 
X-Spam-Status: No, score=-9.723 tagged_above=-999 required=5 tests=[AWL=-0.877, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1g9S5gYTpjHZ for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 08:51:14 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 82F6721F94B2 for <alto@ietf.org>; Mon, 25 Feb 2013 08:51:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9816; q=dns/txt; s=iport; t=1361811073; x=1363020673; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=32EIOEYMAO9u/U9AOT4bfpBdkAXSyQOvxf5ZlfilpuM=; b=bQMGAHzKX3Ak9joVngwAkKmoeIj/a6+zYcKHhkyVcJ0LYG5JcLh1UnHq oMyhv2VJICaTsMMxjsZm07PVfbCq8JDbXyQOE2hVaVy7B7yF4RxoZW77k MvuGT1Lp/eNAJRw0B2LoyXYL1VLPCLT1xCTGgpxLiAJXrztkyl3Ui6DO9 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAGWVK1GtJV2b/2dsb2JhbABFhk+7Bg14FnOCHwEBAQQBAQEkDToLEgEIDgMDAQIBBAYiBCULHQgCBAENBQiICwySSJp7BpFhgR2NQBYQCweCJzhhA5J8hF6PSIMHgic
X-IronPort-AV: E=Sophos;i="4.84,735,1355097600"; d="scan'208";a="180868315"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-2.cisco.com with ESMTP; 25 Feb 2013 16:51:12 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r1PGpCLQ030193 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Feb 2013 16:51:12 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.112]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Mon, 25 Feb 2013 10:51:12 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Sebastian Kiesel <ietf-alto@skiesel.de>, Wendy Roome <w.roome@alcatel-lucent.com>
Thread-Topic: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
Thread-Index: AQHOEFD6VY+ntXZyY0eKp/DUkgLdjpiEwAyAgAHOP4CAAXoFAIAC+fWA
Date: Mon, 25 Feb 2013 16:51:12 +0000
Message-ID: <45A697A8FFD7CF48BCF2BE7E106F060409010F3D@xmb-rcd-x04.cisco.com>
In-Reply-To: <20130223162358.GH9265@gw01.ehlo.wurstkaes.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [10.21.114.32]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <14707B6A1DF5024084D8D385CBFAB5EA@cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2013 16:51:19 -0000

SSBhcHByZWNpYXRlIHRoZSBvYnNlcnZhdGlvbnMgcmVsYXRlZCB0byBjb3N0IGFuZCBiZWxpZXZl
IHNvbWUgZGlzY3Vzc2lvbg0KaXMgd2FycmFudGVkIGJ1dCBzb21lIG9ic2VydmF0aW9uczoNCg0K
LSBMb3dlciBpcyBiZXR0ZXIgaXMgbW9zdGx5IHdoYXQgeW91IGdldCBpbiByb3V0ZXJzLiBGb3Ig
ZXhhbXBsZSwgT1NQRiBoYXMNCmEgd2VsbCBkZWZpbmVkIG1ldHJpYyBidXQgeW91IGNhbiBpbXBv
cnQgQkdQIHJvdXRlcyBpbnRvIE9TUEYgKGFuZA0KdmljZS12ZXJzYSkgd2l0aCBkZWZhdWx0IG9y
IGRpZmZlcmVudCBtZXRyaWNzLiBZb3UgY2FuIGFkZCBzdGF0aWMgcm91dGVzLA0KY2hhbmdlcyBw
cmVmZXJlbmNlcywgZXRjLg0KDQpBbiBBTFRPIFNlcnZlciBpcyBubyBkaWZmZXJlbnQuIEl0IG5l
ZWRzIHRvIHRha2UgaW5wdXRzIGZyb20gZGlmZmVyZW50DQpzb3VyY2VzIGFuZCBjb21lIHVwIHdp
dGggYSBjb3N0IG1ldHJpYy4gSWYgd2UgbmVlZCB0byBkZWZpbmUgd2hhdCBjb3N0DQptZWFucyBJ
IHN1Z2dlc3Qgd2UgdGFrZSB0aGUgZGVmaW5pdGlvbiBmcm9tIHJvdXRpbmcgZm9sa3MgKGZvciBl
eGFtcGxlLA0KcmVmIFBDRS9CR1ApLiBEbyB0aGV5IGhhdmUgb25lPyBGb3IgZXhhbXBsZSwgaWYg
SSBkdW1wIHRoZSBmb3J3YXJkaW5nDQp0YWJsZSBvZiBhIHJvdXRlciBhbmQgaXQgc2hvd3MgdGhh
dCBmb3IgYSBjZXJ0YWluIGRlc3RpbmF0aW9uIHRoZSBjb3N0IGlzDQoiNTAiIHRocm91Z2ggYSBj
ZXJ0YWluIGludGVyZmFjZSwgIHdoYXQgY2FuIEkgaW5mZXIgZnJvbSBpdCBnaXZlbiB0aGUgbWFz
aA0Kb2YgZGlmZmVyZW50IGlucHV0cyBhIHJvdXRlciBjYW4gdGFrZSB0byBjYWxjdWxhdGUgdGhh
dD8NCg0KLSBEaWZmZXJlbnQgQUxUTyBTZXJ2ZXJzIG1pZ2h0IGJlIGEgcHJvYmxlbSBpZiB0aGV5
IGFyZSBpbiBkaWZmZXJlbnQNCmRvbWFpbnMuIEFMVE8gc2VydmVycyB3aXRoaW4gYSBzaW5nbGUg
ZG9tYWluIHRoYXQgbmVlZCB0byBleGNoYW5nZSBjb3N0DQptYXBzIG5lZWQgdG8gdXNlIHRoZSBz
YW1lIGFsZ29yaXRobXMuDQoNCi0gRGlmZmVyZW50IEFMVE8gc2VydmVycyBpbiBkaWZmZXJlbnQg
ZG9tYWlucyBpbiBhbm90aGVyIGlzc3VlLiBUaGlzIHdhcw0KYW4gaXNzdWUgd2Ugd29ya2VkIG9u
Og0KDQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtcGVubm8tYWx0by1jZG4tMDMj
cGFnZS0xNw0KDQpJIGJlbGlldmUgaW1wbGVtZW50YXRpb25zIGp1c3QgdXNlIEJHUCBjb3N0Lg0K
DQpUaGFua3MsDQoNClJlaW5hbGRvDQoNCg0KT24gMi8yMy8xMyAxOjIzIFBNLCAiU2ViYXN0aWFu
IEtpZXNlbCIgPGlldGYtYWx0b0Bza2llc2VsLmRlPiB3cm90ZToNCg0KPkhpLA0KPg0KPnlvdXIg
b2JzZXJ2YXRpb25zIHJlZ2FyZGluZyB0aGUgInJvdXRpbmcgY29zdCIgY29zdCB0eXBlIGFyZSBy
aWdodCAtIHdlDQo+Y2Fubm90IHNheSBtb3JlIHRoYW4gImxvd2VyIGlzdCBiZXR0ZXIiIGFuZCB0
aGVyZSBpcyBubyB3YXkgdG8gY29tcGFyZQ0KPnZhbHVlcyByZXRyaWV2ZWQgZnJvbSBkaWZmZXJl
bnQgQUxUTyBzZXJ2ZXJzLg0KPlRoaXMgd2FzIGEgY29uc2Npb3VzDQo+ZGVjaXNpb24gZm9yIHRo
ZSBkZWZhdWx0IGNvc3QgdHlwZS4gIFBlcnNvbmFsbHksIEkgd291bGQgaGF2ZSBwcmVmZXJyZWQN
Cj50byBjYWxsIHRoZSBkZWZhdWx0IGNvc3QgdHlwZSAicmVsYXRpdmUgcHJlZmVyZW5jZSIgaW4g
b3JkZXIgdG8gMSkgc2hvdw0KPnRoYXQgdGhpcyBpcyBpbmRlZWQgYSByZWxhdGl2ZSBtZWFzdXJl
LCAyKSByZW1vdmUgdGhlIGFtYmlndWl0eSB3aGV0aGVyDQo+Y29zdCBpcyB0byBiZSB1bmRlcnN0
b29kIGluIHRoZSBzZW5zZSBvZiByb3V0aW5nIHByb3RvY29scyBhcyBvcHBvc2VkIHRvDQo+bW9u
ZXRhcnkgY29zdCBmb3Igc2VuZGluZyB0cmFmZmljIG92ZXIgc3BlY2lmaWMgbGlua3MsIGFuZCAz
KSBleHBsaWNpdGx5DQo+YWxsb3cgdGhlIEFMVE8gc2VydmVyIG9wZXJhdG9yIHRvIGV4cHJlc3Mg
cHJlZmVyZW5jZXMgYmFzZWQgb24NCj5jb21wbGV0ZWx5IGRpZmZlcmVudCBpc3N1ZXMgdGhhbiAi
Y29zdCIuDQo+DQo+DQo+T24gdGhlIG90aGVyIGhhbmQsIHRoZXJlIGFyZSBtYW55IG90aGVyIGNv
c3QgdHlwZXMgKG9yICJyYXRpbmcNCj5jcml0ZXJpYSIsIGFzIHRoZSBBTFRPIHJlcXVpcmVtZW50
cyBkb2N1bWVudCBSRkMgNjcwOCBjYWxscyB0aGVtKSwgd2hlcmUNCj5hbiBleGFjdCBzcGVjaWZp
Y2F0aW9uIGhvdyB0byBjb21wdXRlIGFuZCBob3cgdG8gZW5jb2RlIHRoZW0gbWFrZXMNCj5zZW5z
ZSwgZS5nLjoNCj4NCj4tIGRyYWZ0LXNjaGFyZi1hbHRvLXZwbi1zZXJ2aWNlLTAwICB0YWxrcyBh
Ym91dCBwdWJsaXNoaW5nIHRoZQ0KPiAgZ2VvZ3JhcGhpY2FsIGxvY2F0aW9uIG9mIGEgZGF0YSBj
ZW50ZXIgdXNpbmcgQUxUTy4gSG93IGV4Y2F0bHkNCj4gIGRvIHdlIGVuY29kZSBsb25naXR1ZGUv
bGF0aXR1ZGU/ICAgVGhpcyBtaWdodCBmaXQgaW50byB0d28gbGluZXMNCj4gIG9mIHRleHQgZGly
ZWN0bHkgaW4gdGhlIElBTkEgcmVnaXN0cnkuDQo+DQo+LSBIb3AgY291bnQsIGRlZmluZWQgYXMg
dGhlIG9uZS13YXkgVFRMIGRlY3JlYXNlIHlvdSB3aWxsIG9ic2VydmUNCj4gIGluIHRoZSBJUCBw
YWNrZXQgaGVhZGVyIHdoZW4gc2VuZGluZyBwYWNrZXRzIHRvIHRoZSB0YXJnZXQgaG9zdA0KPiAg
LT4gYSB3ZWxsIGRlZmluZWQgbWVhc3VyZSB0aGF0IGNhbiBiZSBjb21wYXJlZCBhbW9uZyBzZXJ2
ZXJzDQo+DQo+LSBXZWlnaHRlZCBwYXRoIGxlbmd0aCwgbWF5YmUgc29tZXRoaW5nIGxpa2UNCj4N
Cj5wYXRoX2xlbmd0aCA6PSANCj4gICAgMiAqIChOdW1iZXIgb2YgdHJhdmVyc2VkICAxMCBHYnBz
IGxpbmtzIGluIHRoZSBhY2Nlc3MgbmV0d29ya3MpDQo+ICArIDQgKiAoTnVtYmVyIG9mIHRyYXZl
cnNlZCAgIDEgR2JwcyBsaW5rcyBpbiB0aGUgYWNjZXNzIG5ldHdvcmtzKQ0KPiArIDE5ICogKE51
bWJlciBvZiB0cmF2ZXJzZWQgMTAwIE1icHMgbGlua3MgaW4gdGhlIGFjY2VzcyBuZXR3b3JrcykN
Cj4gKyAxMDAgKihOdW1iZXIgb2YgdHJhdmVyc2VkICAxMCBNYnBzIGxpbmtzIGluIHRoZSBhY2Nl
c3MgbmV0d29ya3MpDQo+ICsgMzAgKiAoTnVtYmVyIG9mIHRyYXZlcnNlZCBBdXRvbm9tb3VzIFN5
c3RlbXMgYmV0d2VlbiB0aGUgYWNjZXNzIG4udydzKQ0KPg0KPiAgVGhpcyBpcyBmb3IgaWxsdXN0
cmF0aW9uIG9ubHkgLSB0aGUgd2VpZ2h0cyBpbiBlYWNoIGxpbmUgcHJvYmFibHkgbmVlZA0KPiAg
dHdlYWtpbmcuICBTdWNoIGEgcmF0aGVyIGxvbmcgZGVmaW5pdGlvbiBwcm9iYWJseSBuZWVkcyBh
biBvd24NCj4gIHNwZWNpZmljYXRpb24gZG9jdW1lbnQgYmVmb3JlIHJlZ2lzdGVyaW5nLg0KPiAg
DQo+LSBGb3IgYSBsb25nZXIgbGlzdCBvZiBvdGhlciBjcml0ZXJpYSB3ZSBkaXNjdXNzZWQgbG9u
ZyB0aW1lIGFnbyBzZWUNCj4gIHNlY3Rpb24gNSBvZiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaWQv
ZHJhZnQtaWV0Zi1hbHRvLXJlcXMtMDYudHh0DQo+DQo+DQo+DQo+U28gZm9yIG1lIHRoZSBjb25j
bHVzaW9uIGlzOiB0aGUgZmFjdCB0aGF0IHdlIGNhbm5vdCBjb21wYXJlIG91cg0KPmRlZmF1bHQg
Y29zdCB0eXBlICJyb3V0aW5nIGNvc3QiIGJldHdlZW4gZGlmZmVyZW50IEFMVE8gc2VydmVycyBk
b2VzDQo+bm90IGNvbnRyYWRpY3QgdGhlIG5lZWQgdG8gZXN0YWJsaXNoIGEgcmVnaXN0cnkgZm9y
IHJlZ2lzdGVyaW5nIGFuZA0KPmRlZmluaW5nIG1vcmUgY29tcGxleCBjb3N0IHR5cGVzLCB3aGlj
aCBtYXkgb3IgbWF5IG5vdCBoYXZlIGNsZWFyDQo+c2NhbGluZyBmYWN0b3JzIG9yIHVuaXRzIG9m
IG1lYXN1cmVtZW50Lg0KPg0KPlRoYW5rcw0KPlNlYmFzdGlhbg0KPg0KPg0KPg0KPg0KPg0KPg0K
Pk9uIEZyaSwgRmViIDIyLCAyMDEzIGF0IDEyOjUwOjU5UE0gLTA1MDAsIFdlbmR5IFJvb21lIHdy
b3RlOg0KPj4gT2theSwgSSBjYW4gYXZvaWQgdGhlIElBTkEgcmVnaXN0cmF0aW9uIHJlcXVpcmVt
ZW50cyBieSB1c2luZyAicHJpdjoiIG9yDQo+PiAiZXhwOiIgZm9yIGN1c3RvbSBDb3N0IFR5cGVz
Lg0KPj4gDQo+PiBCdXQgdGhhdCBkb2Vzbid0IGFuc3dlciB0aGUgcXVlc3Rpb24gb2YgKndoeSog
d2Ugc2hvdWxkIHJlZ2lzdGVyIENvc3QNCj4+VHlwZXMuDQo+PiBXaGF0J3MgdGhlIGFkdmFudGFn
ZT8gSG93IGRvZXMgdGhhdCBiZW5lZml0IHVzPyBUaGF0J3MgYSBzZXJpb3VzDQo+PnF1ZXN0aW9u
Lg0KPj4gVG8gbWUsIHJlZ2lzdHJhdGlvbiBsb29rcyBsaWtlIGFuIGFubm95YW5jZSB3aXRob3V0
IGFueSByZWRlZW1pbmcNCj4+YmVuZWZpdC4NCj4+IA0KPj4gSSByZWFsaXplIHRoYXQgdGhlIGdv
YWwgbWlnaHQgaGF2ZSBiZWVuIHRvIG1ha2UgY29zdHMgaW50ZXJvcGVyYWJsZSwNCj4+YnV0IEkN
Cj4+IGRvbid0IHRoaW5rIHJlZ2lzdHJhdGlvbiBhY2NvbXBsaXNoZXMgdGhhdC4gVGFrZSAicm91
dGluZ2Nvc3QiLiBJDQo+PmJlbGlldmUNCj4+IGFsbCB0aGUgSUFOQSByZWdpc3RyYXRpb24gc2F5
cyBpcyB0aGF0ICJyb3V0aW5nY29zdCBpcyBhIG5vbi1uZWdhdGl2ZQ0KPj4gbnVtYmVyLCBhbmQg
bG93ZXIgaXMgYmV0dGVyIi4gSSBkb24ndCB0aGluayB0aGF0J3MgZW5vdWdoLiBUbyBtYWtlDQo+
PiByb3V0aW5nY29zdCBpbnRlcm9wZXJhYmxlLCBJJ2QgbGlrZSB0byBrbm93IHdoYXQgIjQwIiBt
ZWFucy4gQmV0dGVyDQo+PnlldCwgSQ0KPj4gdGhpbmsgImludGVyb3BlcmFibGUiIHdvdWxkIG1l
YW4gdGhhdCBJIGNvdWxkIGNvbXBhcmUgcm91dGluZ2Nvc3QgdmFsdWVzDQo+PiBiZXR3ZWVuIGRp
ZmZlcmVudCBBTFRPIHNlcnZlcnMsIHNvIDQwIG9uIG9uZSBzZXJ2ZXIgbWVhbnMgcm91Z2hseSB0
aGUNCj4+c2FtZQ0KPj4gYXMgNDAgb24gYW5vdGhlciBzZXJ2ZXIuDQo+PiANCj4+IFRoYXQncyBj
bGVhcmx5IG5vdCB0cnVlLg0KPj4gDQo+PiBIZXJlJ3MgYSBzYW1wbGUgdXNlLWNhc2UuIEkgd2Fu
dCB0byBzZWxlY3QgYSBob3N0IGZvciBuZXcgVk0uIFRoZSBWTQ0KPj5tYW5hZ2VyDQo+PiBnaXZl
cyBtZSB0aGUgQ1BVIGxvYWQgKDAuMCB0byAxLjApIGZvciBzZXZlcmFsIGhvc3RzLiBJIHRoZW4g
YXNrIGFuIEFMVE8NCj4+IHNlcnZlciBmb3IgdGhlIHJvdXRpbmdjb3N0cyBiZXR3ZWVuIG15IGNs
aWVudCBhbmQgZWFjaCBvZiB0aG9zZSBob3N0cy4NCj4+SSBydW4NCj4+IGEgZnVuY3Rpb24gdG8g
YmxlbmQgdGhlIGFsdG8gY29zdCBhbmQgdGhlIGNwdSBsb2FkIGludG8gYW4gb3ZlcmFsbCBjb3N0
LA0KPj4gdXNpbmcgdGhlIGFwcHJvcHJpYXRlIHdlaWdodGluZyBhbmQgc2NhbGluZyBmYWN0b3Jz
LCBhbmQgSSBzZWxlY3QgdGhlDQo+Pmhvc3QNCj4+IHdpdGggdGhlIGxvd2VzdCBvdmVyYWxsIGNv
c3QuDQo+PiANCj4+IFNvIGhvdyBkbyBJIGRldGVybWluZSB0aG9zZSBzY2FsaW5nIGZhY3RvcnM/
IFRoZSBJQU5BIHJlZ2lzdHJ5IGRvZXNuJ3QNCj4+aGVscC4NCj4+IEkgaGF2ZSB0byB0YWxrIHRv
IHRoZSBmb2xrcyB3aG8gcHJvdmlkZSB0aGF0IEFMVE8gc2VydmVyLCBvciBlbHNlIGp1c3QNCj4+
bG9vaw0KPj4gYXQgdGhlIHZhbHVlcyBpdCByZXR1cm5zLiBJZiBJIHN3aXRjaCB0byBhIGRpZmZl
cmVudCBBTFRPIHNlcnZlciwgSSdsbA0KPj5oYXZlDQo+PiB0byBzdGFydCBvdmVyIGFnYWluLg0K
Pj4gDQo+PiBUbyBtZSwgdGhhdCBpcyBub3QgImludGVyb3BlcmFibGUiLiBUbyBtZSwgImludGVy
b3BlcmFibGUiIHdvdWxkIG1lYW4NCj4+dGhhdCBJDQo+PiBjb3VsZCBkZXRlcm1pbmUgdGhlIHNj
YWxpbmcgZmFjdG9ycyBqdXN0IGZyb20gdGhlIGNlbnRyYWwgcmVnaXN0cnksIGFuZA0KPj51c2UN
Cj4+IHRoZSBzYW1lIGZhY3RvcnMgd2l0aCBhbnkgQUxUTyBzZXJ2ZXIuDQo+PiANCj4+IEFzIGl0
IHN0YW5kcyBub3csICJyb3V0aW5nY29zdCIgdmFsdWVzIGFyZSBvbmx5IG1lYW5pbmdmdWwgaW4g
dGhlDQo+PmNvbnRleHQgb2YNCj4+IGEgc3BlY2lmaWMgQUxUTyBzZXJ2ZXIuIFNvIGV2ZW4gdGhv
dWdoICJyb3V0aW5nY29zdCIgaXMgcmVnaXN0ZXJlZCwgaXQncw0KPj4gc3RpbGwgYSBjdXN0b20g
Y29zdCB0aGF0IHZhcmllcyB3aWRlbHkgZnJvbSBzZXJ2ZXIgdG8gc2VydmVyLiBTbyB3aGF0J3MN
Cj4+dGhlDQo+PiBiZW5lZml0IHRvIHJlZ2lzdHJhdGlvbj8NCj4+IA0KPj4gU29ycnkgdG8gYmUg
YSBwZXN0LCBidXQgaXQgc2VlbXMgdGhhdCBhIHdoaWxlIGJhY2ssIHNvbWVvbmUganVzdA0KPj5k
ZWNsYXJlZCwNCj4+ICJXZWxsLCBvZiBjb3Vyc2Ugd2Ugc2hvdWxkIHRvIHJlZ2lzdGVyIGNvc3Qg
dHlwZXMhIiBTaW5jZSB0aGVuIHdlJ3ZlIGFsbA0KPj4gYWNjZXB0ZWQgdGhhdCBvbiBibGluZCBm
YWl0aC4gQWxsIEknbSBhc2tpbmcgaXMgZm9yIGlzIHdoeSByZWdpc3RyYXRpb24NCj4+IGhlbHBz
Lg0KPj4gDQo+PiAtIFdlbmR5IFJvb21lDQo+PiANCj4+IA0KPj4gRnJvbTogICJSZWluYWxkbyBQ
ZW5ubyAocmVwZW5ubykiIDxyZXBlbm5vQGNpc2NvLmNvbT4NCj4+IERhdGU6ICBUaHUsIEZlYnJ1
YXJ5IDIxLCAyMDEzIDEyOjE2DQo+PiBUbzogIEJpbGwgUm9vbWUgPHcucm9vbWVAYWxjYXRlbC1s
dWNlbnQuY29tPiwgImFsdG9AaWV0Zi5vcmciDQo+PiA8YWx0b0BpZXRmLm9yZz4NCj4+IFN1Ympl
Y3Q6ICBSZTogW2FsdG9dIERpc2N1c3Npb24gSUk6IFVuaWZ5aW5nIGNvc3QtbW9kZSBhbmQgY29z
dC10eXBlIHRvDQo+PmENCj4+IHNpbmdsZSB0eXBlDQo+PiANCj4+IFRoaXMgaXMgd2hhdCB5b3Ug
bmVlZC4gQSBwcml2YXRlIGNvc3QgeW91IGNhbiB1c2Ugd2l0aGluIHlvdXIgQUxUTw0KPj5zZXJ2
ZXJzDQo+PiBhbmQgZG9tYWluLg0KPj4gDQo+PiAiSWRlbnRpZmllcnMgcHJlZml4ZWQgd2l0aCCp
9nByaXY6qfYgYXJlIHJlc2VydmVkIGZvciBQcml2YXRlIFVzZSINCj4+IA0KPj4gDQo+PiANCj4N
Cj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiBh
bHRvIG1haWxpbmcgbGlzdA0KPj4gYWx0b0BpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9hbHRvDQo+DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj5hbHRvIG1haWxpbmcgbGlzdA0KPmFsdG9AaWV0Zi5vcmcN
Cj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2FsdG8NCg0K

From michael.scharf@alcatel-lucent.com  Mon Feb 25 10:07:59 2013
Return-Path: <michael.scharf@alcatel-lucent.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 83EDA21F9084 for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 10:07:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.532
X-Spam-Level: 
X-Spam-Status: No, score=-9.532 tagged_above=-999 required=5 tests=[AWL=0.717,  BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KZZY4GiQ1Ws for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 10:07:58 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 19F0E21F9439 for <alto@ietf.org>; Mon, 25 Feb 2013 10:07:55 -0800 (PST)
Received: from FRMRSSXCHHUB02.dc-m.alcatel-lucent.com (FRMRSSXCHHUB02.dc-m.alcatel-lucent.com [135.120.45.62]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r1PI72O8015255 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 25 Feb 2013 19:07:50 +0100
Received: from FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com ([135.120.45.56]) by FRMRSSXCHHUB02.dc-m.alcatel-lucent.com ([135.120.45.62]) with mapi; Mon, 25 Feb 2013 19:07:24 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "Reinaldo Penno (repenno)" <repenno@cisco.com>, Sebastian Kiesel <ietf-alto@skiesel.de>, "Roome, W D" <w.roome@alcatel-lucent.com>
Date: Mon, 25 Feb 2013 19:07:23 +0100
Thread-Topic: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
Thread-Index: AQHOEFD6VY+ntXZyY0eKp/DUkgLdjpiEwAyAgAHOP4CAAXoFAIAC+fWA///QiAA=
Message-ID: <2A886F9088894347A3BE0CC5B7A85F3E9AA10D62E5@FRMRSSXCHMBSE3.dc-m.alcatel-lucent.com>
References: <20130223162358.GH9265@gw01.ehlo.wurstkaes.de> <45A697A8FFD7CF48BCF2BE7E106F060409010F3D@xmb-rcd-x04.cisco.com>
In-Reply-To: <45A697A8FFD7CF48BCF2BE7E106F060409010F3D@xmb-rcd-x04.cisco.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] Discussion II: Unifying cost-mode and cost-type to a single type
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2013 18:07:59 -0000

> I appreciate the observations related to cost and believe=20
> some discussion is warranted but some observations:
>=20
> - Lower is better is mostly what you get in routers. For=20
> example, OSPF has a well defined metric but you can import=20
> BGP routes into OSPF (and
> vice-versa) with default or different metrics. You can add=20
> static routes, changes preferences, etc.
>=20
> An ALTO Server is no different. It needs to take inputs from=20
> different sources and come up with a cost metric.

Yes. One can indeed use different input sources...

> If we need
> to define what cost means I suggest we take the definition=20
> from routing folks (for example, ref PCE/BGP). Do they have=20
> one? For example, if I dump the forwarding table of a router=20
> and it shows that for a certain destination the cost is "50"=20
> through a certain interface,  what can I infer from it given=20
> the mash of different inputs a router can take to calculate that?

... and there may be input metrics other than BGP/OSPF/... routing cost.

> - Different ALTO Servers might be a problem if they are in=20
> different domains. ALTO servers within a single domain that=20
> need to exchange cost maps need to use the same algorithms.
>=20
> - Different ALTO servers in different domains in another=20
> issue. This was an issue we worked on:
>=20
> https://tools.ietf.org/html/draft-penno-alto-cdn-03#page-17
>=20
> I believe implementations just use BGP cost.

While BGP cost is certainly a very relevant input parameter, we've shown an=
 implementation that can also calculate the ALTO cost e.g. from delay (Sect=
ion IV.C): http://dx.doi.org/10.1109/ICIN.2012.6376038

How to calculate the cost value really depends on the requirements and poli=
cies of the ALTO server operator.

Michael=

From internet-drafts@ietf.org  Mon Feb 25 14:06:30 2013
Return-Path: <internet-drafts@ietf.org>
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 8007921E8118; Mon, 25 Feb 2013 14:06:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level: 
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EFiK-z9sBYyh; Mon, 25 Feb 2013 14:06:30 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 359A121F91AF; Mon, 25 Feb 2013 14:06:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130225220626.17650.19192.idtracker@ietfa.amsl.com>
Date: Mon, 25 Feb 2013 14:06:26 -0800
Cc: alto@ietf.org
Subject: [alto] I-D Action: draft-ietf-alto-protocol-14.txt
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2013 22:06:30 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Application-Layer Traffic Optimization Wo=
rking Group of the IETF.

	Title           : ALTO Protocol
	Author(s)       : Richard Alimi
                          Reinaldo Penno
                          Y. Richard Yang
	Filename        : draft-ietf-alto-protocol-14.txt
	Pages           : 75
	Date            : 2013-02-25

Abstract:
   Applications using the Internet already have access to topology
   information of Internet Service Provider (ISP) networks.  For
   example, views to Internet routing tables at looking glass servers
   are available and can be practically downloaded to many application
   clients.  What is missing is knowledge of the underlying network
   topologies from the point of view of ISPs (henceforth referred as
   Providers).  In other words, what a Provider prefers in terms of
   traffic optimization -- and a way to distribute it.

   The Application-Layer Traffic Optimization (ALTO) Service provides
   network information (e.g., basic network location structure and
   preferences of network paths) with the goal of modifying network
   resource consumption patterns while maintaining or improving
   application performance.  The basic information of ALTO is based on
   abstract maps of a network.  These maps provide a simplified view,
   yet enough information about a network for applications to
   effectively utilize them.  Additional services are built on top of
   the maps.

   This document describes a protocol implementing the ALTO Service.
   Although the ALTO Service would primarily be provided by the network
   operator (e.g., an ISP), content service providers and third parties
   could also operate this service.  Applications that could use this
   service are those that have a choice to which end points to connect.
   Examples of such applications are peer-to-peer (P2P) and content
   delivery networks.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-alto-protocol

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-alto-protocol-14

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-alto-protocol-14


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From leeyoung@huawei.com  Mon Feb 25 14:49:29 2013
Return-Path: <leeyoung@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 13ECD21E8112 for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 14:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wlrpr8LpNgEc for <alto@ietfa.amsl.com>; Mon, 25 Feb 2013 14:49:27 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5C77521E80F2 for <alto@ietf.org>; Mon, 25 Feb 2013 14:49:27 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AQB15523; Mon, 25 Feb 2013 22:49:26 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Feb 2013 22:49:24 +0000
Received: from DFWEML407-HUB.china.huawei.com (10.193.5.132) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 25 Feb 2013 22:49:25 +0000
Received: from dfweml511-mbs.china.huawei.com ([169.254.15.175]) by dfweml407-hub.china.huawei.com ([10.193.5.132]) with mapi id 14.01.0323.007; Mon, 25 Feb 2013 14:49:20 -0800
From: Leeyoung <leeyoung@huawei.com>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: [alto] New ALTO use cases & the upcoming IETF meeting
Thread-Index: AQHOECinm7C2AVtBUEKuLYy9ZUxBv5iLMZ9w
Date: Mon, 25 Feb 2013 22:49:18 +0000
Message-ID: <7AEB3D6833318045B4AE71C2C87E8E1729104FA5@dfweml511-mbs.china.huawei.com>
References: <51260845.1000909@neclab.eu>
In-Reply-To: <51260845.1000909@neclab.eu>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.179]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [alto] New ALTO use cases & the upcoming IETF meeting
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 25 Feb 2013 22:49:29 -0000

Hi all,

http://www.ietf.org/internet-drafts/draft-dhody-pce-cso-enabled-path-comput=
ation-03.txt

I just wanted to bring your attention to this draft where ALTO is implied b=
etween APP and NET (Cross Stratum) in the context of=20
an extended PCE architecture. ALTO is envisioned in this draft as a mechani=
sm to collect network resource information to the application
for their scheduling operation in an effort to select an optimal data cente=
r from a set of candidates.=20

This draft addresses the need for underlying network resource information (=
such as application-specific virtual network topology)=20
that can be made available to APP via ALTO interface.=20

Your comments are appreciated.=20

Regards,
Dhruv and Young

-----Original Message-----
From: alto-bounces@ietf.org [mailto:alto-bounces@ietf.org] On Behalf Of Mar=
tin Stiemerling
Sent: Thursday, February 21, 2013 5:43 AM
To: alto@ietf.org
Subject: [alto] New ALTO use cases & the upcoming IETF meeting

Hi all,

I have seen a number of new ALTO drafts for LMAP, I2RS, etc and also the=20
wish to discuss a rechartering of the ALTO WG.

I still do not see the WG to be ready for any rechartering discussion,=20
as we should first finish up our current chartered items.

However, I can see the utility to discuss new ideas on what to do with=20
ALTO, but outside the ALTO session at the upcoming IETF meeting in Orlando.

My proposal would be to do a side meeting, i.e., we meet sometimes in=20
the evening over a drink and discuss the new drafts/use cases and how to=20
progress ALTO.

But, do not rely on my to organize such a side meeting, i.e., somebody=20
else should take the stab in organizing this.

   Martin

--=20
IETF Transport Area Director

martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto

From enrico.marocco@telecomitalia.it  Wed Feb 27 07:34:43 2013
Return-Path: <enrico.marocco@telecomitalia.it>
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 5E1B721F85AF for <alto@ietfa.amsl.com>; Wed, 27 Feb 2013 07:34:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.719
X-Spam-Level: 
X-Spam-Status: No, score=-101.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z430Xrv9Gd8i for <alto@ietfa.amsl.com>; Wed, 27 Feb 2013 07:34:37 -0800 (PST)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id 04A3D21F859D for <alto@ietf.org>; Wed, 27 Feb 2013 07:34:23 -0800 (PST)
Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 27 Feb 2013 16:34:16 +0100
Received: from MacLab.local (10.229.8.21) by smtp.telecomitalia.it (10.19.9.235) with Microsoft SMTP Server (TLS) id 8.3.297.1; Wed, 27 Feb 2013 16:34:15 +0100
Message-ID: <512E2776.3070306@telecomitalia.it>
Date: Wed, 27 Feb 2013 16:34:14 +0100
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: "alto@ietf.org" <alto@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080604030705010609090802"
X-TI-Disclaimer: Disclaimer1
Subject: [alto] Draft agenda posted
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2013 15:34:43 -0000

--------------ms080604030705010609090802
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Folks,

a draft agenda has been posted:
http://www.ietf.org/proceedings/86/agenda/agenda-86-alto

Other than the time slots allocated to charter items, it contains also a
list of the extensions that people may want to discuss in the side
meeting(s), as anticipated on this list. Please check that all the
information is correct.

--=20
Ciao,
Enrico


--------------ms080604030705010609090802
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINdzCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIHOzCCBiOgAwIBAgIDBKfoMA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTIwODA3MDkxNTQz
WhcNMTMwODA4MDczMzM3WjB1MRkwFwYDVQQNExBvWkNPVnNYc09NME9mcExwMSgwJgYDVQQD
DB9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MS4wLAYJKoZIhvcNAQkBFh9lbnJp
Y28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEAshI2shfUZ7P5RVcP04fJ4OfYmK/RUyokJpuJE4KaSOLArtpNtlYo6MtXfmZzA8y/
5HChSAmPvqUwhMMYh1LurWbOdX4uKXO1gsFrPOtxTa6qin6lXaJ3bo2pKnkN9mQkjvm0E23r
rrT3MC6h6UfyFAcvs01+yq9wVuxxRdC4LZTGAbXGkE34GQAnBy9eqvJ+m351hPaaVw9u8CWN
uyv9YKLXpicS/q8j2EOpFBCkZVp0E8fViSXViGtuhfbW6R+TjTXJZN06DEqb/vpRSWkvBDf0
UqDFrgmlmSnXJ/xpaygAJcHyE5qjRXkIV7adTkg9Z/Z2lJXvtDUdHbNBiYcVOwIDAQABo4ID
ujCCA7YwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBT1YgWCbkVCN8iNgS49Fh9R2ZC8wTAfBgNVHSMEGDAWgBRTcu2S
nODaywFcfH6WNU7y1LhRgjAqBgNVHREEIzAhgR9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRh
bGlhLml0MIICIQYDVR0gBIICGDCCAhQwggIQBgsrBgEEAYG1NwECAjCCAf8wLgYIKwYBBQUH
AgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgfcGCCsGAQUFBwICMIHq
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRp
ZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24g
cmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkg
Zm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcg
cGFydHkgb2JsaWdhdGlvbnMuMIGcBggrBgEFBQcCAjCBjzAnFiBTdGFydENvbSBDZXJ0aWZp
Y2F0aW9uIEF1dGhvcml0eTADAgECGmRMaWFiaWxpdHkgYW5kIHdhcnJhbnRpZXMgYXJlIGxp
bWl0ZWQhIFNlZSBzZWN0aW9uICJMZWdhbCBhbmQgTGltaXRhdGlvbnMiIG9mIHRoZSBTdGFy
dENvbSBDQSBwb2xpY3kuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wu
Y29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6
Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2
aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0
MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOC
AQEAIn8FoRaqvQzo8aGNi4EbPhIMX8aPIMhX3L/N+8sMyFe3cpSyjij47DW1K330zDJnoyZs
kuI10EzfK0wwY+D2qMQPGAmPDkix5t2dYQj6DKh1yBlBwAf7c65Ty1kpgtdymSptDJKVZcK6
R2CJ91oRBCZIObcWrG/0FZIr55+InAYyLDrlk34MwBmINhBZ4oRJdrzG6OC7cK4vG1ZWrAFE
GHVwx1uG2NXRUXQTH9DGYcwwfPo4uinFCwHZAJ2Il/J0Mqui5x+N/7p+WUlGRyb67qxg7ect
f2095+YDnbqIKIz7fGzw8XTwpjYbvWZplkG93qRXr8MRD9ukgxpxpHG2dTGCA90wggPZAgEB
MIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwSn6DAJBgUrDgMCGgUA
oIICHTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzAyMjcx
NTM0MTRaMCMGCSqGSIb3DQEJBDEWBBR6vckJjJx5MHPPbFtuZ7pfEYJjgDBsBgkqhkiG9w0B
CQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcN
AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEE
AYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSsw
KQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9T
dGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBKfoMIGn
BgsqhkiG9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2
BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENB
AgMEp+gwDQYJKoZIhvcNAQEBBQAEggEAalZWYggyjufv6RqpnV3t+YEcy6x5+Ms5rVN+ApzQ
UNRTlyf8yp4kNr16UHB1rT4nJG1KaCeCyJjE9njHpoH6tieJM7vi8efg8Qg2bvzDcnI2ZcI9
AcgwRGx4wjhIg9zb6AUMEYdBoaTssHSOGEF0RAHElFYTqQRZofFZCHb8YCeuRmJFCdi/RmGl
kyBwbI/JMuuY3XxOZd0qafw+LZlog2FqYWGpNOd4jTTaEp5kRUR7I+BpkXjqrlXFpNEd0cZp
qCin3CONu5CHuAaMGzBQYNnPzb+tAylIY3Dfn/uR1nDkRLX/2XvTPJfkJ73LlNb6ohGpJW5z
cI5PXjJZxsFNyAAAAAAAAA==
--------------ms080604030705010609090802--
