IETF Logo Mail Archive

Re: [Pearg] Ten years after Snowden (2013 - 2023), is IETF keeping its promises?

Fernando Gont <fernando@gont.com.ar> Thu, 12 January 2023 10:23 UTC

Return-Path: <fernando@gont.com.ar>
X-Original-To: pearg@ietfa.amsl.com
Delivered-To: pearg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAE5EC14CEED for <pearg@ietfa.amsl.com>; Thu, 12 Jan 2023 02:23:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u0O7G-VF9SnW for <pearg@ietfa.amsl.com>; Thu, 12 Jan 2023 02:23:49 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19E58C14CF16 for <pearg@irtf.org>; Thu, 12 Jan 2023 02:23:49 -0800 (PST)
Received: from [10.0.0.133] (unknown [186.19.8.47]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 552382805C0; Wed, 4 Jan 2023 07:54:12 -0300 (-03)
Message-ID: <f0adf84d-642e-ec85-630e-0b147741e741@gont.com.ar>
Date: Wed, 04 Jan 2023 07:54:08 -0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
To: Christopher Wood <caw@heapingbits.net>, John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>
Cc: "pearg@irtf.org" <pearg@irtf.org>
References: <HE1PR0701MB305098F652DBC34E3C40810B89F49@HE1PR0701MB3050.eurprd07.prod.outlook.com> <FA814364-6745-497E-B61A-FA2589797D18@heapingbits.net>
Content-Language: en-US
From: Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <FA814364-6745-497E-B61A-FA2589797D18@heapingbits.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/pearg/u9hWDguLWA2ahSQnva--lhsOoVs>
Subject: Re: [Pearg] Ten years after Snowden (2013 - 2023), is IETF keeping its promises?
X-BeenThere: pearg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Privacy Enhancements and Assessment Proposed RG <pearg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/pearg>, <mailto:pearg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pearg/>
List-Post: <mailto:pearg@irtf.org>
List-Help: <mailto:pearg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/pearg>, <mailto:pearg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Jan 2023 10:23:53 -0000

On 3/1/23 13:13, Christopher Wood wrote:
[...]
>>
>> - IP layer: While the transport layer and application layer has seen significant improvements such as QUIC and HTTP/3 and the link layer has seen improvements with MAC randomization, not much has happened at the Internet layer. IP addresses are still not only long-lived trackable identifiers, but they also reveal your location.

As noted by Brian, IP addresses are topologically-dependent identifiers 
-- by the very definition of "address".

Dunno how to gauge the work, but there has been a fair share of work in 
this area:

  * RFC7217: Replacement algorithm for SLAAC IID generation
  * RFC8064: Recommendation to use RFC7217
  * RFC7721: Analysis of privacy implications of IP addresses
  * RFC8981: Revision of the temporary addresses specification

The above was meant to address issues in the existing schemes, and 
RFC7217 is implemented in virtually all popular client operating 
systems. OTOH, the more recent RFC8981 already ships with OpenBSD and is 
implemented by the Linux kernel.

Oh, there's also this Internet-Draft: 
https://datatracker.ietf.org/doc/html/draft-gont-v6ops-ipv6-addressing-considerations


Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar
PGP Fingerprint: 7F7F 686D 8AC9 3319 EEAD C1C8 D1D5 4B94 E301 6F01

v2.28.0 | Report a Bug | By Email | System Status