This draft is a proposal for "opportunistic" encryption, that allows
using TLS in more circumstances. My interpretations is: I don't think
there's a consensus to make encryption universal, but this "lowers the
bar" for deploying or using TLS more widely.
-------- Original Message --------
Subject: Fwd: New Version Notification for
draft-nottingham-http2-encryption-02.txt
Resent-Date: Wed, 11 Dec 2013 04:20:10 +0000
Resent-From: [email protected]
Date: Wed, 11 Dec 2013 15:19:11 +1100
From: Mark Nottingham <[email protected]>
To: HTTP Working Group <[email protected]>
FYI.
Begin forwarded message:
From: [email protected]
Subject: New Version Notification for draft-nottingham-http2-encryption-02.txt
Date: 11 December 2013 3:18:55 pm AEDT
To: Mark Nottingham <[email protected]>
A new version of I-D, draft-nottingham-http2-encryption-02.txt
has been successfully submitted by Mark Nottingham and posted to the
IETF repository.
Filename: draft-nottingham-http2-encryption
Revision: 02
Title: Opportunistic Encryption for HTTP URIs
Creation date: 2013-12-11
Group: Individual Submission
Number of pages: 10
URL:
http://www.ietf.org/internet-drafts/draft-nottingham-http2-encryption-02.txt
Status:
http://datatracker.ietf.org/doc/draft-nottingham-http2-encryption
Htmlized: http://tools.ietf.org/html/draft-nottingham-http2-encryption-02
Diff:
http://www.ietf.org/rfcdiff?url2=draft-nottingham-http2-encryption-02
Abstract:
This document proposes two changes to HTTP/2.0; first, it suggests
using ALPN Protocol Identifies to identify the specific stack of
protocols in use, including TLS, and second, it proposes a way to
opportunistically encrypt HTTP/2.0 using TLS for HTTP URIs.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
--
Mark Nottingham http://www.mnot.net/
_______________________________________________
perpass mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/perpass
