Comments on draft-dusseault-caldav-15 and draft-newman-i18n-comparator-14

Hi,

I notice that draft-dusseault-caldav-15 now delegates part of the text 
matching semantics to draft-newman-i18n-comparator-14, which probably is 
a good thing. As far as I can tell, this change was made in following up 
to Sam H's comments in 
<https://datatracker.ietf.org/public/pidtracker.cgi?command=view_comment&id=55575>:

> Section 9.6 contains a facility for doing substring matching on
> internationalized strings but contains no discussion of normalization,
> limited discussion of case folding, and no discussion of other
> matching issues that have been problematic for LDAP, IMAP and other
> IETF technologies.  This seems quite inadequate.  If the
> internationalization community within the IETF is quite sure that this
> is OK, I'll remove the discuss.  I just don't see why text matching in
> caldav should be so much easier than IDN or LDAP.

But as a matter of fact, draft-newman-i18n-comparator-14 doesn't define 
any collations that would actually solve the Unicode NF issue, so it's 
not really clear how this helps CalDAV (except that it now uses a 
framework in which the solution may become available in the future).

Maybe the set of initial registrations in 
<http://tools.ietf.org/html/draft-newman-i18n-comparator-14#section-9> 
needs to be extended?

Best regards, Julian

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf