[websec] [Editorial Errata Reported] RFC6797 (7935)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 13 May 2024 00:10 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9902C14F713 for <websec@ietfa.amsl.com>; Sun, 12 May 2024 17:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level:
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sKg1G_KuoGVQ for <websec@ietfa.amsl.com>; Sun, 12 May 2024 17:10:50 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4008BC14F6EA for <websec@ietf.org>; Sun, 12 May 2024 17:10:50 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 111F7AFB43; Sun, 12 May 2024 17:10:50 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240513001050.111F7AFB43@rfcpa.amsl.com>
Date: Sun, 12 May 2024 17:10:50 -0700
Message-ID-Hash: AYJJRXRLAQTDKZUIZCVZWZAG3PJBN5PE
X-Message-ID-Hash: AYJJRXRLAQTDKZUIZCVZWZAG3PJBN5PE
X-MailFrom: wwwrun@rfcpa.amsl.com
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: dawall.oswaldo1101@gmail.com, Jeff.Hodges@PayPal.com, collin.jackson@sv.cmu.edu, ietf@adambarth.com, websec@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [websec] [Editorial Errata Reported] RFC6797 (7935)
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/websec/ciD-p8QawjQ-rGfD4xbaKWCNr8g>
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/eid7935

--------------------------------------
Type: Editorial
Reported by: david oswaldo azamar alonso <dawall.oswaldo1101@gmail.com>

Section: 1

Original Text
-------------
RFC 6797          HTTP Strict Transport Security (HSTS)    November 2012


Corrected Text
--------------
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload



Notes
-----
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload

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