On 9/17/2013 1:55 PM, Michael Tuexen wrote:
On Sep 17, 2013, at 7:48 PM, Scott Brim <scott.brim@xxxxxxxxx> wrote:
On Tue, Sep 17, 2013 at 1:37 PM, Michael Tuexen
<Michael.Tuexen@xxxxxxxxxxxxxxxxx> 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.
The email address associated with the draft, for example
draft-kutscher-icnrg-netinf-proto@xxxxxxxxxxxxxx, apparently stays
with the RFC. If you go to tracker for any RFC you can click "email
authors". I don't think there's a way to update the authors' current
addresses.
... and that is my point. One level of indirection might be useful here.
I would prefer to update only one mapping and not go through a list
of RFCs and change the mapping for each document.
If there are other purposes for ORCID, then what are those? These are
things the IETF can do in general to improve its electronic
participant and network of world wide contributors.
The idea is great. By why use ORCID? Why not Facebook? linked-in?
etc. So many issues when its 3rd party. While ORCID does offer an API
(another conflict issue when API changes), I think the IETF should
offer its own registry database of contributors.
--
HLS