[stir] [Errata Verified] RFC8588 (6656)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 15 November 2024 20:25 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: stir@ietf.org
Delivered-To: stir@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 AE263C14F6A0; Fri, 15 Nov 2024 12:25:50 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 208343B87C; Fri, 15 Nov 2024 12:25:50 -0800 (PST)
To: xrobau@gmail.com, chris-ietf@chriswendt.net, mary.ietf.barnes@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20241115202550.208343B87C@rfcpa.rfc-editor.org>
Date: Fri, 15 Nov 2024 12:25:50 -0800
Message-ID-Hash: ROF4IKSADOTXT6HM5IE6XWPHDYA4465X
X-Message-ID-Hash: ROF4IKSADOTXT6HM5IE6XWPHDYA4465X
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-stir.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: orie@transmute.industries, iesg@ietf.org, stir@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [stir] [Errata Verified] RFC8588 (6656)
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/sC3W-9AH-nCA2w-B4_kX6nvS-3c>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Owner: <mailto:stir-owner@ietf.org>
List-Post: <mailto:stir@ietf.org>
List-Subscribe: <mailto:stir-join@ietf.org>
List-Unsubscribe: <mailto:stir-leave@ietf.org>
The following errata report has been verified for RFC8588, "Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6656 -------------------------------------- Status: Verified Type: Technical Reported by: Rob Thomas <xrobau@gmail.com> Date Reported: 2021-08-10 Verified by: Orie Steele (IESG) Section: 6 Original Text ------------- Protected Header { "alg":"ES256", "typ":"passport", "ppt":"shaken", "x5u":"https://cert.example.org/passport.cer" } Payload { "attest":"A" "dest":{"tn":["12155550131"]} "iat":"1443208345", "orig":{"tn":"12155550121"}, "origid":"123e4567-e89b-12d3-a456-426655440000" } Corrected Text -------------- Protected Header { "alg":"ES256", "typ":"passport", "ppt":"shaken", "x5u":"https://cert.example.org/passport.cer" } Payload { "attest":"A" "dest":{"tn":["12155550131"]} "iat":1443208345, "orig":{"tn":"12155550121"}, "origid":"123e4567-e89b-12d3-a456-426655440000" } Notes ----- As per RFC8225 (5.1.1), 'iat' is a NumericDate format, which is a number (commonly referred to as a utime). Section 9.4 also specifies that anything that is numeric must be encoded as a number. -------------------------------------- RFC8588 (draft-ietf-stir-passport-shaken-08) -------------------------------------- Title : Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN) Publication Date : May 2019 Author(s) : C. Wendt, M. Barnes Category : PROPOSED STANDARD Source : Secure Telephone Identity Revisited Stream : IETF Verifying Party : IESG
- [stir] [Errata Verified] RFC8588 (6656) RFC Errata System