Re: Proposed Statement on "HTTPS everywhere for the IETF"

"Niels Dettenbach (Syndicat.com)" <nd@syndicat.com> Tue, 02 June 2015 07:09 UTC

Return-Path: <nd@syndicat.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1581AD04E for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2015 00:09:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level:
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 HoKM9xzy4hjO for <ietf@ietfa.amsl.com>; Tue, 2 Jun 2015 00:09:39 -0700 (PDT)
Received: from mail.syndicat.com (mail.syndicat.com [62.146.89.62]) (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 204761ACF09 for <ietf@ietf.org>; Tue, 2 Jun 2015 00:09:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=syndicat.com; s=x; h=Message-ID:To:Date:From:Subject:Content-Type:Content-Transfer-Encoding:MIME-Version:References:In-Reply-To; bh=u8pLJGu4coeq/1G7LKOZ6zof2DbzCOhh0Qnh1Vx/gC8=; b=LiJhykf7wjHrTVCxLx19zG+P1ZQ6zcdfVdyU8tXUeP5+gpNdbcCkugk7uxITC+YwujP5pKfH8SFXoRt0marfnX4AtkVP6RVvJMWFx2RCdNfrAE/zMYY78Po/zHwUqJBY83MgWh33A70Fgfk/J8PZ2Ey2J+Qe0A8+x0GTT6sQqHA=;
Received: from localhost.syndicat.com ([127.0.0.1] helo=localhost) by mail.syndicat.com with esmtp (Syndicat.com PostHamster 4.84) (envelope-from <nd@syndicat.com>) id 1YzgKF-000325-RL; Tue, 02 Jun 2015 09:09:27 +0200
X-Virus-Scanned: amavisd-new at syndicat.com
Received: from mail.syndicat.com ([127.0.0.1]) by localhost (mail.syndicat.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R5ieqcHNrviT; Tue, 2 Jun 2015 09:09:27 +0200 (CEST)
Received: from p50876cb7.dip0.t-ipconnect.de ([80.135.108.183] helo=android-2e6ac67d1822a7c9) by mail.syndicat.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-SHA:256) (Syndicat.com PostHamster 4.84) (envelope-from <nd@syndicat.com>) id 1YzgKF-0001BE-I9; Tue, 02 Jun 2015 09:09:27 +0200
In-Reply-To: <1F11D864-2532-4971-9771-F8037989A9BB@piuha.net>
References: <20150601164359.29999.35343.idtracker@ietfa.amsl.com> <CAL02cgRPFooA5fVFwvdprb3wPD+Y55pD+7RWjkACDv7T_TBW5Q@mail.gmail.com> <1472054.O9DP0qoCQf@gongo> <556CBCF5.3060402@alvestrand.no> <1C4D741C-89EA-4973-8536-D6A02EFD7624@syndicat.com> <556D4C38.6060704@alvestrand.no> <1F11D864-2532-4971-9771-F8037989A9BB@piuha.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF"
From: "Niels Dettenbach (Syndicat.com)" <nd@syndicat.com>
Date: Tue, 02 Jun 2015 09:09:25 +0200
To: Jari Arkko <jari.arkko@piuha.net>,IETF <ietf@ietf.org>
Message-ID: <70AA892E-C97F-4EEA-9BB8-829F654FA57F@syndicat.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/4mIpVoQB4Qnd3ceQHyvH1RIpLnE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 02 Jun 2015 07:09:40 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Am 2. Juni 2015 08:54:43 MESZ, schrieb Jari Arkko <jari.arkko@piuha.net>et>:
>We will (and have) of course participate the broader discussion and
>contribute technology that can help make the Internet more privacy
>friendly. But that is more about the various solutions we produce,
>such as improving efficiency of turning on crypto which HTTP/2 and
>TLS 1.3 help, or fixing bad algorithms or issues in protocols. Lets
>get to continuing that work!

full ack,
thanks
+1

Niels.
- ---
Niels Dettenbach
Syndicat IT & Internet
http://www.syndicat.com
-----BEGIN PGP SIGNATURE-----

iQJZBAEBCABDPBxOaWVscyBEZXR0ZW5iYWNoIChTeW5kaWNhdCBJVCAmIEludGVy
bmV0KSA8bmRAc3luZGljYXQuY29tPgUCVW1WnwAKCRANu1qIRZIqRNI9D/9vqppK
GP1TGmWLkfLrhmAjzbeqvwvHJPIEURDnBOGk99fY+Rg9IBH95MoZCylTilqALZAE
Qe2977W+aw9ZzlQE6ks2eqqMFyGOIM1TxMyWoKaCcX/Ogiy7s/nOMe9rrywWgPIf
cGMjQcapNQ2PSRIXzsnRsDTnRzj5EL4b/e7gey2yxHSBNOVgfJzp4wdXlnfoymwS
dmJVceOGwju3+B9uehasnQJYy48bgYhDZfASmhXkpDl4qpjamDLqYVSoa0NgN5MD
TtYj/XwVpYFEyYsq3/lPyjKIKWidfYj/kAi4YB+10nsuOudhHgMb/JfuagiLz7/4
ynOn0P1cLxpnTZVl3WmllK9MwpM3PbSAi4VFaDhviZK83RcZ+bCIpgQzm0HaTuKO
n6dkO6XjXkmrxcVVU7zKu+MEPmFezHFpvxiiiRZICXfm0Z+GNuaS+GAZIO2X2/07
byaXaZID/DFaZf4l/9PnJTqCQvCOfcZHBMQ4NyurLxpEpK6jAayLbhtGR7sMtVqf
T7vtJZVCSeCdqNzDroALc8BSvSYNzAIjR68tcJW8MIZWU15r8+/H/Y6n/6WKbo75
aKD45dA1wW3akMSeJZhHnm3lGBBGe2KFF8a5IWixSkgg7FpeMnIGdm6ImbBm5tI7
luFiqsmGOKHY6VQac/YllThe8O8XCsBQnyph0Q==
=36LM
-----END PGP SIGNATURE-----