Re: [Ideas] Comments on draft-ccm-ideas-identity-use-cases-02

Uma Chunduri <> Tue, 17 October 2017 00:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BACD1126BF0 for <>; Mon, 16 Oct 2017 17:31:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GDR4Q57WiC59 for <>; Mon, 16 Oct 2017 17:31:55 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9C1ED13202D for <>; Mon, 16 Oct 2017 17:31:54 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DQT65936; Tue, 17 Oct 2017 00:31:52 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 17 Oct 2017 01:31:49 +0100
Received: from ([]) by ([]) with mapi id 14.03.0361.001; Mon, 16 Oct 2017 17:31:42 -0700
From: Uma Chunduri <>
To: "" <>
Thread-Topic: [Ideas] Comments on draft-ccm-ideas-identity-use-cases-02
Thread-Index: AQHTRqsmzhTtyxc/w0CsYMOotXbfdqLnLFXQ
Date: Tue, 17 Oct 2017 00:31:41 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.59E54F78.0108, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 29cc6edb49b2ff973d78594621a6b010
Archived-At: <>
Subject: Re: [Ideas] Comments on draft-ccm-ideas-identity-use-cases-02
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussions relating to the development, clarification, and implementation of control-plane infrastructures and functionalities in ID enabled networks." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 17 Oct 2017 00:31:58 -0000

Thx for the feedback on this version. I saw Alex's responses - some more of it below.

Uma C.


	>I think the most critical use case isn't described here. It is in mobility where a devices may have many thousands of identifiers assigned to it. When the device moves, all the identifiers must move
               > with it and want this to be performed in one operation in the infrastructure. Without the ability to perform a group operation, identifier-locator might not be able to scale. Today this is done by virtue 
               >of moving a device prefix, but device prefixes do not have reasonable privacy or security properties (see ongoing discussion in v6 ops about host prefix assignment and privacy ramifications).
[Uma]: Yes.

	>The phrase "long-lived" is ill-defined. Not just in this document, but I've noticed this popping up in other WGs. The obvious problem is that there is no common definition of the time it takes something to be long-lived. 
                >Someone might say a day, another an hour, a minute, a second, ten milliseconds etc. In identifier-locator, it may be that a node wants to use a different identifier in every connection it creates which is the best privacy it can get.
[Uma]:  It's relative. This is not new and not introduced in IDEAS.  This is nothing but HIT in HIP or EID in LISP (which are used for location resolution today).  The context of this usage is to differentiate from the one time anonymous identifiers used in the data plane.. Can clarify further.

	>This by the way is why I don't think end user devices should ever participate in identifier-locator protocols...
 [Uma]: You  are making a pretty broad statement here.  Which device uses this is orthogonal to IDEAS.   We have a host based solution (ID/LOC) HIP  and a network based solution LISP.