CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 21:41:03 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=v2pjbad26b7fkvkepk4ugr25mo; path=/
set-cookie: __cf_bm=3AK7blaUAJ_6A1uxGp0bKRgA9ykHpiU_GXe1SSVFkJk-1760046063-1.0.1.1-KBN07lqN6l41b.sDIyPZzxf_AqjeV3yrGqemv6d99MJDlLXYRJC7cFGIcM8BCdOR53iAfWQelQNdDt4dI46uAZHEYwsERavEaKmnMnqbO8Y; path=/; expires=Thu, 09-Oct-25 22:11:03 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 98c10a337e3b1ec2-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
See Also: RFC 4013 w/ inline errata
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
RFC 4013, "SASLprep: Stringprep Profile for User Names and Passwords", February 2005
Note: This RFC has been obsoleted by RFC 7613
Source of RFC: sasl (sec)See Also: RFC 4013 w/ inline errata
Errata ID: 1812
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alexey Melnikov
Date Reported: 2009-07-18
Verifier Name: Sean Turner
Date Verified: 2010-04-19
Section 2.3 says:
This profile specifies the following characters as prohibited input:
It should say:
This profile specifies the following characters as prohibited output:
Notes:
Per RFC 3454, the check for prohibited characters is done after the "Map" and "Normalize" steps. Characters listed here are actually allowed as inputs if they get removed by the "Map" or "Normalize" steps.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us