> I don't want everyone to "ping <tom's-computer>" :-) Then you don't make your EID available. But you can source from it.
> Not everyone wants to be easy to find, in fact for privacy it's really When I say "everyone" I mean services you want to make available. And you may not want to make them available to the entire world. > just the opposite. Instead of have one host address, I'd rather have > millions of addresses assigned to my device so that for each You can do that. If the addresses aren't tied to the topology. That is the main point I want to get across. > connection I can use different source address and a third party seeing Yes, in the future, we can use random or crypto addresses. > my packets going to two different destinations couldn't correlate that > they are from the same source and much less that they are from the Right, definitely agree. Just like you use different credit card numbers for each financial transaction. Just like you use different wallet addresses for each crypto transaction. > same individual. This is fixable with IPv6 with it's immense address > space, but it is going to require breaking the concept that an address > conveys both identity and location of a user. Agree. But you don't want the app to store the location part. They means if the location is no longer reachable the app has to know that and take action. The app should run business logic and not networking logic. Dino _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
