Hi Pascal, Thanks for the feedback and time you gave during IETF. We will get back to you soon.
Regards, AR On Fri, Jul 25, 2025, 12:53 Pascal Thubert <[email protected]> wrote: > Dear all > > I made a pass on the current version of the draft and have a number of > high level comments / proposals. > > 1) use the P field as in the registration to indicate whether the node > requests an address or a prefix. In the future, the method could be > extended to obtain an anycast address or a multicast address associated > with a named resource. > > 2) not to overload the status in the response. The prefix length may be > indicated in a currently reserved space in the GAAO > > 3) optionally use the address field in the request to indicate the prefix > from which the address should be derived. If not provided, indicate that > the address returned is implicitly used on the interface which was used to > make the request > > 4) return a prefix length for an address (e.g., /64) if the prefix is on > link so the node may create a connected route > > 5) in the protocol operation, be clear on what is done for all types of > requests, then what is specific for address, and what is specific for a > prefix. In the text sometimes the term request is associated with "address" > and sometimes with "address or prefix", though in places the intent in the > former case appears to be for prefixes as well.. > > 6) consider using a bit in the request to indicate that the router should > register the address or prefix without a second round (Ratification Phase). > The router would pick the missing EARO field from a default and return the > complete EARO to indicate that the registration succeeded. In that case, > maybe add also an "R bit" to the GAAO like the one in the EARO and rename > the current R bit to avoid confusion. > > 7) change the term Ratification Phase to "registration phase" with a ref > to RFC 8505 and the prefix registration draft. > > I suggest we also start thinking of providing a name (like mDNS) in the > request to ask the router to publish the association of the name and > address. This will be useful for multicast and anycast as well. > > I hope this helps > > -- > Pascal > _______________________________________________ > 6lo mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ 6lo mailing list -- [email protected] To unsubscribe send an email to [email protected]
