EthernetInterface schema property "DHCPv6OperatingMode"

My understanding is that, the property is used to indicate the state of DHCPv6OperatingMode and allowing user to PATCH the property to the status as they want.
But now there is definition conflict between the redfish schema and wiki's information,
1. Redfish schema mentioned the default when DHCPv6 enable is stateless
2. wiki mentioned the no DHCPv6 involved in this process for Link-local (DHCPv6)

I would like to know if the DHCPv6 with Link-local, what enumeration value (Disable/Stateless) should display?

Hi Jeff,
Thanks for the details.We are clear about IPv6Address below point

But if no DHCPv6 server is located, the IPv6Address entry will show the AddressOrigin as "LinkLocal" (not "DHCPv6").

In above case what will be the value of DHCPv6OperatingMode after system rebooted?
Do we need show DHCPv6OperatingMode attribute value as stateless or disabled or not show DHCPv6OperatingMode attribute in response for Ethernetinterface instance?
If DHCPv6OperatingMode value is stateless means, it will generate IP address without DHCPv6  server(locally) and get remaining configuration from DHCP server as per Schema

"enumLongDescriptions": {

"Disabled": "DHCPv6 shall be disabled for this interface.",

"Stateful": "DHCPv6 shall operate in stateful mode on this interface. DHCPv6 stateful mode is used to configure addresses, and when it is enabled, stateless mode is also implicitly enabled.",

"Stateless": "DHCPv6 shall operate in stateless mode on this interface. DHCPv6 stateless mode allows configuring the interface using DHCP options but does not configure addresses. It is always enabled by default whenever DHCPv6 Stateful mode is also enabled."

}

Stateless is enabled by default whenever Stateful is enabled, but in DHCPv6OperatingMode only stateful is applicable as per above schema definition(not showing Stateless also)
So little bit confused about usage of stateless in DHCPv6OperatingMode , please explain about Stateless OperatingMode

Thanks,
Mani

Hi Jeff,
Thanks for the details
I understand the below point and it's applicable when user patches for required DHCPv6OperatingMode

DHCPv6 object is showing the configuration of that feature, while the contents of the IPv6Addresses (and IPv4Addresses) properties show the actual outcome of the IP config process.

I have three use cases and details below

Case 1
Redfish service is running for first time and gathering  data from all interfaces(user is not patching DHCPv6OperatingMode at this time). In this case AddressOrigin will be showing  as link-local. What value we need to show for DHCPv6OperatingMode in this case?(DHCPv6OperatingMode  value as null or disabled)

Case 2
user is  patching DHCPv6OperatingMode as stateless and after reboot IPV6 address provided by DHCPv6 server  using stateful mode.
AddressOrigin will be DHCv6 (Actual outcome). In this case we need to show DHCPv6OperatingMode as Stateless(Desired configuration) or Stateful(Actual outcome)

Case 3
user is patching DHCPv6OperatingMode as stateful and after reboot IPV6 address provided by DHCPv6 server using stateless mode.

AddressOrigin will be DHCv6 (Actual outcome). In this case we need to show DHCPv6OperatingMode as Stateful(Desired configuration) or Stateless(Actual outcome)
As per my understanding, We can show DHCPv6OperatingMode as Stateful(Desired configuration), since Stateless will be enabled once stateful is applicable as per schema

"DHCPv6 shall operate in stateful mode on this interface. DHCPv6 stateful mode configures addresses, and when it is enabled, stateless mode is also implicitly enabled."

Thanks,
Mani