Lines Matching refs:profiles

38    strings.  Protocols must create profiles of stringprep in order to
129    text.  Other protocols can create profiles of these rules; these
130    profiles will allow users to enter internationalized text strings in
143    In addition to helping string matching, profiles of stringprep can
155    string would contain a prohibited character.  Stringprep profiles
158    Stringprep profiles cannot account for all of the variations that
213    When two protocols that use different profiles of stringprep
216    strongly consider re-using existing profiles of stringprep.
233    stringprep profiles SHOULD NOT do so.
238    profiles of stringprep select among those defined tables.
297    profile registry when creating new profiles for stringprep, and to
298    re-use logic from earlier profiles where possible in new profiles.
418    appendix B.3.  appendix B.2 is for profiles that also use Unicode
419    normalization form KC, while appendix  B.3 is for profiles that do
459    Authors of profiles of this document need to consider the effects of
461    updating their profiles.  Adding a new mapping for a currently-
523    normalized value of an existing character, authors of profiles of
577    contains the non-ASCII code points.  Most profiles of this document
606    ASCII code points.  Most profiles of this document that want to
849    stringprep profiles.  This is very useful since it makes the overall
1083    Most profiles of stringprep can cause changes in strings that are
1143    Stringprep profiles MUST have IETF consensus as described in
1147    IANA has set up a registry of stringprep profiles.  This registry is
1148    a single text file that lists the known profiles.  Each entry in the
1163    It is probably harmful if a large number of profiles of stringprep
1165    profiles and instead suggest that protocols reuse existing profiles.