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

"Brian Trammell (IETF)" <ietf@trammell.ch> Sat, 15 September 2018 08:49 UTC

Return-Path: <ietf@trammell.ch>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97A381271FF; Sat, 15 Sep 2018 01:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=unavailable 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 w0G08LV8KWBX; Sat, 15 Sep 2018 01:49:45 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5898130E14; Sat, 15 Sep 2018 01:49:44 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 0A4B634119D; Sat, 15 Sep 2018 10:49:42 +0200 (CEST)
X-Iway-Path: 0
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/14501.9021); Sat, 15 Sep 2018 10:49:41 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Sat, 15 Sep 2018 10:49:41 +0200 (CEST)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.78]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 67349976; Sat, 15 Sep 2018 10:49:41 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail-32D3C32E-B08C-45C7-90E5-BDB056470048"
Mime-Version: 1.0 (1.0)
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <m236ubsn8p.wl-randy@psg.com>
Date: Sat, 15 Sep 2018 10:49:40 +0200
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IAB <iab@iab.org>, architecture-discuss@ietf.org, IETF-Discussion <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <3836209E-60C5-4F55-A5AB-8D9EB6E4B935@trammell.ch>
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>
To: Randy Bush <randy@psg.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/i0wVdH_gpA4N4wwKN0wjLVPbneQ>
Subject: Re: [arch-d] Call for Comment: <draft-trammell-wire-image-04> (The Wire Image of a Network Protocol)
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Sep 2018 08:49:47 -0000

> On 15 Sep 2018, at 00:55, Randy Bush <randy@psg.com> wrote:

>> Sure. But isn't it the move to encrypt more that's motivating this and
>> other drafts? If so, then I think ack'ing that there are valid and
>> pressing motivations for that move is needed. If there are other
>> motivations, those aren't clear to me at least and therefore probably
>> also deserve a mention.
>> We've seen (with Kathleen and Al's draft),
>> that some people (not the authors here) do quote drafts like this when
>> arguing against more confidentiality, so I think this draft, and
>> similar ones, really ought say that we do need more use of
>> confidentiality, and not just assume that that's accepted by all
>> readers. Yes, that only needs to be a sentence or two and some
>> reference, but I do think it needs to be there.
> 
> extremely much so, tyvm.  to me, this is *the* critical issue here.

Ok. The motivation for this draft is indeed he increasing deployment and coverage of encryption down the stack, which we take as a given. A few sentences to make this context clear could be useful.

> the other issues we can ietf to death, like trains to maastricht or
> visas to bangkok.  but making clear that strong encryption is here to
> stay and that is a good thing is principle.

The whole point of this line of work is to define a solution space for the (technical) problems that arise when “strong encryption is here to stay”, and follows from its statement that weaning various communities off an addiction to clear text is an important part of moving the Internet to a default-confidential stance (see https://www.iab.org/documents/correspondence-reports-documents/2014-2/iab-statement-on-internet-confidentiality/). 

Cheers,

Brian