[perpass] Fwd: New Version Notification for draft-nottingham-http2-encryption-02.txt

Albert Lunde <atlunde@panix.com> Wed, 11 December 2013 19:31 UTC

Return-Path: <atlunde@panix.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F41E1AE195 for <perpass@ietfa.amsl.com>; Wed, 11 Dec 2013 11:31:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5jy0_7oJRDek for <perpass@ietfa.amsl.com>; Wed, 11 Dec 2013 11:31:29 -0800 (PST)
Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by ietfa.amsl.com (Postfix) with ESMTP id 14E3A1AE15B for <perpass@ietf.org>; Wed, 11 Dec 2013 11:31:28 -0800 (PST)
Received: from [192.168.15.3] (unknown [50.9.9.201]) by mailbackend.panix.com (Postfix) with ESMTP id E19DE35956; Wed, 11 Dec 2013 14:31:22 -0500 (EST)
Message-ID: <52A8BD80.4070603@panix.com>
Date: Wed, 11 Dec 2013 13:31:12 -0600
From: Albert Lunde <atlunde@panix.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: perpass <perpass@ietf.org>
References: <44FFE527-F884-4E29-BA29-167CF909F78D@mnot.net>
In-Reply-To: <44FFE527-F884-4E29-BA29-167CF909F78D@mnot.net>
X-Forwarded-Message-Id: <44FFE527-F884-4E29-BA29-167CF909F78D@mnot.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [perpass] Fwd: New Version Notification for draft-nottingham-http2-encryption-02.txt
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Dec 2013 19:31:31 -0000

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: ietf-http-wg@w3.org
Date: Wed, 11 Dec 2013 15:19:11 +1100
From: Mark Nottingham <mnot@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>

FYI.


Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-nottingham-http2-encryption-02.txt
> Date: 11 December 2013 3:18:55 pm AEDT
> To: Mark Nottingham <mnot@mnot.net>
>
>
> 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/