Diff: draft-ietf-httpbis-http2-encryption-11.txt - draft-ietf-httpbis-http2-encryption-latest.txt

	draft-ietf-httpbis-http2-encryption-11.txt	draft-ietf-httpbis-http2-encryption-latest.txt

	HTTP Working Group M. Nottingham	HTTP Working Group M. Nottingham
	Internet-Draft	Internet-Draft
	Intended status: Experimental M. Thomson	Intended status: Experimental M. Thomson

	Expires: September 18, 2017 Mozilla	Expires: January 7, 2025 Mozilla
	March 17, 2017	July 6, 2018

	Opportunistic Security for HTTP/2	Opportunistic Security for HTTP/2

	draft-ietf-httpbis-http2-encryption-11	draft-ietf-httpbis-http2-encryption-latest

	Abstract	Abstract

	This document describes how "http" URIs can be accessed using	This document describes how "http" URIs can be accessed using
	Transport Layer Security (TLS) and HTTP/2 to mitigate pervasive	Transport Layer Security (TLS) and HTTP/2 to mitigate pervasive
	monitoring attacks. This mechanism not a replacement for "https"	monitoring attacks. This mechanism not a replacement for "https"
	URIs; it is vulnerable to active attacks.	URIs; it is vulnerable to active attacks.

	Status of This Memo	Status of This Memo

	This Internet-Draft is submitted in full conformance with the	This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.	provisions of BCP 78 and BCP 79.

	Internet-Drafts are working documents of the Internet Engineering	Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute	Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-	working documents as Internet-Drafts. The list of current Internet-

	Drafts is at http://datatracker.ietf.org/drafts/current/.	Drafts is at https://datatracker.ietf.org/drafts/current/.

	Internet-Drafts are draft documents valid for a maximum of six months	Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any	and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference	time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."	material or to cite them other than as "work in progress."


	This Internet-Draft will expire on September 18, 2017.	This Internet-Draft will expire on January 7, 2025.

	Copyright Notice	Copyright Notice


	Copyright (c) 2017 IETF Trust and the persons identified as the	Copyright (c) 2018 IETF Trust and the persons identified as the
	document authors. All rights reserved.	document authors. All rights reserved.

	This document is subject to BCP 78 and the IETF Trust's Legal	This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents	Provisions Relating to IETF Documents

	(http://trustee.ietf.org/license-info) in effect on the date of	(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents	publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect	carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must	to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of	include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as	the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.	described in the Simplified BSD License.

	Table of Contents	Table of Contents

	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2

	skipping to change at page 7, line 44 ¶	skipping to change at page 7, line 44 ¶
	describe policies across an entire origin, servers SHOULD NOT permit	describe policies across an entire origin, servers SHOULD NOT permit
	user content to set or modify the value of this header.	user content to set or modify the value of this header.

	5. References	5. References

	5.1. Normative References	5.1. Normative References

	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,	Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,	DOI 10.17487/RFC2119, March 1997,

	<http://www.rfc-editor.org/info/rfc2119>.	<https://www.rfc-editor.org/info/rfc2119>.

	[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,	[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,
	DOI 10.17487/RFC2818, May 2000,	DOI 10.17487/RFC2818, May 2000,

	<http://www.rfc-editor.org/info/rfc2818>.	<https://www.rfc-editor.org/info/rfc2818>.

	[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security	[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
	(TLS) Protocol Version 1.2", RFC 5246,	(TLS) Protocol Version 1.2", RFC 5246,
	DOI 10.17487/RFC5246, August 2008,	DOI 10.17487/RFC5246, August 2008,

	<http://www.rfc-editor.org/info/rfc5246>.	<https://www.rfc-editor.org/info/rfc5246>.

	[RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known	[RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known
	Uniform Resource Identifiers (URIs)", RFC 5785,	Uniform Resource Identifiers (URIs)", RFC 5785,
	DOI 10.17487/RFC5785, April 2010,	DOI 10.17487/RFC5785, April 2010,

	<http://www.rfc-editor.org/info/rfc5785>.	<https://www.rfc-editor.org/info/rfc5785>.

	[RFC6454] Barth, A., "The Web Origin Concept", RFC 6454,	[RFC6454] Barth, A., "The Web Origin Concept", RFC 6454,
	DOI 10.17487/RFC6454, December 2011,	DOI 10.17487/RFC6454, December 2011,

	<http://www.rfc-editor.org/info/rfc6454>.	<https://www.rfc-editor.org/info/rfc6454>.

	[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data	[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
	Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March	Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March

	2014, <http://www.rfc-editor.org/info/rfc7159>.	2014, <https://www.rfc-editor.org/info/rfc7159>.

	[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer	[RFC7230] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP/1.1): Message Syntax and Routing",	Protocol (HTTP/1.1): Message Syntax and Routing",
	RFC 7230, DOI 10.17487/RFC7230, June 2014,	RFC 7230, DOI 10.17487/RFC7230, June 2014,

	<http://www.rfc-editor.org/info/rfc7230>.	<https://www.rfc-editor.org/info/rfc7230>.

	[RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer	[RFC7232] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP/1.1): Conditional Requests", RFC 7232,	Protocol (HTTP/1.1): Conditional Requests", RFC 7232,
	DOI 10.17487/RFC7232, June 2014,	DOI 10.17487/RFC7232, June 2014,

	<http://www.rfc-editor.org/info/rfc7232>.	<https://www.rfc-editor.org/info/rfc7232>.

	[RFC7234] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,	[RFC7234] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",	Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
	RFC 7234, DOI 10.17487/RFC7234, June 2014,	RFC 7234, DOI 10.17487/RFC7234, June 2014,

	<http://www.rfc-editor.org/info/rfc7234>.	<https://www.rfc-editor.org/info/rfc7234>.

	[RFC7540] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext	[RFC7540] Belshe, M., Peon, R., and M. Thomson, Ed., "Hypertext
	Transfer Protocol Version 2 (HTTP/2)", RFC 7540,	Transfer Protocol Version 2 (HTTP/2)", RFC 7540,
	DOI 10.17487/RFC7540, May 2015,	DOI 10.17487/RFC7540, May 2015,

	<http://www.rfc-editor.org/info/rfc7540>.	<https://www.rfc-editor.org/info/rfc7540>.

	[RFC7838] Nottingham, M., McManus, P., and J. Reschke, "HTTP	[RFC7838] Nottingham, M., McManus, P., and J. Reschke, "HTTP
	Alternative Services", RFC 7838, DOI 10.17487/RFC7838,	Alternative Services", RFC 7838, DOI 10.17487/RFC7838,

	April 2016, <http://www.rfc-editor.org/info/rfc7838>.	April 2016, <https://www.rfc-editor.org/info/rfc7838>.

	5.2. Informative References	5.2. Informative References

	[RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an	[RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an
	Attack", BCP 188, RFC 7258, DOI 10.17487/RFC7258, May	Attack", BCP 188, RFC 7258, DOI 10.17487/RFC7258, May

	2014, <http://www.rfc-editor.org/info/rfc7258>.	2014, <https://www.rfc-editor.org/info/rfc7258>.

	[RFC7435] Dukhovni, V., "Opportunistic Security: Some Protection	[RFC7435] Dukhovni, V., "Opportunistic Security: Some Protection
	Most of the Time", RFC 7435, DOI 10.17487/RFC7435,	Most of the Time", RFC 7435, DOI 10.17487/RFC7435,

	December 2014, <http://www.rfc-editor.org/info/rfc7435>.	December 2014, <https://www.rfc-editor.org/info/rfc7435>.

	[RFC7469] Evans, C., Palmer, C., and R. Sleevi, "Public Key Pinning	[RFC7469] Evans, C., Palmer, C., and R. Sleevi, "Public Key Pinning
	Extension for HTTP", RFC 7469, DOI 10.17487/RFC7469, April	Extension for HTTP", RFC 7469, DOI 10.17487/RFC7469, April

	2015, <http://www.rfc-editor.org/info/rfc7469>.	2015, <https://www.rfc-editor.org/info/rfc7469>.

	[W3C.CR-mixed-content-20160802]	[W3C.CR-mixed-content-20160802]

	West, M., "Mixed Content", World Wide Web Consortium CR	West, M., Ed., "Mixed Content", W3C CR CR-mixed-content-
	CR-mixed-content-20160802, August 2016,	20160802, W3C CR-mixed-content-20160802, August 2016,
	<https://www.w3.org/TR/2016/CR-mixed-content-20160802>.	<https://www.w3.org/TR/2016/CR-mixed-content-20160802/>.

	Appendix A. Acknowledgements	Appendix A. Acknowledgements

	Mike Bishop contributed significant text to this document.	Mike Bishop contributed significant text to this document.

	Thanks to Patrick McManus, Stefan Eissing, Eliot Lear, Stephen	Thanks to Patrick McManus, Stefan Eissing, Eliot Lear, Stephen
	Farrell, Guy Podjarny, Stephen Ludin, Erik Nygren, Paul Hoffman, Adam	Farrell, Guy Podjarny, Stephen Ludin, Erik Nygren, Paul Hoffman, Adam
	Langley, Eric Rescorla, Julian Reschke, Kari Hurtta, and Richard	Langley, Eric Rescorla, Julian Reschke, Kari Hurtta, and Richard
	Barnes for their feedback and suggestions.	Barnes for their feedback and suggestions.


End of changes. 21 change blocks.
	24 lines changed or deleted	24 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/