poy : your proposal misses the possibility to link the 2 connections to 1 unique client i think.
There can be more then 1 same ip4 or ip6 in the hub already.
Nore the CID gives a uniquenes @ the moment of connecting to the second address there can be already same CID (other client) in the hub who then get a support he should not have ...
Thats exactly why the HBRI is there , there it gives the hub the original's client connection's SID and tolken so it is sure its that client that gets the support for the second ip version.
poy : your proposal misses the possibility to link the 2 connections to 1 unique client i think.
There can be more then 1 same ip4 or ip6 in the hub already.
Nore the CID gives a uniquenes @ the moment of connecting to the second address there can be already same CID (other client) in the hub who then get a support he should not have ...
Thats exactly why the HBRI is there , there it gives the hub the original's client connection's SID and tolken so it is sure its that client that gets the support for the second ip version.