Re: [Ideas] Diasambugating Identifier and Identity

Dino Farinacci <farinacci@gmail.com> Wed, 29 March 2017 15:38 UTC

Return-Path: <farinacci@gmail.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 37EF91296DF for <ideas@ietfa.amsl.com>; Wed, 29 Mar 2017 08:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 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, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 OvTA8kO5JW8H for <ideas@ietfa.amsl.com>; Wed, 29 Mar 2017 08:38:16 -0700 (PDT)
Received: from mail-it0-x241.google.com (mail-it0-x241.google.com [IPv6:2607:f8b0:4001:c0b::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C929B129735 for <ideas@ietf.org>; Wed, 29 Mar 2017 08:38:15 -0700 (PDT)
Received: by mail-it0-x241.google.com with SMTP id e75so10322815itd.1 for <ideas@ietf.org>; Wed, 29 Mar 2017 08:38:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=OiE2bGV8MGL0mKZgznHIoUujow9p5m+tAlJqCY7DyuM=; b=RU6CTAsHm0GseImAoPuKXcCshkphhUqqKY8lNmp5j8tNuVyiTYjxM0lrm2vLStFZCE dI/c43wJMmkfnkGystMGI+5ivEebPZXyJPKC0TICFIpCEnRvODi+aQIfotAYi2KIOTmG 9MYN6I9TEmhKhduzuv1LN2HGTR82qgnJFeGdw005rT7QQpfKp/EDFzy2Tv46I3i1o+a0 wu6ELgJHvcwWBrGhS4jm0rNrULJqMNoTMU4+fy0bJA9uFsW2Jb5Ih18toragxck/2pMi FaXzCCbEBtcV+5WWLT6Xhkoq8DKBj/+/AzLiyO0zlUK6EAtEzH/R8XNM5mUZxbi+qXVk sbRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=OiE2bGV8MGL0mKZgznHIoUujow9p5m+tAlJqCY7DyuM=; b=bwinc81Sso/gW3yYIzFyP2WGozYPMh/1HBuJS5TjMAkAxVeFGa98DSZNKmVwwbshtm xhV0tXc0VQ5FNwvRkW1+TWJL29VTfv1QzfqxWJL5sbI6lSb6yHCiltRjI6NgJ17bYI3+ 69Nv/wlEhRHEcGYByDIJwIDTz8QtSKdX8hvnSAZeHcA8GsfLlNHCnYDDG+ItaY3Kbp/N b17XYlRpQrzbpveMjgv7L/ufwWRt3ellnl6Vm5lqQtPxdfUtSjLv/OEm2dh5w6OqSYx7 7J09BpHrxSht9ZLePKPAa6+I3cbSdkcVMp0oP73eZt5f0s+4raZqrtwBQPC2lLNoIyNf hLNA==
X-Gm-Message-State: AFeK/H01+s31cbwjtV1s52ZVhyWFI5oh/+QD/hDE8UrzcqcuwBpfQMDkTrNE0RcJkSFFug==
X-Received: by 10.36.87.15 with SMTP id u15mr1396129ita.58.1490801895197; Wed, 29 Mar 2017 08:38:15 -0700 (PDT)
Received: from t2001067c0370012884d8aab4995e42dc.v6.meeting.ietf.org (t2001067c0370012884d8aab4995e42dc.v6.meeting.ietf.org. [2001:67c:370:128:84d8:aab4:995e:42dc]) by smtp.gmail.com with ESMTPSA id f127sm3485595ite.14.2017.03.29.08.38.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 08:38:14 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <28a19ae6-bf14-a848-ba17-6b0d0bb2b887@htt-consult.com>
Date: Wed, 29 Mar 2017 08:38:13 -0700
Cc: Axel.Nennker@telekom.de, Hesham Elbakoury <Hesham.ElBakoury@huawei.com>, alexander.clemm@huawei.com, Padma Pillay-Esnault <padma.ietf@gmail.com>, ideas@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <68650443-E3C6-4810-AD0E-B0EBC336BB1F@gmail.com>
References: <7443f8eb-181c-be31-8e80-9250b4a54e60@htt-consult.com> <CAG-CQxrADDG68WO6eA0v2Shg79d2Ro2pDEMMUMzCpf4iaCcQ=g@mail.gmail.com> <etPan.58dae51d.6489b56.379d@localhost> <644DA50AFA8C314EA9BDDAC83BD38A2E0DF8E814@SJCEML701-CHM.china.huawei.com> <C3855D43D6701846AD1151A536E7A0582405C202@SJCEML701-CHM.china.huawei.com> <e64ae39f16584eb0b2f92afa490b70aa@HE101655.emea1.cds.t-internal.com> <28a19ae6-bf14-a848-ba17-6b0d0bb2b887@htt-consult.com>
To: Robert Moskowitz <rgm-ietf@htt-consult.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ideas/GYU5Pzn8-6jWsU26PhNxmgmPUSk>
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: Wed, 29 Mar 2017 15:38:23 -0000

Why is this so important?

An Identifier identifies an entity. Can’t we move on to bigger fish to fry?

Dino

> On Mar 29, 2017, at 7:25 AM, Robert Moskowitz <rgm-ietf@htt-consult.com> wrote:
> 
> For many, the distinction is of small value or just perhaps confusing to them.  RFID is an example of confounding Identifier and Identity.
> 
> In Loc/EID work, the distinction is important.  With HIP, it is obvious, though it did take us some time to settle on HI and HIT.  In '99 in draft-moskowitz-hip-arch-00.txt, I called them HI and HIGH, but talking about them was challenging.  :)  
> 
> It was the -02 draft where we adopted HIT.  So I don't expect us, with generic naming, to 'get it right' the first time.
> 
> The distinction between Identifiers used for 'labels' or the more limited 'addresses' is potential constraints on Identifier construction rules.  There are other classes of Identifiers other than addresses that have constraining construction rules.
> 
> This is helping me work out the wording of defining Identifier and Identity.  I have talked around this for over 20 years and have written it down many times.  But almost always in a specific context.  Here I am striving for a general discussion of the two.
> 
> 
> On 03/29/2017 01:40 AM, Axel.Nennker@telekom.de wrote:
>> E.g. 3GPP does not really distinguish between identity and identifier and use Id for both.
>>  
>> I would prefer to spell them out especially in a work that tries to further distinguish identifiers that are labels and identifiers that are addresses.
>>  
>> Axel
>>  
>>  
>> From: Ideas [mailto:ideas-bounces@ietf.org] On Behalf Of Hesham ElBakoury
>> Sent: Wednesday, March 29, 2017 4:58 AM
>> To: Alexander Clemm; padma.ietf@gmail.com; rgm-ietf@htt-consult.com
>> Cc: ideas@ietf.org; padma.ietf@gmail.com
>> Subject: Re: [Ideas] Diasambugating Identifier and Identity
>>  
>> Alex,
>>  
>> I was actually thinking to use IDF for identifier, but in may of the projects I worked on, we used ID for identifier.
>>  
>> Hesham
>>  
>> From: Alexander Clemm 
>> Sent: Tuesday, March 28, 2017 7:54 PM
>> To: Hesham ElBakoury; padma.ietf@gmail.com; rgm-ietf@htt-consult.com
>> Cc: ideas@ietf.org; padma.ietf@gmail.com
>> Subject: RE: [Ideas] Diasambugating Identifier and Identity
>>  
>> I also think that ID is better used for identifier, not identity. 
>>  
>> That said, it seems either way there is potential for confusion, so maybe we just need to bite the bullet and spell it out wherever possible. 
>>  
>> In cases where abbreviation cannot be avoided, it may be a good idea to refrain from using “ID” at all (also avoid mixed upper/lower case).  IDT works for Identity, how about IDF for identifier (since there is no F in identity)?
>>  
>> --- Alex
>>  
>> From: Ideas [mailto:ideas-bounces@ietf.org] On Behalf Of Hesham ElBakoury
>> Sent: Tuesday, March 28, 2017 3:35 PM
>> To: padma.ietf@gmail.com; rgm-ietf@htt-consult.com
>> Cc: ideas@ietf.org; padma.ietf@gmail.com
>> Subject: Re: [Ideas] Diasambugating Identifier and Identity
>>  
>> We can use ID for identifier, and IDn, or IDT for identity (although sometimes IDT is used for identity theft).
>> 
>> Sent from HUAWEI AnyOffice
>> From:Padma Pillay-Esnault
>> To:Robert Moskowitz
>> Cc:ideas@ietf.org,Padma Pillay-Esnault
>> Date:2017-03-28 14:54:43
>> Subject:Re: [Ideas] Diasambugating Identifier and Identity
>>  
>> Hi Robert 
>>  
>> Thanks for our comment.
>>  
>>  
>> On Tue, Mar 28, 2017 at 11:07 AM, Robert Moskowitz <rgm-ietf@htt-consult.com> wrote:
>> The Identifier/Identity definitions in draft-padma-ideas-problem-statement-01.txt is a good start, it fails in the appreviations used. (There is NO abbreviation for Identity!)
>>  
>> Yes I see your point.
>>  
>> 
>> ID should NOT be the appreviation of Identitfier.  People will default to thinking 'Identity' when they see it.  Think about people outside our discussion group.
>> 
>> I propose 'IDf' for Identifier.  'ID' is too owned by Identity.
>>  
>> I feel in the past they were used  interchangeably depending on protocols which further muddles the water.
>> May be we should have IDy and IDr?
>>  
>> 
>> I will be working on proposed wording to improve these definitions.
>>  
>> Great!
>>  
>> Thanks
>> Padma 
>> 
>> 
>> _______________________________________________
>> Ideas mailing list
>> Ideas@ietf.org
>> https://www.ietf.org/mailman/listinfo/ideas
>>  
> 
> _______________________________________________
> Ideas mailing list
> Ideas@ietf.org
> https://www.ietf.org/mailman/listinfo/ideas