Hi Ruediger, There will be a message from IANA with the completed actions for your review. That message will require a reply from you. These are independent of the intake questions.
I suggest you reply to the intake questions with that assumption. Thank you. Cheers, Med > -----Message d'origine----- > De : [email protected] <[email protected]> > Envoyé : vendredi 19 septembre 2025 11:08 > À : [email protected]; BOUCADAIR Mohamed INNOV/NET > <[email protected]>; [email protected] > Cc : [email protected]; [email protected]; rfc- > [email protected]; [email protected] > Objet : AW: Document intake questions about <draft-ietf-ippm- > capacity-protocol-25> > > > Dear Sarah, dear Med and dear David, > > I'm not sure, whether we've completed IANA review. I'd be glad to > get a go or comments to this regard, before replying to Sarah's > questions. > > Regards, > > Ruediger > > -----Ursprüngliche Nachricht----- > Von: Sarah Tarrant <[email protected]> > Gesendet: Donnerstag, 18. September 2025 22:21 > An: [email protected]; Geib, Rüdiger > <[email protected]> > Cc: [email protected]; [email protected]; > [email protected]; [email protected] > Betreff: Document intake questions about <draft-ietf-ippm- > capacity-protocol-25> > > 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). > * 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]. > > 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 is still accurate? > * Are the References, Authors' Addresses, Contributors, and > Acknowledgments sections current? > > > 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? > If so, please provide a pointer to that document (e.g., this > document's terminology should match DNS terminology in RFC 9499). > * Is there a pattern of capitalization or formatting of terms? > (e.g., field names should have initial capitalization; parameter > names should be in double quotes; <tt/> should be used for token > names; etc.) > > > 3) Is there any text that should be handled extra cautiously? For > example, are there any sections that were contentious when the > document was drafted? > > > 4) Is there anything else that the RPC should be aware of while > editing this document? > > > 5) This document contains sourcecode: > > * Does the sourcecode validate? > * Some sourcecode types (e.g., YANG) require certain references > and/or text in the Security Considerations section. Is this > information correct? > * Is the sourcecode type indicated in the XML? (see information > about sourcecode types). > > > > On Sep 18, 2025, at 3:17 PM, [email protected] wrote: > > > > Author(s), > > > > Your document draft-ietf-ippm-capacity-protocol-25, which has > been > > approved for publication as an RFC, has been added to the RFC > Editor > > queue > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fwww.rfc- > editor.org%2Fcurrent_queue.php&data=05%7C02%7Cmohamed.boucadair%40 > orange.com%7Cd77109ca68534f70b3a808ddf75c1498%7C90c7a20af34b40bfbc > 48b9253b6f5d20%7C0%7C0%7C638938697042854475%7CUnknown%7CTWFpbGZsb3 > d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO > IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=JmlAECFUQZMKUYXTSk > 42%2BmjrnPn6U%2BSWaiwucRsjBAo%3D&reserved=0>. > > > > If your XML file was submitted using the I-D submission tool > > > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fdat > > > atracker.ietf.org%2Fsubmit%2F&data=05%7C02%7Cmohamed.boucadair%40o > range.com%7Cd77109ca68534f70b3a808ddf75c1498%7C90c7a20af34b40bfbc4 > 8b9253b6f5d20%7C0%7C0%7C638938697042894010%7CUnknown%7CTWFpbGZsb3d > 8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOI > joiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=niWnhVnwkj9cMp45uT4 > D5TgMnmWprMD945M2g2ehqWg%3D&reserved=0>, 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://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fwww.rfc-editor.org%2Fpubprocess%2Fhow-we- > update%2F&data=05%7C02%7Cmohamed.boucadair%40orange.com%7Cd77109ca > 68534f70b3a808ddf75c1498%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C > 0%7C638938697042918983%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnR > ydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyf > Q%3D%3D%7C0%7C%7C%7C&sdata=EUsG%2FKhE5Y%2FntJHoY9u6oEwP2rRBeXAgkHF > 1jBjpbY8%3D&reserved=0>. > > Next, we will edit for clarity and apply the style guide > > > (<https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F% > 2Fwww.rfc- > editor.org%2Fstyleguide%2F&data=05%7C02%7Cmohamed.boucadair%40oran > ge.com%7Cd77109ca68534f70b3a808ddf75c1498%7C90c7a20af34b40bfbc48b9 > 253b6f5d20%7C0%7C0%7C638938697042943424%7CUnknown%7CTWFpbGZsb3d8ey > JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoi > TWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=x6pqzMktShp2zBDh2SzqIh > oULhbQyQPM%2BsGY%2FR3Qm2U%3D&reserved=0>). > > > > You can check the status of your document at > > > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fwww.rfc- > editor.org%2Fcurrent_queue.php&data=05%7C02%7Cmohamed.boucadair%40 > orange.com%7Cd77109ca68534f70b3a808ddf75c1498%7C90c7a20af34b40bfbc > 48b9253b6f5d20%7C0%7C0%7C638938697042966087%7CUnknown%7CTWFpbGZsb3 > d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO > IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=EfHmfsat7Le6jdL2Av > lkY8NeXE200y%2FBW%2FATpEeprPE%3D&reserved=0>. > > > > You will receive automatic notifications as your document > changes > > queue state (for more information about these states, please see > > > <https://fra01.safelinks.protection.outlook.com/?url=https%3A%2F%2 > Fwww > > .rfc- > editor.org%2Fabout%2Fqueue%2F&data=05%7C02%7Cmohamed.boucadair%40 > > > orange.com%7Cd77109ca68534f70b3a808ddf75c1498%7C90c7a20af34b40bfbc > 48b9253b6f5d20%7C0%7C0%7C638938697042988285%7CUnknown%7CTWFpbGZsb3 > d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFO > IjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=u9E5aSndXhrKsy6gVO > A0rKALBnZeskRtpQm%2BAFmr%2FCw%3D&reserved=0>). 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 > > ____________________________________________________________________________________________________________ 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]
