On 20-Oct-08, at 7:37 PM, Peter Saint-Andre wrote:
Please understand that even if we use MUST instead of SHOULD with
respect to namespace-awareness, the existing servers are not going to
be left behind. Newer servers and server versions are still going to
continue to support their legacy counterparts. The benefit of course
would be that eventually we will have a sterilized network, where
clients wouldn't need to worry about rolling out their own
(non-conforming) namespace handling. In my opinion this is a better
long term direction.
I too think that is a worthy goal. The question is: how can we get
there
in a reasonable fashion?
Why not limit the scope of XML-NAMES ?
I think xml like this should be prohibited by the xmpp spec.
<presence
from='[EMAIL PROTECTED]/ICS065868CA'
to='[EMAIL PROTECTED]/aluminium'
xmlns:ns2='urn:ietf:params:xml:ns:xmpp-stanzas'
xmlns:ns4='urn:ietf:params:xml:ns:xmpp-streams'
xmlns:ns5='jabber:iq:auth'
xmlns:ns6='jabber:iq:roster'
xmlns:ns7='google:roster'
xmlns:ns8='jabber:iq:privacy'
xmlns:ns9='urn:ietf:params:xml:ns:xmpp-tls'
xmlns:ns10='urn:ietf:params:xml:ns:xmpp-sasl'
xmlns:ns11='urn:ietf:params:xml:ns:xmpp-bind'
xmlns:ns12='vcard-temp'
xmlns:ns13='vcard-temp:x:update'
xmlns:ns14='jabber:x:event'
xmlns:ns15='http://jabber.org/protocol/caps'
xmlns:ns16='http://jabber.org/protocol/muc#user'
xmlns:ns17='http://jabber.org/protocol/commands'
xmlns:ns18='google:nosave'
xmlns:ns19='google:subscribe'
xmlns:ns20='http://jabber.org/protocol/disco#info'
xmlns:ns21='http://jabber.org/protocol/disco#items'
xmlns:ns22='google:shared-status'
xmlns:ns23='google:jingleinfo'xmlns:ns24='jabber:x:delay'
xmlns:ns25='google:domain'
xmlns:ns26='http://www.google.com/session'
xmlns:ns27='http://www.google.com/session/share'
xmlns:ns28='http://www.google.com/transport/p2p'
xmlns:ns29='urn:ietf:params:xml:ns:xmpp-session'
xmlns:ns30='http://jabber.org/protocol/chatstates'>
<status/>
<ns13:x>
<ns13:photo>9s8s8a99x9as99</ns13:photo>
</ns13:x>
</presence>
The fact it's bloat should be reason enough :-)
ck
