IETF Logo Mail Archive

Re: [Tcpcrypt] v3 of the charter

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Wed, 30 April 2014 20:07 UTC

Return-Path: <dkg@fifthhorseman.net>
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 D6D051A097D for <tcpcrypt@ietfa.amsl.com>; Wed, 30 Apr 2014 13:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 mPQ-C-aumMtI for <tcpcrypt@ietfa.amsl.com>; Wed, 30 Apr 2014 13:07:13 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by ietfa.amsl.com (Postfix) with ESMTP id 67AC41A0972 for <tcpcrypt@ietf.org>; Wed, 30 Apr 2014 13:07:13 -0700 (PDT)
Received: from [10.70.10.85] (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id BFADDF984; Wed, 30 Apr 2014 16:07:09 -0400 (EDT)
Message-ID: <536157E1.2060202@fifthhorseman.net>
Date: Wed, 30 Apr 2014 16:06:57 -0400
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.3.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Marcelo Bagnulo <marcelo@it.uc3m.es>
References: <536099A0.30900@it.uc3m.es> <23862F2E-9D56-4651-9202-FC676D15720B@netapp.com> <07C2D017-9342-4742-990C-7D3BC795049F@netapp.com>
In-Reply-To: <07C2D017-9342-4742-990C-7D3BC795049F@netapp.com>
X-Enigmail-Version: 1.6+git0.20140323
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="6fs9jWn7rE1NxIT0hlMKO2j6D8IEMRXJ3"
Archived-At: http://mailarchive.ietf.org/arch/msg/tcpcrypt/_iQTZS8m4XF0epw8PWfcZbQMtdE
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 20:07:15 -0000

On 04/30/2014 04:27 AM, Eggert, Lars wrote:
> 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.

TCP is bidirectional, but the handshake is asymmetric: one party
listen()s and accept()s, and the other party connect()s.  These parties
are widely known as the "server" and "client", respectively.    I think
that's what the draft charter refers to.  What other names do you
recommend using for these roles?

	--dkg

v2.23.0 | Report a Bug | By Email