[Standards] About stream namespaces

Peter Saint-Andre stpeter at jabber.org
Fri Mar 16 17:12:59 UTC 2007

Robin Redeker wrote:
> On Fri, Mar 16, 2007 at 09:51:24AM -0700, JD Conley wrote:
>>> So in literal does it mean that I should not generate something like
>>> this:
>>>     <__NS1:starttls xmlns:__NS1="urn:ietf:params:xml:ns:xmpp-tls"/>
>> Yes.
> :-(
>>> I'm confused... preventing such prefixes does make implementation, at
>>> least for me, a bit more complicated. As I have to take care that my
>>> XML writer does not generate prefixes for the first-level children of
>>> the <stream> element.
>> Don't worry. You're not alone. But this is the way it is. :)
> Enforcing this kind of backward compatibility for new client
> implementations does not make much sense for me. It would make more
> sense if servers would would be told that they MAY not generate
> such prefixes to take care of old clients.
> At least with that SHOULD NOT in place this issue will never be
> resolved because server implementors might say: "Well, RFC says you
> SHOULD NOT do that. I won't fix it.". And client developers will
> have to obey :-)

One of our rules in writing the RFCs was not to break things since we 
already had such a large installed base at that time. Sorry.


Peter Saint-Andre
XMPP Standards Foundation

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

More information about the Standards mailing list