[rfc-i] draft-iab-xml2rfc-02 and draft-flanagan-nonascii feedback: Internationalization Considerations and 7760

Joe Hildebrand (jhildebr) jhildebr at cisco.com
Thu Mar 24 09:39:06 PDT 2016

Full names aren't unique either.  People also change their names over time.  How much do we care about the stats being perfect?

If possible, I'd like to build the system we've spec'd out here, then after we have a little implementation experience, starting with requirements for the next version.  One of the things we could begin discussing is creating accounts for authors, giving each account a unique ID (such as a UUID), having the submission tool check the email addresses that are used by the author, ensuring that each author has a valid account, then injecting the UUIDs into the document in the preptool step.

When we do that, I expect vocal community outcry about how we're tracking them and putting up hurdles to document submission, and whether those downsides are worth some small improvements in our statistics.

I don't want that (long) conversation to keep us from shipping this version.

Joe Hildebrand

On 3/24/16, 10:24 AM, "rfc-interest on behalf of Benoit Claise (bclaise)" <rfc-interest-bounces at rfc-editor.org on behalf of bclaise at cisco.com> wrote:

>Hi Paul,
>Yes, it does the job ... until we have collisions from real names to a 
>single ASCII name
>Low probability I guess but my point was more: shouldn't RFC 7760 work 
>with the author's full name?
>Regards, Benoit
>> On 28 Jan 2016, at 2:50, Benoit Claise wrote:
>>> I believe we miss a requirement in RFC 7760 "Statement of Work for 
>>> Extensions to the IETF Datatracker for Author Statistics"
>>> Indeed, people might start authoring draft/RFC with their real live 
>>> names.
>>> If we want the stats to be correct, the tool should have a feature to 
>>> combine the ASCII with the non-ASCII author name stats.
>> Benoit:
>> In Section 2.7, the <author> element has three new attributes:
>> 2.7.1.  "asciiFullname" Attribute
>>    The ASCII equivalent of the author's full name.
>> 2.7.2.  "asciiInitials" Attribute
>>    The ASCII equivalent of the author's initials, to be used in
>>    conjunction with the separately specified asciiSurname.
>> 2.7.3.  "asciiSurname" Attribute
>>    The ASCII equivalent of the author's surname, to be used in
>>    conjunction with the separately specified asciiInitials.
>> Do these not meet your concern? Or is your concern that the RFC Editor 
>> might not enforce the use of those attributes?
>> --Paul Hoffman
>> .
>rfc-interest mailing list
>rfc-interest at rfc-editor.org

More information about the rfc-interest mailing list