[saag] draft-paulwh-crypto-components-01

Paul Hoffman <[email protected]>
Newsgroups gmane.ietf.saag
Message-ID <[email protected]>
Greetings again. PaulW and I have updated the draft based on the SAAG list discussion from the past few weeks. Please see the revised version, particularly the new text about the use of Internet Drafts for code point references.

There were a few proposed changes that we didn't do:

- Michael Richardson proposed that we add current examples of protocols in Section 3. This seems like a bad idea because WGs sometimes change the way that their codepoint registries are managed, including what is or is not allowed for future codepoints. It would be bad if we listed one that later got changed.

- Watson Ladd said "I would appreciate clarifying the scope to be things like (but not limited to) signatures, ciphers etc. It's not clear to me how this draft is meant to apply to something like PPM." It's not clear at this point if this document has such a scope limitation.

Thanks for all the list input; more is appreciated. Please start new threads for each topic, given that this document covers many diverse topics.

--Paul Hoffman

=====

A new version of Internet-Draft draft-paulwh-crypto-components-01.txt has been
successfully submitted by Paul Hoffman and posted to the
IETF repository.

Name:     draft-paulwh-crypto-components
Revision: 01
Title:    Documenting and Referencing Cryptographic Components in IETF Documents
Date:     2025-02-03
Group:    Individual Submission
Pages:    8
URL:      https://www.ietf.org/archive/id/draft-paulwh-crypto-components-01.txt
Status:   https://datatracker.ietf.org/doc/draft-paulwh-crypto-components/
HTMLized: https://datatracker.ietf.org/doc/html/draft-paulwh-crypto-components
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-paulwh-crypto-components-01


_______________________________________________
saag mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.