IETF Logo Mail Archive

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

Sean Turner <sean@sn3rd.com> Wed, 29 November 2017 20:23 UTC

Return-Path: <sean@sn3rd.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 B46661241F3 for <sidr@ietfa.amsl.com>; Wed, 29 Nov 2017 12:23:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 IjhtaMCJOILP for <sidr@ietfa.amsl.com>; Wed, 29 Nov 2017 12:23:23 -0800 (PST)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (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 7F61712426E for <sidr@ietf.org>; Wed, 29 Nov 2017 12:23:23 -0800 (PST)
Received: by mail-qk0-x22e.google.com with SMTP id i130so6114603qke.4 for <sidr@ietf.org>; Wed, 29 Nov 2017 12:23:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7XyxkK3y2kRzMbsgVImn1x8Byb+MOiDWbpPpkF5WOJA=; b=exFmAsZ4kARM2BCM6ZPsw1HEwKgViQ17lYQtHQvse8b2z1ia3YFnJnlRvV6ep6kajQ cp0ZXleS1AZcu+MDAaNybDY/jTRu3cTTSmfubk184kCo28qF96M6mB0UeJgeTby17olp bVbn/ntvS3XteAZOIhQXRD2D3AI6+zHB+ikwY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7XyxkK3y2kRzMbsgVImn1x8Byb+MOiDWbpPpkF5WOJA=; b=uY0sdHK8BlifMYOSPnbF8y2a/y3WwfrDPFu3a+CpsM80lxnqnxRtp9pS9KF9sWMUEu 0HB++BPiE+r8aOrnEgSRAdNTDBwL+XbEKzfHWmBcgj5S9nS1JpTbHQsNOq3zElSHKW/D lY3G5geBjEb96kF38BBXr/czb0Scog1osEFZqxAw3SopszMmTmIydk4a0sdmUGJ7e9+8 mAWj7rE4zu76Fl6lGnsZxqQlhF10ttRaEvjNk4R+zNoj3VFqWhujqOELZyN3WNAJxdX9 iGjQr2b+7jE9HXTqF6lxQMe/rtx2IuSiARj3JGvOOCUTL7ZaFmuTsDHItzFFyRdTJnwF biIg==
X-Gm-Message-State: AKGB3mK9MEI0Dplf5WzrIJ56YdUcYl0Q4WfFYn0vpkAQhCTu+bfWA8h3 2Z/emG2UZbX76FucdUVHpbo4KQ==
X-Google-Smtp-Source: AGs4zMbdpqJdARPl+0Q5XQxxjwqaJoeMkHcAbtAayIzaCJF8jezyC4PHqcH3W+ko73MhVsO8fgs1yw==
X-Received: by 10.55.73.13 with SMTP id w13mr126259qka.201.1511987002622; Wed, 29 Nov 2017 12:23:22 -0800 (PST)
Received: from [172.16.0.18] ([96.231.220.27]) by smtp.gmail.com with ESMTPSA id u73sm1795554qki.7.2017.11.29.12.23.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Nov 2017 12:23:21 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <CAL9jLaZzWNOMgLNNf300qRF_vjOucyDB+fgx2B2OC1t4+VjEzg@mail.gmail.com>
Date: Wed, 29 Nov 2017 15:23:20 -0500
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, nmalykh@gmail.com, db3546@att.com, sidr@ietf.org, Chris Morrow <morrowc@ops-netman.net>, robertl@apnic.net, George Michaelson <ggm@apnic.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D541E44-2B65-4B74-8E57-2D62BEF941A1@sn3rd.com>
References: <20171128142820.41FB9B8174E@rfc-editor.org> <CAL9jLaZzWNOMgLNNf300qRF_vjOucyDB+fgx2B2OC1t4+VjEzg@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/EjrRHI7ZOHn4WDH646tpSkS6Ik0>
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: Wed, 29 Nov 2017 20:23:26 -0000

Yep, but mark it HFDU (Hold For Document Update).

spt

> On Nov 28, 2017, at 10:09, Christopher Morrow <morrowc.lists@gmail.com> wrote:
> 
> 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
> 
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr

v2.23.0 | Report a Bug | By Email