Re: [kitten] Call for adoption on draft-whited-tls-channel-bindings-for-tls13

Simo Sorce <simo@redhat.com> Thu, 04 June 2020 18:37 UTC

Return-Path: <simo@redhat.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACBD3A0E37 for <kitten@ietfa.amsl.com>; Thu, 4 Jun 2020 11:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
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 qoObTaNvC9bb for <kitten@ietfa.amsl.com>; Thu, 4 Jun 2020 11:37:45 -0700 (PDT)
Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C98123A0E30 for <kitten@ietf.org>; Thu, 4 Jun 2020 11:37:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1591295863; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WsfEWhUWKdSfrM4KZ3NYsal0dMctakKoIcQaGDSIAok=; b=SHE+Blvj4El3TX4t5tBxw/Hxzgiiw8xTsNiCjcI7sdPqS9gk2Z5A89alIfSZeKIIvpUTef TIYcVEaA3tmP/IXZGfMrLLLftT+58Zmi5Zc40/YsMCb1xFQcLce/FgPItpbxsbSrfcls4T 9VZKUOf9BnBNtrQQ+b4iNLmw7FENLes=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-442-7azWY3LjOhK1WtS9pvu6lA-1; Thu, 04 Jun 2020 14:37:38 -0400
X-MC-Unique: 7azWY3LjOhK1WtS9pvu6lA-1
Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 78C15108BD11 for <kitten@ietf.org>; Thu, 4 Jun 2020 18:37:37 +0000 (UTC)
Received: from ovpn-114-18.phx2.redhat.com (ovpn-114-18.phx2.redhat.com [10.3.114.18]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 182387CCCE; Thu, 4 Jun 2020 18:37:36 +0000 (UTC)
Message-ID: <ead6071b1264f4eb83ccfba8800e98e97147d702.camel@redhat.com>
From: Simo Sorce <simo@redhat.com>
To: Robbie Harwood <rharwood@redhat.com>, kitten@ietf.org
Date: Thu, 04 Jun 2020 14:37:35 -0400
In-Reply-To: <jlgmu5ivkel.fsf@redhat.com>
References: <jlgmu5ivkel.fsf@redhat.com>
Organization: Red Hat, Inc.
Mime-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/l2FiYIRBLt8IVC2A0tfKhshfZ0I>
Subject: Re: [kitten] Call for adoption on draft-whited-tls-channel-bindings-for-tls13
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2020 18:37:47 -0000

On Thu, 2020-06-04 at 12:57 -0400, Robbie Harwood wrote:
> On behalf of Sam Whited, I'm issuing a call for adoption of
> https://datatracker.ietf.org/doc/draft-whited-tls-channel-bindings-for-tls13/
> 
> We've discussed this with the TLS working group, and consensus is that
> this work should take place in kitten (with consultation from TLS
> folks).
> 
> Besides Sam, I've seen interest expressed by Alexey,  Anyone else
> interested in this, or have objections?

Over time I've heard comments that the current tls-unique bindings are
not working out as initially expected. It would be nice to know if we
also plan to address those issues in this draft (or whether this draft
already avoid those).

Note that in practice, in the wild, I see that most implementations I
am exposed to are opting for tls-server-end-point, so it would be
important to know that this new bindings of type unique for TLS 1.3
will be usable and there are consumers wanting to use them.

Not pushing back just asking to address these questions in due course.

Simo.

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc