IETF Logo Mail Archive

Re: [Ideas] Diasambugating Identifier and Identity

Dino Farinacci <farinacci@gmail.com> Wed, 29 March 2017 16:08 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 E117A129841 for <ideas@ietfa.amsl.com>; Wed, 29 Mar 2017 09:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 0eKLV0RWWbuL for <ideas@ietfa.amsl.com>; Wed, 29 Mar 2017 09:08:38 -0700 (PDT)
Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (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 8CDAB127201 for <ideas@ietf.org>; Wed, 29 Mar 2017 09:08:34 -0700 (PDT)
Received: by mail-io0-x243.google.com with SMTP id f84so264658ioj.0 for <ideas@ietf.org>; Wed, 29 Mar 2017 09:08:34 -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=CCQMGaSbaXla7OVm+Xbdfm9eI7SecOmHHNovibPU1O0=; b=gk/wk/GCkk7Jo27akF+iLLNBwVUCS+bv+0a7XioeXQOApjrXIogbp/Ictzo4Vh/y8U njDlk1HEfg0D6yk8+CYVbJmT5mJz6mKpEZzMg4D9a6/KbjgrXXzHxLdZarXAdSTE1qEy FYWwy2S8R4Q5roxjcyEVqlnPYdmgb+Y0gXxVcevBBq8Wu93upl5A/v9SaxgyCyDaFDiL pU5S6paLoCiMz+IkhzCUsST+qgIL6Vd/QrsjDXmT6iG1NTtHtzmz3o8lcs4f0+8hDseq sePva70b9pPc3WST5wi9G3DXEADddCNPMpwZoLVhm4+H/Xjcq2/NB9BEPSFemtplHNHQ co9Q==
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=CCQMGaSbaXla7OVm+Xbdfm9eI7SecOmHHNovibPU1O0=; b=a2oD53LbognZF+ZaQklbDk08/uG7kJQuXobz9KwxVubm0MR3NXRjW45+at379Dj41J 0jLtwmf11OtmmMFOZKlSWPAEPdGAp3JSFSZSMuc63+IISOCBlKMorbVirnbyZCHN+hSZ 3B3Dc8ZLWVSonk3zJd7Sb3H+qg+n710h7x1jij1yCFDcBp/39/HvSt5dY4kVoYaklwkf uJeQb50g8UhUIIMPXEhKBjB+Xg/LyaaR3ZyAp1Cjay2ALwZy8Soj6o5XBjZpOzNbT+mr lw3+Ca4zpoQblzsQ32GrdA90somh8dhMAALRO/zjRO8wDUh9Knu0V8l/TrLnVxjOBGLK sMSQ==
X-Gm-Message-State: AFeK/H3JLjWnWUlKRwv7QzNEqc9TS9IwquUVAwoRlWyRZetKg+Yi7OSmQ1GtiwD1FLUe7Q==
X-Received: by 10.107.37.12 with SMTP id l12mr1533824iol.159.1490803713923; Wed, 29 Mar 2017 09:08:33 -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 g23sm3923867ioi.20.2017.03.29.09.08.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2017 09:08:33 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <52460b04-55a6-1ade-31f6-d27f814ccd06@htt-consult.com>
Date: Wed, 29 Mar 2017 09:08:32 -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: <BA3B59A3-9B89-4DEB-8B92-BA0096A559F3@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> <68650443-E3C6-4810-AD0E-B0EBC336BB1F@gmail.com> <52460b04-55a6-1ade-31f6-d27f814ccd06@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/0mfT4w6W-O2Vaz8i6tT0YyvvDsQ>
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 16:08:40 -0000

> For some there is seems to be no distinction between Identifier and Identity, but when you get to registration and services, Identity starts going into policy decisions.

But an Identifier identifies an entity, so when the entity is registered it is described by an Identifier value. When an identity is described in a policy statement, it is described by an Identifier value.

It is hard to disagree with my statement above because it is such a fundamental and basic definition.

Dino

v2.23.0 | Report a Bug | By Email