Lightweight Directory Access Protocol (LDAP): Internationalized String Preparation
RFC 4518

[Ballot discuss]
(From dialog between Gen-ART reviewer Harald Alvestrand and Kurt Zeilenga)

> 6.1. Normative References
>
> ....
> [StringPrep]  Hoffman P. and M. Blanchet, "Preparation of
>              Internationalized Strings ('stringprep')",
>              draft-hoffman-rfc3454bis-xx.txt, a work in progress.



This reference should be revert to RFC 3454.  I have
reviewed the differences between the hoffman-rfc3454bis and
RFC3454, and all references to StringPrep in ldapbis-strprep to
ensure all is well.

> Appendix A claims to be "normative", but the reference to it in section "Conventions and Terms" says that it's derived from Unicode data. I think it would be better if Appendix A said "This data is derived from the Unicode 3.2 data files by listing all characters with the Mn, Mc or Me properties. It is reproduced here for convenience." In that case, it's clear what to do if there should ever be a conflict between the two - Unicode rules.

The WG discussed whether "Unicode rules" or "Appendix A rules"
and, on the advice of Paul Hoffman, the WG choose the later.
Basically, Stringprep is table driven.  The tables, including
not only this table but also all other referenced tables, are
to be considered definitive for the purpose of implementing this
algorithm.

I suggest adding the following to 1.3:
  It is noted that while various tables of Unicode characters included
  and/or referenced by this specification are derived from Unicode
  [UNICODE] data, these tables are to be considered definitive for
  the purpose of implementing this specification.