2 ms·
If you want to implement what in the OSI model we call "session" state, you are almost certainly doing it because of transport agility. It winds up demanding so
by ggm 4y ago
If you want to implement what in the OSI model we call "session" state, you are almost certainly doing it because of transport agility. It winds up demanding something morally in the space of an ID.
If the ID can be used to find you on diferent link layers, cross-platform, and if the ID has a locator or 'ARP' like service, its almost inevitable it leaks. Simply asking who is on a substrate probably naturally leads to "who are you" queries which go to exposing session state, to anyone who can tickle you.