IETF Logo Mail Archive

Re: [Tcpcrypt] v3 of the charter

Joe Touch <touch@isi.edu> Wed, 30 April 2014 20:17 UTC

Return-Path: <touch@isi.edu>
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 C53B41A884D for <tcpcrypt@ietfa.amsl.com>; Wed, 30 Apr 2014 13:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] 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 5dQEQs2J05Eo for <tcpcrypt@ietfa.amsl.com>; Wed, 30 Apr 2014 13:17:29 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id E9D5A1A097D for <tcpcrypt@ietf.org>; Wed, 30 Apr 2014 13:17:28 -0700 (PDT)
Received: from [128.9.184.196] ([128.9.184.196]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s3UKH4R3023871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 30 Apr 2014 13:17:05 -0700 (PDT)
Message-ID: <53615A40.9050903@isi.edu>
Date: Wed, 30 Apr 2014 13:17:04 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, "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> <536157E1.2060202@fifthhorseman.net>
In-Reply-To: <536157E1.2060202@fifthhorseman.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/tcpcrypt/F1QSpRPkhuRxy99VS6LiRILTMAs
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:17:29 -0000

On 4/30/2014 1:06 PM, Daniel Kahn Gillmor wrote:
> 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.

TCP supports simultaneous open too. In which case, who's the client and 
who's the server?

Joe

v2.23.0 | Report a Bug | By Email