On 2009/06/09 11:50, Randy Presuhn wrote:
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.As a technical contributor... While I recognized that the proposed text is well-meant, I cannot support it. It introduces a technical change to what the WG had agreed. It changes advice ("probably frowned upon") into a prohibition ("are not considered sufficient"). Furthermore, I would argue that the use of MAY is in this case correct - it's used to describe an optional activity, and those taking part in or relying on this procedure must account for both the possibility that the action can occur, and the possibility that it might not occur. Consequently, I do not agree with making the proposed change. Randy _______________________________________________ Ltru mailing list Ltru at ietf.org https://www.ietf.org/mailman/listinfo/ltru
-- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst at it.aoyama.ac.jp
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.