Hi Ike, all, For this one:
[QoO] We would be happy to participate if that is ok for Med and Marcus. Your favorite option is mine :-) Cheers, Med De : Ike Kunze <[email protected]> Envoyé : mardi 19 mai 2026 12:19 À : Sarah Tarrant <[email protected]>; Bjorn Ivar Teigen Monclair <[email protected]>; Magnus Olden <[email protected]>; [email protected]; BOUCADAIR Mohamed INNOV/NET <[email protected]> Cc : [email protected]; [email protected] Objet : Re: Document intake questions about <draft-ietf-ippm-qoo-10> Dear RPC Team, Dear Sarah, Thanks for reaching out! Please find responses to your questions below, indicated by [QoO]. In order to address some of your questions, we have also done a very minor update of the draft, so the latest version is now -11. As we would be happy to participate in the RPC Pilot Test for kramdown-rfc, we have also attached the markdown version of the draft to this email; it’s the same version you can also find in the corresponding github repository (https://github.com/getCUJO/QoOID/blob/main/draft-ietf-ippm-qoo.md). @[email protected]<mailto:[email protected]>, @[email protected]<mailto:[email protected]>: If it is ok for you, we would also like to participate in the RPC Pilot Test for completing AUTH48 in GitHub. Please let us know if you have any further questions. Thanks again! Cheers, Ike Friendly Note: I send emails at times that work best for me. Please don’t feel any pressure to reply outside your usual working hours. [Background pattern Description automatically generated] Ike Kunze Senior Researcher Phone +47 408 81 254 CUJO AI<https://cujo.com/> | News<https://cujo.com/blog/> <https://cujo.com/blog/> | LinkedIn<https://www.linkedin.com/company/cujoai> From: Sarah Tarrant <[email protected]<mailto:[email protected]>> Date: Monday, 18 May 2026 at 21:41 To: Bjorn Ivar Teigen Monclair <[email protected]<mailto:[email protected]>>; Magnus Olden <[email protected]<mailto:[email protected]>>; Ike Kunze <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Subject: Document intake questions about <draft-ietf-ippm-qoo-10> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Author(s), Congratulations, your document has been successfully added to the RFC Editor queue! The team at the RFC Production Center (RPC) is looking forward to working with you as your document moves forward toward publication. To help reduce processing time and improve editing accuracy, please respond to the questions below. Please confer with your coauthors (or authors of other documents if your document is in a cluster) as necessary prior to taking action in order to streamline communication. If your document has multiple authors, only one author needs to reply to this message. As you read through the rest of this email: * If you need/want to make updates to your document, we encourage you to make those changes and resubmit to the Datatracker. This allows for the easy creation of diffs, which facilitates review by interested parties (e.g., authors, ADs, doc shepherds). [QoO] We have updated the draft with a new -11 version, which fixes capitalization in the Terminology section and sorts the individuals listed in the Acknowledgements alphabetically. * If you feel no updates to the document are necessary, please reply with any applicable rationale/comments. Please note that the RPC team will not work on your document until we hear from you (that is, your document will remain in AUTH state until we receive a reply). Even if you don't have guidance or don't feel that you need to make any updates to the document, you need to let us know. After we hear from you, your document will start moving through the queue. You will be able to review and approve our updates during AUTH48. Please feel free to contact us with any questions you may have at [email protected]<mailto:[email protected]>. Thank you! The RPC Team -- 1) As there may have been multiple updates made to the document during Last Call, please review the current version of the document: * Is the text in the Abstract still accurate? [QoO] Still accurate. * Are the Authors' Addresses, Contributors, and Acknowledgments sections current? [QoO] We have updated the document with an alphabetically sorted version of the Acknowledgements (see -11). The content is now current again. 2) Please share any style information that could help us with editing your document. For example: * Is your document's format or its terminology based on another document, WG style guide, etc.? If so, please provide a pointer to that information (e.g., "This document's terminology should match DNS terminology in RFC 9499." or "This document uses the style info at <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhttpwg.org%2Fadmin%2Feditors%2Fstyle-guide&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300630887144%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=IamCRiuA7sHq6MoyS0O0xaR5HFvxZoQNkaHS64DVpuk%3D&reserved=0>.<https://httpwg.org/admin/editors/style-guide>"). [QoO] The format of the document does not use any style guide. * Is there a general pattern of capitalization or formatting of terms that editors can follow (e.g., "Field names should have initial capitalization." or "Parameter names should be in double quotes." or "<tt/> should be used for token names." etc.)? [QoO] We use title case for some formally defined terms in the Terminology section and then keep capitalization stable across the document. Note that there are two exceptions for ROP and CPUP, where we deliberately use lowercase. Should you find that it is more appropriate to also use title case in those instances, please feel free to make that change. 3) Please carefully review the entries and their URLs in the References section with the following in mind. Note that we will update as follows unless we hear otherwise at this time: * References to obsoleted RFCs will be updated to point to the current RFC on the topic in accordance with Section 4.8.6 of RFC 7322 (RFC Style Guide). * References to I-Ds that have been replaced by another I-D will be updated to point to the replacement I-D. * References to documents from other organizations that have been superseded will be updated to their superseding version. Note: To check for outdated RFC and I-D references, you can use idnits <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthor-tools.ietf.org%2Fidnits&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300630920459%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ifRz6obrW7u4iRJ5drnFZsXPjQS17SDFKD7v7FvzDpw%3D&reserved=0<https://author-tools.ietf.org/idnits>>. You can also help the IETF Tools Team by testing idnits3 <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fauthor-tools.ietf.org%2Fidnits3%2F&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300630939939%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=RTSRdw6ECebsb042lih7xK1%2BBq5EDsktSGK9PgUR2lQ%3D&reserved=0<https://author-tools.ietf.org/idnits3/>> with your document and reporting any issues to them. [QoO] All references should be up to date and they all pass idnits3. 4) Is there any text that requires special handling? For example: * Are there any sections that were contentious when the document was drafted? [QoO] No. * Are any sections that need to be removed before publication marked as such (e.g., Implementation Status sections (per RFC 7942)). [QoO] Yes, they are marked: one “About this Document” paragraph on the title page and then the entire Section 9 (Implementation Status). * Are there any instances of repeated text/sections that should be edited the same way? [QoO] No. 5) Would you like to participate in the RPC Pilot Test for editing in kramdown-rfc? If so, please let us know and provide a self-contained kramdown-rfc file. For more information about this experiment, see: https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frpc%2Fwiki%2Fdoku.php%3Fid%3Dpilot_test_kramdown_rfc&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300630960441%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=ukAIltY8w%2F0UFtyiXkQCw9rs%2BsIZh50bou8KuhcVPYQ%3D&reserved=0<https://www.rfc-editor.org/rpc/wiki/doku.php?id=pilot_test_kramdown_rfc>. [QoO] We would be happy to participate. We have attached the latest kramdown-rfc file to this email. 6) Would you like to participate in the RPC Pilot Test for completing AUTH48 in GitHub? If so, please let us know and provide all author, AD, and/or document shepherd GitHub usernames. For more information about this experiment, see: https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frpc%2Fwiki%2Fdoku.php%3Fid%3Drpc-github-phase-0-pilot-test&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300630978940%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=6vK0fARqWeOBlQHtQe2kK15HYxKpF6nF0HxUqPsfQR8%3D&reserved=0<https://www.rfc-editor.org/rpc/wiki/doku.php?id=rpc-github-phase-0-pilot-test>. [QoO] We would be happy to participate if that is ok for Med and Marcus. GitHub usernames: * authors: cj-bjorn-monclair, cj-magnus-olden, cj-ike-kunze * AD: boucadair * document shepherd: ihlar 7) Is there anything else that the RPC should be aware of while editing this document? [QoO] No. > On May 18, 2026, at 2:37 PM, > [email protected]<mailto:[email protected]> wrote: > > Author(s), > > Your document draft-ietf-ippm-qoo-10, which has been approved for publication > as > an RFC, has been added to the RFC Editor queue > <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fcurrent_queue.php&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300630997688%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=RlohQYI5zgwh7d6yMm76kp6KFC4u5044UQd%2BmVfduYc%3D&reserved=0<https://www.rfc-editor.org/current_queue.php>>. > > If your XML file was submitted using the I-D submission tool > <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fsubmit%2F&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300631015231%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=yC6RW8H8tQFnlQ%2BWdeyiZJv1xE8N4cZtgKAhE2UW3Uo%3D&reserved=0<https://datatracker.ietf.org/submit/>>, > we have already retrieved it > and have started working on it. > > If you did not submit the file via the I-D submission tool, or > if you have an updated version (e.g., updated contact information), > please send us the file at this time by attaching it > in your reply to this message and specifying any differences > between the approved I-D and the file that you are providing. > > You will receive a separate message from us asking for style input. > Please respond to that message. When we have received your response, > your document will then move through the queue. The first step that > we take as your document moves through the queue is converting it to > RFCXML (if it is not already in RFCXML) and applying the formatting > steps listed at > <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fpubprocess%2Fhow-we-update%2F&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300631032704%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=mSdgYwHryy5mAhOJC6o%2BWmrJMwxpf6Nk%2FsNsSJnA7QM%3D&reserved=0<https://www.rfc-editor.org/pubprocess/how-we-update/>>. > Next, we will edit for clarity and apply the style guide > (<https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fstyleguide%2F&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300631050380%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=gbQbYNiBX%2Foue9uOK4HB7s1CgpiL0XKoAmTYjO1zcO8%3D&reserved=0<https://www.rfc-editor.org/styleguide/>>). > > You can check the status of your document at > <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fcurrent_queue.php&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300631067233%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=Q5l%2FcgOSeG3ssv3c7i6Ig90PZDDLpQDWWFY381hEwLg%3D&reserved=0<https://www.rfc-editor.org/current_queue.php>>. > > You will receive automatic notifications as your document changes > queue state (for more information about these states, please see > <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fabout%2Fqueue%2F&data=05%7C02%7Cike.kunze%40cujo.com%7C6d26a605acf242d8639d08deb51561b7%7Ca5d2f1ce8ca649ce893ab4f922d7fc6b%7C0%7C0%7C639147300631084187%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=s%2B7W2hxBi3tIN5G5xw38UOq%2FEQ276n66By9gPts5W24%3D&reserved=0<https://www.rfc-editor.org/about/queue/>>). > When we have completed > our edits, we will move your document to AUTH48 state and ask you > to perform a final review of the document. > > Please let us know if you have any questions. > > Thank you. > > The RFC Editor Team > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
