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

Jensen Zhang <> Tue, 27 February 2018 07:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9A1E91274D2 for <>; Mon, 26 Feb 2018 23:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RksOVa1x1UJX for <>; Mon, 26 Feb 2018 23:10:41 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4002:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B485C1276AF for <>; Mon, 26 Feb 2018 23:10:38 -0800 (PST)
Received: by with SMTP id b70so5987781ywh.5 for <>; Mon, 26 Feb 2018 23:10:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2cddxObOPpLbWlkQ1kmV0TX9ejWgNcN4gPAoffdUMdg=; b=jLxQII0WFabAgMxSdQJhKzWJv5Wx2/LJJiSdai5sjfwn4lD+b7K9OXt6jUjBD8sNKv ENQUIuiCCxusVloO6Y9cwXGlajP3THYB7/jDgOMvPms21zEQ3zaWma63jD5kEOtkeIKg vbC3oz+f7ND4FgxbJPuywml2zTObi8k5W1U/eazEL3rohwtc6RxFugMqpZOc6uJ4qXvG uCyOS8/Bwj7kEjUTm/MUHgCzWFdJtfGRjgvBOXdUj30a9BlbE65kSMg3CEQX+efRXqJz Tn3Xk27n5I5+BqtrkoXb9DSSCBKNnfe4rRL76DyzGic0GouoxCwOxitmCNQ/g9riE6Jk JAPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2cddxObOPpLbWlkQ1kmV0TX9ejWgNcN4gPAoffdUMdg=; b=fKFALtkrDL4ax82SWKy5SS074NqptEm6MaSel9RXICMiOob6zf07/+GiRhvuE+Pw79 ynFe9IKUd/HjkerLC+NGq08m5C5nckqe8MAv6W6qFtYVIxYpBnFv7lqcMPqbQCxttmBr 7hweMZZ/oUbBfjSgOQubUOM1965k2BtqSPueCcDaRD2a44RZaek9Fm3pbcdhjV2bj9QT uL7cYQyxk/CgxMPxKAO00KGOoDBDdCHg75uYbMceZqtBnTdr9OpNHLC3tsjU6Q3KSuNC ozT2zHI7fWLVa9OlImWDPmmiw8xgOsxz3tVHTZicWmqq0qVG0xtg+b0hPSAHljcW9PUO ZzRw==
X-Gm-Message-State: APf1xPD5E652Efdu1NAdvoBvxQ+LsgR6oReQ4aXj8JIxuWEzdI0rbMra y1qOSsaXUIhI9GvUhXLkmKHW5Upg7R6YiZMg4Oo=
X-Google-Smtp-Source: AG47ELtdKNgu/AqJV55jsfez63/+Emkzp38/3mu6UDaKlZKrXHvy7ruFMe1VHL+5+mzyS/GcE6yFY+OSfQjZ36efU6Y=
X-Received: by with SMTP id d5mr6337440ywg.510.1519715437853; Mon, 26 Feb 2018 23:10:37 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <>
In-Reply-To: <>
From: Jensen Zhang <>
Date: Tue, 27 Feb 2018 07:10:27 +0000
Message-ID: <>
To: "Vijay K. Gurbani" <>
Cc: "Randriamasy, Sabine (Nokia - FR/Paris-Saclay)" <>, "Y. Richard Yang" <>, Dawn Chan <>, "" <>
Content-Type: multipart/alternative; boundary="f403045e6450d5418a05662c5291"
Archived-At: <>
Subject: Re: [alto] unified-props, cellular addresses and path-vector
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: Tue, 27 Feb 2018 07:10:49 -0000

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 <>

> [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
> ALTO RFC [1].
> 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

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

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.


> [1]
> [2]
> Thanks,
> 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
> Calendar:
> _______________________________________________
> alto mailing list