Re: New Version Notification for draft-troan-6man-universal-ra-option-03.txt

[[e-mail]]

> The architectural change that this brings, is that no longer is changes to router operating systems or the host stack kernel required.
> 
> I don't see how this is an advantage of this particular proposal. Changing RA options is possible today; there is nothing stopping an implementation such as radvd from allowing the user to configure arbitrary options. For hosts, Linux already has the ability to pass arbitrary RA options to userspace via the RTM_NEWNDUSEROPT netlink message which contains the option. And of course, it's possible to get the raw RA in userspace via a packet socket. Other OSes almost certainly provide the latter.

Not without hijacking the numbering space.

This draft was experimental previously, for this reason. What would be the consequence of the IETF letting go of control.
How much standardisation is required depends very much on the configuration information. E.g. I doubt that RFC3898 information has much consequence apart from between the network operator and whatever daemon running on the hosts. While other configuration information has wider consequences, and may or may not benefit from being standardized.
This option proposes an opaque transport mechanism that makes it optional to involve the IETF or not. Is that scary for people in the IETF... likely. ;-)

Best regards,
Ole