Hi Guilin, > It seems that the v07 version, uploaded on 1 April, has not announced in > this list. > https://www.ietf.org/archive/id/draft-ietf-ipsecme-ikev2-pqc-auth-07.html
Oh, somehow we forgot to announce it. > I have one question here: Does this document no need to apply code points at > all? No. Please see Section 3.1. > The document specifies 3 ML_DSA algorithms and 12 SLH-DSA, according to > Sections 4 and 5, as well as > Appendix B. However, no Section for IANA Considerations, and also no code > points for these 15 signature > algorithms in IANA registry under the IKEv2 Authentication Method > (https://www.iana.org/assignments/ikev2- > parameters/ikev2-parameters.xhtml#ikev2-parameters-6) All these signature algorithm will be used with the already defined "Digital Signature" (14) authentication method. The particular signature algorithm is determined by the AlgorithmIdentifier ASN.1 object. For the signature algorithm in question these the AlgorithmIdentifier objects are defined in NIST documents and also in RFC 9881 and RFC 9909. For convenience, they are also provided in Appendix B in binary form with DER encoding. Regards, Valery. > > Cheers, > > Guilin > > -----Original Message----- > From: Valery Smyslov <[email protected]> > Sent: Monday, 30 March 2026 4:22 pm > To: 'Tero Kivinen' <[email protected]>; [email protected]; [email protected] > Cc: [email protected] > Subject: [IPsec] Re: draft-ietf-ipsecme-ikev2-pqc-auth-06 > > Hi Tero, > > I'm not aware of any IPRs related to this document and I'm willing to be > listed as co-author. > > Regards, > Valery. > > > While writing the shepherd writeup, I need to get confirmation from > > each author that there is no IPRs known that are not already > > submitted, and that all authors are willing to be listed as authors. > > > > So if you can respond to this email and specify those things. > > > > Ps. The current draft has couple of ID nits (in addition to my > > previous comments to the draft), which needs to be fixed before I can > > request publication (no IANA consideration section, reference to > > RFC7296 in abstract). After you have responded to this email, and new > > version of the draft has been submitted fixing the issues I pointed > > out earlier (and the idnits), then I can submit this draft for the > > publication. > > -- > > [email protected] > > _______________________________________________ > IPsec mailing list -- [email protected] > To unsubscribe send an email to [email protected] > _______________________________________________ > IPsec mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ IPsec mailing list -- [email protected] To unsubscribe send an email to [email protected]
