established to the target and if applicable via that path this is done as follows the data shown in fig1 4 are contained in the data for the ice candidates the following are also known the host addresses u201c base u201d for both partners the server reflexive address es depending on whether only one or both endpoints are located behind nat the turn server and turn relayed addresses if turn is involved address and path groups for which the same qos criteria apply are generated from these values it is not always helpful to maintain statistical data for every contacted partner endpoint ep 1 epn for which only the host addresses ha 1 and ha 2 for endpoints ep 1 and ep 2 are shown since the resulting data volumes can become rather large it is therefore possible to define groups of endpoints to which the same predictions may apply then data only need to be maintained by group in this case an ip subnet can be defined as such a group because the paths through a network are generally defined at the subnet level in the routers however the host addresses that have been typically transmitted in prior systems do not contain any reference to the subnet here an expansion to the network suffix e g u201c 24 u201d ipv4 or ipv6 or the subnet mask e g u201c 255 255 2550 u201d ipv4 only is recommended in order to comprehensively solve this problem it is different for the nat devices server reflexive addresses and turn servers turn server and relay addresses there are comparatively few of these devices which must be considered individually depending on the connection scenario see fig1 to fig3 the.