Yamato Tanaka c97dcfd03f doc: state that O flag can be 0 in dhcpv6-stateful ... The current document states that O flag will be 1 when ipv6_ra_mode is dhcpv6_stateful, but the actual implementations of both ml2/OVS and ml2/OVN set O flag to 0 according to the following implementations: ML2/OVS f545c002dc/neutron/agent/linux/ra.py (L53-L55) ML2/OVN a5238e6234/controller/pinctrl.c (L3733-L3734) a5238e6234/lib/actions.c (L3349-L3350) This actual behavior looks correct because O flag can be either 1 or 0 when M flag is 1, according to the following statement of RFC 4861: https://www.rfc-editor.org/rfc/rfc4861#section-4.2 If the M flag is set, the O flag is redundant and can be ignored because DHCPv6 will return all available configuration information. To make consistency between the documet and actually behavior, this commit changes the document to state that O flag can be either 1 or 0 when ipv6_ra_mode is dhcpv6_stateful. Closes-Bug: #2011687 Change-Id: Id61031d7e707d0ba7b007bae0c9e0f59b8b40f8b		2023-03-19 20:17:55 +09:00
..
source	doc: state that O flag can be 0 in dhcpv6-stateful	2023-03-19 20:17:55 +09:00
Makefile	Merge from launchpad quantum/diablo branch:	2011-09-23 20:17:44 -07:00
requirements.txt	Fix requirements for doc build	2022-07-05 10:26:08 +02:00