[Tools-discuss] Fwd: Datatracker Email addresses

[Alice Russo <[e-mail]>]

On Dec 21, 2014, at 1:51 PM, Robert Sparks <[e-mail]> wrote:
> Your particular case of an auth48 bouncing is odd - it should have been using the addresses for the authors of the draft.
> I didn't think the RFC Editor was using the datatracker addresses for that yet - if so, pleasant surprise.
> Would you be willing to forward the bounce to me and let me track down how the older address got selected?
> (If you were in that loop due to a role other than author, let me know, the answer there could be different).

Robert,

In this case, the address comes from
http://datatracker.ietf.org/doc/draft-ietf-6man-why64/doc.json

specifically:
 "shepherd": "\"Robert M. Hinden\" <[e-mail]>", 

[For background: Upon approval of a draft for publication as an RFC, the RFC Editor database is automatically populated with the datatracker's data, per the implementation of RFC 6359, Section 4.2.  This is not new.]

This issue occurs for regularly for the addresses of document shepherds. I reported the issue to you in April, and we discussed it. For a given user, you wrote "at the moment that guess is the most recently edited active email address" - and I replied that the determination of "most recently edited" seems broken.

In the RPC db, we can manually remove the out-of-date addresses that have been propagated from the datatracker, if we spot them or are notified of them. For the datatracker, we advise:

"As for removing it from the IETF datatracker, we suggest that you sign in
(https://datatracker.ietf.org/accounts/) and update your contact information,
or contact the IETF Secretariat at [e-mail]."

Please let us know if we should be advising otherwise.

Thanks,
Alice