Re: Last Call: <draft-ietf-appsawg-rfc3536bis-02.txt> (Terminology Used in Internationalization in the IETF) to BCP

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

 



At 06:04 16-06-2011, The IESG wrote:
The IESG has received a request from the Applications Area Working Group
WG (appsawg) to consider the following document:
- 'Terminology Used in Internationalization in the IETF'
  <draft-ietf-appsawg-rfc3536bis-02.txt> as a BCP

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@xxxxxxxx mailing lists by 2011-06-30. Exceptionally, comments may be

This document uses an unusual format to show the source of a definition (Section 1.2). It's clearer (to me) if the document used the regular format for references.

The anchor9 comment in Section 3.2, minus the last sentence, could be folded in as part of the I-D. Pointing out that the definition is not precisely correct is correct in itself.

In Section 4:

  "Code Point order is usually not how any human educated by a local
   school system expects to see strings ordered; if one orders to the
   expectations of a human, one has a language-specific sort."

This is generally referred to as natural language sort.

There is a view within the IETF that a BCP comes with the obligatory RFC 2119 key words. This old school "BCP" was a pleasant read.

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]