IPv6StaticAddresses attribute in EthernetInterfaces URI

muthumariu
Minnow

Posts: 3

IPv6StaticAddresses attribute in EthernetInterfaces URI Aug 8, 2024 7:30:53 GMT

Quote

Post by muthumariu on Aug 8, 2024 7:30:53 GMT

Hi All,

I want clarification on IPv6StaticAddresses attribute in Ethernet Interfaces URI.

Scenario 1 :

1. Initially IPv6 in DHCP mode and I am trying to change the mode to static with static ipv6 addresses with below request body

Request Body

{

    "DHCPv6": {

        "OperatingMode": "Disabled"

    },

    "IPv6StaticAddresses": [

    {

        "Address": "3001:df24:df25:df26::6458:5da1:4805",

        "PrefixLength": 64

    },

    {

        "Address": "3001:df24:df25:df26::6458:5da1:4806",

        "PrefixLength": 64

    },

    {

        "Address": "3001:df24:df25:df26::6458:5da1:4807",

        "PrefixLength": 64

    }

    ]

}

Question1 :

Once patch got applied in response, order of the Addresses are getting changed as showing below, can you please confirm whether this behavior is correct or we need to show the order as same as request body order?

{
    "DHCPv6": {

        "OperatingMode": "Disabled"
    }
    "IPv6StaticAddresses": [

    {

        "Address": "3001:df24:df25:df26:0:6458:5da1:4807",

        "PrefixLength": 64

    },

    {

        "Address": "3001:df24:df25:df26:0:6458:5da1:4806",

        "PrefixLength": 64

    },

    {

        "Address": "3001:df24:df25:df26:0:6458:5da1:4805",

        "PrefixLength": 64

    }

    ]
}

Scenario 2 :

In this scenario IPv6 in static mode with the below IPv6StaticAddresses (values are updated from Scenario 1st requestbody) :

Response Body

{

"DHCPv6": {

"OperatingMode": "Disabled"

}

"IPv6StaticAddresses": [

{

"Address": "3001:df24:df25:df26:0:6458:5da1:4807",

"PrefixLength": 64

},

{

"Address": "3001:df24:df25:df26:0:6458:5da1:4806",

"PrefixLength": 64

},

{

"Address": "3001:df24:df25:df26:0:6458:5da1:4805",

"PrefixLength": 64

}

]

}

Question 2 :

I am giving the patch request with the below body

{

"IPv6StaticAddresses": [

    {}

]

}

After giving patch request , please give clarification for what are all the "Addresses" we need to show under "IPv6StaticAddresses" attribute ?

Scenario 3 :

In this scenario also IPv6 in static mode with the below IPv6StaticAddresses (values are updated from Scenario 1st requestbody) :

Response Body

{

"DHCPv6": {

"OperatingMode": "Disabled"

}

"IPv6StaticAddresses": [

{

"Address": "3001:df24:df25:df26:0:6458:5da1:4807",

"PrefixLength": 64

},

{

"Address": "3001:df24:df25:df26:0:6458:5da1:4806",

"PrefixLength": 64

},

{

"Address": "3001:df24:df25:df26:0:6458:5da1:4805",

"PrefixLength": 64

}

]

}

Question 3 :

Now I am giving the request body as below

{

    "IPv6StaticAddresses": [

    {},

    {

        "Address": "3001:df24:df25:df26::6458:5da1:4808",

        "PrefixLength": 64

    },

    null
    ]

}

In this time how we need to show the response once the above request body is applied ?

Kindy check and give the clarification for the above three scenario and respective questions mentioned in here.

Thanks,

Muthu Mari U.

mraineri
Administrator

Posts: 1,132

IPv6StaticAddresses attribute in EthernetInterfaces URI Aug 8, 2024 12:58:15 GMT

Quote

Post by mraineri on Aug 8, 2024 12:58:15 GMT

For scenario 1, I would not expect a different array order after the operation. Arrays are defined as "ordered" in the JSON RFC, so the service is expected to maintain the client's ordering.

For scenario 2, you specified a single empty object as array index 0, signifying the user wants to preserve that array index. This is per the following statement in the "PATCH on array properties" clause:

> Within a PATCH request, the service shall accept null to remove an element, and accept an empty object {} to leave an element unchanged.

Since the client did not send any other array members, that would indicate truncating the rest of the data for the property. This is also described in the "PATCH on array properties" clause:

> A PATCH request with fewer elements than in the current array shall remove the remaining elements of the array.

So, the IPv6StaticAddresses property would contain:

"IPv6StaticAddresses": [
    {
        "Address": "3001:df24:df25:df26:0:6458:5da1:4807",
        "PrefixLength": 64
    }
]

For scenario 3, similar to the previous scenario, the usage of an empty object indicates the client wants to preserve array index 0. The second member of the array indicates the user is attempting to apply new values for array index 1. The third member indicates removing array index 2. Since this is the last member of the array, all other members of the array beyond index 2 are removed. Technically the client could have provided the request without the null and achieve the same result since the null in the request is the last member of the array in their request.

So, the IPv6StaticAddresses property would contain:

"IPv6StaticAddresses": [
    {
        "Address": "3001:df24:df25:df26:0:6458:5da1:4807",
        "PrefixLength": 64
    },
    {
        "Address":  "3001:df24:df25:df26::6458:5da1:4808",
        "PrefixLength": 64
    }
]

muthumariu Minnow Posts: 3	IPv6StaticAddresses attribute in EthernetInterfaces URI Aug 9, 2024 6:29:06 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by muthumariu on Aug 9, 2024 6:29:06 GMT Got it! Thanks for your suggestion.

IPv6StaticAddresses attribute in EthernetInterfaces URI

Post by muthumariu on Aug 8, 2024 7:30:53 GMT

Post by mraineri on Aug 8, 2024 12:58:15 GMT

Post by muthumariu on Aug 9, 2024 6:29:06 GMT