Hi Richard, Thank you for notifying us that you approve the RFC for publication. We have marked your approval on the AUTH48 page <https://www.rfc-editor.org/auth48/rfc9768>. We have not seen Mirja’s final approval, so we will wait to hear from her and Bob before continuing with publication.
Thank you, Sandy Ginoza RFC Production Center > On Aug 21, 2025, at 10:51 AM, Scheffenegger, Richard > <[email protected]> wrote: > > > Hi, > > I've seen that Mirja made/signed off on the final changes, and with those, I > approve this RFC for publication! > > In addition, thanks a lot for using the reserved RFC number! > > > Richard Scheffenegger > Senior Solution Architect > NAS & Networking > > NetApp > +43 1 3676 811 3157 Direct Phone > +43 664 8866 1857 Mobile Phone > [email protected] > > > -----Original Message----- > From: [email protected] <[email protected]> > Sent: Dienstag, 12. August 2025 21:32 > To: [email protected]; [email protected]; Scheffenegger, Richard > <[email protected]> > Cc: [email protected]; [email protected]; [email protected]; > [email protected]; [email protected]; > [email protected] > Subject: AUTH48: RFC-to-be 9768 <draft-ietf-tcpm-accurate-ecn-34> for your > review > > EXTERNAL EMAIL - USE CAUTION when clicking links or attachments > > > > > *****IMPORTANT***** > > Updated 2025/08/12 > > 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://urldefense.com/v3/__https://www.rfc-editor.org/faq/__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwziGck49A$ > ). > > 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://urldefense.com/v3/__https://trustee.ietf.org/license-info__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwxVHgFJ9g$ > ). > > * 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://urldefense.com/v3/__https://authors.ietf.org/rfcxml-vocabulary__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwwU1JXVnw$ > >. > > * 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://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwxaanKYsQ$ > > * The archive itself: > > https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/auth48archive/__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwz9Ua_AlA$ > > * 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://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9768.xml__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwxslf7wEw$ > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9768.html__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwwEmRJojA$ > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9768.pdf__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwy5J6XreA$ > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9768.txt__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwxFJ3CLPw$ > > Diff file of the text: > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9768-diff.html__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwwQlC5WSA$ > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9768-rfcdiff.html__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwwysbvRxQ$ > (side by side) > > Diff of the XML: > > https://urldefense.com/v3/__https://www.rfc-editor.org/authors/rfc9768-xmldiff1.html__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwyH5n7yOw$ > > > Tracking progress > ----------------- > > The details of the AUTH48 status of your document are here: > > https://urldefense.com/v3/__https://www.rfc-editor.org/auth48/rfc9768__;!!Nhn8V6BzJA!Q35gJuduJBNoS9dEpEp7nYsAhY0L0CFUXpHFNyUH1k_E6dtdba4CymPQXDf3QykFTk71oHRcVbMaKbyHlxAzNGsSTwyNVEnvew$ > > Please let us know if you have any questions. > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC 9768 (draft-ietf-tcpm-accurate-ecn-34) > > Title : More Accurate Explicit Congestion Notification (AccECN) > Feedback in TCP > Author(s) : B. Briscoe, M. Kühlewind, R. Scheffenegger > WG Chair(s) : Yoshifumi Nishida, Michael Tüxen > > Area Director(s) : Gorry Fairhurst, Mike Bishop -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
