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

"Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <> Mon, 05 March 2018 16:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9F6DA12D94A for <>; Mon, 5 Mar 2018 08:42:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LwyS78tQKBer for <>; Mon, 5 Mar 2018 08:42:16 -0800 (PST)
Received: from ( [IPv6:2a01:111:f400:fe02::719]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C45DA1270AC for <>; Mon, 5 Mar 2018 08:42:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=6aDitYiU/VqW7iMlVxHywnES7EiWQJZFEPWPLNjVFco=; b=P7Wn6A6goncfI4FwR32yqhDPF3Ru9tKHPbyPALzNa56Ak39bIlS3vRoXtYgv7a4U+9GDRh4616EUFSMxXmi8xoHEZpknLzFtGtdAknFWoBgU2vxL89EY1GiMgVlpgormXwM6AGwHrniaLBNlIN1z/9I/W+YdsvsMidU0PbqZMFQ=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.567.6; Mon, 5 Mar 2018 16:42:10 +0000
Received: from ([fe80::4941:5181:f15b:104f]) by ([fe80::4941:5181:f15b:104f%4]) with mapi id 15.20.0567.011; Mon, 5 Mar 2018 16:42:10 +0000
From: "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <>
To: "Y. Richard Yang" <>, Jensen Zhang <>
CC: "" <>
Thread-Topic: [alto] unified-props, cellular addresses and path-vector - registry
Thread-Index: AdOwEMI8sY2dTvALT8OecvWaJ3/KrgBJEI6AAFLXewAAh9mX8A==
Date: Mon, 5 Mar 2018 16:42:10 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
x-originating-ip: []
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0702MB3801; 7:QdlT4NhfcSyzXuG4jWILCqYlyTGKq/VJlHdeRubT1uccbTNnXyMktVyvh+TaqK08P8RdHscqPMycs9oDO1enWUg+BknForYZNIQI5EoilY9S6HUal9JmpUgMNvv8m1jntnIO1MqMShXQh3NpqOJVeaI+dJmKwsi6Uy+o9MZtCoQFIDF1Q82oB7cTr69bXYtwg7tXQg6k1EV8KZHJUYKc5uIA26HfdVOxq8d16I/o2z40PrUP4aJLyLvLFMbXTZCK
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: ed63f495-2a4e-41ab-379a-08d582b80a57
x-microsoft-antispam: UriScan:(189865482101610); BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603307)(7193020); SRVR:HE1PR0702MB3801;
x-ms-traffictypediagnostic: HE1PR0702MB3801:
authentication-results: spf=none (sender IP is );
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:(28532068793085)(82608151540597)(85827821059158)(148501403981450)(21748063052155)(189865482101610);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231220)(11241501184)(944501244)(52105095)(3002001)(6055026)(6041288)(20161123562045)(20161123558120)(201703131423095)(201703031522075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(6072148)(201708071742011); SRVR:HE1PR0702MB3801; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0702MB3801;
x-forefront-prvs: 06022AA85F
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39380400002)(39860400002)(366004)(376002)(346002)(396003)(53754006)(189003)(199004)(51914003)(53936002)(2171002)(4326008)(790700001)(6116002)(3846002)(2906002)(229853002)(25786009)(39060400002)(81156014)(66066001)(8676002)(81166006)(8936002)(3280700002)(68736007)(97736004)(106356001)(53366004)(53376002)(6246003)(74316002)(3660700001)(7736002)(55016002)(54896002)(236005)(6306002)(9686003)(2950100002)(6436002)(102836004)(53546011)(5660300001)(11609785009)(6506007)(59450400001)(26005)(606006)(478600001)(76176011)(2900100001)(33656002)(105586002)(316002)(296002)(86362001)(14454004)(7696005)(966005)(186003)(5250100002)(110136005)(99286004)(90052001)(9984715007)(4068875011); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR0702MB3801;; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
x-microsoft-antispam-message-info: Kq6qLalf29AIplZkKssHkdNHoahg2UUNXqJlYzfgOzt5xx3albwBE0VKnYuSNRpGkebQfpUrfSH1pnHBPNa7BdHXibp920NEyO0Y9Mw/XxHO90EJMDYEi3ZNkr+BXy+pOuEHl7n43OKi/hGYKHMjbseoZbdhVc3WWNKNo1txY5YHRTMtw/UAkQiAzAO689HqmkHZYhzIdn8pg/R8Oh9974NDiCjgCnRkNnqBSzZnQGIvLZzHDYVQRvU90HhsUrCsNV22FGuNUKt1ICx345dhnvulMTMo0odiE4nWiOl4BC5GTNUxjtjmzXEksj0EgC8YgTRcC5ICMcSYVPs9G+3W6g==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR0702MB37381A4A540346C2E3DF938895DA0HE1PR0702MB3738_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ed63f495-2a4e-41ab-379a-08d582b80a57
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Mar 2018 16:42:10.0903 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3801
Archived-At: <>
Subject: Re: [alto] unified-props, cellular addresses and path-vector - registry
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 05 Mar 2018 16:42:20 -0000


Definitely there is a need to expose the motivation to cell addresses registered in the ALTO address type registry and the ALTO domain registry.  For the moment, I will add the related text to the [draft-randriamasy-alto-cellular-adresses] draft.

From: [] On Behalf Of Y. Richard Yang
Sent: Saturday, March 03, 2018 12:44 AM
To: Jensen Zhang <>
Cc: Randriamasy, Sabine (Nokia - FR/Paris-Saclay) <>om>;
Subject: Re: [alto] unified-props, cellular addresses and path-vector - registry

Hi Jensen,

Thanks for the comments. Please see below.

On Thu, Mar 1, 2018 at 3:12 AM, Jensen Zhang <<>> wrote:
Hi Sabine, all

Let me post some considerations on this topic. Please see my comments inline.
On Wed, Feb 28, 2018 at 6:17 AM Randriamasy, Sabine (Nokia - FR/Paris-Saclay) <<>> wrote:
Hi Jensen, Kai, Vijay, all

Thanks all for this discussion on registries, which needs a separate thread so I added “registry” to the initial thread.
The ALTO Entity Domain Registry of the Unified Properties (UP) draft is to be seen as an extension of the ALTO Address Type Registry specified in RFC 7285. Indeed ipv4 and ipv6 map to both ALTO Address Type and ALTO Domain Type where the latter set covers the first one.

Yes. I think the goal of the ALTO Entity Domain Registry is to be an extension of the ALTO Address Type Registry. But the relationship between these two registries need to be clarified in the documents.

This is a good discussion. I can see two views regarding the extension word:
1. ALTO Entity Domain Registry is a superset of ALTO Address Type Registry;
2. ALTO Entity Domain Registry and ALTO Address Type Registry are two distinct sets, and we only want the intersection to be specified consistently.

My understanding/view is one, and we should make it clear.

Definitely, Jensen’s explanations (items 1) and 2) ) in his e-mail of Feb 27, 2018 at 3:10 PM should be used in sections 2.7 or 9.2 of the UP draft to clarify the relation between both.

Yes, agree. I will edit it.

OK. Let's edit it.

For section 9.2  of the UP draft, I agree with Jensen’s views and understand Kai’s concerns. We may consider adding a sentence generalized from Sections and to have something like :
"When a new address type is registered in the ALTO Address Type Registry of [RFC7285], the same identifier MUST be also registered in the ALTO Entity Domain Registry. And the Entity Address Encoding for this entity domain identifier MUST cover both Address Encoding and Prefix Encoding of the same identifier registered in the ALTO Address Type Registry [RFC7285]."
“For the purpose of defining properties, an individual Entity address and the corresponding full-length prefix are considered aliases for the same entity.”

Yes, such a sentence is helpful.

Would this help addressing the issue?

Yes, enforce address type registered as entity domain can help to guarantee consistency. But I think it is not enough.

Considering a prior document registers a new entity domain called 'AAA' first, the 'AAA' can be a valid entity domain but not a valid address type at this moment. Then, another later document registers a new address type also called 'AAA'. If the encoding of the address type 'AAA' is not consistent with the encoding of the entity domain 'AAA', there will be some issue.

So I propose we add a new column in the ALTO Entity Domain Registry table, maybe called 'Valid for ALTO Addresses', to indicate which entity domain can also be used as an address type and which cannot. Those entity domains marked as 'Valid for ALTO Addresses' don't have to be registered in ALTO Address Type Registry again. In this way, we can make 'ALTO Entity Domain Registry' a superset of 'ALTO Address Type Registry'. But of course, other columns of the ALTO Entity Domain Registry should be adjusted to distinguish individual address encoding from the prefix/block address encoding.

Any thougthts?

This seems to be a good idea---I always like syntax enforced consistency.




From: alto [<>] On Behalf Of Jensen Zhang
Sent: Tuesday, February 27, 2018 10:11 AM
To: Kai Gao <<>>
Subject: Re: [alto] unified-props, cellular addresses and path-vector

Hi Kai,

Thanks for your comment. See inline.
On Tue, Feb 27, 2018 at 4:38 PM Kai Gao <<>> wrote:
Hi Jensen,

Please see inline.

On 02/27/2018 03:44 PM, Jensen Zhang wrote:
Hi all,

Continue the discussion above. I suggest modifying the first paragraph of page 26 of draft-ietf-alto-unified-props-new-01

"It is RECOMMANDED that a new ALTO entity domain be registered when the corresponding address type is registered based on ALTO Address Type Registry [RFC7285]."

as the following:

"When a new address type is registered in the ALTO Address Type Registry [RFC7285], the same identifier MUST be also registered in the ALTO Entity Domain Registry. And the Entity Address Encoding of this entity domain identifier MUST include both Address Encoding and Prefix Encoding of the same identifier registered in the ALTO Address Type Registry [RFC7285]."
It might be odd to have two encodings for a single entry. Since address encoding is actually a special case of prefix encoding, maybe we can use prefix encoding alone?

The words may need to be revised. But we indeed hope to accept both Address Encoding and Prefix Encoding as the valid Entity Address Encoding. Using prefix encoding alone is not consistent with what "ipv4" and "ipv6" domain do in Section 3.1 of draft-alto-unified-props-new-01.

Any comment?

On Tue, Feb 27, 2018 at 3:10 PM Jensen Zhang <<>> wrote:
Hi Vijay,

It is a good point to explain the relationship of "ALTO Address Type Registry" and "ALTO Entity Domain Registry".

See my comment inline.
On Tue, Feb 27, 2018 at 3:21 AM Vijay K. Gurbani <<>> wrote:
[As co-chair]

Sabine, Richard: If you decide to proceed as you outline below, then
please realize that time is of essence.

[As individual contributor]

I am a bit confused by this discussion though.  Are cellular addresses
ALTO address types?  In which case they will have to be registered in
the ALTO Address Type Registry as detailed in Section 14.4 of the base
Yes, cellular address are ALTO address types. So of course they should be registered in the "ALTO Address Type Registry" based on RFC7285.

Or are cellular address ALTO entities?  In which case they will have to
be registered through unified-props registry in Section 9.2 of the
unified-props document [2]?
And yes, cellular addresses "should" also be ALTO entities. But let's delay the answer to this question and see the following questions first.

Why do we have legacy identifiers like 'ipv4' and 'ipv6' being
registered in two registries, i.e., in the registries of [1] and [2]?
In fact, why do we have a ALTO Entity Domain Registry in [2] at all?
Why we introduce a new Registry? Because the key idea is to move the property map service from endpoint scope to the more general scope (which we call "entity domain" in the draft).

1) in this general scope, an entity MAY or MAY NOT be an endpoint. For example, "pid" is introduced as an entity domain, but it is not an endpoint address type. To allow this, we need this new registry.
2) But to cover the capability of the endpoint property service, an endpoint MUST be an entity. As the result, "ipv4" and "ipv6" are registered in both "ALTO Address Type Register" and "ALTO Entity Domain Registry".

Now let's go back to the question "are cellular addresses ALTO entities?". Sure, as they are ALTO endpoint addresses, they MUST be ALTO entities. So they MUST be registered in the "ALTO Entity Domain Registry".

I am afraid I am missing something ... can you please elaborate?

Is it clear now? Do we agree on this? Or Sabine and Richad want to say anything?

I think we need to well define the process of the ALTO Entity Domain Registry to guarantee the syntax and semantics of the same indentifier registered in both Registries are consistent. And I think this may be a missing item in the current unified-props draft. If we fix this part, the draft should be ready.




On 02/26/2018 10:18 AM, Randriamasy, Sabine (Nokia - FR/Paris-Saclay) wrote:
> Hi Richard,
> I agree, the Unified Property draft is definitely a good placeholder for
> the cellular addresses. Domain and entities are already defined in
> . 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?

- vijay
Vijay K. Gurbani /<>
Network Data Science, Nokia Networks

alto mailing list<>


alto mailing list<>

alto mailing list<>

| Y. Richard Yang <<>>   |
| Professor of Computer Science       |
|        |