[Standards] summary: allowable characters

Peter Saint-Andre stpeter at jabber.org
Thu Aug 2 21:34:30 UTC 2007


Mridul Muralidharan wrote:
> 
> Peter Saint-Andre wrote:
>> Mridul Muralidharan wrote:
>>> Btw, changing nodeprep now will cause quite a lot of problem with
>>> existing deployments - since the contact jid's are part of the user data
>>> - and would pretty much mean we cant adopt bis spec.
>>
>> What specifically breaks? Does it depend on which characters would be
>> allowed in nodeprep2? I agree that / and @ are problematic, but the
>> characters " & ' < > seem less so. But I may be missing something.
> 
> 
> The problem essentially is that any place where we have a JID persisted
> in the backend (user roster, acl's, affiliations, privacy lists/block
> lists, etc), it will become incompatible change.
> For example, what used to be contact\26id at domain will now become
> contact&id at domain - causing incompatibilities.

Well we're having a looooong discussion about this in the jdev room
right now:

http://www.jabber.org/muc-logs/jdev@conference.jabber.org/2007-08-02.html

I volunteer elmex for posting a summary once we're done. :)

/psa
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7354 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070802/e6084d13/attachment.bin>


More information about the Standards mailing list