Re: [Ltru] LTRU submission: draft-ietf-ltru-registry-10

["Kent Karlsson" <[e-mail]>]

I'm sorry, but I'm still not happy with the references.

9.1  Normative References

   [ISO10646]
              International Organization for Standardization, "ISO/IEC
              10646:2003. 	Information technology -- Universal Multiple-
              Octet Coded Character Set (UCS), as, from time to time,
              amended, replaced by a new edition or expanded by the
              addition of new parts", 2003.

----> Remove the excess spaces, remove the ", as, from time to time,
----> amended, replaced by a new edition or expanded by the
----> addition of new parts" as that is absolutely not part of
----> the title. (And recall my note about the ISO convention of dated
----> and undated references.) No need to repeat the year twice for any
----> of the references.

   [ISO15924]
              International Organization for Standardization, "ISO
              15924:2004. Information and documentation -- Codes for the
              representation of names of scripts", January 2004.

   [ISO3166-1]
              International Organization for Standardization, "ISO 3166-
              1:1997. 	Codes for the representation of names of
              countries and their subdivisions -- Part 1: Country
              codes", 1997.

----> What about part 3?

   [ISO639-1]
              International Organization for Standardization, "ISO 639-
              1:2002. Codes for the representation of names of languages
              -- Part 1: Alpha-2 code", 2002.

   [ISO639-2]
              International Organization for Standardization, "ISO 639-
              2:1998. Codes for the representation of names of languages
              -- Part 2: Alpha-3 code, first edition", 1998.

----> Either consistently include edition (for dated references...)
----> or consistenly exclude it.

   [ISO646]   ISO/IEC 646 JTC 1/SC 2, "ISO/IEC 646:1991, Information
              technology -- ISO 7-bit coded character set for
              information interchange.", 1991.

----> I thought it was agreed that "ISO/IEC 646 JTC 1/SC 2" should not be
----> author (the ISO WG is never cited in referring to published standards).

   [RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
              3", BCP 9, RFC 2026, October 1996.

----> I still think this one should not be listed as "normative". It is
----> more "metanormative" for IETF standards, and would then not need to be
----> listed as "normative" for any particular RFC. (ISO standards never
----> refer to the "ISO directives" normatively, only informatively.)

   [RFC2028]  Hovey, R. and S. Bradner, "The Organizations Involved in
              the IETF Standards Process", BCP 11, RFC 2028,
              October 1996.

----> I thought it was agreed that this wasn't (and cannot be) a normative
----> reference.

   [RFC2047]  Moore, K., "MIME (Multipurpose Internet Mail Extensions)
              Part Three: Message Header Extensions for Non-ASCII Text",
              RFC 2047, November 1996.

----> I thought it was agreed that this wasn't a normative reference here.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

----> I still think this one should not be listed as "normative". It is
----> more "metanormative" for IETF standards, and would then not need to be
----> listed as "normative" for any particular RFC.

   [RFC2234bis]
              Crocker, D. and P. Overell, "Augmented BNF for Syntax
              Specifications: ABNF", draft-crocker-abnf-rfc2234bis-00
              (work in progress), March 2005.

   [RFC2434]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 2434,
              October 1998.

----> I thought it was agreed that this wasn't a normative reference.

   [RFC2781]  Hoffman, P. and F. Yergeau, "UTF-16, an encoding of ISO
              10646", RFC 2781, February 2000.

----> I thought it was agreed that this wasn't a normative reference here.

   [RFC2860]  Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
              Understanding Concerning the Technical Work of the
              Internet Assigned Numbers Authority", RFC 2860, June 2000.

   [RFC3339]  Klyne, G. and C. Newman, "Date and Time on the Internet:
              Timestamps", RFC 3339, July 2002.

   [RFC3552]  Rescorla, E. and B. Korver, "Guidelines for Writing RFC
              Text on Security Considerations", BCP 72, RFC 3552,
              July 2003.

----> I thought it was agreed that this wasn't a normative reference.

   [UN_M.49]  Statistical Division, United Nations, "Standard Country or
              Area Codes for Statistical Use", UN Standard Country or
              Area Codes for Statistical Use, Revision 4 (United Nations
              publication, Sales No. 98.XVII.9, June 1999.

  /kent k



_______________________________________________
Ltru mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ltru