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
..
_static	Neutron Feature Classification	2017-03-15 23:31:58 +00:00
admin	doc: state that O flag can be 0 in dhcpv6-stateful	2023-03-19 20:17:55 +09:00
cli	Remove "vf_management" and "vf_extended_management" checks	2020-07-27 10:47:16 +00:00
configuration	[goal] Deprecate the JSON formatted policy file	2021-01-08 09:10:49 +00:00
contributor	Merge "Add Jens Harbott as Lieutenants in Infra area"	2023-03-14 08:57:12 +00:00
feature_classification	Update Interop doc	2021-11-08 10:42:22 +00:00
install	Fix incorrect mysql examples	2023-01-03 11:16:34 -05:00
ovn	Merge "Rename setup-mtu-t1 argument because it is misleading"	2022-12-22 17:28:00 +00:00
reference	PDF documentation build	2019-08-26 02:50:58 +09:00
_intro.rst	PDF documentation build	2019-08-26 02:50:58 +09:00
conf.py	remove unicode from code	2021-12-24 10:02:03 +08:00
index.rst	Merge networking-ovn documentation into neutron	2020-02-13 18:54:15 +09:00
pdf-index.rst	Merge networking-ovn documentation into neutron	2020-02-13 18:54:15 +09:00