IETF Logo Mail Archive

Re: ORCID - unique identifiers for contributors

Yoav Nir <ynir@checkpoint.com> Tue, 17 September 2013 20:52 UTC

Return-Path: <ynir@checkpoint.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 87FBC11E8197 for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 13:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.252
X-Spam-Level:
X-Spam-Status: No, score=-10.252 tagged_above=-999 required=5 tests=[AWL=0.347, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 1+TCMwweGA1B for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 13:52:34 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 4F4A111E810A for <ietf@ietf.org>; Tue, 17 Sep 2013 13:52:34 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r8HKq8Qu006132; Tue, 17 Sep 2013 23:52:24 +0300
X-CheckPoint: {5238C0F8-D-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.30]) by IL-EX10.ad.checkpoint.com ([169.254.2.246]) with mapi id 14.02.0347.000; Tue, 17 Sep 2013 23:52:08 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: ORCID - unique identifiers for contributors
Thread-Topic: ORCID - unique identifiers for contributors
Thread-Index: AQHOsuqxQ28fLP9rCkajZh5xZKb7LpnImDaAgAAHKoCAAAiBgIAAJlqAgADTagCAAAMigIAABXsAgAAIR4CAAChCgIAAD5WAgAAFqoCAABEdAIAAAvCAgAACAgCAAB5+AIAAEtqA
Date: Tue, 17 Sep 2013 20:52:08 +0000
Message-ID: <230E3867-634B-4364-BFA3-CAAB89BF7A83@checkpoint.com>
References: <20130916203141.86927.qmail@joyce.lan> <C65F64A8-2D7B-47AF-BAAC-DE4DE57586B7@checkpoint.com> <523791FB.2070807@gmail.com> <CABiXOEm+D4oE7NePHmR5gviOJURqkSAhDhGb=s1o1ayJZAc7kQ@mail.gmail.com> <523845F5.9050902@gmail.com> <CABiXOEmhe5p8jMW2W=9qnhUZ_ORhwKCgA1_-dxK_NtGNy7g1zA@mail.gmail.com> <5238517F.8060705@joelhalpern.com> <6014.1379431237@sandelman.ca> <A3B67B91B80804CC611555AD@JcK-HP8200.jck.com> <A6729341-EF60-40A3-830E-2138A6A60AEE@shinkuro.com> <7406B04A-903D-4765-9FC1-4880F68DD9FF@lurchi.franken.de> <CAPv4CP-2h_=GnO7JQPPhFc=TFn5kinmWaurZUn4B0G69vhWE7g@mail.gmail.com> <E664BD6A-EADF-4FAF-A2A6-F0429595989C@lurchi.franken.de> <5238B12C.9020103@isdg.net>
In-Reply-To: <5238B12C.9020103@isdg.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.20.42]
x-kse-antivirus-interceptor-info: protection disabled
Content-Type: text/plain; charset="us-ascii"
Content-ID: <004B0F9DF0DDA947828612E3421B2601@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John C Klensin <john-ietf@jck.com>, Michael Richardson <mcr@sandelman.ca>, IETF discussion list <ietf@ietf.org>
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: Tue, 17 Sep 2013 20:52:40 -0000

On Sep 17, 2013, at 10:44 PM, Hector Santos <hsantos@isdg.net>
 wrote:

> On 9/17/2013 1:55 PM, Michael Tuexen wrote:
>> On Sep 17, 2013, at 7:48 PM, Scott Brim <scott.brim@gmail.com> wrote:
>> 
>>> On Tue, Sep 17, 2013 at 1:37 PM, Michael Tuexen
>>> <Michael.Tuexen@lurchi.franken.de> wrote:
>>>> I was always wondering the authors can't get an @ietf.org address, which is listed
>>>> in the RFC and is used to forward e-mail to another account.
> 
> Me too!  I would even suggest that all I-D authors, at the very least, should need to register with the IETF to submit documents.  Optional @ietf.org offered.

Having an IETF identity is OK if all you ever publish is in the IETF. Some of our participants also publish at other SDOs such as IEEE, W3C, ITU, and quite a few publish Academic papers. Using the same identifier for all these places would be useful, and that single identifier is not going to be an @ietf.org email address.

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