There has been no mention of NAT in this thread as an obscuring technique. There's probably scope for a 'best practices for preserving privacy for carrier grade NATs' or somesuch document -- I doubt much can be done at the low end for a NATted residential 192.168.1.1 network, but CGNAT for millions of users is a very different beast. Lloyd Wood lloyd.wood@xxxxxxxxxxx > On 4 Jan 2023, at 19:59, Antoine FRESSANCOURT <antoine.fressancourt=40huawei.com@xxxxxxxxxxxxxx> wrote: > > Hello, > > IP addresses are indeed topological. As you mentioned, the challenge with making the network layer privacy-preserving is how to route the packet without revealing the source and destination of packets. > > In the literature, there has been two approaches to this challenge: using a set of indirection elements (proxies, onion relays, private relays, you name them) in order to keep a sense of destination-based routing or using a source routing approach so that the source encodes the path to the destination using a sequentially encrypted data structure that is decrypted little by little by the elements relaying the packet. The latter approach is for example demonstrated in Sphinx or Hornet, two academic work in the area of privacy-preserving communications. I think this later approach has not been given enough attention in practical solutions, and I would be interested in working on the challenges raised by such an approach in the realm of the IETF. > > If the data plane becomes anonymous, there is indeed a need to also have privacy in the control plane. In my view, this is less challenging because the timing constraints in the control plane are (a bit) less constraining, and we can use techniques studied in PPM or OHAI WG. For instance, if we adopt the source-routed approach to protect privacy at the IP layer, we need to have a privacy-preserving path computation element of some sort. This element could be developed using techniques from private information retrieval, secure multiparty computation or oblivious transfer. > > Would there be interest in the community to have a document summarizing the state of affairs and remaining challenges of IP layer anonymization? I volunteer to start such a document if there is. > > Best regards, > > Antoine > > -----Original Message----- > From: saag <saag-bounces@xxxxxxxx> On Behalf Of Stewart Bryant > Sent: mercredi 4 janvier 2023 09:06 > To: Dino Farinacci <farinacci@xxxxxxxxx> > Cc: Brian E Carpenter <brian.e.carpenter@xxxxxxxxx>; John Mattsson <john.mattsson=40ericsson.com@xxxxxxxxxxxxxx>; ietf@xxxxxxxx; hrpc@xxxxxxxx; pearg@xxxxxxxx; saag <saag@xxxxxxxx> > Subject: Re: [saag] Ten years after Snowden (2013 - 2023), is IETF keeping its promises? > > For all end to end communications the routing system needs to know how to deliver the packet. Obscuring the mapping between the address and the location moves the anonymisation problem from the data plane to the routing plane. This makes life harder for the observer, but I am not sure that it makes it sufficiently hard as to be worth the cost. One advantage of the topological association of addresses is the intrinsic address aggregation property which both reduces routing traffic overhead and speeds up convergence. > > Stewart > > Sent from my iPad > >> On 3 Jan 2023, at 22:29, Dino Farinacci <farinacci@xxxxxxxxx> wrote: >> >> EIDs are not topological. We have all known this for a very long time. We can make them ephemeral as well, we can make them cryptographic. >> >> Dino >> >>>> On Jan 3, 2023, at 11:38 AM, Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> wrote: >>> >>>> On 03-Jan-23 23:27, John Mattsson wrote: >>>> >>>> IP addresses are still not only long-lived trackable identifiers, but they also reveal your location. >>> >>> IP addressing is intrinsically topological, so this is never going to change. >>> >>> (Temporary IPv6 addresses are not long-lived, but they remain topological.) >>> >>> Brian >>> >>> _______________________________________________ >>> saag mailing list >>> saag@xxxxxxxx >>> https://www.ietf.org/mailman/listinfo/saag >> > > _______________________________________________ > saag mailing list > saag@xxxxxxxx > https://www.ietf.org/mailman/listinfo/saag
