Dear all: I added some text in section 3 to cover Carles' point about NS vs NA EARO format. I actually made the 2 figures to illustrate that the Status is 6 bits since RFC 9010.
Le mar. 13 mai 2025 à 07:51, Carles Gomez Montenegro <[email protected]> a écrit : > Dear Adnan, > > Thanks for your response. > > Please find below my inline comments: > > On Mon, 12 May 2025 at 15:38, Adnan Rashid <[email protected]> wrote: > >> Dear Carles, >> >> Thanks for the review. We will update the draft soon. >> >> I have two questions >> >> - Figure 1: there are two different bits called 'R'. Please consider >> renaming the reserved bit with a letter other than 'R'. >> >> We used the small letter "r". Please let me know if the IETF/WG is ok >> with this. if not then suggest any other. >> >> > Do you mean you are considering to use "r" in the update you are > preparing, and for the "reserved" bit? > > Well, "r" is better than the previous "R", but I am unsure if it is > sufficiently different. Once I used "V" (from "reserVed"), but we are > entering some subjective realm here. > > >> As we update RFC 8928, should we explicitly notify readers about the >> previously incorrect caption name 'Enhanced Address Registration Option' >> and clarify that the correct term is 'Extended Address Registration Option >> (EARO)'? If yes then we will update it in Section 3. >> >> > I don't think so. The term is actually the same either way, and once the > acronym EARO has been defined in the main text, then I understand it is not > strictly necessary to define it again in a figure caption. Nevertheless, > the RFC Editor will eventually address this if necessary (e.g., if there > are special rules for acronyms in figure captions I am not aware of). > > Cheers, > > Carles > > >> On Tue, 29 Apr 2025 at 16:38, Shwetha <[email protected]> wrote: >> >> Hi All, >> >> This email initiates a Working Group Last Call (WGLC) for >> draft-ietf-6lo-updating-rfc-8928-01 [1]. The Last Call will run for 2 >> weeks, ending on Wednesday, May 14, 2025. >> >> This document updates RFC 8928 [2], “Address-Protected Neighbor Discovery >> for Low-Power and Lossy Networks” (AP-ND), by updating the bit >> position for the C-flag and registering it with IANA. >> The authors have addressed the initial set of comments received since the >> draft was adopted. >> >> Please send your comments, feedback, and reviews to the mailing list >> before the end of the Last Call. >> >> Thank you! >> Carles and Shwetha >> >> [1] >> https://www.ietf.org/archive/id/draft-ietf-6lo-updating-rfc-8928-01.txt >> [2] https://www.rfc-editor.org/rfc/rfc8928.txt >> >> 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. >> > All the best -- Pascal
_______________________________________________ 6lo mailing list -- [email protected] To unsubscribe send an email to [email protected]
