[websec] [Editorial Errata Reported] RFC6797 (8186)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 22 November 2024 20:57 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: websec@ietf.org
Delivered-To: websec@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 B4A67C1516F3; Fri, 22 Nov 2024 12:57:18 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 278841BC19C; Fri, 22 Nov 2024 12:57:18 -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: <20241122205718.278841BC19C@rfcpa.rfc-editor.org>
Date: Fri, 22 Nov 2024 12:57:18 -0800
Message-ID-Hash: SLHT3V4HXBU55JVRJUX4NHNCPF7MTKVD
X-Message-ID-Hash: SLHT3V4HXBU55JVRJUX4NHNCPF7MTKVD
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-websec.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: joe-ietf@cursive.net, Jeff.Hodges@PayPal.com, collin.jackson@sv.cmu.edu, ietf@adambarth.com, websec@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [websec] [Editorial Errata Reported] RFC6797 (8186)
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/websec/ZcugO4zeNBLj0VpE2wzGlwVgIIQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/websec>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Owner: <mailto:websec-owner@ietf.org>
List-Post: <mailto:websec@ietf.org>
List-Subscribe: <mailto:websec-join@ietf.org>
List-Unsubscribe: <mailto:websec-leave@ietf.org>
The following errata report has been submitted for RFC6797, "HTTP Strict Transport Security (HSTS)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8186 -------------------------------------- Type: Editorial Reported by: Joe Hildebrand <joe-ietf@cursive.net> Section: 6.1 Original Text ------------- directive-value = token | quoted-string Corrected Text -------------- directive-value = token / quoted-string Notes ----- The "directive-value" production should use a "/" for alternatives, not a "|". See RFC 5234, which should be referenced by this spec but isn't. This is an editorial nitpick. 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. -------------------------------------- RFC6797 (draft-ietf-websec-strict-transport-sec-14) -------------------------------------- Title : HTTP Strict Transport Security (HSTS) Publication Date : November 2012 Author(s) : J. Hodges, C. Jackson, A. Barth Category : PROPOSED STANDARD Source : Web Security Stream : IETF Verifying Party : IESG
- [websec] [Editorial Errata Reported] RFC6797 (818… RFC Errata System
- [websec] Re: [Editorial Errata Reported] RFC6797 … Joe Hildebrand