Hello Mahesh and Adnan, Let me reply about putting an I-D on the next IESG telechat while the I-D was still in IETF Last Call. I have tried to explain it in my original YES ballot (updated yesterday), but basically it boils down to:
1. This I-D is related to draft-ietf-6lo-prefix-registration-11<https://datatracker.ietf.org/doc/draft-ietf-6lo-prefix-registration/> , which is on the same telechat and I wanted to ease the ‘context switching’ task of my fellow ADs and ensure consistency 2. The IETF Last Call was concluded on Monday 2nd of June; this should leave enough time to the IESG to review a 7-page document before Thursday 5th. 3. Based on the content of the I-D, I was not expecting *technical* changes in the I-D after the IETF Last Call, only *editorial* (like the ones based on your review – thank you for it) I hope this clarifies the situation (and I have seen this happening in previous telechats), I think this is between the lines, but I agree that having only 3 days between the end of the IETF Last Call and the IESG telechat is unusual and I would not mind if any AD pressed the ‘defer’ button. Regards -éric From: Adnan Rashid <[email protected]> Date: Monday, 2 June 2025 at 23:09 To: The IESG <[email protected]>, Mahesh Jethanandani <[email protected]>, Eric Vyncke (evyncke) <[email protected]> Cc: [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]> Subject: Re: Mahesh Jethanandani's No Objection on draft-ietf-6lo-updating-rfc-8928-04: (with COMMENT) Dear Mahesh, Thanks for the time and effort you put in my comments are inline ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- It is unusual, but I find this statement under the ballot text. "This document has not completed IETF Last Call. Please do not issue the ballot early without good reason. This document is in an IESG state of "In Last Call". It would be unexpected to issue a ballot while in this state". I know the document is short, and is a quick fix, but is this expected? @Eric Vyncke<mailto:[email protected]> please have a look ------------------------------------------------------------------------------- NIT ------------------------------------------------------------------------------- All comments below are about very minor potential issues that you may choose to address in some way - or ignore - as you see fit. Some were flagged by automated tools (via https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flarseggert%2Fietf-reviewtool&data=05%7C02%7Cadnan.rashid%40poliba.it%7C0ef6fba43349423ae40708dda14c628a%7C5b406aaba1f14f13a7aadd573da3d332%7C0%7C0%7C638844071630170054%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=a4vHUmqePiD932mwZbDxTB98PPRQ%2FQOyNZGqzjYOy5Q%3D&reserved=0)<https://github.com/larseggert/ietf-reviewtool>, so there will likely be some false positives. There is no need to let me know what you did with these suggestions. Section 2.2, paragraph 0 > This document uses terms and concepts that are discussed in Neighbor > Discovery (ND) for IPv6 [RFC4861], [RFC4862] and Subnet ND [RFC6775], > [RFC8505] [RFC8928], [RFC8929] [RFC9685], and > [I-D.ietf-6lo-prefix-registration]. One too many ands in the statement. Maybe: s/[RFC4682] and Subnet ND/[RFC4682], Subnet ND/ Its RFC4862. Yes you are right that sentence was not in a correct form. I changed like this This document uses terms and concepts that are discussed in IPv6-Neighbor Discovery (ND) [RFC4861], [RFC4862], as well as 6LoWPAN-ND [RFC6775], [RFC8505] [RFC8928], [RFC8929] [RFC9685], and [I-D.ietf-6lo-prefix-registration]. Reference entries duplicated in both normative and informative sections: [RFC8929]. I am unable to find any duplication. May be you are confused/github tool with RFC8929 and RFC8928. Uncited references: [RFC4861], [RFC6775], [RFC4862], and [RFC8929]. As noted in your earlier comment, these references are cited in Section 2.2. Since they are not required elsewhere in the document. 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.
_______________________________________________ 6lo mailing list -- [email protected] To unsubscribe send an email to [email protected]
