Authors, While reviewing this document during AUTH48, please resolve (as necessary) the following questions, which are also in the XML file.
1) <!--[rfced] Title a) We note that the document's title expands PCEP as "PCE Communication Protocol"; however, the IANA registry group expands it as "Path Computation Element Protocol" (see <https://www.iana.org/assignments/pcep>). Should this document's title be updated to reflect the name of the registry group being updated, with the inclusion of "Numbers", as shown below? Original: Update to the IANA PCE Communication Protocol (PCEP) Registration Procedures and Allowing Experimental Error Codes Perhaps: Update to the IANA Path Computation Element Protocol (PCEP) Numbers Registration Procedures and the Allowance of Experimental Error Codes b) FYI - To closer reflect the document's full title, we have updated the short title as follows. The short title appears in the running header in the PDF output. Original: PCEP-IANA Current: PCEP IANA Update --> 2) <!-- [rfced] Please insert any keywords (beyond those that appear in the title) for use on https://www.rfc-editor.org/search. --> 3) <!--[rfced] To avoid repetition of "case", may we update this sentence as follows? Original: It will often be the case that previously assigned error codes (in the PCEP-ERROR Object Error Types and Values sub- registry) can be used to indicate the error cases within an experiment, but there may also be cases where new, experimental error codes are needed. Perhaps: It will often be that previously assigned error codes (in the PCEP-ERROR Object Error Types and Values sub- registry) can be used to indicate the error cases within an experiment, but there may also be instances where new, experimental error codes are needed. --> 4) <!--[rfced] Would it be clearer for readers if the following information matches the IANA registry and is in table format (see <https://www.iana.org/assignments/pcep/>)? Please let us know your preference. Original: IANA is requested to change the assignment policy for this registry to read: Error-Types 0-251 : IETF Review 252-255 : Experimental Use Error-value For all IETF Review Error-Types : IETF Review For all Experimental Use Error-Types : Experimental Use Perhaps: IANA has changed the assignment policy for the "PCEP-ERROR Object Error Types and Values" registry as follows: Range Registration Procedures Note - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0-251 IETF Review The IETF Review procedure applies to all Error-values (0-255) for Error-Types in this range. 252-255 Experimental Use The Experimental Use policy applies to all Error-values (0-255) for Error-Types in this range. Table 2: PCEP-ERROR Object Error Types and Values Registry Assignment Policy --> 5) <!--[rfced] FYI - For consistency, and because the capitalization infers that these are procedures, we have removed the quotation marks from the following terms. "Standards Action" "IETF Review" --> 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/ap/kc On Mar 03, 2025, at 11:57 AM, rfc-edi...@rfc-editor.org wrote: *****IMPORTANT***** Updated 2025/03/03 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/rfc9756.xml https://www.rfc-editor.org/authors/rfc9756.html https://www.rfc-editor.org/authors/rfc9756.pdf https://www.rfc-editor.org/authors/rfc9756.txt Diff file of the text: https://www.rfc-editor.org/authors/rfc9756-diff.html https://www.rfc-editor.org/authors/rfc9756-rfcdiff.html (side by side) Diff of the XML: https://www.rfc-editor.org/authors/rfc9756-xmldiff1.html Tracking progress ----------------- The details of the AUTH48 status of your document are here: https://www.rfc-editor.org/auth48/rfc9756 Please let us know if you have any questions. Thank you for your cooperation, RFC Editor -------------------------------------- RFC9756 (draft-ietf-pce-iana-update-03) Title : Update to the IANA PCE Communication Protocol (PCEP) Registration Procedures and Allowing Experimental Error Codes Author(s) : D. Dhody, A. Farrel WG Chair(s) : Julien Meuric, Dhruv Dhody Area Director(s) : Jim Guichard, John Scudder, Gunter Van de Velde -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
