Hello Adnan, Never hesitate to ask a question ;-)
Good question, BTW, my suggestion would be to have all known flags (published and in draft stage) in the 2 drafts. My reasoning is that when published it will be easier for implementers. Normally, before the publication as RFC (i.e., in AUTH48 stage), the IANA and the RFC Editor (and authors & AD) should make a final check anyway. Regards -éric From: Adnan Rashid <adnanrashi...@gmail.com> Date: Tuesday, 15 April 2025 at 13:14 To: Eric Vyncke (evyncke) <evyn...@cisco.com> Cc: 6lo@ietf.org <6lo@ietf.org> Subject: Re: [6lo] Re: I-D Action: draft-ietf-6lo-updating-rfc-8928-00.txt Hi Eric, You are welcome. I have a few questions for my knowledge. Do we need to add the IANA accepted packet/options field in the working I-D, or can we keep fields that are in progress in other I-Ds? What is the rule of IETF? For example, we use the following figure in the above draft (Moving the C Flag in EAR) [cid:ii_m9iejo824] The prefix draft is using the following figure (IPv6 Neighbor Discovery Prefix Registration) [cid:ii_m9iel2ft6] On Tue, Apr 15, 2025 at 8:40 AM Eric Vyncke (evyncke) <evyncke=40cisco....@dmarc.ietf.org<mailto:40cisco....@dmarc.ietf.org>> wrote: Pascal and Adnan, Big big thank you for writing this I-D, it is really needed. Let’s try to get it moving fast (even with my point below). Carles and Shwetha, the IETF process must be followed even for such a short and expedite I-D, i.e., please mark this I-D as not adopted in the data tracker and issue a WG call for adoption (I suggest a 1-week duration for this call for adoption). Let’s all use this call for adoption period to make a review of this short I-D :-) Regards -éric From: internet-dra...@ietf.org<mailto:internet-dra...@ietf.org> <internet-dra...@ietf.org<mailto:internet-dra...@ietf.org>> Date: Monday, 14 April 2025 at 16:06 To: i-d-annou...@ietf.org<mailto:i-d-annou...@ietf.org> <i-d-annou...@ietf.org<mailto:i-d-annou...@ietf.org>> Cc: 6lo@ietf.org<mailto:6lo@ietf.org> <6lo@ietf.org<mailto:6lo@ietf.org>> Subject: [6lo] I-D Action: draft-ietf-6lo-updating-rfc-8928-00.txt Internet-Draft draft-ietf-6lo-updating-rfc-8928-00.txt is now available. It is a work item of the IPv6 over Networks of Resource-constrained Nodes (6LO) WG of the IETF. Title: Moving the C Flag in EARO Authors: Pascal Thubert Adnan Rashid Name: draft-ietf-6lo-updating-rfc-8928-00.txt Pages: 7 Dates: 2025-04-14 Abstract: This document updates RFC 8928, “Address-Protected Neighbor Discovery for Low-Power and Lossy Networks” (AP-ND), by explicitly specifying the bit position for the “C” flag and registering it with IANA. This clarification ensures consistent implementation and interoperability of the AP-ND protocol, which protects against address theft and impersonation attacks in Low-Power and Lossy Networks (LLNs). This update provides a precise definition of the “C” flag’s bit position, enabling correct deployment and verification of AP-ND’s security features. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-6lo-updating-rfc-8928/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-6lo-updating-rfc-8928-00.html Internet-Drafts are also available by rsync at: rsync.ietf.org::internet-drafts _______________________________________________ 6lo mailing list -- 6lo@ietf.org<mailto:6lo@ietf.org> To unsubscribe send an email to 6lo-le...@ietf.org<mailto:6lo-le...@ietf.org> _______________________________________________ 6lo mailing list -- 6lo@ietf.org<mailto:6lo@ietf.org> To unsubscribe send an email to 6lo-le...@ietf.org<mailto:6lo-le...@ietf.org> -- Regards, Adnan
_______________________________________________ 6lo mailing list -- 6lo@ietf.org To unsubscribe send an email to 6lo-le...@ietf.org
