You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ]
You may elaborate why a structure similar to TCP one is not used here:
grouping tcp-client-grouping:
+-- remote-address
+-- remote-port?
+-- local-address?
| {local-binding-supported}?
+-- local-port? inet:port-number | {local-binding-supported}?
(*) also clarify why the case where the remote address is a name is not supported here for UDP.
[ ]
grouping udp-client-grouping
MED: You may explain how to cover the case of multiple addresses/port numbers are used to reach the same server instance. For example, the case of dual-stack.
[ ]
grouping udp-client-grouping
Specifies an IP address of the UDP client. (Or the remote peer?)
udp-server
how to cover when the server is reachable over ipv4 and ipv6
The text was updated successfully, but these errors were encountered:
[ ]
You may elaborate why a structure similar to TCP one is not used here:
grouping tcp-client-grouping:
+-- remote-address
+-- remote-port?
+-- local-address?
| {local-binding-supported}?
+-- local-port? inet:port-number | {local-binding-supported}?
(*) also clarify why the case where the remote address is a name is not supported here for UDP.
[ ]
grouping udp-client-grouping
MED: You may explain how to cover the case of multiple addresses/port numbers are used to reach the same server instance. For example, the case of dual-stack.
[ ]
grouping udp-client-grouping
Specifies an IP address of the UDP client. (Or the remote peer?)
udp-server
how to cover when the server is reachable over ipv4 and ipv6
The text was updated successfully, but these errors were encountered: