IETF Logo Mail Archive

Re: [CFRG] XDR in RFC8391

stefan@gazdag.de Thu, 03 December 2020 08:34 UTC

Return-Path: <stefan@gazdag.de>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E644E3A0B18 for <cfrg@ietfa.amsl.com>; Thu, 3 Dec 2020 00:34:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NONE=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 2CA5a3mAKUTP for <cfrg@ietfa.amsl.com>; Thu, 3 Dec 2020 00:34:29 -0800 (PST)
Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de [80.67.31.97]) (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 8E3AB3A0B23 for <cfrg@irtf.org>; Thu, 3 Dec 2020 00:34:29 -0800 (PST)
Received: from [134.119.228.3] (helo=webmailfront-cgn01.ispgateway.de) by smtprelay05.ispgateway.de with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.92.3) (envelope-from <stefan@gazdag.de>) id 1kkk4H-00028j-HS; Thu, 03 Dec 2020 09:34:25 +0100
Received: from gg-0.genua.de (gg-0.genua.de [80.154.94.10]) by webmail.df.eu (Horde Framework) with HTTP; Thu, 03 Dec 2020 09:34:25 +0100
Date: Thu, 03 Dec 2020 09:34:25 +0100
Message-ID: <20201203093425.Horde.zzLgaonniDlwff9qSq1X8A1@webmail.df.eu>
From: stefan@gazdag.de
To: "Kretschmer, Andreas" <andreas.kretschmer@siemens.com>
Cc: "cfrg@irtf.org" <cfrg@irtf.org>
References: <VI1PR10MB22850F4780CA2E97A7EA18F795F30@VI1PR10MB2285.EURPRD10.PROD.OUTLOOK.COM>
In-Reply-To: <VI1PR10MB22850F4780CA2E97A7EA18F795F30@VI1PR10MB2285.EURPRD10.PROD.OUTLOOK.COM>
User-Agent: Internet Messaging Program (IMP) H5 (6.0.4)
Content-Type: text/plain; charset="UTF-8"; format="flowed"; DelSp="Yes"
MIME-Version: 1.0
Content-Disposition: inline
X-Df-Sender: c3RlZmFuQGdhemRhZy5kZQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/qHEl4v_NsxT5UaaLhu-g_XHlmF8>
Subject: Re: [CFRG] XDR in RFC8391
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2020 08:34:31 -0000

Hi Andreas,

thanks for pointing out the issues and please excuse the inconvencience.

> - some Identifiers contain "/" and "-", RFC4506 allows only letter,  
> digits and underbars
The easy fix for which I'd settle as suggested by David is to use underbars.

> - some enum bodies end with  ",}", RFC4506 requests "}" here
You're right. Please omit the commas.

> - some union definitions have incomplete declarations in the  
> case-spec, e.g. the union xmss_ots_signature refers to the  
> wotsp-sha2_256 without giving a type.
It's just a numeric identifier, as pointed out by Carsten, defined as  
ots_algorithm_type. Does this help or do you have any further  
questions about it?

> - Is there a fixed formal correct version of the  RFC8391 XDR  
> definitions available?
No, there isn't, yet. But we could e.g. go for an errata for the RFC.

Kind Regards,
Stefan (speaking for the authors)

v2.23.0 | Report a Bug | By Email