Draft:  draft-saintandre-xmpp-iri-03
Reviewer: Black_David@emc.com
Review Date: Thursday 3/9/2006 8:55 PM CST
IETF LC Date: 3/15/2006

Summary: This draft is on the right track but has open issues, described
in the review.

Section 2.5 contains the following note:

   (Note: In pursuit of interoperability, it may be helpful to maintain
   a registry of query types and perhaps even of keys for use in XMPP
   query components.  Given that such values will most likely be
   specific to particular applications of XMPP rather than core to XMPP
   itself, it seems reasonable that such a registry, if created, would
   be maintained by the Jabber Registrar function of the Jabber Software
   Foundation as described in [JEP-0053], rather than by the IANA.  A
   proposal for creating such a registry can be found in [JEP-0147].)

Given the importance of interoperability to the IETF, IESG approval of this
draft should probably be delayed until that registry is functional so that
the draft can document registration requirements for query components.
This problem is ironically caused by XMPP's success in being used by
multiple independent applications (e.g., list in Section 2.1), requiring
a registry like this to prevent collisions among their use of URIs/IRIs.

Nit - In Section 3.6 add "RFC " before "XXXX" and add an RFC Editor note
to tell the RFC Editor to replace "XXXX" with the number of the published
RFC and delete the note.