…ust 2015 This document obsoletes RFC 4013 (the SASLprep profile of stringprep [ RFC3454 ]) but can be used by technologies other than SASL [ RFC4422 ], such as HTTP authentication as specified in [ HTTP-BASIC-AUTH ] and [ HTTP-DIGEST-AUTH ]. This document does not modify the hand…
…stringprep" technology for preparation and comparison of non-ASCII characters [ RFC3454 ]. Following the movement of internationalized domain names away from stringprep, this document defines the XMPP address format in a way that no longer depends on stringprep (see the Preparati…
…"stringprep" technology for preparation and comparison of non-ASCII characters [RFC3454]. Following the movement of internationalized domain names away from stringprep, this document defines the XMPP address format in a way that no longer depends on stringprep (see the Preparatio…
…stringprep" technology for preparation and comparison of non-ASCII characters [ RFC3454 ]. Following the movement of internationalized domain names away from stringprep, this document defines the XMPP address format in a way that no longer depends on stringprep (see the Preparati…
…to Left August 2010 1.2. Background and History The "Stringprep" specification [RFC3454], part of IDNA2003, made the following statement in its Section 6 on the Bidi algorithm: 3) If a string contains any RandALCat character, a RandALCat character MUST be the first character of t…
…stringprep" technology for preparation and comparison of non-ASCII characters [ RFC3454 ]. Following the movement of internationalized domain names away from stringprep, this document defines the XMPP address format in a way that no longer depends on stringprep (see the Preparati…
…statement [ RFC6885 ], many IETF protocols have used the Stringprep framework [ RFC3454 ] as the basis for preparing, enforcing, and comparing protocol strings that contain Unicode characters, especially characters outside the ASCII range [ RFC20 ]. The Stringprep framework was d…
…of IETF RFCs: IDNA [ RFC3490 Nameprep [ RFC3491 Punycode [ RFC3492 Stringprep [ RFC3454 ]. IDNA2008 The IDNA2008 specification is defined by a cluster of IETF RFCs: Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework Internationalized Domain…
…4690 RFC4690 ] and elsewhere in these documents. Any change to the Stringprep [ RFC3454 ] procedure that is profiled and used in IDNA2003, or, more broadly, the IETF's model of the use of internationalized character strings in different protocols, creates some risk of inadvertent…
…of IETF RFCs: IDNA [ RFC3490 Nameprep [ RFC3491 Punycode [ RFC3492 Stringprep [ RFC3454 ]. IDNA2008 The IDNA2008 specification is defined by a cluster of IETF RFCs: Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework Internationalized Domain…
…of IETF RFCs: IDNA [ RFC3490 Nameprep [ RFC3491 Punycode [ RFC3492 Stringprep [ RFC3454 ]. IDNA2008 The IDNA2008 specification is defined by a cluster of IETF RFCs: Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework Internationalized Domain…
…of IETF RFCs: IDNA [ RFC3490 Nameprep [ RFC3491 Punycode [ RFC3492 Stringprep [ RFC3454 ]. IDNA2008 The IDNA2008 specification is defined by a cluster of IETF RFCs: Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework Internationalized Domain…
…of IETF RFCs: IDNA [ RFC3490 Nameprep [ RFC3491 Punycode [ RFC3492 Stringprep [ RFC3454 ]. IDNA2008 The IDNA2008 specification is defined by a cluster of IETF RFCs: Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework Internationalized Domain…
… part of the earlier IDN effort [ RFC3490 ] (IDNA2003): Stringprep Stringprep [ RFC3454 ] provides a model and character tables for preparing and handling internationalized strings. It was used in the original IDN specification (IDNA2003) via a profile called "Nameprep" [ RFC3491…
…2, Map, the mapping shall include case folding as specified in Appendix B.2 of [RFC3454] . * In step 6, Insignificant Character Removal, perform white space compression as specified in Section 2.6.1 , Insignificant Space Handling, of [ RFC4518 ]. When performing the string prepar…