IETF Logo Mail Archive

Re: [kitten] TLS export for channel binding

Robbie Harwood <rharwood@redhat.com> Thu, 07 May 2020 16:04 UTC

Return-Path: <rharwood@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 33E963A0A10 for <kitten@ietfa.amsl.com>; Thu, 7 May 2020 09:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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_H2=-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 ZQvXDt6oc4j2 for <kitten@ietfa.amsl.com>; Thu, 7 May 2020 09:04:52 -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 D1E563A09FB for <kitten@ietf.org>; Thu, 7 May 2020 09:04:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1588867490; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eEjOOOJqf1SKANwJh6ZExxKteqsc2FsD7ny7IpXyGos=; b=Ggi4sZVwo4tdmI/NFx5rndW0McGPyVtmOapGDw9D6noCSoFoWuzIOO06IIfWZ3VYJlRBtM +hAtB89NyRMncwZbeo82MPSxA8ICf31JPvahz7SEEwhI2jh19ml/o5H30T5a8peedsuQ68 9tUJcz/lT/yGwOlu4rdPaH5pSTaRMPs=
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-440-IBX8xh4yONiv2Pnig44p8Q-1; Thu, 07 May 2020 12:04:45 -0400
X-MC-Unique: IBX8xh4yONiv2Pnig44p8Q-1
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id ECE44835B47; Thu, 7 May 2020 16:04:43 +0000 (UTC)
Received: from localhost (unknown [10.10.110.52]) by smtp.corp.redhat.com (Postfix) with ESMTP id A0F68690E6; Thu, 7 May 2020 16:04:43 +0000 (UTC)
From: Robbie Harwood <rharwood@redhat.com>
To: Sam Whited <sam@samwhited.com>, Alexey Melnikov <alexey.melnikov@isode.com>
Cc: KITTEN Working Group <kitten@ietf.org>
In-Reply-To: <80f32eca-9625-4c16-872f-5b0edb975483@www.fastmail.com>
References: <ddff592a-4774-43c7-8b23-392516d892ab@www.fastmail.com> <85d7fb9a-92f7-4b5a-bb20-bb9cfeeae67d@www.fastmail.com> <3d1e7257-004c-aabf-a259-6e532259c78e@isode.com> <80f32eca-9625-4c16-872f-5b0edb975483@www.fastmail.com>
Date: Thu, 07 May 2020 12:04:35 -0400
Message-ID: <jlg7dxn20ks.fsf@redhat.com>
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/fZ_VLJduqGBwIuaB81YMJulbBYo>
Subject: Re: [kitten] TLS export for channel binding
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, 07 May 2020 16:04:53 -0000

"Sam Whited" <sam@samwhited.com> writes:

> Sounds good. There's been more interest here, so would the next step be
> for me to change the draft from "draft-whited-tls" to "draft-whited-
> kitten" ? If so I'll move it over and reset the version to 0.
>
> Thanks for your help as I try to understand this process (again)!

(Chair/obnoxious process hat on) I think it would be best to have a
formalized call for adoption in kitten - that's a separate email with
"call for adoption" and the thing to adopt in the subject.  What I've
observed so far is interest in the document existing (and willingness to
work on it), but not specifically in kitten.  We'll let that simmer
about a week, and then if there's consensus, we can adopt.

(As a contributor) I've certainly no objections to adoption, but TLS is
not exactly my wheelhouse.

Thanks,
--Robbie

v2.23.0 | Report a Bug | By Email