The following errata report has been submitted for RFC6797, "HTTP Strict Transport Security (HSTS)".
-------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5204 -------------------------------------- Type: Technical Reported by: Nick Dilßner <[email protected]> Section: 6.1.2 Original Text ------------- includeSubDomains Corrected Text -------------- include-sub-domains or includesubdomains Notes ----- - In Section 6.1 the Strict-Transport-Security is defined as follows: Strict-Transport-Security = "Strict-Transport-Security" ":" [ directive ] *( ";" [ directive ] ) - valueless Directive "includeSubDomains" is defined as a optional directive - a directive is definied as followed: directive = directive-name [ "=" directive-value ] - so "includeSubDomains" is only a directive-name which is defined as "token" - according to "[RFC2616], Section 2.2" a token is any octet from 0 - 127 except CTL's (octets 0 - 31 + 127) and separators which NOT exclude '-' (octet 45) So all Fine? Yes, BUT at [RFC6797], Section 6.1 the "overall reuqirements for directives", Rule 3 defines: 3. Directive names are case-insensitive. And there is no other specification in Section 6.1.2 or has a IANA policy definition [RFC5226] like it is defined for additionals. - That means the "directive-name" includeSubDomains is "case-insensitive"! The "case-sensitive" camelized directive-name is misleading, because of many other definitions with "-", like seen in all examples or in Header Field itself. - to aware the clear understanding the "directive definition" in section 6.1.2 and ALL occurences needs to be renamend. the minimum of renaming is "includesubdomains" OR "INCLUDESUBDOMAINS", but this is not readable anymore. - So it should be renamed like other valuless directives for Example the "schemes-source's" directives at "Content-Security-Policy", which means: "include-sub-domains" Best Regards Nick Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can 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 Area : Applications Stream : IETF Verifying Party : IESG _______________________________________________ websec mailing list [email protected] https://www.ietf.org/mailman/listinfo/websec
