Skip to content


IETF Advancement

As previously mentioned, we are working to update the core XMPP specifications by incorporating feedback based on the significant implementation and deployment experience with XMPP technologies we have gained since RFC 3920 and RFC 3921 were published in October, 2004. To date we have expected the revised versions to advance XMPP to a status of Draft Standard within the Internet Standards Process managed by the IETF. However, it seems that we overlooked some of the rules from RFC 2026, specifically that “standards track specifications normally must not depend on other standards track specifications which are at a lower maturity level”. What this means is that the XMPP specifications will not be able to advance to Draft until the specs defining IETF technologies on which XMPP depends also advance to Draft (i.e., until there are no more downward references or “downrefs”).

Unfortunately, the XMPP specs have many downrefs, including the following:

Given the serious number of significant downrefs, I think it’s unrealistic for us to expect advancement of XMPP to Draft Standard anytime soon. It appears that the best we can do is update the XMPP specs as we have been doing, resulting in revised specifications that reflect our community’s implementation and deployment experience but that are still at the Proposed Standard level.

And speaking of updated specs, expect revised versions of rfc3920bis and rfc3920bis soon.

UPDATE: As Joe Hildebrand mentions (see also my reply), things are probably not quite so dire. Check for further updates as we work with folks at the IETF on this topic…

Posted in IETF.


One Response

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

Continuing the Discussion

  1. EigenPresence : IETF process linked to this post on October 13, 2008

    [...] In the blog at xmpp.org, stpeter says: It appears that the best we can do is update the XMPP specs as we have been doing, resulting in revised specifications that reflect our community’s implementation and deployment experience but that are still at the Proposed Standard level. [IETF Advancement] [...]