[Ltru] Issue #61: Problem with MAY in 3.5 on Description errata (Apps #13)

["Randy Presuhn" <randy_presuhn at mindspring.com>]

Hi -

> From: "Alexey Melnikov" <alexey.melnikov at isode.com>
> To: "LTRU Working Group" <ltru at ietf.org>
> Cc: "Martin J. Dürst" <duerst at it.aoyama.ac.jp>; "Randy Presuhn" <randy_presuhn at mindspring.com>
> Sent: Saturday, June 06, 2009 1:14 PM
> Subject: Re: Additional issues with 4646bis raised by an Apps Review Team review
...
> 13). In Section 3.5:
>
> >    While the 'Description' field itself is not guaranteed to be stable
> >    and errata corrections MAY be undertaken from time to time, attempts
> >    to provide translations or transcriptions of entries in the registry
> >    itself will probably be frowned upon by the community or rejected
> >    outright, as changes of this nature have an impact on the provisions
> >    in Section 3.4.
>
> Suggested replacement for the paragraph:
>
>    The 'Description' field itself is not guaranteed to be
>    stable.  Corrections (possibly as errata) and updates are
>    permitted with adequate justification.   However, addition
>    of translations or transliterations are not considered
>    sufficient justification for corrections or updates.
>
> Reason: use of MAY is not an appropriate use of RFC 2119, as it is
> trying to forecast the future and doesn't specify a protocol option.

This is filed as report #61 in the tracker.
http://trac.tools.ietf.org/wg/ltru/trac/ticket/61

Randy