seems legit.

On Tue, Nov 28, 2017 at 9:28 AM, RFC Errata System <
[email protected]> 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/eid5191
>
> --------------------------------------
> Type: Editorial
> Reported by: Nikolai Malykh <[email protected]>
>
> Section: 8
>
> Original Text
> -------------
>             (The issuing CA may wish to be able to extract the database
>             key or subscriber ID from the commonName.  Since only the
>             issuing CA would need to be able to parse the commonName,
>             the database key and the source of entropy (e.g., a UUID)
>             could be separated in any way that the CA wants, as long as
>             it conforms to the rules for PrintableString.  The separator
>
>
>
>
> Huston, et al.               Standards Track                   [Page 21]
>
> RFC 6487              Resource Certificate Profile         February 2012
>
>
>             could be a space character, parenthesis, hyphen, slash,
>             question mark, etc.
>
>
> Corrected Text
> --------------
>             (The issuing CA may wish to be able to extract the database
>             key or subscriber ID from the commonName.  Since only the
>             issuing CA would need to be able to parse the commonName,
>             the database key and the source of entropy (e.g., a UUID)
>             could be separated in any way that the CA wants, as long as
>             it conforms to the rules for PrintableString.  The separator
>
>
>
>
> Huston, et al.               Standards Track                   [Page 21]
>
> RFC 6487              Resource Certificate Profile         February 2012
>
>
>             could be a space character, parenthesis, hyphen, slash,
>             question mark, etc).
>
>
> 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
> [email protected]
> https://www.ietf.org/mailman/listinfo/sidr
>
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to