(in my role as individual, not as chair) On 9/23/09 11:47 AM, "Jehan Pagès" <jehan.marmottard at gmail.com> wrote: > No, I don't say that it is not a logical way to do. I just say that there > are others and that the RFC should not force to do a specific way. The RFC should promote interoperability, and backwards-compatibility is a goal from the charter. > For > instance, you could imagine that you set the stream ns as the default ns and > declare a prefix for "jabber:client" (or "jabber:server", or whatever) and > use this prefix in the stanzas, instead of doing the opposite. I just say it > should not matter, as at the end, what matters is the qualified name. As long as your server has not been coded to check the first byte of the element name for fast routing decisions. I know of at least two servers that do this. -- Joe Hildebrand
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.