radvd.conf.5.man is wrong about M/O flags documented in RFC 4862

[Zocker1999NET]

to quote from the man page:

radvd/radvd.conf.5.man

Lines 272 to 289 in f2de476

	.TP
	.BR AdvManagedFlag " " on | off
	When set, hosts use the administered (stateful) protocol for address
	autoconfiguration in addition to any addresses autoconfigured using
	stateless address autoconfiguration. The use of this flag is
	described in RFC 4862.
	Default: off
	.TP
	.BR AdvOtherConfigFlag " " on | off
	When set, hosts use the administered (stateful) protocol for
	autoconfiguration of other (non-address) information. The use of
	this flag is described in RFC 4862.
	Default: off

The man page states that the Managed & OtherInformation flags are documented in RFC 4862. However, this does not seem the case. Quoted from RFC 4862, Appendix C:

• Removed the text regarding the M and O flags, considering the maturity of implementations and operational experiences. ManagedFlag and OtherConfigFlag were removed accordingly. (Note that this change does not mean the use of these flags is deprecated.)

I do not have a better source for information yet, as I’m trying myself to find out which of these flags is supposed to be set when having DHCPv6 in prefix delegation mode only.

[heliosfa]

RFC4861, Section 4.2 is likely the correct reference.

RFC5175 Section 3 has a list of where all of the other flags come from.

as I’m trying myself to find out which of these flags is supposed to be set when having DHCPv6 in prefix delegation mode only.

Reading RFC7084 Section 4.2:

WPD-4: By default, the IPv6 CE router MUST initiate DHCPv6 prefix
delegation when either the M or O flags are set to 1 in a
received Router Advertisement (RA) message. Behavior of the
CE router to use DHCPv6 prefix delegation when the CE router
has not received any RA or received an RA with the M and the
O bits set to zero is out of scope for this document.

[stappersg]

On Tue, Dec 10, 2024 at 05:38:41PM -0800, Graeme Bragg wrote: [RFC4861, Section 4.2](https://datatracker.ietf.org/doc/html/rfc4861#section-4.2) is likely the correct reference. [RFC5175 Section 3](https://datatracker.ietf.org/doc/html/rfc5175#section-3) has a list of where all of the other flags come from.

Patches welcome