Re: [CFRG] XDR in RFC8391

stefan@gazdag.de Fri, 11 December 2020 06:20 UTC

Date: Fri, 11 Dec 2020 07:20:15 +0100
Message-ID: <20201211072015.Horde.i8r1RH78vi6IDmJjt7_Avw1@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> <20201203093425.Horde.zzLgaonniDlwff9qSq1X8A1@webmail.df.eu> <AM0PR10MB227452DD0D56F5641145D86F95F20@AM0PR10MB2274.EURPRD10.PROD.OUTLOOK.COM> <20201209164901.Horde.w7UXKDdX5Q6zpxhnXKDU-A5@webmail.df.eu> <AM0PR10MB227468C62ECD1419EB9D07C095CB0@AM0PR10MB2274.EURPRD10.PROD.OUTLOOK.COM>
In-Reply-To: <AM0PR10MB227468C62ECD1419EB9D07C095CB0@AM0PR10MB2274.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
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/zw9fmguQqbd7xQ77n4eLggsngA8>
Subject: Re: [CFRG] XDR in RFC8391
Precedence: list

Hi Andreas,

sure, would be a pleasure.

Taking this discussion off-list. Gonna text you soon.

Kind Regards,
Stefan


Zitat von "Kretschmer, Andreas" <andreas.kretschmer@siemens.com>:

> Hallo Stefan,
>
> I submitted already an errata:  
> https://www.rfc-editor.org/errata/eid6352 . Maybe we can push it  
> together?
>
> Kind regards,
> Andreas
>
> -----Original Message-----
> From: stefan@gazdag.de <stefan@gazdag.de>
> Sent: Mittwoch, 9. Dezember 2020 16:49
> To: Kretschmer, Andreas (T RDA CST SEA-DE) <andreas.kretschmer@siemens.com>
> Cc: cfrg@irtf.org
> Subject: Re: [CFRG] XDR in RFC8391
>
> Hi Andreas,
>
> please excuse the late answer.
>
> The identifier should be 4 byte, yet it looks like the ots_signature  
> itself is missing.
>
> Currently working on an errata.
>
> Kind Regards,
> Stefan
>
> Quoting "Kretschmer, Andreas" <andreas.kretschmer@siemens.com>:
>
>> Hallo Stefan,
>>
>> Is this right:
>>
>> If I want to encode a xmss_ots_signature (e.g. as part of a
>> xmss_signature) I have to write at first 4 byte for the "
>> xmss_algorithm_type type" discriminator followed by 4 byte for an
>> specific arm?
>>
>> Thanks,
>> Andreas
>>
>> -----Original Message-----
>> From: stefan@gazdag.de <stefan@gazdag.de>
>> Sent: Donnerstag, 3. Dezember 2020 09:34
>> To: Kretschmer, Andreas (T RDA CST SEA-DE)
>> <andreas.kretschmer@siemens.com>
>> Cc: cfrg@irtf.org
>> Subject: Re: [CFRG] XDR in RFC8391
>>
>> 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)

[CFRG] XDR in RFC8391 Kretschmer, Andreas
Re: [CFRG] XDR in RFC8391 David McGrew (mcgrew)
Re: [CFRG] XDR in RFC8391 Kretschmer, Andreas
Re: [CFRG] XDR in RFC8391 Carsten Bormann
Re: [CFRG] XDR in RFC8391 stefan
Re: [CFRG] XDR in RFC8391 Kretschmer, Andreas
Re: [CFRG] XDR in RFC8391 stefan
Re: [CFRG] XDR in RFC8391 Kretschmer, Andreas
Re: [CFRG] XDR in RFC8391 stefan