Re: [arch-d] Call for Comment: <draft-trammell-wire-image-04> (The Wire Image of a Network Protocol)

John C Klensin <john-ietf@jck.com> Sat, 15 September 2018 01:05 UTC

Return-Path: <john-ietf@jck.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 96720126F72; Fri, 14 Sep 2018 18:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 sxf_iXK42RW7; Fri, 14 Sep 2018 18:05:13 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B23C912008A; Fri, 14 Sep 2018 18:05:13 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1g0z1F-000Hhv-Ek; Fri, 14 Sep 2018 21:05:05 -0400
Date: Fri, 14 Sep 2018 21:04:58 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
cc: IAB <iab@iab.org>, architecture-discuss@ietf.org, IETF-Discussion <ietf@ietf.org>
Subject: Re: [arch-d] Call for Comment: <draft-trammell-wire-image-04> (The Wire Image of a Network Protocol)
Message-ID: <B6B4A91F91E91993931707C6@PSB>
In-Reply-To: <m236ubsn8p.wl-randy@psg.com>
References: <153619287953.19753.5995314701986579146.idtracker@ietfa.amsl.com> <8b52dce5-1ee4-b40b-e1ba-e7c9b241dd82@cs.tcd.ie> <6080E931-DEB6-48C8-BEB1-96A69112F67A@trammell.ch> <255e0d12-fbce-1448-90db-daadc4e39c3f@cs.tcd.ie> <m236ubsn8p.wl-randy@psg.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dPLPifluqoxQU8NvuvYtInqSuJE>
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: Sat, 15 Sep 2018 01:05:16 -0000


--On Friday, September 14, 2018 15:55 -0700 Randy Bush
<randy@psg.com>; wrote:

> i am less comfortable with hiding this critical discussion off
> in some obscure mailing list.  we already have enough problems
> with closed iab discussions.

+1 

> but making clear that strong
> encryption is here to stay and that is a good thing is
> principle.

Yes, I certainly hope so.   However, I also think we need to be
aware that, while I hope history doesn't repeat itself in this
case, the historical trend ("historical" = centuries, not
Internet time) has been that, if whatever passes for strong
encryption at the time starts becoming sufficiently intrusive,
governments have often responded by banning encryption entirely
and trying to enforce those bans.   That potentially provides a
new way to fragment the Internet with a boundary between those
who use strong encryption and those who are put at considerable
risk by trying to do so.   I'm still prepared to believe that
strong encryption is a good thing in principle, but we should
also all be careful what we wish for.

   Cassandra