Re: [tcpinc] Consensus call: questions posed at the Berlin session

"Black, David" <david.black@emc.com> Wed, 03 August 2016 21:19 UTC

Return-Path: <david.black@emc.com>
X-Original-To: tcpinc@ietfa.amsl.com
Delivered-To: tcpinc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 368EE12D86B for <tcpinc@ietfa.amsl.com>; Wed, 3 Aug 2016 14:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level:
X-Spam-Status: No, score=-2.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=emc.com header.b=ahN377s1; dkim=pass (1024-bit key) header.d=emc.com header.b=pK0gYPN9
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 I-4hrJY_5V7X for <tcpinc@ietfa.amsl.com>; Wed, 3 Aug 2016 14:19:34 -0700 (PDT)
Received: from esa5.dell-outbound.iphmx.com (esa5.dell-outbound.iphmx.com [68.232.153.95]) (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 61FBD12D852 for <tcpinc@ietf.org>; Wed, 3 Aug 2016 14:19:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=emc.com; i=@emc.com; q=dns/txt; s=jan2013; t=1470259174; x=1501795174; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=Ez0ERr1MWeDtSM2Udy1TBxuKWpv8ukynMt/3arKVsSk=; b=ahN377s1lNF+o7QyLweNIfuRuE7UsPAQ9LKLPXsTRB8zxB9Vz5KfnIDb hM2VZJQlPsB1TuVMFx8IsN48KfxAZSuTo4IdV04yoA+nykgtwzzpMLTgD v1bVcGI3iAgSJUoiHGgjeh2LjxwbnbpTICpnLd65yRcTOHnlqZjgjZn1K s=;
Received: from mailuogwhop.emc.com ([168.159.213.141]) by esa5.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Aug 2016 02:19:24 +0500
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id u73LJNaN004698 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <tcpinc@ietf.org>; Wed, 3 Aug 2016 17:19:23 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com u73LJNaN004698
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1470259163; bh=oMf/8Zb0uF/a07QMx2RyXpe5NAs=; h=From:To:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=pK0gYPN9q+SyNuK5/Bw/qEG9nasza9weMk8FAG8m7EqwFU8z40Ucwk7PFEsnvxIOs 2U2scifRUeB0EoycC/eMq7RVVjOA81BqNvs5Jzydt0LA5+9na0ZrO7Ji7EEXMrqwwv GkbdVNhpQlPhXN0DrMp9JssGGNkcgo0KBxk73tEo=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com u73LJNaN004698
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd04.lss.emc.com (RSA Interceptor) for <tcpinc@ietf.org>; Wed, 3 Aug 2016 17:18:03 -0400
Received: from MXHUB305.corp.emc.com (MXHUB305.corp.emc.com [10.146.3.31]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id u73LJ1Cl032272 (version=TLSv1.2 cipher=AES128-SHA256 bits=128 verify=FAIL) for <tcpinc@ietf.org>; Wed, 3 Aug 2016 17:19:05 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB305.corp.emc.com ([10.146.3.31]) with mapi id 14.03.0266.001; Wed, 3 Aug 2016 17:16:03 -0400
From: "Black, David" <david.black@emc.com>
To: tcpinc <tcpinc@ietf.org>
Thread-Topic: [tcpinc] Consensus call: questions posed at the Berlin session
Thread-Index: AQHR5mfPeLMqYalIfkWx+JTzHrFEmaApmVmAgAAa8ACADgsx4A==
Date: Wed, 03 Aug 2016 21:16:02 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362F6238E8@MX307CL04.corp.emc.com>
References: <CAJU8_nUAvgOzOxrq03YOnZDBBKiqSQN_m53UTBdd4PC8MAF=wA@mail.gmail.com> <8737mxlm1o.fsf@alice.fifthhorseman.net> <CAJU8_nU28hDRoUWdM0wmkOrFt9HyxZgMngdUQ_X1qn4p_cmbjQ@mail.gmail.com>
In-Reply-To: <CAJU8_nU28hDRoUWdM0wmkOrFt9HyxZgMngdUQ_X1qn4p_cmbjQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.238.44.116]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949362F6238E8MX307CL04corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpinc/wH7xXL5FUfntkStSR5p1JKH6iDs>
Subject: Re: [tcpinc] Consensus call: questions posed at the Berlin session
X-BeenThere: tcpinc@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for adding encryption to TCP." <tcpinc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpinc>, <mailto:tcpinc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpinc/>
List-Post: <mailto:tcpinc@ietf.org>
List-Help: <mailto:tcpinc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpinc>, <mailto:tcpinc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 21:19:37 -0000

What Kyle said ;-).

Kyle’s original message reported the “sense of the room” in Berlin.   The purpose of that email was to give anyone who wasn’t in Berlin an opportunity to object - having seen no such objections, the chairs will proceed on the basis that this is the rough consensus of the tcpinc WG on these matters:

TCP-ENO

1. Eliminate the m bit for now and replace it with another z bit? (The intention is that the m bit will be defined by a later draft that makes use of it.) Y*/N
2. Eliminate length word for ENO suboptions (restricting all but the last suboption to 32 bytes of data)? Y*/N
3. Change "spec" to "TCPINC Encryption Protocol", and use "TEP" as acronym? Y*/N
4. Add RFC-5705-like key exporter mechanism? Y/N*

tcpcrypt

5. Encrypt frame lengths? Y/N*
** The next question was a bit muddied, so I have separated it into two questions:

6a. Add a separate API document for tcpcrypt? Y/N*
6b. Move API description in tcpcrypt draft to a separate section of the ENO API draft? Y*/N

FWIW, I have seen situations where mailing list discussion has overturned, or at least called into question, a meeting “sense of the room” conclusion.  It only takes one cogent technical objection on the list ...

Thanks, --David

From: Tcpinc [mailto:tcpinc-bounces@ietf.org] On Behalf Of Kyle Rose
Sent: Monday, July 25, 2016 2:05 PM
To: Daniel Kahn Gillmor
Cc: tcpinc
Subject: Re: [tcpinc] Consensus call: questions posed at the Berlin session

What I'm looking for is substantive dissent from what was decided in the room, such that rough consensus is called into question, and to save folks the effort of responding if they are in agreement with what was provisionally decided at the meeting.

But you (or anyone else) should absolutely feel free to post a response even if you were in attendance.

I think this is in the spirit of "conduct business on the mailing list" because the questions are still open until we've either confirmed or overturned rough consensus on each.
Thanks,
Kyle

On Mon, Jul 25, 2016 at 12:28 PM, Daniel Kahn Gillmor <dkg@fifthhorseman.net<mailto:dkg@fifthhorseman.net>> wrote:
On Mon 2016-07-25 07:29:23 -0400, Kyle Rose wrote:
> Here is a list of questions posed at the Berlin session, along with the
> rough consensus established among those in the room. Please respond to each
> by number if you were not in attendance and have an opinion, especially if
> that differs from the meeting consensus, indicated by a * after each
> question.

Does this mean that the chairs do not want e-mailed responses from
people who were in attendance?

     --dkg