Re: [netconf] Create IANA-defined modules?

[Qin Wu <[e-mail]>]

-----邮件原件-----
>>发件人: tom petch [mailto:[e-mail]] 
>>发送时间: 2021年6月15日 19:32
>>收件人: Qin Wu <[e-mail]>; Kent Watsen <[e-mail]>; Per Andersson (perander) <[e-mail]>
>>抄送: [e-mail]
>>主题: Re: [netconf] Create IANA-defined modules?

>>From: Qin Wu <[e-mail]>
>>Sent: 15 June 2021 06:54

>> Kent Watsen [mailto:[e-mail]]
 2021 6 5 0:22

>>Thank you Qin, Tom, and Per for the responses to my last post…this message addresses them all.

>>Since the discussion has been mostly about *how* to create the IANA-defined module (not *if* we should, e.g., dropping the work for some future effort to pickup), I take it that folks believe having the ability for configure supported-algorithms is needed now.  
>>no one offered to help (:sigh:, and people wonder why this work takes so long), I wrote the attached script that creates the attached module directly from the data obtained from the IANA-maintained "TLS Cipher Suites" sub-registry of the "Transport Layer 
>>Security (TLS) Parameters” registry here: https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml.  The resulting module is also attached.

>[Qin Wu]  The proposed module looks good to me, I assume these cipher-suite identities are not specific to particular version of TLS, e.g., TLS1.3.

><tp>
>No, the exact opposite.  AFAIK there is no recommended ciphersuite that is common to TLS1.2 and TLS1.3 (or indeed one that is not recommended).  TLS1.3 is very different!

[Qin Wu] Thanks for your clarification, this aligns with what I understand.