Hi Authors, We do not believe we have heard from you regarding this document's readiness for publication. Please review our previous messages describing the AUTH48 process and containing our document-specific questions.
We will wait to hear from you before continuing with the publication process. The AUTH48 status page for this document is located here: https://www.rfc-editor.org/auth48/rfc9811 Thank you, RFC Editor/ap > On Jun 30, 2025, at 3:45 PM, rfc-edi...@rfc-editor.org wrote: > > Authors, > > While reviewing this document during AUTH48, please resolve (as necessary) > the following questions, which are also in the XML file. > > 1) <!-- [rfced] We have updated "E-mail-" to "email-", even though RFC 2510 > refers to "(file based, on-line, E-mail, and WWW)". Please let us know if > you have concerns. > > Original: > Additionally, it was mentioned > that PKI messages could also be conveyed using file-, E-mail-, and > HTTP-based transfer, but those were not specified in detail. > --> > > > 2) <!-- [rfced] Would you like the references to be alphabetized > or left in their current order? > --> > > > 3) <!-- [rfced] The 1994 version of ITU-T Recommendation X.690 > (https://www.itu.int/rec/T-REC-X.690-199407-S/en) has been superseded > by the version published in February 2021 > (https://www.itu.int/rec/T-REC-X.690-202102-I/en). May we update this > reference to use the most current version? > > Current: > [ITU.X690.1994] > International Telecommunications Union, "Information > Technology - ASN.1 encoding rules: Specification of Basic > Encoding Rules (BER), Canonical Encoding Rules (CER) and > Distinguished Encoding Rules (DER)", ITU-T Recommendation > X.690, 1994. > > Perhaps: > [ITU.X690.2021] > ITU-T, "Information Technology - ASN.1 encoding rules: > Specification of Basic Encoding Rules (BER), Canonical Encoding > Rules (CER) and Distinguished Encoding Rules (DER)", ITU-T > Recommendation X.690, 2021, > <https://www.itu.int/rec/T-REC-X.690-202102-I/en>. > --> > > > 4) <!--[rfced] FYI, We have updated the reference entry to RFC 9205 with > one for BCP 56 since the BCP is mentioned in the text. Please review > and let us know of any objections. > --> > > > 5) <!-- [rfced] FYI - We have added an expansion for the following > abbreviation per Section 3.6 of RFC 7322 ("RFC Style Guide"). Please review > each expansion in the document carefully to ensure correctness. > > Certificate Revocation List (CRL) > --> > > > 6) <!-- [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. > --> > > > Thank you. > > RFC Editor > > > On Jun 30, 2025, at 3:42 PM, rfc-edi...@rfc-editor.org wrote: > > *****IMPORTANT***** > > Updated 2025/06/30 > > 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 > > * rfc-edi...@rfc-editor.org (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). > > * auth48archive@rfc-editor.org, 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, > auth48archive@rfc-editor.org 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/rfc9811.xml > https://www.rfc-editor.org/authors/rfc9811.html > https://www.rfc-editor.org/authors/rfc9811.pdf > https://www.rfc-editor.org/authors/rfc9811.txt > > Diff file of the text: > https://www.rfc-editor.org/authors/rfc9811-diff.html > https://www.rfc-editor.org/authors/rfc9811-rfcdiff.html (side by side) > > Diff of the XML: > https://www.rfc-editor.org/authors/rfc9811-xmldiff1.html > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > https://www.rfc-editor.org/auth48/rfc9811 > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC 9811 (draft-ietf-lamps-rfc6712bis-10) > > Title : Internet X.509 Public Key Infrastructure -- HTTP Transfer > for the Certificate Management Protocol (CMP) > Author(s) : H. Brockhaus, D. von Oheimb, M. Ounsworth, J. Gray > WG Chair(s) : Russ Housley, Tim Hollebeek > Area Director(s) : Deb Cooley, Paul Wouters > > -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
