[sidr] [Errata Held for Document Update] RFC6487 (5191)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 01 December 2017 21:31 UTC

To: nmalykh@gmail.com, gih@apnic.net, ggm@apnic.net, robertl@apnic.net
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: aretana.ietf@gmail.com, iesg@ietf.org, sidr@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20171201213132.8676EB81685@rfc-editor.org>
Date: Fri, 01 Dec 2017 13:31:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/AhK2iVEutWMb1WGbC5Xnpy-9Y0I>
Subject: [sidr] [Errata Held for Document Update] RFC6487 (5191)
Precedence: list

The following errata report has been held for document update 
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

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Nikolai Malykh <nmalykh@gmail.com>
Date Reported: 2017-11-28
Held by: Alvaro Retana (IESG)

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.

--------------------------------------
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] [Errata Held for Document Update] RFC6487 … RFC Errata System