sure! On Tue, Nov 28, 2017 at 5:02 AM, Geoff Huston <g...@apnic.net> wrote:
> agreed. > > > On 28 Nov 2017, at 8:17 pm, RFC Errata System <rfc-edi...@rfc-editor.org> > wrote: > > > > The following errata report has been submitted for RFC6487, > > "A Profile for X.509 PKIX Resource Certificates". > > > > -------------------------------------- > > You may review the report below and at: > > http://www.rfc-editor.org/errata/eid5188 > > > > -------------------------------------- > > Type: Editorial > > Reported by: Nikolai Malykh <nmal...@gmail.com> > > > > Section: 7.1 > > > > Original Text > > ------------- > > Validation of a certificate's resource extension in the context of a > > certification path (see Section 7.2 entails that for every adjacent > > > > > > Corrected Text > > -------------- > > Validation of a certificate's resource extension in the context of a > > certification path (see Section 7.2) entails that for every adjacent > > > > > > Notes > > ----- > > The closing parenthesis is missing. > > > > 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. > > > > -------------------------------------- > > RFC6487 (draft-ietf-sidr-res-certs-22) > > -------------------------------------- > > Title : A Profile for X.509 PKIX Resource Certificates > > Publication Date : February 2012 > > Author(s) : G. Huston, G. Michaelson, R. Loomans > > Category : PROPOSED STANDARD > > Source : Secure Inter-Domain Routing > > Area : Routing > > Stream : IETF > > Verifying Party : IESG > > _______________________________________________ > sidr mailing list > sidr@ietf.org > https://www.ietf.org/mailman/listinfo/sidr >
_______________________________________________ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr