>> Minor issues:
>>
>> There are a few downref errors reported. Two are in the downref registry and
>> are thus OK. The two of significance are thus:
>> ** Downref: Normative reference to an Informational RFC: RFC 8391
>> -- Possible downref: Non-RFC (?) normative reference: ref. ‘SP800208'
>>
>> The RFC 8391 error needs to be formally addressed. The SP800208 error is a
>> pointer to the work of a reputable body and thus should be accepted as OK.
> The draft references RFC 8554, which is the description of the LMS/HSS
> algorithm, and is in the downref registry.
>
> RFC 8391 is the description of the XMSS(MT) algorithm.
>
> If RFC 8554 can be in the downref registry then I think RFC 8391 should be as
> well.
>
This topic was discussed in the shepherd write-up:
The IETF Last Call for this document will need to call out RFC 8391 as a
downref.
This document has a normative reference to RFC 5911, which is
already in the downref registry.
This document specified the conventions for using the HSS/LMS, XMSS, and
XMSS^MT signature algorithms in X.509 certificates. HSS/LMS is specified
in RFC 8554, which is already in the downref registry. XMSS and XMSS^MT
are specified in RFC 8391, which is not yet in the downref registry.
The IETF Last Call also calls out the downref:
The document contains these normative downward references.
See RFC 3967 for additional information:
rfc8391: XMSS: eXtended Merkle Signature Scheme (Informational - Internet
Research Task Force (IRTF) stream)
Russ_______________________________________________
Gen-art mailing list -- gen-art@ietf.org
To unsubscribe send an email to gen-art-le...@ietf.org
