Re: [TLS] RFC4492bis next steps
Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 16 March 2017 12:55 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DAAE129496 for <tls@ietfa.amsl.com>; Thu, 16 Mar 2017 05:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level:
X-Spam-Status: No, score=-4.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 x9xIfmCefITP for <tls@ietfa.amsl.com>; Thu, 16 Mar 2017 05:55:41 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 725A412948D for <tls@ietf.org>; Thu, 16 Mar 2017 05:55:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id F36A2BE2F; Thu, 16 Mar 2017 12:55:38 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bA15lSAseQ8P; Thu, 16 Mar 2017 12:55:37 +0000 (GMT)
Received: from [10.87.48.75] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 607A2BE3E; Thu, 16 Mar 2017 12:55:37 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1489668937; bh=dPJy4Mz8otzXtGElEqRqZ1d5H6rArg1V6BL1mhYKPlI=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=CJquOYt3aCKqWEpU2nUdM+nMYyW4mt8xDMVAhhxJMomQcSnCK5J2klrresplr7bAN GtCCKxLA0zK9OCQ0QPT+1nYJ2PVPco9ZHCT8FwZksY/3xWxtmowUu4VqDvrGNgNHWb n4HBDzc4XANyYfvjI581cbTseB2gTQIKvQzZx9XM=
To: Yoav Nir <ynir.ietf@gmail.com>
References: <FB8927B7-85FC-4FA1-8258-C5FC0D3C4AD1@gmail.com> <44eec6fe-7f9f-ae73-558a-74e20c8029e4@cs.tcd.ie> <CFA4608F-D17C-423C-A11B-E971C493FA98@gmail.com>
Cc: "tls@ietf.org list" <tls@ietf.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <206ffc40-8ae6-9b46-44c5-1470c52a21c3@cs.tcd.ie>
Date: Thu, 16 Mar 2017 12:55:36 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CFA4608F-D17C-423C-A11B-E971C493FA98@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="jcwvFwDSlpucEmHJok8vswOlcBTlfqe4D"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/M6NKrGddXtTpH3eVe2TG64DS1gs>
Subject: Re: [TLS] RFC4492bis next steps
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Mar 2017 12:55:43 -0000
On 16/03/17 12:52, Yoav Nir wrote: > OK, so I’ll merge the PRs tomorrow morning and start working on ekr’s > comments over the weekend. Excellent, thanks, S > > Yoav > >> On 16 Mar 2017, at 14:41, Stephen Farrell >> <stephen.farrell@cs.tcd.ie> wrote: >> >> >> >> On 16/03/17 06:20, Yoav Nir wrote: >>> Hopefully I’ll be all done and ready to submit a new version as >>> soon as submissions are re-opened on the 27th. >> >> If we're ready sooner, I'd prefer try get that out of the way next >> week. I can tell to secretariat to accept updates for this draft. >> (I'll likely do that after the IESG telechat this afternoon) >> >> Cheers, S. >> >
- [TLS] RFC4492bis next steps Yoav Nir
- Re: [TLS] RFC4492bis next steps Sean Turner
- Re: [TLS] RFC4492bis next steps Stephen Farrell
- Re: [TLS] RFC4492bis next steps Yoav Nir
- Re: [TLS] RFC4492bis next steps Stephen Farrell