Re: [Editorial Errata Reported] RFC6844 (5091)
Kathleen Moriarty <[email protected]>
| Newsgroups | gmane.ietf.x509 |
|---|---|
| Message-ID | <CAHbuEH4yDTKk2n_7DrzTpMGNKED6Scgy2C+EjbgtV-crb-1o7Q@mail.gmail.com> |
Thanks, Philip. I see your point on errata of errata, but your errata didn't fix the space, so HFDU seems right to me so this change isn't forgotten. Best regards, Kathleen On Fri, Aug 18, 2017 at 12:27 PM, Phillip <[email protected]> wrote: > Please reject, Errata 5065 already updates this section, we should avoid > errata of errata. > > https://www.rfc-editor.org/errata_search.php?rfc=6844&rec_status=15&presenta > tion=records > > The second space does not worry me nearly as much as the issues to do with > CNAME handling. > > > -----Original Message----- > From: Russ Housley [mailto:[email protected]] > Sent: Friday, August 18, 2017 11:15 AM > To: Kathleen Moriarty <[email protected]>; Eric Rescorla > <[email protected]> > Cc: Phillip Hallam-Baker <[email protected]>; Rob Stradling > <[email protected]>; IETF PKIX <[email protected]> > Subject: Re: [pkix] [Editorial Errata Reported] RFC6844 (5091) > > I do not think the extra space will confuse any implementers. Also, since > the LAMPS WG is considering a charter item to update this document, a > resolution of "held for future update" seems right to me. > > Russ > > >> On Aug 18, 2017, at 11:06 AM, RFC Errata System > <[email protected]> wrote: >> >> The following errata report has been submitted for RFC6844, "DNS >> Certification Authority Authorization (CAA) Resource Record". >> >> -------------------------------------- >> You may review the report below and at: >> http://www.rfc-editor.org/errata/eid5091 >> >> -------------------------------------- >> Type: Editorial >> Reported by: Mak Kolybabi <[email protected]> >> >> Section: 4 >> >> Original Text >> ------------- >> o If CAA(X) is not empty, R(X) = CAA (X), otherwise >> >> Corrected Text >> -------------- >> o If CAA(X) is not empty, R(X) = CAA(X), otherwise >> >> Notes >> ----- >> Remove unnecessary space after second CAA, making appearances of CAA(X) > consistent throughout the section. >> >> Instructions: >> ------------- >> This erratum is currently posted as "Reported". If necessary, please >> use "Reply All" to discuss whether it should be verified or rejected. >> When a decision is reached, the verifying party can log in to change >> the status and edit the report, if necessary. >> >> -------------------------------------- >> RFC6844 (draft-ietf-pkix-caa-15) >> -------------------------------------- >> Title : DNS Certification Authority Authorization (CAA) > Resource Record >> Publication Date : January 2013 >> Author(s) : P. Hallam-Baker, R. Stradling >> Category : PROPOSED STANDARD >> Source : Public-Key Infrastructure (X.509) >> Area : Security >> Stream : IETF >> Verifying Party : IESG >> >> _______________________________________________ >> pkix mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/pkix > > -- Best regards, Kathleen _______________________________________________ pkix mailing list [email protected] https://www.ietf.org/mailman/listinfo/pkix