[netconf] [Editorial Errata Reported] RFC8572 (6807)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 04 January 2022 07:43 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFC133A18B5 for <netconf@ietfa.amsl.com>; Mon, 3 Jan 2022 23:43:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ecIzJg2ayese for <netconf@ietfa.amsl.com>; Mon, 3 Jan 2022 23:43:14 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 787FB3A18B4 for <netconf@ietf.org>; Mon, 3 Jan 2022 23:43:14 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 51ED235225; Mon, 3 Jan 2022 23:43:14 -0800 (PST)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: lijun.liao@gmail.com, kent+ietf@watsen.net, ian.farrer@telekom.de, mikael.abrahamsson@t-systems.se, netconf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220104074314.51ED235225@rfc-editor.org>
Date: Mon, 03 Jan 2022 23:43:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/couhnT_0oJKoQM2_75M1QtPdeQw>
Subject: [netconf] [Editorial Errata Reported] RFC8572 (6807)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Jan 2022 07:43:19 -0000
The following errata report has been submitted for RFC8572, "Secure Zero Touch Provisioning (SZTP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6807 -------------------------------------- Type: Editorial Reported by: Lijun Liao <lijun.liao@gmail.com> Section: 3.3 Original Text ------------- When unencrypted, the ownership voucher artifact is as defined in [RFC8366]. As described, it is a CMS structure whose topmost content type MUST be the OID id-signedData (1.2.840.113549.1.7.2), whose eContentType MUST be OID id-ct-animaJSONVoucher (1.2.840.113549.1.9.16.1), or the OID id-data (1.2.840.113549.1.7.1). When the OID id-data is used, the encoding (JSON, XML, etc.) SHOULD be communicated externally. In either case, the associated content is an octet string containing ietf-voucher data in the expected encoding. When encrypted, the topmost content type of the ownership voucher artifact's CMS structure MUST be the OID id-envelopedData (1.2.840.113549.1.7.3), and the encryptedContentInfo's content type MUST be the OID id-signedData (1.2.840.113549.1.7.2), whose eContentType MUST be OID id-ct-animaJSONVoucher (1.2.840.113549.1.9.16.1), or the OID id-data (1.2.840.113549.1.7.1). When the OID id-data is used, the encoding (JSON, XML, etc.) SHOULD be communicated externally. In either case, the associated content is an octet string containing ietf-voucher data in the expected encoding. Corrected Text -------------- When unencrypted, the ownership voucher artifact is as defined in [RFC8366]. As described, it is a CMS structure whose topmost content type MUST be the OID id-signedData (1.2.840.113549.1.7.2), whose eContentType MUST be OID id-ct-animaJSONVoucher (1.2.840.113549.1.9.16.1.40), or the OID id-data (1.2.840.113549.1.7.1). When the OID id-data is used, the encoding (JSON, XML, etc.) SHOULD be communicated externally. In either case, the associated content is an octet string containing ietf-voucher data in the expected encoding. When encrypted, the topmost content type of the ownership voucher artifact's CMS structure MUST be the OID id-envelopedData (1.2.840.113549.1.7.3), and the encryptedContentInfo's content type MUST be the OID id-signedData (1.2.840.113549.1.7.2), whose eContentType MUST be OID id-ct-animaJSONVoucher (1.2.840.113549.1.9.16.1.40), or the OID id-data (1.2.840.113549.1.7.1). When the OID id-data is used, the encoding (JSON, XML, etc.) SHOULD be communicated externally. In either case, the associated content is an octet string containing ietf-voucher data in the expected encoding. Notes ----- The OID for id-ct-animaJSONVoucher is 1.2.840.113549.1.9.16.1.40. 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. -------------------------------------- RFC8572 (draft-ietf-netconf-zerotouch-29) -------------------------------------- Title : Secure Zero Touch Provisioning (SZTP) Publication Date : April 2019 Author(s) : K. Watsen, I. Farrer, M. Abrahamsson Category : PROPOSED STANDARD Source : Network Configuration Area : Operations and Management Stream : IETF Verifying Party : IESG
- [netconf] [Editorial Errata Reported] RFC8572 (68… RFC Errata System
- Re: [netconf] [Editorial Errata Reported] RFC8572… Kent Watsen