JID case sensitivity
stpeter at stpeter.im
Fri Mar 27 01:38:30 UTC 2009
On 3/26/09 6:03 PM, Alex Vandiver wrote:
> On Thu, 2009-03-26 at 16:25 -0700, Martin Atkins wrote:
>> Can you reference the specific section of the spec you're referring to?
> ...states that:
> A node identifier MUST be formatted such that the Nodeprep
> profile of [STRINGPREP] can be applied without failing. Before
> comparing two node identifiers, a server MUST (and a client
> SHOULD) first apply the Nodeprep profile to each identifier.
> ..defines the Nodeprep Stringprep type, which includes Table b.2
> in its mapping table. Table B.2 defines case folding for Unicode
> in the KC normalization.
> Domain names apply Nameprep, which also specifies Table B.2 for
> mappings, and are hence case-folded. Note that resources
> identifiers (which use Resourceprep) do _not_ apply Table B.2,
> and are thus case sensitive.
Correct. That might change slightly in rfc3920bis (probably by ripping
out the dependency on stringprep because it is tied to Unicode 3.2 and
has all those long, scary character tables), but in a way that will be
as backwards-compatible as possible.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 6751 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.danga.com/pipermail/djabberd/attachments/20090326/072f196f/smime.bin
More information about the Djabberd