Problem description
Currently, application server IP addresses provided in the QoD session creation response just echo the parameters provided in the request. e.g.:
201 Session Created
{
"applicationServer": {
"ipv4Address": "198.51.100.0/24",
"ipv6Address": "2001:db8:85a3:8d3:1319:8a2e:370:7344"
},
...
This is fine when the request parameters are limited to ipv4Address and/or ipv6Address, but could be improved if the additional parameters domainName and possibly ipAddresses are added as proposed in #522, which would require up to 4 parameters to be echoed.
Further, it may be that some IP addresses are specified (possibly indirectly) by multiple parameters.
Possible evolution
The QoD session creation response should provide a consolidated list of all application server IP addresses that are prioritised. This would be constructed from all IP addresses (both IPv4 and IPv4) identified in the request. e.g.:
201 Session Created
{
"applicationServer": {
"ipAddresses": ["198.51.100.0/24", "2001:db8:85a3:8d3:1319:8a2e:370:7344", "2606:4700::6812:1b78", "104.18.26.120"]
},
...
Note that this is a breaking change
Alternative solution
ipv4 and ipv6 addresses could be in separate (and shorter) lists, even though there is no possibility of ambiguity between them.
201 Session Created
{
"applicationServer": {
"ipv4Addresses": ["198.51.100.0/24", "104.18.26.120"],
"ipv6Addresses": ["2001:db8:85a3:8d3:1319:8a2e:370:7344", "2606:4700::6812:1b78"]
},
...
Note that this is still a breaking change
Additional context
None
Problem description
Currently, application server IP addresses provided in the QoD session creation response just echo the parameters provided in the request. e.g.:
This is fine when the request parameters are limited to
ipv4Addressand/oripv6Address, but could be improved if the additional parametersdomainNameand possiblyipAddressesare added as proposed in #522, which would require up to 4 parameters to be echoed.Further, it may be that some IP addresses are specified (possibly indirectly) by multiple parameters.
Possible evolution
The QoD session creation response should provide a consolidated list of all application server IP addresses that are prioritised. This would be constructed from all IP addresses (both IPv4 and IPv4) identified in the request. e.g.:
Note that this is a breaking change
Alternative solution
ipv4 and ipv6 addresses could be in separate (and shorter) lists, even though there is no possibility of ambiguity between them.
Note that this is still a breaking change
Additional context
None