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

Christopher Morrow <morrowc.lists@gmail.com> Tue, 28 November 2017 15:10 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DFA3124E15 for <sidr@ietfa.amsl.com>; Tue, 28 Nov 2017 07:10:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fuAyCgaqtWZi for <sidr@ietfa.amsl.com>; Tue, 28 Nov 2017 07:09:55 -0800 (PST)
Received: from mail-vk0-x241.google.com (mail-vk0-x241.google.com [IPv6:2607:f8b0:400c:c05::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3D6C1200B9 for <sidr@ietf.org>; Tue, 28 Nov 2017 07:09:54 -0800 (PST)
Received: by mail-vk0-x241.google.com with SMTP id o70so207243vkc.9 for <sidr@ietf.org>; Tue, 28 Nov 2017 07:09:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=d+hS87512nURU62cJlyTBugcPAiLLrWOpGEClwg5nDU=; b=kGOEvpqypPsSKR7BUep9bigoSX/V1TuSmyX84OEc1iErZGlFM0uZ7ffFoeKEiCJCqO ywj1Ar7bJSF3w8SLbOn6l/qAqJqcKT8j2dz5DQRySmYb04rkxOAdEJ2VxsRvXdfwVLS/ zAfTp3N30Vb9ig3CRFyVH1UTEkdRLeYf4ObYgQhzVTfe5EPY5wteZPHedINFs0VO6g90 HCIMx+3RcqlfSxo/yEmZmDSztyCsoJxq4mDXtRgz4f8VIRYkrtHe+VZiY4aE/8dLPMLX YlCQU6GHxhyKQANHflDw09eStOAwTjHlrFWUtpv8U1DPNHu+uxB387p9uWVmtTq/47x0 qjkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=d+hS87512nURU62cJlyTBugcPAiLLrWOpGEClwg5nDU=; b=ITq5ybbKqEE1L/I0RjjLoZ0LdMAd6LS+1g32qIY2dW6pCm1JdvdMlM5cTmfsNRkupH Kv7GgtHMni+XIQQyb0XA+My6C1HThFBFfWxOFH+v9hY+zzMaE6bIlWbW2r3t7rawHurR weh9fmDC+zj7FSR1Szb323C9WsZ2gHtr638OPa1BawafiTAPs7vlHmN0+YvYYNh1G7w1 GxRBbr5qw0f02oai5nUGQnAY52dSlbM47jsnddNvPxw5FZlh+CtgBPTktR2NUiGhgVL1 DBymMhwbh7IXlBymJNXHGJVgKVJSraZF5LgOfmJVEFT4FCunm3kqCr9wyK0EODfgrWCf Z35w==
X-Gm-Message-State: AJaThX5XTTLZBDqJIebg+Woj5TU5qFg+KDt6L+0kP77Fzx45vkSie9KV JC2sCjzftJFdSJp18prNhpF/WHT7TGfTkOujDgM=
X-Google-Smtp-Source: AGs4zMZVqnbbKYrItiEh4ERB5DIA/a9APNqkIcOhjplvSaFlyPyXmogjITv2O5aSoaF3MPv5mAnmU90KjYIXnsjCP0A=
X-Received: by 10.31.218.194 with SMTP id r185mr31779065vkg.110.1511881793753; Tue, 28 Nov 2017 07:09:53 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.176.80.139 with HTTP; Tue, 28 Nov 2017 07:09:53 -0800 (PST)
In-Reply-To: <20171128142820.41FB9B8174E@rfc-editor.org>
References: <20171128142820.41FB9B8174E@rfc-editor.org>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Tue, 28 Nov 2017 10:09:53 -0500
X-Google-Sender-Auth: REuB4LjVg-SkEB3SCmR0LSe0fBc
Message-ID: <CAL9jLaZzWNOMgLNNf300qRF_vjOucyDB+fgx2B2OC1t4+VjEzg@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: Geoff Huston <gih@apnic.net>, George Michaelson <ggm@apnic.net>, robertl@apnic.net, Alia Atlas <akatlas@gmail.com>, db3546@att.com, aretana.ietf@gmail.com, Chris Morrow <morrowc@ops-netman.net>, Sandy Murphy <sandy@tislabs.com>, nmalykh@gmail.com, sidr@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c07b1ea4258e9055f0c6930"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/vNilGF6NMVdPjHJfy8lBw6PbxAw>
Subject: Re: [sidr] [Editorial Errata Reported] RFC6487 (5191)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Nov 2017 15:10:01 -0000

seems legit.

On Tue, Nov 28, 2017 at 9:28 AM, RFC Errata System <
rfc-editor@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/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 mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>