[auth48] Re: AUTH48: RFC-to-be 9927 for your review

Wed, 28 Jan 2026 12:43:19 -0800

Hello Alice and Adnan 

I volière this version is ready for publication.

Many thanks!

Pascal

Le 28 janv. 2026 à 09:45, Adnan Rashid <[email protected]> a écrit :


From my side ok.



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: Alice Russo <[email protected]>
Sent: Wednesday, January 28, 2026 02:28
To: Pascal Thubert <[email protected]>; Adnan Rashid <[email protected]>
Cc: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; Eric Vyncke (evyncke) <[email protected]>; auth48archive <[email protected]>; RFC Editor <[email protected]>
Subject: Re: AUTH48: RFC-to-be 9927 <draft-ietf-6lo-updating-rfc-8928-05> for your review
 
Authors,

Thank you for your replies. Please see the follow-ups below. The revised files are here (please refresh):
  https://eur03.safelinks.protection.outlook.com/?url="">
  https://eur03.safelinks.protection.outlook.com/?url="">
  https://eur03.safelinks.protection.outlook.com/?url="">
  https://eur03.safelinks.protection.outlook.com/?url="">

- Adnan, good catch; updated 2.2 to "Related Documents".

- Re: #3, <strong> has been removed, in keeping with RFC-to-be 9926.

This diff file shows all changes from the approved I-D:
  https://eur03.safelinks.protection.outlook.com/?url="">
  https://eur03.safelinks.protection.outlook.com/?url=""> (side by side)

This diff file shows the changes made during AUTH48 thus far:
  https://eur03.safelinks.protection.outlook.com/?url="">
  https://eur03.safelinks.protection.outlook.com/?url=""> (side by side)

We will wait to hear from you again before continuing the publication
process. This page shows the AUTH48 status of your document:
  https://eur03.safelinks.protection.outlook.com/?url="">

Thank you.

Alice Russo
RFC Production Center

> On Jan 27, 2026, at 3:37 AM, Adnan Rashid <[email protected]> wrote:
>
> Dear RFC Editor,
>
> ++ @Pascal Thubert 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
>

> On Jan 27, 2026, at 1:55 AM, Pascal Thubert <[email protected]> wrote:
>
> 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]> 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://eur03.safelinks.protection.outlook.com/?url="">. -->
>
>
> 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://eur03.safelinks.protection.outlook.com/?url="">
>               icmpv6-parameters/icmpv6-parameters.xhtml#p-field-values.
>
> Current:
>    [IANA.ICMP.ARO.P-FIELD]
>               IANA, "P-Field Values",
>               <https://eur03.safelinks.protection.outlook.com/?url="">>.
> -->   
>
>
> 5) <!-- [rfced] Please review the "Inclusive Language" portion of the online
> Style Guide <https://eur03.safelinks.protection.outlook.com/?url="">>
> 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
>

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]

Reply via email to