…[ XEP-0029 ] in 2002, and then defined canonically by [ RFC3920 ] in 2004 and [ RFC6122 ] in 2011. As specified in RFCs 3920 and 6122, the XMPP address format used the "stringprep" technology for preparation and comparison of non-ASCII characters [ RFC3454 ]. Following the moveme…

…d by [XEP-0029] in 2002, and then defined canonically by [RFC3920] in 2004 and [RFC6122] in 2011. As specified in RFCs 3920 and 6122, the XMPP address format used the "stringprep" technology for preparation and comparison of non-ASCII characters [RFC3454]. Following the movement …

…[ XEP-0029 ] in 2002, and then defined canonically by [ RFC3920 ] in 2004 and [ RFC6122 ] in 2011. As specified in RFCs 3920 and 6122, the XMPP address format used the "stringprep" technology for preparation and comparison of non-ASCII characters [ RFC3454 ]. Following the moveme…

…[ XEP-0029 ] in 2002, and then defined canonically by [ RFC3920 ] in 2004 and [ RFC6122 ] in 2011. As specified in RFCs 3920 and 6122, the XMPP address format used the "stringprep" technology for preparation and comparison of non-ASCII characters [ RFC3454 ]. Following the moveme…

…tocol definition (one example is [ XMPP-ADDR ], which is intended to obsolete [ RFC6122 ]). Non-coordinated updates to protocol implementations are discouraged because they can have a negative impact on interoperability and security. 2 . Terminology Many important terms used in t…