…orm careful testing before migrating accounts and other data (see Section 6 of [RFC7613] for guidance). This document obsoletes RFC 6122 . 2 . Terminology Many important terms used in this document are defined in [ RFC7564 ], [ RFC5890 ], [ RFC6120 ], [ RFC6365 ], and [ Unicode ]…

…orm careful testing before migrating accounts and other data (see Section 6 of [RFC7613] for guidance). This document obsoletes RFC 6122. 2. Terminology Many important terms used in this document are defined in [RFC7564], [RFC5890], [RFC6120], [RFC6365], and [Unicode]. The key wo…

…orm careful testing before migrating accounts and other data (see Section 6 of [RFC7613] for guidance). This document obsoletes RFC 6122 . Terminology Many important terms used in this document are defined in [ RFC7564 ], RFC5890 ], [ RFC6120 ], [ RFC6365 ], and [ Unicode ]. The …

…orm careful testing before migrating accounts and other data (see Section 6 of [RFC7613] for guidance). This document obsoletes RFC 6122 . Terminology Many important terms used in this document are defined in [ RFC7564 ], RFC5890 ], [ RFC6120 ], [ RFC6365 ], and [ Unicode ]. The …

… Preparation and Enforcement steps according to the OpaqueString profile (see [ RFC7613 ]) to a UTF-8 RFC3629 ] encoded "str". The resulting string is also in UTF-8. Note that implementations MUST either implement OpaqueString profile operations from [ RFC7613 ] or disallow the u…

…cters defined in the "UsernameCasePreserved" profile defined in Section 3.3 of [RFC7613] , with the exception of the colon (":") character. For the password, recipients MUST support all characters defined in the "OpaqueString" profile defined in Section 4.2 of [RFC7613] Other val…

…e prepared using the "UsernameCasePreserved" profile defined in Section 3.3 of [RFC7613] o Passwords received from users SHOULD be prepared using the "OpaqueString" profile defined in Section 4.2 of [RFC7613] In both cases, it is the sender's duty to correctly prepare the charact…

…cters defined in the "UsernameCasePreserved" profile defined in Section 3.3 of [RFC7613] , with the exception of the colon (":") character. For the password, recipients MUST support all characters defined in the "OpaqueString" profile defined in Section 4.2 of [RFC7613] Other val…

…cters defined in the "UsernameCasePreserved" profile defined in Section 3.3 of [RFC7613] , with the exception of the colon (":") character. For the password, recipients MUST support all characters defined in the "OpaqueString" profile defined in Section 4.2 of [RFC7613] If the us…

…cters defined in the "UsernameCasePreserved" profile defined in Section 3.3 of [RFC7613] , with the exception of the colon (":") character. For the password, recipients MUST support all characters defined in the "OpaqueString" profile defined in Section 4.2 of [RFC7613] If the us…

…reparation, Enforcement, and Comparison of Internationalized Strings (PRECIS) [ RFC7613 ], or the Unicode Identifier and Pattern Syntax specification [ UAX31 ]. Saint-Andre & Klensin Standards Track [Page 11] RFC 8141 URNs April 2017 In order to make URNs as stable and persistent…

…reparation, Enforcement, and Comparison of Internationalized Strings (PRECIS) [ RFC7613 ], or the Unicode Identifier and Pattern Syntax specification [ UAX31 ]. Saint-Andre & Klensin Standards Track [Page 11] RFC 8141 URNs April 2017 In order to make URNs as stable and persistent…

…reparation, Enforcement, and Comparison of Internationalized Strings (PRECIS) [ RFC7613 ], or the Unicode Identifier and Pattern Syntax specification [ UAX31 ]. Saint-Andre & Klensin Standards Track [Page 11] RFC 8141 URNs April 2017 In order to make URNs as stable and persistent…

…Password column of the first table. As the first table is a direct excerpt from RFC7613, it should not be modified and so the second table should be corrected to contain a proper corresponding example. RFC 7998 , ""xml2rfc" Version 3 Preparation Tool Description", December 2016 S…

…Password column of the first table. As the first table is a direct excerpt from RFC7613, it should not be modified and so the second table should be corrected to contain a proper corresponding example. RFC 7998 , ""xml2rfc" Version 3 Preparation Tool Description", December 2016 S…