[ietf-calsify] Issue RK-5 in rfc2445bis-08 [Was: [Ietf-calsify] Review of rfc2447bis-05]
bernard.desruisseaux at oracle.com
Thu Oct 16 14:00:43 PDT 2008
> Issues in rfc2445bis-08:
> 5. Sec. "184.108.40.206. Unique Identifier" (p.120f): As detailled in issue
> * above, it should be clarified how spaces in a UID property value
> should be handled. In particular, are they allowed at all? Are
> leading or trailing spaces to be ignored when looking for or
> comparing UIDs?
BTW, the recommended syntax of the "UID" property was previously
discussed on the list, though from a different angle:
If we are to discourage the use of specific characters perhaps '/', '?'
and '&' should be added to the list since some CalDAV clients are using
the UID value as the name of the calendar object resource. Limiting
ourselves to US-ASCII would also help avoid issues.
Can you propose a textual change?
More information about the ietf-calsify