[websec] RFC 6797 on HTTP Strict Transport Security (HSTS)

rfc-editor@rfc-editor.org Mon, 19 November 2012 23:47 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 B961721F86C7; Mon, 19 Nov 2012 15:47:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.933
X-Spam-Level:
X-Spam-Status: No, score=-101.933 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J2huqQ3FTjH1; Mon, 19 Nov 2012 15:47:37 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 18A8E21F86AD; Mon, 19 Nov 2012 15:47:37 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4E111B1E003; Mon, 19 Nov 2012 15:40:18 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121119234018.4E111B1E003@rfc-editor.org>
Date: Mon, 19 Nov 2012 15:40:18 -0800 (PST)
Cc: websec@ietf.org, rfc-editor@rfc-editor.org
Subject: [websec] RFC 6797 on HTTP Strict Transport Security (HSTS)
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/websec>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2012 23:47:37 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6797

        Title:      HTTP Strict Transport Security (HSTS) 
        Author:     J. Hodges, C. Jackson, A. Barth
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2012
        Mailbox:    Jeff.Hodges@PayPal.com, 
                    collin.jackson@sv.cmu.edu, 
                    ietf@adambarth.com
        Pages:      46
        Characters: 103554
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-websec-strict-transport-sec-14.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6797.txt

This specification defines a mechanism enabling web sites to declare
themselves accessible only via secure connections and/or for users to
be able to direct their user agent(s) to interact with given sites
only over secure connections.  This overall policy is referred to as
HTTP Strict Transport Security (HSTS).  The policy is declared by web
sites via the Strict-Transport-Security HTTP response header field
and/or by other means, such as user agent configuration, for example.
[STANDARDS-TRACK]

This document is a product of the Web Security Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC