Sorry for the delay, this got buried in my inbox. On Mon, Apr 6, 2026 at 6:58 PM <[email protected]> wrote:
> Authors, > > While reviewing this document during AUTH48, please resolve (as necessary) > the following questions, which are also in the source file. > > 1) <!-- [rfced] Please insert any keywords (beyond those that appear in > the title) for use on https://www.rfc-editor.org/search. --> > I see the XML file contains <keyword>example</keyword>. I assume that is not intended to end up in the final file? (Not sure where it came from.) Some additional keywords which may be appropriate: pkcs1 (in case it doesn't match "RSASSA-PKCS1-v1_5") rsa (in case it doesn't match RSASSA-PKCS1-v1_5) No others come to mind. > 2) <!-- [rfced] Please clarify whether "them" refers to the "legacy keys" > or "signature algorithms". May we update the text as follows? > > Original (the full paragraph included for context): > Clients with such legacy keys MAY negotiate the use of these > signature algorithms if offered by the server. Clients SHOULD NOT > negotiate them with keys that support RSASSA-PSS, though this may not > be practical to determine in all applications. For example, > attempting to test a key for support might display a message to the > user or have other side effects. > > Perhaps: > ... Clients with such legacy keys MAY negotiate the use of these > signature algorithms if offered by the server. Clients SHOULD NOT > negotiate the use of these signature algorithms with keys that support > RSASSA-PSS, though it may not be practical to determine which keys > support RSASSA-PSS in all applications. > > In addition, please clarify "display" in the last sentence - we wonder > whether "might result in" or "might expose" might be more clear. > > --> > "them" indeed referred to "signature algorithms". The suggested change sounds good. By "display a message to the user", that was referring to how, on some systems where keys live on hardware dongles, etc., prodding the key may result in user PIN prompts, or other user-visible effects. Replacing "display" with "might result in" sounds good. Thanks! 3) <!-- [rfced] draft-ietf-tls-hybrid-design is currently in AUTH48 as RFC- > to-be 9954. We have updated the reference to point to RFC 9954, in hopes > it will complete AUTH48 around the same time as this document. > --> > Ack. Sounds good. Nice to see these documents getting through the finish line! > 4) <!-- [rfced] Please review the "Inclusive Language" portion of the > online Style Guide < > https://www.rfc-editor.org/styleguide/part2/#inclusive_language> > and let us know if any changes are needed. Updates of this nature > typically result in more precise language, which is helpful for readers. > > Note that our script did not flag any words in particular, but this should > still be reviewed as a best practice. > --> > Ack. Nothing jumps out to me. > Thank you. > > Sandy Ginoza > RFC Production Center > > > On Apr 6, 2026, at 6:54 PM, [email protected] wrote: > > *****IMPORTANT***** > > Updated 2026/04/06 > > RFC Author(s): > -------------- > > Instructions for Completing AUTH48 > > Your document has now entered AUTH48. Once it has been reviewed and > approved by you and all coauthors, it will be published as an RFC. > If an author is no longer available, there are several remedies > available as listed in the FAQ (https://www.rfc-editor.org/faq/). > > You and you coauthors are responsible for engaging other parties > (e.g., Contributors or Working Group) as necessary before providing > your approval. > > Planning your review > --------------------- > > Please review the following aspects of your document: > > * RFC Editor questions > > Please review and resolve any questions raised by the RFC Editor > that have been included in the XML file as comments marked as > follows: > > <!-- [rfced] ... --> > > These questions will also be sent in a subsequent email. > > * Changes submitted by coauthors > > Please ensure that you review any changes submitted by your > coauthors. We assume that if you do not speak up that you > agree to changes submitted by your coauthors. > > * Content > > Please review the full content of the document, as this cannot > change once the RFC is published. Please pay particular attention to: > - IANA considerations updates (if applicable) > - contact information > - references > > * Copyright notices and legends > > Please review the copyright notice and legends as defined in > RFC 5378 and the Trust Legal Provisions > (TLP – https://trustee.ietf.org/license-info). > > * Semantic markup > > Please review the markup in the XML file to ensure that elements of > content are correctly tagged. For example, ensure that <sourcecode> > and <artwork> are set correctly. See details at > <https://authors.ietf.org/rfcxml-vocabulary>. > > * Formatted output > > Please review the PDF, HTML, and TXT files to ensure that the > formatted output, as generated from the markup in the XML file, is > reasonable. Please note that the TXT will have formatting > limitations compared to the PDF and HTML. > > > Submitting changes > ------------------ > > To submit changes, please reply to this email using ‘REPLY ALL’ as all > the parties CCed on this message need to see your changes. The parties > include: > > * your coauthors > > * [email protected] (the RPC team) > > * other document participants, depending on the stream (e.g., > IETF Stream participants are your working group chairs, the > responsible ADs, and the document shepherd). > > * [email protected], which is a new archival mailing list > to preserve AUTH48 conversations; it is not an active discussion > list: > > * More info: > > https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc > > * The archive itself: > https://mailarchive.ietf.org/arch/browse/auth48archive/ > > * Note: If only absolutely necessary, you may temporarily opt out > of the archiving of messages (e.g., to discuss a sensitive matter). > If needed, please add a note at the top of the message that you > have dropped the address. When the discussion is concluded, > [email protected] will be re-added to the CC list and > its addition will be noted at the top of the message. > > You may submit your changes in one of two ways: > > An update to the provided XML file > — OR — > An explicit list of changes in this format > > Section # (or indicate Global) > > OLD: > old text > > NEW: > new text > > You do not need to reply with both an updated XML file and an explicit > list of changes, as either form is sufficient. > > We will ask a stream manager to review and approve any changes that seem > beyond editorial in nature, e.g., addition of new text, deletion of text, > and technical changes. Information about stream managers can be found in > the FAQ. Editorial changes do not require approval from a stream manager. > > > Approving for publication > -------------------------- > > To approve your RFC for publication, please reply to this email stating > that you approve this RFC for publication. Please use ‘REPLY ALL’, > as all the parties CCed on this message need to see your approval. > > > Files > ----- > > The files are available here: > https://www.rfc-editor.org/authors/rfc9963.xml > https://www.rfc-editor.org/authors/rfc9963.html > https://www.rfc-editor.org/authors/rfc9963.pdf > https://www.rfc-editor.org/authors/rfc9963.txt > > Diff file of the text: > https://www.rfc-editor.org/authors/rfc9963-diff.html > https://www.rfc-editor.org/authors/rfc9963-rfcdiff.html (side by side) > > Diff of the XML: > https://www.rfc-editor.org/authors/rfc9963-xmldiff1.html > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > https://www.rfc-editor.org/auth48/rfc9963 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC 9963 (draft-ietf-tls-tls13-pkcs1-07) > > Title : Legacy RSASSA-PKCS1-v1_5 codepoints for TLS 1.3 > Author(s) : D. Benjamin, A. Popov > WG Chair(s) : Joseph A. Salowey, Sean Turner, Deirdre Connolly > > Area Director(s) : Deb Cooley, Christopher Inacio > > >
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
