Dear RFC Editor, ++ @Pascal Thubert<mailto:[email protected]> comment.
I disagree with the Terminology word used twice for Sections 2 and Subsection 2.2. I would suggest changing 2.2 from Terminology into Terms and Concepts or Related Documents. The rest of the document is fine. Thank you Regards, Adnan Rashid - Ph.D. Assistant Professor, Dpt. Electrical and Information Engineering (DEI), Politecnico di Bari, Via Orabona 4, 70125, Bari, Italy. E-mail: [email protected] [email protected] Phone: +39-080-596-3066 Mobile:+39 376 262 1282 ________________________________ From: Pascal Thubert <[email protected]> Sent: Tuesday, January 27, 2026 10:55 To: [email protected] <[email protected]> Cc: Adnan Rashid <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: Re: AUTH48: RFC-to-be 9927 <draft-ietf-6lo-updating-rfc-8928-05> for your review Dear RFC Editor I review the 3 occurrences of [rfced] in the xml and I'm good with the proposals. In particular for "strong" the best is to retain consistency with RFC to be 9926. Many thanks! Pascal Le mar. 27 janv. 2026 à 05:50, <[email protected]<mailto:[email protected]>> a écrit : Authors, While reviewing this document during AUTH48, please resolve (as necessary) the following questions, which are also in the source file. 1) <!-- [rfced] Please insert any keywords (beyond those that appear in the title) for use on https://www.rfc-editor.org/search. --> 2) <!-- [rfced] Some author comments are present in the XML. Please confirm that no updates related to these comments are outstanding. Note that the comments will be deleted prior to publication. --> 3) <!-- [rfced] Regarding usage of <strong> elements in this document. please review the occurrences and let us know if any updates needed for consistency. In the HTML and PDF outputs, <strong> yields bold. In the text output, <strong> yields an asterisk before and after. We suggest removing usage in this document because the asterisks seem to clutter the text output in Sections 2.3 and 3. --> 4) <!-- [rfced] FYI, regarding [IANA.ICMP.ARO.P-FIELD], we updated the reference's title to "P-Field Values" to match what seems to have been intended. Please let us know if this is not accurate. Original: [IANA.ICMP.ARO.P-FIELD] IANA, "IANA Registry for the Address Registration Option Status Value", IANA, https://www.iana.org/assignments/ icmpv6-parameters/icmpv6-parameters.xhtml#p-field-values. Current: [IANA.ICMP.ARO.P-FIELD] IANA, "P-Field Values", <https://www.iana.org/assignments/icmpv6-parameters>. --> 5) <!-- [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. Alice Russo RFC Production Center On Jan 26, 2026, [email protected]<mailto:[email protected]> wrote: *****IMPORTANT***** Updated 2026/01/26 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 * [email protected]<mailto:[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]<mailto:[email protected]>, 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, [email protected]<mailto:[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://www.rfc-editor.org/authors/rfc9927.xml https://www.rfc-editor.org/authors/rfc9927.html https://www.rfc-editor.org/authors/rfc9927.pdf https://www.rfc-editor.org/authors/rfc9927.txt Diff file of the text: https://www.rfc-editor.org/authors/rfc9927-diff.html https://www.rfc-editor.org/authors/rfc9927-rfcdiff.html (side by side) Diff of the XML: https://www.rfc-editor.org/authors/rfc9927-xmldiff1.html Tracking progress ----------------- The details of the AUTH48 status of your document are here: https://www.rfc-editor.org/auth48/rfc9927 Please let us know if you have any questions. Thank you for your cooperation, RFC Editor -------------------------------------- RFC9927 (draft-ietf-6lo-updating-rfc-8928-05) Title : Fixing the C-Flag in the Extended Address Registration Option (EARO) Author(s) : P. Thubert, A. Rashid WG Chair(s) : Shwetha Bhandari, Carles Gomez Area Director(s) : Erik Kline, Éric Vyncke -- Pascal Informativa Privacy - Ai sensi del Regolamento (UE) 2016/679 si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio in parola Le fosse pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie. Privacy Information - This message, for the Regulation (UE) 2016/679, may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
