IETF Logo Mail Archive

Re: [Curdle] IETF time slot / next step for CURDLE

Russ Housley <housley@vigilsec.com> Tue, 27 June 2017 13:58 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: curdle@ietfa.amsl.com
Delivered-To: curdle@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E883A129B2B for <curdle@ietfa.amsl.com>; Tue, 27 Jun 2017 06:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 HEOZpPgN5F9A for <curdle@ietfa.amsl.com>; Tue, 27 Jun 2017 06:58:14 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ABB3129B11 for <curdle@ietf.org>; Tue, 27 Jun 2017 06:58:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id DF72D3004D8 for <curdle@ietf.org>; Tue, 27 Jun 2017 09:58:13 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 2PBZZA5_orvn for <curdle@ietf.org>; Tue, 27 Jun 2017 09:58:12 -0400 (EDT)
Received: from [5.5.33.101] (vpn.snozzages.com [204.42.252.17]) by mail.smeinc.net (Postfix) with ESMTPSA id D20EC30026D; Tue, 27 Jun 2017 09:58:11 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <81B91E89-9FF9-46D7-A03A-B6AE16BF086C@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A5D6EF85-0F0D-4AE3-ACCE-AF99688DFBB0"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 27 Jun 2017 09:58:12 -0400
In-Reply-To: <2DD56D786E600F45AC6BDE7DA4E8A8C118C878F5@eusaamb107.ericsson.se>
Cc: curdle <curdle@ietf.org>
To: Daniel Migault <daniel.migault@ericsson.com>, Rich Salz <rsalz@akamai.com>
References: <2DD56D786E600F45AC6BDE7DA4E8A8C118C878F5@eusaamb107.ericsson.se>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/0dWxrKHB808h7ui-NPQsaVk00KM>
Subject: Re: [Curdle] IETF time slot / next step for CURDLE
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "List for discussion of potential new security area wg." <curdle.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/curdle>, <mailto:curdle-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/curdle/>
List-Post: <mailto:curdle@ietf.org>
List-Help: <mailto:curdle-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/curdle>, <mailto:curdle-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jun 2017 13:58:17 -0000

This is the status of my two documents:

 -- draft-ietf-curdle-cms-ecdh-new-curves — waiting to be put on the IESG telechat agenda

 -- draft-ietf-curdle-cms-eddsa-signatures — waiting for IETF Last Call

If the IESG or IETF Last Call raises an issue, then we can talk about it.  Nothing to say at this point.

Russ



> On Jun 27, 2017, at 8:46 AM, Daniel Migault <daniel.migault@ericsson.com> wrote:
> 
> Hi, 
>  
> We will have a short session at the next IETF. In order to prepare the session we would like to understand if anyone would request a slot for presenting. If so, please let us know.
>  
> As we are close to have all our document sent to the IESG, we would like to understand if you see any future work items. Please provide any thoughts on the mailing list.
>  
> Yours, 
> Daniel and Rich
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org <mailto:Curdle@ietf.org>
> https://www.ietf.org/mailman/listinfo/curdle <https://www.ietf.org/mailman/listinfo/curdle>

v2.23.0 | Report a Bug | By Email