[pkix] Re: [Technical Errata Reported] RFC4211 (8391 )
Paul Wouters <[email protected]> Wed, 23 Apr 2025 15:51:45 -0400
| Newsgroups | gmane.ietf.x509 |
|---|---|
| Message-ID | <CAGL5yWZxzEBcELQLHJ-m1Y87_A396BfD=O70JduWEicN1ThZ5w@mail.gmail.com> |
--===============6375841997419663684== Content-Type: multipart/alternative; boundary="000000000000017e470633776f64" --000000000000017e470633776f64 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable thanks, marked as verified. Paul On Wed, Apr 23, 2025 at 2:52=E2=80=AFPM Russ Housley <[email protected]>= wrote: > I discovered this mistake when talking to Joe Mandel about a new document > that uses CRMF as defined in RFC 4211. > > Russ > > > > On Apr 23, 2025, at 2:50=E2=80=AFPM, RFC Errata System < > [email protected]> wrote: > > > > The following errata report has been submitted for RFC4211, > > "Internet X.509 Public Key Infrastructure Certificate Request Message > Format (CRMF)". > > > > -------------------------------------- > > You may review the report below and at: > > https://www.rfc-editor.org/errata/eid8391 > > > > -------------------------------------- > > Type: Technical > > Reported by: Russ Housley <[email protected]> > > > > Section: 4.2 > > > > Original Text > > ------------- > > challengeResponse indicates that a challenge message is to be > > sent from the CA/RA to the requestor. > > > > Corrected Text > > -------------- > > challengeResp indicates that a challenge message is to be > > sent from the CA/RA to the requestor. > > > > Notes > > ----- > > Earlier in the section, SubsequentMessage is defined with two possible > values: encrCert (0) and challengeResp (1). This aligns with that > definition. > > > > Instructions: > > ------------- > > This erratum is currently posted as "Reported". (If it is spam, it > > will be removed shortly by the RFC Production Center.) Please > > use "Reply All" to discuss whether it should be verified or > > rejected. When a decision is reached, the verifying party > > will log in to change the status and edit the report, if necessary. > > > > -------------------------------------- > > RFC4211 (draft-ietf-pkix-rfc2511bis-08) > > -------------------------------------- > > Title : Internet X.509 Public Key Infrastructure > Certificate Request Message Format (CRMF) > > Publication Date : September 2005 > > Author(s) : J. Schaad > > Category : PROPOSED STANDARD > > Source : Public-Key Infrastructure (X.509) > > Stream : IETF > > Verifying Party : IESG > > --000000000000017e470633776f64 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>thanks,</div><div><br></div><div>marked as verified.<= /div><div><br></div><div>Paul</div></div><br><div class=3D"gmail_quote gmai= l_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Apr 23, 20= 25 at 2:52=E2=80=AFPM Russ Housley <<a href=3D"mailto:[email protected]= om">[email protected]</a>> wrote:<br></div><blockquote class=3D"gmail= _quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204= ,204);padding-left:1ex">I discovered this mistake when talking to Joe Mande= l about a new document that uses CRMF as defined in RFC 4211.<br> <br> Russ<br> <br> <br> > On Apr 23, 2025, at 2:50=E2=80=AFPM, RFC Errata System <<a href=3D"= mailto:[email protected]" target=3D"_blank">[email protected]= rg</a>> wrote:<br> > <br> > The following errata report has been submitted for RFC4211,<br> > "Internet X.509 Public Key Infrastructure Certificate Request Mes= sage Format (CRMF)".<br> > <br> > --------------------------------------<br> > You may review the report below and at:<br> > <a href=3D"https://www.rfc-editor.org/errata/eid8391" rel=3D"noreferre= r" target=3D"_blank">https://www.rfc-editor.org/errata/eid8391</a><br> > <br> > --------------------------------------<br> > Type: Technical<br> > Reported by: Russ Housley <<a href=3D"mailto:[email protected]" = target=3D"_blank">[email protected]</a>><br> > <br> > Section: 4.2<br> > <br> > Original Text<br> > -------------<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0challengeResponse indicates that a ch= allenge message is to be<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sent from the CA/RA to the requestor.= <br> > <br> > Corrected Text<br> > --------------<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0challengeResp indicates that a challe= nge message is to be<br> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sent from the CA/RA to the requestor.= <br> > <br> > Notes<br> > -----<br> > Earlier in the section, SubsequentMessage is defined with two possible= values: encrCert (0) and challengeResp (1).=C2=A0 This aligns with that de= finition.<br> > <br> > Instructions:<br> > -------------<br> > This erratum is currently posted as "Reported". (If it is sp= am, it <br> > will be removed shortly by the RFC Production Center.) Please<br> > use "Reply All" to discuss whether it should be verified or<= br> > rejected. When a decision is reached, the verifying party=C2=A0 <br> > will log in to change the status and edit the report, if necessary.<br= > > <br> > --------------------------------------<br> > RFC4211 (draft-ietf-pkix-rfc2511bis-08)<br> > --------------------------------------<br> > Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Internet= X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)<= br> > Publication Date=C2=A0 =C2=A0 : September 2005<br> > Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: J. Schaad<br> > Category=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : PROPOSED STANDARD<= br> > Source=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Public-Key In= frastructure (X.509)<br> > Stream=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : IETF<br> > Verifying Party=C2=A0 =C2=A0 =C2=A0: IESG<br> <br> </blockquote></div> --000000000000017e470633776f64-- --===============6375841997419663684== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcGtpeCBtYWls aW5nIGxpc3QgLS0gcGtpeEBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVtYWlsIHRv IHBraXgtbGVhdmVAaWV0Zi5vcmcK --===============6375841997419663684==--