[Other] SCS-0128 vs. SCS-0126

It came to my attention that in SCS-0128 we have these tempest tests regarding floating ips:

tempest.api.network.test_floating_ips.FloatingIPTestJSON.test_create_floating_ip_specifying_a_fixed_ip_address[id-36de4bd0-f09c-43e3-a8e1-1decc1ffd3a5]
tempest.api.network.test_floating_ips.FloatingIPTestJSON.test_create_update_floatingip_with_port_multiple_ip_address[id-45c4c683-ea97-41ef-9c51-5e9802f2f3d7]
tempest.api.network.test_floating_ips.FloatingIPTestJSON.test_floating_ip_delete_port[id-e1f6bffd-442f-4668-b30e-df13f2705e77]
tempest.api.network.test_floating_ips.FloatingIPTestJSON.test_floating_ip_update_different_router[id-1bb2f731-fe5a-4b8c-8409-799ade1bed4d]

(see here: https://github.com/SovereignCloudStack/standards/blob/2a52e2d601e1987a18a95214918278763db076ca/Tests/iaas/scs_0128_e2e_testing/tempest-tests-non-admin.lst#L141-L144)

The Draft Standard for Networking (SCS-0126-V1) actually says:

External Addresses
We define an external address as an IPv4 or IPv6 address that is accessible to a user of the SCS-compliant OpenStack API. For public clouds, external addresses MUST be either IPv4 public addresses or IPv6 global unicast addresses (GUA).

The CSP MUST offer allocation of external IPv6 addresses to user projects. The CSP SHOULD offer allocation of external IPv4 addresses to user projects.

(https://docs.scs.community/standards/scs-0126-v1-provider-networks#external-addresses)

From my understanding this makes IPv4 optional, while our tempest end-to-end test require IPv4.

I have the feeling we should solve this before SCS-0126 is stabilized and becomes part of a future certificate scope.