Re: [alto] unified-props, cellular addresses and path-vector

"Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <sabine.randriamasy@nokia-bell-labs.com> Mon, 26 February 2018 16:18 UTC

Return-Path: <sabine.randriamasy@nokia-bell-labs.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C51F127078 for <alto@ietfa.amsl.com>; Mon, 26 Feb 2018 08:18:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b2DBqaQB2HfE for <alto@ietfa.amsl.com>; Mon, 26 Feb 2018 08:18:55 -0800 (PST)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30138.outbound.protection.outlook.com [40.107.3.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6466D124217 for <alto@ietf.org>; Mon, 26 Feb 2018 08:18:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=twqUPSoSFj1XBgBoSCZYK/+Q3yYtcnU3TtRWrS0uqdw=; b=SonkE8MGT3arf/oudyDfJpRPdPZJ5e/G/lschzfnTHyROZwMZwKU9eXb6EyJRjCsINxzXlV2jvj62AwIE11/YE/GT6mLtnXJvHF9HtkAnVmhZxDci2xS6kVAp3+YJSwQzi4AW/4adi7Gh40VKu8q286BeujEoxu+DGO0D8zeFs4=
Received: from HE1PR0702MB3738.eurprd07.prod.outlook.com (52.133.6.156) by HE1PR0702MB3722.eurprd07.prod.outlook.com (52.133.6.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.548.6; Mon, 26 Feb 2018 16:18:51 +0000
Received: from HE1PR0702MB3738.eurprd07.prod.outlook.com ([fe80::4941:5181:f15b:104f]) by HE1PR0702MB3738.eurprd07.prod.outlook.com ([fe80::4941:5181:f15b:104f%3]) with mapi id 15.20.0548.011; Mon, 26 Feb 2018 16:18:50 +0000
From: "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <sabine.randriamasy@nokia-bell-labs.com>
To: "Y. Richard Yang" <yry@cs.yale.edu>, Dawn Chan <dawn_chen_f@hotmail.com>
CC: "Gurbani, Vijay (Nokia - US/Naperville)" <vijay.gurbani@nokia.com>, Wendy Roome <wendy@wdroome.com>, "alto@ietf.org" <alto@ietf.org>
Thread-Topic: unified-props, cellular addresses and path-vector
Thread-Index: AQHTrG/+QjqpMK2egUKBpsef0w4zIqOyWxgAgASB9+A=
Date: Mon, 26 Feb 2018 16:18:50 +0000
Message-ID: <HE1PR0702MB3738F145B3656EEC8E59957795C10@HE1PR0702MB3738.eurprd07.prod.outlook.com>
References: <5e6a98ff-3c8d-f1b8-2deb-21788cdfef09@nokia.com> <BLUPR02MB1202578B8645F956E30B7066B5CC0@BLUPR02MB1202.namprd02.prod.outlook.com> <CANUuoLrAR=b9b36extXU6Hc6VSv1ExsD7Yze09b8WUnfSnbJCg@mail.gmail.com>
In-Reply-To: <CANUuoLrAR=b9b36extXU6Hc6VSv1ExsD7Yze09b8WUnfSnbJCg@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=sabine.randriamasy@nokia-bell-labs.com;
x-originating-ip: [135.245.212.163]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0702MB3722; 7:dOOhNoDaT7cpSU0D3wiTwph0xbVmwT6+0ENAU1qM58uAxrc9/rKXeBaqr8VigGZ1sWJCfAIGnY1QYJaDakejdyogKUCJd8wTjdVokoBXt3Kd6sKMW3wyNIGuwjPiYZU846ByDx/A4SJ9/HpzDsF2F9OTGy6kU8PoCpJ38U3UPcmugUP52xjAG/RX/nXTiO7L9NXJgTcSWVJROM6E22zLMS1viMIxcDSccpOxYseMsIX/ULcOtbP7YB/MX3tPD9Xn
x-ms-exchange-antispam-srfa-diagnostics: SSOS;SSOR;
x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10019020)(39380400002)(396003)(346002)(39860400002)(366004)(376002)(53754006)(189003)(199004)(99286004)(966005)(3660700001)(7736002)(5250100002)(7696005)(45080400002)(105586002)(2906002)(3280700002)(74316002)(53366004)(53376002)(790700001)(3846002)(6116002)(316002)(606006)(296002)(2171002)(4326008)(106356001)(6506007)(25786009)(229853002)(53546011)(86362001)(54906003)(110136005)(5660300001)(11609785009)(68736007)(53936002)(59450400001)(39060400002)(6246003)(76176011)(14454004)(102836004)(26005)(81156014)(8676002)(81166006)(33656002)(97736004)(55016002)(186003)(6306002)(54896002)(236005)(2950100002)(478600001)(8936002)(9686003)(66066001)(6436002)(2900100001)(90052001)(9984715007)(4068875011); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0702MB3722; H:HE1PR0702MB3738.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: dfbbcc27-a6dd-4884-19bf-08d57d349f6a
x-microsoft-antispam: UriScan:(17574466456847); BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7193020); SRVR:HE1PR0702MB3722;
x-ms-traffictypediagnostic: HE1PR0702MB3722:
x-microsoft-antispam-prvs: <HE1PR0702MB372227DD4ADC55BA2D5C9CAA95C10@HE1PR0702MB3722.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(120809045254105)(82608151540597)(85827821059158)(148501403981450)(130873036417446)(194151415913766)(21748063052155)(17574466456847);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(3002001)(3231220)(11241501184)(944501161)(52105095)(93006095)(93001095)(10201501046)(6055026)(6041288)(201703131423095)(201703031522075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(6072148)(201708071742011); SRVR:HE1PR0702MB3722; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0702MB3722;
x-forefront-prvs: 05954A7C45
received-spf: None (protection.outlook.com: nokia-bell-labs.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: vZ1EQZXyqB5DG9268L0GQh6E34bKposWpNuHdpVmF4MrApf4Il27fSG0tP4oqpWuM7/jm/MKFmEqzagOxjFdwYq9XA5O9bd/dfC9uI5zCPSBm1VTf+oA96KtDZ1GJZGg1zIeQAa/az6gPEjjiOXNg0ZGzm8+mSUUZc2sV65hut0=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0702MB3738F145B3656EEC8E59957795C10HE1PR0702MB3738_"
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: dfbbcc27-a6dd-4884-19bf-08d57d349f6a
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Feb 2018 16:18:50.7689 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3722
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/GPCbknE8cMWSUeVoAZTsEGwU9Hk>
Subject: Re: [alto] unified-props, cellular addresses and path-vector
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Feb 2018 16:18:58 -0000

Hi Richard,

I agree, the Unified Property draft is definitely a good placeholder for the cellular addresses. Domain and entities are already defined in https://tools.ietf.org/html/draft-randriamasy-alto-cellular-adresses-01 . So how about in a next step, we consider pouring the content of the latter draft in the UP draft and in a further step propose a list of properties, while looking at other WG to see whether they already specified any?

Sabine

From: yang.r.yang@gmail.com [mailto:yang.r.yang@gmail.com] On Behalf Of Y. Richard Yang
Sent: Friday, February 23, 2018 8:11 PM
To: Dawn Chan <dawn_chen_f@hotmail.com>
Cc: Gurbani, Vijay (Nokia - US/Naperville) <vijay.gurbani@nokia.com>om>; Wendy Roome <wendy@wdroome.com>om>; Randriamasy, Sabine (Nokia - FR/Paris-Saclay) <sabine.randriamasy@nokia-bell-labs.com>om>; alto@ietf.org
Subject: Re: unified-props, cellular addresses and path-vector

It looks that the suggestion by Dawn is reasonable.

I am taking a look again at the possibility of integrating cellular into UP quickly. An alternative is that we get it done shortly, in the next couple days.

If this is the approach, Sabine is a great person to work together. Make sense, Sabine?

Richard


On Fri, Feb 23, 2018 at 1:31 AM, Dawn Chan <dawn_chen_f@hotmail.com<mailto:dawn_chen_f@hotmail.com>> wrote:
Hi all,

Draft Unified Property is quite stable at the moment, and the major problem left is whether the cellular address needs to be appended. Actually, since the Unified Property maintains an entity domain registry to achieve extensibility so that we suggest the new entity domain cellular address to be registered in the https://www.ietf.org/id/draft-randriamasy-alto-cellular-adresses-01.txt itself. This way, the draft Unified Property can proceed first.

Besides, path-vector and unified property depend on each other so they should move as a bundle.

Do you think this is a feasible solution?

On 23 Feb 2018, at 3:16 AM, Vijay K. Gurbani <vijay.gurbani@nokia.com<mailto:vijay.gurbani@nokia.com>> wrote:

All: In preparation for moving the unified property draft [0] ahead, the
minutes of the December 2017 Virtual Interim Meeting [1] indicate that
the chairs seek answers to the following questions from the WG:

(1) Are cellular addresses an important abstraction that the working
group will like to introduce in ALTO?  Currently, cellular address
format is specified in a companion draft [2].

(2) If yes, is the unified-props-new draft the correct place to add the
cellular representation?

Please note that the unified property draft [0] gates path-vector [3],
as there is a dependency of path-vector on unified-props.  Thus, the
plan is to move these two drafts ahead as a bundle.

Which means that we need to reach a conclusion on the questions posed
above so unified-props and path-vector can move ahead.

Please express an substantive opinion on the above questions in the
mailing list.

[0] https://datatracker.ietf.org/doc/draft-ietf-alto-unified-props-new/
[1]
https://datatracker.ietf.org/meeting/interim-2017-alto-01/materials/minutes-interim-2017-alto-01-201712180600/
[2]
https://datatracker.ietf.org/doc/draft-randriamasy-alto-cellular-adresses/
[3] https://datatracker.ietf.org/doc/draft-ietf-alto-path-vector/

Thank you,

- vijay
--
Vijay K. Gurbani / vijay.gurbani@nokia.com<mailto:vijay.gurbani@nokia.com>
Network Data Science, Nokia Networks
Calendar: http://goo.gl/x3Ogq




--
--
 =====================================
| Y. Richard Yang <yry@cs.yale.edu<mailto:yry@cs.yale.edu>>   |
| Professor of Computer Science       |
| http://www.cs.yale.edu/~yry/        |
 =====================================