RE: draft-sun-handle-system-protocol-04.txt

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

By the way, their reference 3 still points to obsoleted RFC2044
It should be RFC2279

Thanks,
Bert 

> -----Original Message-----
> From: Wijnen, Bert (Bert) 
> Sent: donderdag 17 april 2003 18:48
> To: Ted Hardie (E-mail)
> Cc: Iesg (E-mail)
> Subject: draft-sun-handle-system-protocol-04.txt
> 
> 
> How do (or do they) the below sections jive with RFC 2279 ??
> 
> 2.1.3  Character Case
> 
>    Handles are character strings based on the ISO-10646 character set
>    and must be encoded in UTF-8. By default, handle characters are
>    treated as case-sensitive under the handle protocol. A handle
>    service, however, may be implemented in such a way that ASCII
>    characters are processed case-insensitively. For example, the
>    Global Handle Registry (GHR) provides a handle service where ASCII
>    characters are processed in a case-insensitive manner. This
>    suggests that ASCII characters in any naming authority are case-
>    insensitive.
> 
>    When handles are created under a case-insensitive handle server,
>    their original case should be preserved. To avoid any confusion,
>    the server should avoid creating any handle whose character string
>    matches that of an existing handle, ignoring the case difference.
>    For example, if the handle "X/Y" was already created, the server
>    should refuse any request to create the handle "x/y" or any of its
>    case variations.
> 
> 2.1.4  Standard String Type: UTF8-String
> 
>    Handles are transmitted as UTF8-Strings under the handle protocol.
>    Throughout this document, UTF8-String stands for the data type that
>    consists of a 4-byte unsigned integer followed by a character
>    string in UTF-8 encoding. The leading integer specifies the number
>    of octets of the character string.
> 
> Thanks,
> Bert 
>