[pkix] [Editorial Errata Reported] RFC5934 (8191)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 29 November 2024 20:38 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: pkix@ietf.org
Delivered-To: pkix@ietfa.amsl.com
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 64001C18DB91; Fri, 29 Nov 2024 12:38:02 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id A7FB51C5A2F; Fri, 29 Nov 2024 12:38:01 -0800 (PST)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20241129203801.A7FB51C5A2F@rfcpa.rfc-editor.org>
Date: Fri, 29 Nov 2024 12:38:01 -0800
Message-ID-Hash: IQFGKDKQYQKO3IKFQJ7NUAL45GRMYRCY
X-Message-ID-Hash: IQFGKDKQYQKO3IKFQJ7NUAL45GRMYRCY
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pkix.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: corey.j.bonnell@outlook.com, srashmo@radium.ncsc.mil, cwallace@cygnacom.com, pkix@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [pkix] [Editorial Errata Reported] RFC5934 (8191)
List-Id: PKIX Working Group <pkix.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/4pLumd5pIbQdzKlIX1KDdK3gWv4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pkix>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Owner: <mailto:pkix-owner@ietf.org>
List-Post: <mailto:pkix@ietf.org>
List-Subscribe: <mailto:pkix-join@ietf.org>
List-Unsubscribe: <mailto:pkix-leave@ietf.org>
The following errata report has been submitted for RFC5934, "Trust Anchor Management Protocol (TAMP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8191 -------------------------------------- Type: Editorial Reported by: Corey Bonnell <corey.j.bonnell@outlook.com> Section: 1 Original Text ------------- TAMP messages may be exchanged in real time over a network, such as via HTTP as described in Appendix A, or may be stored and transferred using other means. Corrected Text -------------- TAMP messages may be exchanged in real time over a network, such as via HTTP as described in Appendix C, or may be stored and transferred using other means. Notes ----- The appendix reference is incorrect. Appendix A defines the ASN.1 module whereas Appendix C defines the protocol over HTTP. 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. -------------------------------------- RFC5934 (draft-ietf-pkix-tamp-08) -------------------------------------- Title : Trust Anchor Management Protocol (TAMP) Publication Date : August 2010 Author(s) : R. Housley, S. Ashmore, C. Wallace Category : PROPOSED STANDARD Source : Public-Key Infrastructure (X.509) Stream : IETF Verifying Party : IESG
- [pkix] [Editorial Errata Reported] RFC5934 (8191) RFC Errata System
- [pkix] Re: [Editorial Errata Reported] RFC5934 (8… Russ Housley