IETF Logo Mail Archive

Re: [Tcpcrypt] New version of the charter text

Joe Touch <touch@isi.edu> Wed, 23 April 2014 17:19 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 3F70F1A03BF for <tcpcrypt@ietfa.amsl.com>; Wed, 23 Apr 2014 10:19:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level:
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 DzNha0rcBhHc for <tcpcrypt@ietfa.amsl.com>; Wed, 23 Apr 2014 10:19:34 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 5641A1A021F for <tcpcrypt@ietf.org>; Wed, 23 Apr 2014 10:19:34 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s3NHIrYY002735 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 23 Apr 2014 10:18:54 -0700 (PDT)
Message-ID: <5357F5FD.4070103@isi.edu>
Date: Wed, 23 Apr 2014 10:18:53 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: marcelo bagnulo braun <marcelo@it.uc3m.es>, tcpcrypt@ietf.org
References: <53576572.5030805@it.uc3m.es> <5357F05C.3060507@isi.edu> <5357F2AD.9070307@it.uc3m.es>
In-Reply-To: <5357F2AD.9070307@it.uc3m.es>
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/WJloWC16a11WHlpiHEOnVWPqOX0
Subject: Re: [Tcpcrypt] New version of the charter text
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, 23 Apr 2014 17:19:35 -0000

On 4/23/2014 10:04 AM, marcelo bagnulo braun wrote:
...
>> > The WG will define the
>>> TCP extensions to perform an unauthenticated key exchange resulting in
>>> encryption
>>> without authentication.
>>
>> This implies in-band.
>
> Yes, the idea here is to provide a fully automatic mechanism, that
> people simply install and dont need to configure keys or anything.

That is orthogonal as to whether the key exchange is in-band.

Yes, a key exchange mechanism needs to be defined as part of the system, 
but not necessarily inside the connection being protected.

Joe

v2.23.0 | Report a Bug | By Email