[Anima] [Editorial Errata Reported] RFC8994 (7071)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 04 August 2022 14:57 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D335C14F74F for <anima@ietfa.amsl.com>; Thu, 4 Aug 2022 07:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBaWJRczYvcl for <anima@ietfa.amsl.com>; Thu, 4 Aug 2022 07:57:47 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 357D4C157B49 for <anima@ietf.org>; Thu, 4 Aug 2022 07:57:46 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 630CB4C0A4; Thu, 4 Aug 2022 07:57:46 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: corey.bonnell@digicert.com, tte+ietf@cs.fau.de, Michael.H.Behringer@gmail.com, sbjarnason@arbor.net, anima@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220804145746.630CB4C0A4@rfcpa.amsl.com>
Date: Thu, 04 Aug 2022 07:57:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/DkZEFjaJ4FSxhXBMyBrn7BfnYxA>
Subject: [Anima] [Editorial Errata Reported] RFC8994 (7071)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Aug 2022 14:57:51 -0000

The following errata report has been submitted for RFC8994,
"An Autonomic Control Plane (ACP)".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7071

--------------------------------------
Type: Editorial
Reported by: Corey Bonnell <corey.bonnell@digicert.com>

Section: 6.2.2

Original Text
-------------
   The acp-node-name in Figure 2 is the ABNF definition ("Augmented BNF
   for Syntax Specifications: ABNF" [RFC5234]) of the ACP Node Name.  An
   ACP certificate MUST carry this information.  It MUST contain an
   otherName field in the X.509 Subject Alternative Name extension, and
   the otherName MUST contain an AcpNodeName as described in
   Section 6.2.2.

Corrected Text
--------------
   The acp-node-name in Figure 2 is the ABNF definition ("Augmented BNF
   for Syntax Specifications: ABNF" [RFC5234]) of the ACP Node Name.  An
   ACP certificate MUST carry this information.  It MUST contain an
   otherName field in the X.509 Subject Alternative Name extension, and
   the otherName MUST contain an AcpNodeName as described in
   Section 6.2.2.1.

Notes
-----
David von Oheimb discovered [1] that section 6.2.2 is self-referential and incorrect regarding the section reference to the ASN.1 module.

The correct section number is 6.2.2.1.

[1] https://mailarchive.ietf.org/arch/msg/spasm/-ymZk94KFzzolZSsJh6HONnypXQ/

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. 

--------------------------------------
RFC8994 (draft-ietf-anima-autonomic-control-plane-30)
--------------------------------------
Title               : An Autonomic Control Plane (ACP)
Publication Date    : May 2021
Author(s)           : T. Eckert, Ed., M. Behringer, Ed., S. Bjarnason
Category            : PROPOSED STANDARD
Source              : Autonomic Networking Integrated Model and Approach
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG