Shepherd writeup
rfc7622-24

1. Summary

The document shepherd is Matthew Miller.  The responsible Area Director
is Ben Campbell.

This document defines the address format for the Extensible Messaging
and Presence Protocol (XMPP), including support for code points outside
the ASCII range.  This document obsoletes RFC 6122.

This document replaces the XMPP address format, and as such is intended
to be a Proposed Standard.

2. Review and Consensus

This document received review from a small but active number of
individuals from the Working Group and the XMPP Community.  There is
consensus to publish this document.

The XMPP Community did raise the concern that some addresses which are
valid using RFC 6122 are no longer valid using this document.  However,
the consensus of the XMPP Community and the Working Group is that: this
document adequately describes the concerns and potential ways to
resolve such issues; and that such JIDs are exceedingly rare, if they
have ever been encountered.

3. Intellectual Property

There are no IPR declarations against this document.  The author has
confirmed that to the best of his knowledge, all IPR (for which there
is none) has been disclosed.

The Working Group did not explicitly discuss any IPR concerns.  Because
this document is heavily reusing technology from
draft-ietf-precis-framework, and adapting existing address format
specifics from RFC 6122, there is very little concern about IPR issues
in addition to those that apply to draft-ietf-precis-framework and
RFC 6122.  There are no IPR disclosures against
draft-ietf-precis-framework and RFC 6122.

4. Other Points

This document does have requests on IANA, but does not require more
than IETF consensus at best.  It does request IANA update the existing
Nodeprep and Resourceprep profile be marked "not current" and update
the reference for those profiles to point to this document.

The external reference to UNICODE is necessary as this document is
entirely about internationalized identifiers (and therefore is entirely
about UNICODE), and is consistent with the other PRECIS-related
documents.

The external reference to UTR36 is necessary to describe security
concerns, particularly the Address Mimicking problem.

The outdated references to draft-ietf-precis-framework and
draft-ietf-precis-nickname are expected to be resolved by the RFC
Editor before AUTH48 concludes.

The information downward reference to RFC 3490 is intentional as it is
used to discuss interoperability concerns with existing XMPP software,
which still use the stringprep profiles Nodeprep and Resourceprep.

The informational downward reference to RFC 3920 is intentional as it
illustrates the history of the XMPP address format, and is used to
describe interoperability concerns for existing software which still
uses the stringprep profiles Nodeprep and Resourceprep.

The informational downward reference to RFC 3921 is intentional as it
describes specific "JID slots" for server dialback (now defined in
XSF XEP-0220) and privacy lists (now defined in XSF XEP-0016). 
Back