Re: [Ideas] Diasambugating Identifier and Identity

Alexander Clemm <> Wed, 26 April 2017 19:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9CEEB129450 for <>; Wed, 26 Apr 2017 12:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Status: No, score=-4.222 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iU6bmNao6EmX for <>; Wed, 26 Apr 2017 12:38:52 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 742F41314B1 for <>; Wed, 26 Apr 2017 12:38:51 -0700 (PDT)
Received: from (EHLO ([]) by (MOS 4.3.7-GA FastPath queued) with ESMTP id DFO45205; Wed, 26 Apr 2017 19:38:48 +0000 (GMT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 26 Apr 2017 20:38:46 +0100
Received: from ([]) by ([]) with mapi id 14.03.0235.001; Wed, 26 Apr 2017 12:38:37 -0700
From: Alexander Clemm <>
To: Dino Farinacci <>, "Liubingyang (Bryan)" <>
CC: Michael Menth <>, Robert Moskowitz <>, "" <>
Thread-Topic: [Ideas] Diasambugating Identifier and Identity
Thread-Index: AQHSp916fQ6Ay+5HYEmqQas6XmYXz6HEiTEAgABx9QCAAMPZAIAAAjuAgA+nLqCAAdr0gIAAy1IAgAB7XwD//60WgA==
Date: Wed, 26 Apr 2017 19:38:35 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5900F748.0352, 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: 9bbd9fb42d3f22b96b673e9c96398629
Archived-At: <>
Subject: Re: [Ideas] Diasambugating Identifier and Identity
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: Wed, 26 Apr 2017 19:38:55 -0000

Yes, I think we agree on the notion of identifier.  

Of course, this is not just about identifier- but identity-enabled networking, so there is still that other aspect needing to be fleshed out. Re: Michael's question, authentication is one of its applications, but I think there are others, for example related to metadata (back to the earlier point of whether identity is a data record) - an example would be the "type" of endpoint which applies regardless whether one or many identifiers are being used.  Related to metadata, you could have policies that are applied based on identity (e.g. an entity with a paid contract), not based on which one of several identifiers an entity happens to use.   

-- Alex

-----Original Message-----
From: Dino Farinacci [] 
Sent: Wednesday, April 26, 2017 10:26 AM
To: Liubingyang (Bryan) <>
Cc: Michael Menth <>de>; Alexander Clemm <>om>; Robert Moskowitz <>om>;
Subject: Re: [Ideas] Diasambugating Identifier and Identity

> For example, (one of) the real reason we want identifiers is that we want something that does not change with topology locations to identify mobile communication end point, which functions that cannot be carried by IP addresses. Since (I believe) we all have consensus on this function, we can at least agree that identifier is topology-independent label that identifies a communication end point. 


So to extend the definition to be specific. The identifier is used for a host stack transport connection. Its the “thing” (the arguments) you pass to connect(), bind(), sendto(), etc, socket API calls. And what you “get back” from gethostbyname().