Re: [Tcpcrypt] v3 of the charter

"Eggert, Lars" <lars@netapp.com> Wed, 30 April 2014 08:28 UTC

Return-Path: <lars@netapp.com>
X-Original-To: tcpcrypt@ietfa.amsl.com
Delivered-To: tcpcrypt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7881A6F1F for <tcpcrypt@ietfa.amsl.com>; Wed, 30 Apr 2014 01:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.553
X-Spam-Level:
X-Spam-Status: No, score=-7.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 sIrTGPPdQfYg for <tcpcrypt@ietfa.amsl.com>; Wed, 30 Apr 2014 01:27:56 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id B9B671A6F14 for <tcpcrypt@ietf.org>; Wed, 30 Apr 2014 01:27:56 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.97,956,1389772800"; d="asc'?scan'208"; a="161230398"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx12-out.netapp.com with ESMTP; 30 Apr 2014 01:27:55 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.246]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Wed, 30 Apr 2014 01:27:55 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Marcelo Bagnulo <marcelo@it.uc3m.es>
Thread-Topic: [Tcpcrypt] v3 of the charter
Thread-Index: AQHPZD5fGlguXnvFmU2xabuFLE2C2ZsqRtmAgAACKYA=
Date: Wed, 30 Apr 2014 08:27:54 +0000
Message-ID: <07C2D017-9342-4742-990C-7D3BC795049F@netapp.com>
References: <536099A0.30900@it.uc3m.es> <23862F2E-9D56-4651-9202-FC676D15720B@netapp.com>
In-Reply-To: <23862F2E-9D56-4651-9202-FC676D15720B@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.122.105.11]
Content-Type: multipart/signed; boundary="Apple-Mail=_E6EE952E-96A5-4007-B907-7589A4EEDCAA"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tcpcrypt/NyxiKgZod8vllNxkRnJboYLakoY
Cc: "tcpcrypt@ietf.org" <tcpcrypt@ietf.org>
Subject: Re: [Tcpcrypt] v3 of the charter
X-BeenThere: tcpcrypt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for adding encryption to TCP." <tcpcrypt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpcrypt>, <mailto:tcpcrypt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpcrypt/>
List-Post: <mailto:tcpcrypt@ietf.org>
List-Help: <mailto:tcpcrypt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpcrypt>, <mailto:tcpcrypt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 08:28:00 -0000

Oh, forgot one more overall issue: The charter talks about clients and servers a lot. While that's convenient, because it matches the communication flow of the app layer protocols on top of TCP, and NATs now demand a directionality of connection establishment, those terms don't actually have a lot of meaning for TCP, which is a bidirectional protocol. Suggest to rephrase.

Lars