Hi Michael,
At 03:58 PM 05-12-2024, Michael Richardson wrote:
The recently published rfc9563 references SM2, which is an ITU-T for fee
document, with an english translation which does seem to not load for me.
  http://www.gmbz.org.cn/upload/2024-11-18/1731899501687024253.pdf

I would prefer that "Specification Required" included the words "available",
and for which the principles of open-stand.org applied.

RFC 9563 was was published through the Independent Submissions Stream {1]. My reading of the boilerplate text is that it is not an Internet Standard. There is a paragraph under Section 1 which starts with the following word: "Caution". I reading that as meaning that the reader should be careful. There is an explanation that the specification "makes use of cryptographic algorithms that are national standards for China, as well as ISO/IEC standards ..." If I am not mistaken, standards which do not originate from within the
Internet Standards Process are usually referred to as external specifications.

RFC 9558 is also an external specification. It contains a similar paragraph about "caution" and an explanation that it is a national standard for Russia.

RFC 9206 specifies the conventions for using the United States National Security Agency's (NSA's) Commercial National Security Algorithm (CNSA) Suite algorithms ... I would view it as an external specification if the discussion is about "code points".

The code points in the above three cases were allocated by the IETF. Did the allocations cause any problem? :-)

I was able to access the "english translation" (please see above) for SM2 some time ago. I got a "failed to connect to www.gmbz.org.cn" error when I tried to do that a few minutes ago.

One or more of the standard bodies which signed up for openstand charges a fee to access some of its specifications.

Regards,
S. Moonesamy

1. https://www.rfc-editor.org/about/independent/
_______________________________________________
rfc-interest mailing list -- rfc-interest@rfc-editor.org
To unsubscribe send an email to rfc-interest-le...@rfc-editor.org

Reply via email to