Re: [Curdle] Should we meet in Berlin?

"Jim Schaad" <ietf@augustcellars.com> Sat, 04 June 2016 02:46 UTC

Return-Path: <ietf@augustcellars.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 DE94F12D50F for <curdle@ietfa.amsl.com>; Fri, 3 Jun 2016 19:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 cbQDC0hlkJri for <curdle@ietfa.amsl.com>; Fri, 3 Jun 2016 19:46:09 -0700 (PDT)
Received: from smtp2.pacifier.net (smtp2.pacifier.net [64.255.237.172]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E19D612D0CE for <curdle@ietf.org>; Fri, 3 Jun 2016 19:46:09 -0700 (PDT)
Received: from hebrews (c-24-21-96-37.hsd1.or.comcast.net [24.21.96.37]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: schaad@nwlink.com) by smtp2.pacifier.net (Postfix) with ESMTPSA id 29EC12CA9D; Fri, 3 Jun 2016 19:46:09 -0700 (PDT)
From: Jim Schaad <ietf@augustcellars.com>
To: "'Salz, Rich'" <rsalz@akamai.com>, curdle@ietf.org
References: <1398fd6401e24d5a848ca8380db47e3b@usma1ex-dag1mb1.msg.corp.akamai.com>
In-Reply-To: <1398fd6401e24d5a848ca8380db47e3b@usma1ex-dag1mb1.msg.corp.akamai.com>
Date: Fri, 03 Jun 2016 19:46:08 -0700
Message-ID: <010201d1be0b$3f921130$beb63390$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQINZ1N6Ny+esemMd8e5uO3ehBKCf59hRrqQ
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/curdle/zcpyskZDuLcwnCEQOpxcN62lSPI>
Subject: Re: [Curdle] Should we meet in Berlin?
X-BeenThere: curdle@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 04 Jun 2016 02:46:12 -0000

Do we expect to see authors?  I believe that I am currently waiting for
comments on the pkix eddsa draft, the cms eddsa draft is stuck on this one.

I would really like to discuss how the ECDH and EdDSA algorithms are being
identified in PKIX, in part because I want it to match what is being done in
other groups.  So I would appreciate a meeting.

Jim


> -----Original Message-----
> From: Curdle [mailto:curdle-bounces@ietf.org] On Behalf Of Salz, Rich
> Sent: Friday, June 03, 2016 8:15 AM
> To: curdle@ietf.org
> Subject: [Curdle] Should we meet in Berlin?
> 
> We are trying to decide if it makes sense to meet at the next IETF in
Berlin.
> 
> There are several threads on the mailing list, and if a good set of them
will be
> present, we can perhaps come to some good initial consensus (to be
verified, as
> always, on the mailing list afterwards)  The threads we see include:
>                 Eddsa-signatures draft
>                 David Benjamin's "simplification" proposal
> 
> The deadline for scheduling is next Friday, so please speak up *now* if
you think
> we should ask for a one-hour slot.
> 
> 
> 
> --
> Senior Architect, Akamai Technologies
> IM: richsalz@jabber.at Twitter: RichSalz
> 
> 
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org
> https://www.ietf.org/mailman/listinfo/curdle