Re: [Ideas] Diasambugating Identifier and Identity

"Liubingyang (Bryan)" <liubingyang@huawei.com> Thu, 27 April 2017 01:30 UTC

Return-Path: <liubingyang@huawei.com>
X-Original-To: ideas@ietfa.amsl.com
Delivered-To: ideas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF8812441E for <ideas@ietfa.amsl.com>; Wed, 26 Apr 2017 18:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 0gG0ahZi0djo for <ideas@ietfa.amsl.com>; Wed, 26 Apr 2017 18:30:48 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 454FF124281 for <ideas@ietf.org>; Wed, 26 Apr 2017 18:30:48 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DLV18851; Thu, 27 Apr 2017 01:30:45 +0000 (GMT)
Received: from SZXEMI404-HUB.china.huawei.com (10.82.75.40) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 27 Apr 2017 02:30:43 +0100
Received: from SZXEMI508-MBS.china.huawei.com ([169.254.10.152]) by SZXEMI404-HUB.china.huawei.com ([10.82.75.40]) with mapi id 14.03.0235.001; Thu, 27 Apr 2017 09:30:35 +0800
From: "Liubingyang (Bryan)" <liubingyang@huawei.com>
To: Michael Menth <menth@uni-tuebingen.de>, Alexander Clemm <alexander.clemm@huawei.com>, Dino Farinacci <farinacci@gmail.com>
CC: Robert Moskowitz <rgm-ietf@htt-consult.com>, "ideas@ietf.org" <ideas@ietf.org>
Thread-Topic: [Ideas] Diasambugating Identifier and Identity
Thread-Index: AQHSp914j5eOmWLOQkutGf2RD5x5MqHDjbwAgABx9QCAAMPZAIAAAjuAgBAfzYCAAWJVgIABSuQw///7zQCAACT0gIAABM6AgADigCA=
Date: Thu, 27 Apr 2017 01:30:34 +0000
Message-ID: <C1CE72EE84AF224E94DA21AE134209EE0102F2A7@SZXEMI508-MBS.china.huawei.com>
References: <7443f8eb-181c-be31-8e80-9250b4a54e60@htt-consult.com> <abd7608c-54b9-a381-fdf2-c5964dc37078@htt-consult.com> <082a1bcc-d79a-75b0-18e6-6db705627ce5@uni-tuebingen.de> <afbac9ba-0b9c-c479-8db5-8abc4e8a998a@htt-consult.com> <c260d5f8-d349-8a33-5bc6-8cbf375cf908@uni-tuebingen.de> <644DA50AFA8C314EA9BDDAC83BD38A2E0DF92CB0@SJCEML701-CHM.china.huawei.com> <161f2434-d3ab-efdc-2b5b-5582d80c6b9c@uni-tuebingen.de> <C1CE72EE84AF224E94DA21AE134209EE0102F0EF@SZXEMI508-MBS.china.huawei.com> <454B13B3-E2E5-41DB-84F4-BF880374F696@gmail.com> <644DA50AFA8C314EA9BDDAC83BD38A2E0DF93415@SJCEML701-CHM.china.huawei.com> <a4f0687d-917f-6507-50a0-63b3b77a0caa@uni-tuebingen.de>
In-Reply-To: <a4f0687d-917f-6507-50a0-63b3b77a0caa@uni-tuebingen.de>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.168.116]
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.0A090201.590149C5.0078, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.10.152, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: a5271462e6ccc4de9b0f102f77736dfd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/zCCvAhjDIHRcrL318CsNtwwSUIM>
Subject: Re: [Ideas] Diasambugating Identifier and Identity
X-BeenThere: ideas@ietf.org
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." <ideas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ideas>, <mailto:ideas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ideas/>
List-Post: <mailto:ideas@ietf.org>
List-Help: <mailto:ideas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ideas>, <mailto:ideas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 01:30:50 -0000

Hi Michael, 

What do you mean by authentication? 
Is it used by mapping system to authenticate whether an entity can update properties of an identifier, or used by the corresponding node to authenticate whether the entity indeed owns the identifier? 

Bingyang (Bryan)

-----Original Message-----
From: Michael Menth [mailto:menth@uni-tuebingen.de] 
Sent: Thursday, April 27, 2017 3:56 AM
To: Alexander Clemm <alexander.clemm@huawei.com>om>; Dino Farinacci <farinacci@gmail.com>om>; Liubingyang (Bryan) <liubingyang@huawei.com>
Cc: Robert Moskowitz <rgm-ietf@htt-consult.com>om>; ideas@ietf.org
Subject: Re: [Ideas] Diasambugating Identifier and Identity

Hi Alex,

can't a contract be represented by a contract identifier (cidX) to which several networking identifiers (nidn) are mapped?

nid0 -> cidX
nid1 -> cidX
nid2 -> cidX
cidX -> someProperty

This contract identifier may be mapped to some property yielding a kind of hierarchical mapping. What I want to say is, I don't see the gain of an identity concept in this example.

I ask again: what's the value of identities beyond authentication for registration purposes?

Regards,

Michael


Am 26.04.2017 um 21:38 schrieb Alexander Clemm:
> 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 [mailto:farinacci@gmail.com]
> Sent: Wednesday, April 26, 2017 10:26 AM
> To: Liubingyang (Bryan) <liubingyang@huawei.com>
> Cc: Michael Menth <menth@uni-tuebingen.de>de>; Alexander Clemm 
> <alexander.clemm@huawei.com>om>; Robert Moskowitz 
> <rgm-ietf@htt-consult.com>om>; ideas@ietf.org
> 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. 
> 
> Exactly.
> 
> 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().
> 
> Dino
> 

--
Prof. Dr. habil. Michael Menth
University of Tuebingen
Faculty of Science
Department of Computer Science
Chair of Communication Networks
Sand 13, 72076 Tuebingen, Germany
phone: (+49)-7071/29-70505
fax: (+49)-7071/29-5220
mailto:menth@uni-tuebingen.de
http://kn.inf.uni-tuebingen.de