IETF Logo Mail Archive

Re: [Curdle] Agenda / draft status

Jim Schaad <ietf@augustcellars.com> Tue, 22 November 2016 21:05 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 05D8F1297AA for <curdle@ietfa.amsl.com>; Tue, 22 Nov 2016 13:05:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.398
X-Spam-Level:
X-Spam-Status: No, score=-3.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.497, SPF_PASS=-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 vM5hU0uPsbQv for <curdle@ietfa.amsl.com>; Tue, 22 Nov 2016 13:05:38 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B30BE129518 for <curdle@ietf.org>; Tue, 22 Nov 2016 13:05:37 -0800 (PST)
Received: from hebrews (24.21.96.37) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 22 Nov 2016 13:23:00 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Nikos Mavrogiannopoulos' <nmav@redhat.com>, "'Salz, Rich'" <rsalz@akamai.com>, curdle@ietf.org
References: <1a84efb68dad4227b505a1501966c379@usma1ex-dag1mb1.msg.corp.akamai.com> <1479812914.31825.25.camel@redhat.com>
In-Reply-To: <1479812914.31825.25.camel@redhat.com>
Date: Tue, 22 Nov 2016 13:05:18 -0800
Message-ID: <08f601d24504$22921370$67b63a50$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQL7L2JQ82FfpJxOQ6jnPI3cdymY5wGYIwHpnoblTUA=
X-Originating-IP: [24.21.96.37]
Archived-At: <https://mailarchive.ietf.org/arch/msg/curdle/WY2R6pknLZviXDh8hDj2TOKjSpw>
Subject: Re: [Curdle] Agenda / draft status
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: Tue, 22 Nov 2016 21:05:40 -0000


> -----Original Message-----
> From: Curdle [mailto:curdle-bounces@ietf.org] On Behalf Of Nikos
> Mavrogiannopoulos
> Sent: Tuesday, November 22, 2016 3:09 AM
> To: Salz, Rich <rsalz@akamai.com>; curdle@ietf.org
> Subject: Re: [Curdle] Agenda / draft status
> 
> On Thu, 2016-11-17 at 12:08 +0000, Salz, Rich wrote:
> > We’ll go over the documents, hopefully move some along.  If you have
> > any feedback, or in particular a *blocking item* to bring up, please
> > reply here.
> 
> > draft-ietf-curdle-cms-eddsa-signatures-00 – ready for WGLC?
> >                 Use of EdDSA Signatures in the Cryptographic Message
> > draft-ietf-curdle-dnskey-eddsa-02
> >                 EdDSA for DNSSEC
> > draft-ietf-curdle-pkix-02 – ready for WGLC?
> >                 Algorithm Identifiers for Ed25519, Ed25519ph, Ed448,
> > Ed448ph, X25519 and X448 for use in the Internet X.509 Public Key
> > Infrastructure
> 
> Are there any implementations of the above drafts?

What do you consider to be an implementation?  

The certificate at the end of draft-ietf-curdle-pkix-02 is created by a program that was generated in part from the ASN.1 module.  The rest of the examples were also generated in the same way, but this is not a CA and I did not setup so that I could use the certificate in a browser or email program.

I have done a paper fill in the fields for the cms draft, which lead to several changes in the draft over the last week as we tried to get things correct, but I have not yet done the same thing in an ASN.1 structure and then encoded it using a program.  However, again this is not going to be like it is an Email client implementing S/MIME.  

Jim

> 
> regards,
> Nikos
> 
> _______________________________________________
> Curdle mailing list
> Curdle@ietf.org
> https://www.ietf.org/mailman/listinfo/curdle

v2.23.0 | Report a Bug | By Email