[sidr] [Editorial Errata Reported] RFC6487 (5191)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 28 November 2017 14:28 UTC

To: gih@apnic.net, ggm@apnic.net, robertl@apnic.net, akatlas@gmail.com, db3546@att.com, aretana.ietf@gmail.com, morrowc@ops-netman.net, sandy@tislabs.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: nmalykh@gmail.com, sidr@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20171128142820.41FB9B8174E@rfc-editor.org>
Date: Tue, 28 Nov 2017 06:28:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/lTNsOKEYZ1izDpENc3qdVh6n2yQ>
Subject: [sidr] [Editorial Errata Reported] RFC6487 (5191)
Precedence: list

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 <nmalykh@gmail.com>

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] [Editorial Errata Reported] RFC6487 (5191) RFC Errata System
Re: [sidr] [Editorial Errata Reported] RFC6487 (5… Christopher Morrow
Re: [sidr] [Editorial Errata Reported] RFC6487 (5… Sean Turner