[sidr] [Technical Errata Reported] RFC6488 (8307)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 21 February 2025 15:02 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from mail2.ietf.org (mail2.ietf.org [166.84.6.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 394B4C14F6BC; Fri, 21 Feb 2025 07:02:48 -0800 (PST)
Received: from mail.ietf.org (mail.ietf.org [50.223.129.194]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPSA id 88AAC1E44E6; Fri, 21 Feb 2025 15:02:47 +0000 (UTC)
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7DCAC14F5ED; Fri, 21 Feb 2025 07:02:46 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 4C029258393; Fri, 21 Feb 2025 07:02:46 -0800 (PST)
To: mlepinski@bbn.com, achi@bbn.com, kent@bbn.com, james.n.guichard@futurewei.com, jgs@juniper.net, gunter.van_de_velde@nokia.com, morrowc@ops-netman.net, sandy@tislabs.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20250221150246.4C029258393@rfcpa.rfc-editor.org>
Date: Fri, 21 Feb 2025 07:02:46 -0800
Message-ID-Hash: BK52AZDHIDMH7BCMJMVNNESBPVWCOGYS
X-Message-ID-Hash: BK52AZDHIDMH7BCMJMVNNESBPVWCOGYS
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sidr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: tb@theobuehler.org, sidr@ietf.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [sidr] [Technical Errata Reported] RFC6488 (8307)
List-Id: Secure Interdomain Routing <sidr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/UUGbU9R89nM9poA5cRHya7EUfcw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Owner: <mailto:sidr-owner@ietf.org>
List-Post: <mailto:sidr@ietf.org>
List-Subscribe: <mailto:sidr-join@ietf.org>
List-Unsubscribe: <mailto:sidr-leave@ietf.org>
The following errata report has been submitted for RFC6488, "Signed Object Template for the Resource Public Key Infrastructure (RPKI)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8307 -------------------------------------- Type: Technical Reported by: Theo Buehler <tb@theobuehler.org> Section: 2 Original Text ------------- The content-type is the signed-data type of id-data, namely the id-signedData OID [RFC5652], 1.2.840.113549.1.7.2. Corrected Text -------------- The content-type is the id-signedData OID [RFC5652], 1.2.840.113549.1.7.2. Notes ----- id-data (OID 1.2.840.113549.1.7.1) and id-signedData are siblings in the pkcs7 arc, so the latter is not a type of the former. See also https://mailarchive.ietf.org/arch/msg/sidrops/_FuWIR0d5V53VGGGSh-6MKlqLxI/ Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- RFC6488 (draft-ietf-sidr-signed-object-04) -------------------------------------- Title : Signed Object Template for the Resource Public Key Infrastructure (RPKI) Publication Date : February 2012 Author(s) : M. Lepinski, A. Chi, S. Kent Category : PROPOSED STANDARD Source : Secure Inter-Domain Routing Stream : IETF Verifying Party : IESG
- [sidr] [Technical Errata Reported] RFC6488 (8307) RFC Errata System