Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make the intro to http2-encryption clearer about the scope #301

Merged
merged 1 commit into from Feb 21, 2017
Merged

Make the intro to http2-encryption clearer about the scope #301

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
20 changes: 11 additions & 9 deletions draft-ietf-httpbis-http2-encryption.md
View file
Open in desktop
Expand Up @@ -48,7 +48,7 @@ informative:

--- abstract

This document describes how `http` URIs can be accessed using Transport Layer Security (TLS) to
This document describes how `http` URIs can be accessed using Transport Layer Security (TLS) in HTTP/2 to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in -> and

mitigate pervasive monitoring attacks.

--- note_Note_to_Readers
Expand All @@ -64,16 +64,18 @@ for this draft can be found at <https://github.com/httpwg/http-extensions/labels
# Introduction

This document describes a use of HTTP Alternative Services {{RFC7838}} to decouple
the URI scheme from the use and configuration of underlying encryption, allowing a `http` URI
{{RFC7230}} to be accessed using Transport Layer Security (TLS) {{RFC5246}} opportunistically.

Serving `https` URIs requires avoiding Mixed Content {{W3C.CR-mixed-content-20160802}}, which is
problematic in many deployments. This document describes a usage model whereby sites can serve
`http` URIs over TLS, thereby avoiding these issues, while still providing protection against
the URI scheme from the use and configuration of underlying encryption.
It allows HTTP/2 {{RFC7540}} to access a `http` URI
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is worded oddly. Suggest "It allows a http URI to be accessed using HTTP/2 {{RFC7230}} and Transport Layer..."

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"a" or "an" for "http"?

{{RFC7230}} using Transport Layer Security (TLS) {{RFC5246}}
with Opportunistic Security {{RFC7435}}.

This document describes a usage model whereby sites can serve
`http` URIs over TLS, thereby avoiding the problem of serving
Mixed Content (describe in {{W3C.CR-mixed-content-20160802}}) while still providing protection against
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

described

passive attacks.

Opportunistic Security {{RFC7435}} does not provide the same guarantees as using TLS with `https`
URIs; it is vulnerable to active attacks, and does not change the security context of the
Opportunistic Security does not provide the same guarantees as using TLS with `https`
URIs; Opportunistic Security is vulnerable to active attacks, and does not change the security context of the
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this would read more clearly if it were just "...URIs, because it is vulnerable..."

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WFM

connection. Normally, users will not be able to tell that it is in use (i.e., there will be no
"lock icon").

Expand Down