IETF Logo Mail Archive

Re: [Secdispatch] Call for agenda items at IETF 103

Daniel Van Geest <Daniel.VanGeest@isara.com> Sun, 14 October 2018 02:55 UTC

Return-Path: <Daniel.VanGeest@isara.com>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCADF12D7F8 for <secdispatch@ietfa.amsl.com>; Sat, 13 Oct 2018 19:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 5na5w2gAUrxZ for <secdispatch@ietfa.amsl.com>; Sat, 13 Oct 2018 19:55:10 -0700 (PDT)
Received: from esa2.isaracorp.com (esa2.isaracorp.com [207.107.152.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D18F128CFD for <secdispatch@ietf.org>; Sat, 13 Oct 2018 19:55:10 -0700 (PDT)
Received: from unknown (HELO V0501WEXGPR01.isaracorp.com) ([10.5.8.20]) by ip2.isaracorp.com with ESMTP; 14 Oct 2018 02:55:08 +0000
Received: from V0501WEXGPR01.isaracorp.com (10.5.8.20) by V0501WEXGPR01.isaracorp.com (10.5.8.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1466.3; Sat, 13 Oct 2018 22:55:05 -0400
Received: from V0501WEXGPR01.isaracorp.com ([fe80::d802:5aec:db34:beba]) by V0501WEXGPR01.isaracorp.com ([fe80::d802:5aec:db34:beba%7]) with mapi id 15.01.1466.003; Sat, 13 Oct 2018 22:55:05 -0400
From: Daniel Van Geest <Daniel.VanGeest@isara.com>
To: Roman Danyliw <rdd@cert.org>, "secdispatch@ietf.org" <secdispatch@ietf.org>
Thread-Topic: [Secdispatch] Call for agenda items at IETF 103
Thread-Index: AQHUY2lPpSWqERz+f0S/p9XagRupKA==
Date: Sun, 14 Oct 2018 02:55:05 +0000
Message-ID: <7F95BA9C-08CE-4568-9EB1-7DD220C3FFBF@isara.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.5.52]
Content-Type: multipart/alternative; boundary="_000_7F95BA9C08CE45689EB17DD220C3FFBFisaracom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/LHsJ3tC8RvNGnRIQkEoThnkymEI>
Subject: Re: [Secdispatch] Call for agenda items at IETF 103
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Oct 2018 02:55:15 -0000

I’d like this to be added to the agenda:

https://tools.ietf.org/html/draft-vangeest-x509-hash-sigs-01

It was posted to the LAMPS mailing list (https://mailarchive.ietf.org/arch/browse/spasm/?gbt=1&index=5ZvLCxo3HTakvUZnv5KzkMzlqGE) with some discussion, and Russ suggested it should go through secdispatch, with a discussion at the end of the LAMPS session as well, if time allows.

The draft defines algorithm identifiers for HSS and XMSS(^MT) hash-based signature schemes for use in X.509 certificates.  Hash-based signatures are a well-studied class of quantum-safe signature algorithms which can be deployed now for roots of trust and code signing.  My employer has seen interest in these signature schemes for X.509 certificates and is implementing support for them.  I know of at least one other company doing the same and we’d like to standardize on a set of publicly accepted algorithm identifiers.

The desired next steps would be to have this added to the LAMPS charter.

Thanks,
Daniel

On 2018-10-03, 8:48 AM, "Secdispatch on behalf of Roman Danyliw" <secdispatch-bounces@ietf.org<mailto:secdispatch-bounces@ietf.org> on behalf of rdd@cert.org<mailto:rdd@cert.org>> wrote:

Hello!

SecDispatch will be meeting at IETF 103 (at a time yet to be determined).  If you would like time on the agenda, send your request to the mailing list.  Helpful items to include in your request (if known/applicable) are:

(1) pointers to a draft(s)
(2) pointers to ongoing/prior discussions
(3) pointers to implementations
(4) pointers to any other background materials
(5) summarizing prior engagement with existing WGs
(6) summarizing who would want to advance this work
(7) desired next steps

If needed, precedence will be given to documents that have demonstrated interest in the form of active drafts and list discussion.

If you have questions, please reach out to the co-chairs.

Regards,
Roman and Richard

_______________________________________________
Secdispatch mailing list
Secdispatch@ietf.org<mailto:Secdispatch@ietf.org>
https://www.ietf.org/mailman/listinfo/secdispatch

v2.23.0 | Report a Bug | By Email