IETF Logo Mail Archive

Re: [IAB] IAB report to the community for IETF 103

Randy Bush <randy@psg.com> Wed, 14 November 2018 09:42 UTC

Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AFD312D4E6; Wed, 14 Nov 2018 01:42:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 Mqphd1HWdRsD; Wed, 14 Nov 2018 01:42:31 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D4661293FB; Wed, 14 Nov 2018 01:42:30 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1gMrgp-00085G-Cd; Wed, 14 Nov 2018 09:42:27 +0000
Date: Wed, 14 Nov 2018 18:42:25 +0900
Message-ID: <m2pnv8xaf2.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: IAB <iab@iab.org>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: [IAB] IAB report to the community for IETF 103
In-Reply-To: <CABkgnnXuePQLxfp_ussLG31y0WessCVgA7xzG3ZbBGex_8u5bw@mail.gmail.com>
References: <CA+9kkMDEP-JKDwcwRMT7QUs-yQi+PsuKo22mFZxB6yKTEqTuSQ@mail.gmail.com> <6.2.5.6.2.20181111093128.0bd80f60@elandnews.com> <CA+9kkMAcJSixn2-S-OwK0tojyJLQZ=mrhr4NT7OM9+ji0vb=GA@mail.gmail.com> <CABkgnnXuePQLxfp_ussLG31y0WessCVgA7xzG3ZbBGex_8u5bw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="ISO-2022-JP"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kPgD2xwZ-6zHXgwrJtXcBQ9dmDs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2018 09:42:34 -0000

tony arciery:

It takes an awful lot of doublethink to take TLS 1.3, remove forward
secrecy, introduce a deliberate self-MitM capability, and call the
result a “security protocol”. Call me crazy but TLS’s one job is
avoiding decryption by third parties

v2.23.0 | Report a Bug | By Email