CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 08:49:17 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
set-cookie: PHPSESSID=egpaevbacbpelbilep0o2dql36; path=/
set-cookie: __cf_bm=OyT2x1pfq021kyyWX4hJmQC5LxWADX5afXmRw0Srlpw-1760172557-1.0.1.1-k9agKWxbkHhGMoTxkmegZwVp25ViRGiVuO78muTk4UniOqUwa1zGZ9ZOiFz9d_3_jVrY84SuA1sHRtaIapEDLxT_Hzps9py8wJLnOcW6.CU; path=/; expires=Sat, 11-Oct-25 09:19:17 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: 98cd1a6c2afca403-BLR
alt-svc: h3=":443"; ma=86400
RFC Errata Report » RFC Editor
Search RFCs
The Series
For Authors
Sponsor
RFC Errata
RFC 4211, "Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)", September 2005
Note: This RFC has been updated by RFC 9045
Source of RFC: pkix (sec)
Errata ID: 2343
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2005-11-08
Held for Document Update by: Sean Turner
Date Held: 2010-07-20
Section 6.1 says:
In the first paragraph on page 19, refers to a wrong subsection; it says: The regToken control is used only for initialization of an end entity into the PKI, whereas the authenticator control (see section 7.2) can ^ be used for the initial as well as subsequent certification requests. It should say: The regToken control is used only for initialization of an end entity into the PKI, whereas the authenticator control (see section 6.2) can be used for the initial as well as subsequent certification requests.
It should say:
[see above]
Notes:
Changed to editorial.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us