This errata can be rejected. rfc6797 relies on the bespoke BNF from 2616, which uses '|' instead of '/'.
— Joe Hildebrand > On Nov 22, 2024, at 1:57 PM, RFC Errata System <[email protected]> > wrote: > > 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 <[email protected]> > > 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 mailing list -- [email protected] To unsubscribe send an email to [email protected]
