Re: [hrpc] [rfc-editor@rfc-editor.org: RFC 8164 on Opportunistic Security for HTTP/2]

Niels ten Oever <niels@article19.org> Tue, 16 May 2017 14:41 UTC

Return-Path: <niels@article19.org>
X-Original-To: hrpc@ietfa.amsl.com
Delivered-To: hrpc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C17B129AB6 for <hrpc@ietfa.amsl.com>; Tue, 16 May 2017 07:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 kg42h2cPzA5S for <hrpc@ietfa.amsl.com>; Tue, 16 May 2017 07:41:47 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08C98129C2A for <hrpc@irtf.org>; Tue, 16 May 2017 07:37:04 -0700 (PDT)
Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <niels@article19.org>) id 1dAdaw-0005uD-HS for hrpc@irtf.org; Tue, 16 May 2017 16:37:02 +0200
To: hrpc@irtf.org
References: <20170516141003.ubdlqsjpnpbx6h7z@nic.fr>
From: Niels ten Oever <niels@article19.org>
Message-ID: <c840b038-ce2e-727a-2a3f-f4d38c5cafab@article19.org>
Date: Tue, 16 May 2017 16:37:01 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170516141003.ubdlqsjpnpbx6h7z@nic.fr>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="NUJ8v8rcApL6ueCsQIerQt7l6RvipL3d0"
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: f4db13d1ab50da585241c80c5e12767b
Archived-At: <https://mailarchive.ietf.org/arch/msg/hrpc/CPr5hzVfVy6KIVVkhVtFll8CE3g>
Subject: Re: [hrpc] [rfc-editor@rfc-editor.org: RFC 8164 on Opportunistic Security for HTTP/2]
X-BeenThere: hrpc@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "niels@article19.org" <hrpc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hrpc>, <mailto:hrpc-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hrpc/>
List-Post: <mailto:hrpc@irtf.org>
List-Help: <mailto:hrpc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hrpc>, <mailto:hrpc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 May 2017 14:41:49 -0000

Hi Stephane,

Do you have more background on why it was postponed then, and OK to pass
now?

Cheers,

Niels

Niels ten Oever
Head of Digital

Article 19
www.article19.org

PGP fingerprint    2458 0B70 5C4A FD8A 9488
                   643A 0ED8 3F3A 468A C8B3

On 05/16/2017 04:10 PM, Stephane Bortzmeyer wrote:
> This was a very hot discussion at the IETF 2-3 years ago during the
> development of HTTP/2: should we have mandatory encryption,
> opportunistic (best effort) encryption or what? At this time,
> opportunistic encryption was postponed and the RFC is now published.
> 
> 
> 
> _______________________________________________
> hrpc mailing list
> hrpc@irtf.org
> https://www.irtf.org/mailman/listinfo/hrpc
>