IETF Logo Mail Archive

Re: ORCID - unique identifiers for contributors

"John Levine" <johnl@taugh.com> Mon, 16 September 2013 20:32 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AD0811E8113 for <ietf@ietfa.amsl.com>; Mon, 16 Sep 2013 13:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.673
X-Spam-Level:
X-Spam-Status: No, score=-102.673 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xc3ql-j2vWJn for <ietf@ietfa.amsl.com>; Mon, 16 Sep 2013 13:32:05 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id E405911E8145 for <ietf@ietf.org>; Mon, 16 Sep 2013 13:32:04 -0700 (PDT)
Received: (qmail 18525 invoked from network); 16 Sep 2013 20:32:04 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 16 Sep 2013 20:32:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52376ac3.xn--30v786c.k1309; i=johnl@user.iecc.com; bh=bUDAeUupGUPqCfk+h/wXcsL1H51t3QzJ/ZXMYEcJ3O8=; b=VR3CvR+bCZFcFO91uN66TEQBa9mLfAfVzYdxgduhktYQeKiUTmV72/q69m1o920s0R2zmRJzqwC+JzU3IQkLJ4By7BQsLgk0BFOFHByDyw9A8c9IN3c3kP2iRgJXPo8hcZVudhOhqOw/5DDC+i2XYKdeZIxAwnHnrgTozOTwBfDLn1JNXGxmTTpkLqefQT+TeYWd0Ht3eOvry+7uqvO9BLy/W+ryCK65KZn4spMj1uYmUtlaYqsdpSB37sIPp9wa
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52376ac3.xn--30v786c.k1309; olt=johnl@user.iecc.com; bh=bUDAeUupGUPqCfk+h/wXcsL1H51t3QzJ/ZXMYEcJ3O8=; b=Nf72+IU/F9bWNN1RXk6Gi+1jv/U/HMszyTv4600JsyDJx16IQXlPotGaUzoeN3uaPyoWZ7b8FnT77PIRDxxRYgVINDxhU3NAhpHVBFcITk7FxFPAIlxmR+cm+ZXSEWpcZJaqUSAKfcEISxUF4JoRb/D0pDIe+B96rsAPuizmf69Dfy5Ku3jl/TAO8J9ekiEkWQfRjI8Pi755B5A42UaEDfZJIEenSNwFXGDqkOQnDOyuTY9KGnRTpUR3y8ZH63xq
Date: Mon, 16 Sep 2013 20:31:41 -0000
Message-ID: <20130916203141.86927.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: ORCID - unique identifiers for contributors
In-Reply-To: <523764AB.9070809@gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2013 20:32:09 -0000

>How do I know that the sender of this message actually has the right
>to claim the ORCID in question (0000-0001-5882-6823)? The web page
>doesn't present anything (such as a public key) that could be used
>for authentication.

I dunno.  How do we know who brian.e.carpenter@gmail.com is?  I can
tell you from experience that a lot of people think they are
john.levine@gmail.com, and all but one of them are mistaken.

R's,
John

PS: Now that I think about it, you can already put in a personal URL
in rfc2xml, so if someone wants to use an ORCID URL, they can do so
right now.

v2.28.0 | Report a Bug | By Email | System Status