Re: Last Call On draft-yevstifeyev-tn3270-uri-12

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----- Original Message -----
From: "SM" <sm@xxxxxxxxxxxx>
To: <ietf@xxxxxxxx>
Sent: Wednesday, January 12, 2011 2:00 AM

> At 08:29 11-01-11, t.petch wrote:
> >The provenance of the editor is unknown to
> >me - and of course, once an RFC has been through the IETF processes,
> >then the editorship is an irrelevance - but I am concerned that I have
> >no awareness of the contact provided as the scheme 'Author/Change
controller',
> >no track record, no affiliation, a gmail address.  This seems more than
> >discourtesy, this seems wrong.
>
> There is a city and country mentioned under Author's Address.  It is
> not the first time an author uses a gmail address.  If an author is
> new to the IETF, he or she won't have any track record within the IETF.
>
> According to the RFC Style Guide:
>
>    "Contact information must include at least one, and ideally would
>     include all, of a postal address, a telephone number and/or FAX
>     number, and a long-lived email address.  The purpose of this section
>     is to (1) unambiguously define author/contributor identity (e.g., the
>     John Smith who works for FooBar Systems) and to (2) provide contact
>     information for future readers who have questions or comments.  Note
>     that some professional societies offer long-lived email addresses for
>     their members."

True, but not relevant to the point I am making.

This is a provisional registration of an URI scheme (for which a provisional
registration already exists in IANA) so it is the rules of  RFC4395 which apply.

Except that they do not appear to cater for re-registration of a provisional
scheme.

The nearest would appear to be
"   o  Contact information identifying the person supplying the
      registration is included.  Previously unregistered URI schemes
      discovered in use may be registered by third parties on behalf of
      those who created the URI scheme; in this case, both the
      registering party and the scheme creator SHOULD be identified."

and it is the complete lack of the original scheme creator that
concerns me.  Yes we have contact details for the third party
but that is not enough.

Tom Petch

> Regards,
> -sm

_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]