IETF Logo Mail Archive

Re: Disabling temporary addresses by default?

Ole Troan <otroan@employees.org> Tue, 28 January 2020 19:19 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 943711200DB for <ipv6@ietfa.amsl.com>; Tue, 28 Jan 2020 11:19:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvKhMlDdhv3s for <ipv6@ietfa.amsl.com>; Tue, 28 Jan 2020 11:19:24 -0800 (PST)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5436A1200F6 for <ipv6@ietf.org>; Tue, 28 Jan 2020 11:19:24 -0800 (PST)
Received: from [IPv6:2a01:79d:53aa:d30:d19b:e302:4503:c36d] (unknown [IPv6:2a01:79d:53aa:d30:d19b:e302:4503:c36d]) (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 clarinet.employees.org (Postfix) with ESMTPSA id 209724E11AF0; Tue, 28 Jan 2020 19:19:23 +0000 (UTC)
Content-Type: multipart/alternative; boundary="Apple-Mail-22F31842-57E0-4A9B-8642-A009CA124558"
Content-Transfer-Encoding: 7bit
From: Ole Troan <otroan@employees.org>
Mime-Version: 1.0 (1.0)
Subject: Re: Disabling temporary addresses by default?
Date: Tue, 28 Jan 2020 20:19:19 +0100
Message-Id: <853C8880-A6A2-4F67-996D-02F20C3D3039@employees.org>
References: <45FE2F3C-EA41-4442-A680-C3875D056A89@fugue.com>
Cc: Nick Hilliard <nick@foobar.org>, 6man WG <ipv6@ietf.org>
In-Reply-To: <45FE2F3C-EA41-4442-A680-C3875D056A89@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: iPhone Mail (17D5026c)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FEN13Wjw0o2WeMwA52Lylwp4o-E>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2020 19:19:29 -0000


> On 28 Jan 2020, at 19:31, Ted Lemon <mellon@fugue.com> wrote:
> 
>> On Jan 28, 2020, at 11:51 AM, Nick Hilliard <nick@foobar.org> wrote:
>> in which case you've defeated the entire purpose of the privacy address.
> 
> No, you haven’t.  You just aren’t getting privacy with that connection.  You still get it with all your HTTP connections.   When I ssh into my server at work, they know who I am; this isn’t a problem for me.

We should probably be a bit more careful with terms here. A temporary address does not give the user privileges. It might at best avoid leaking an identifier that can be used to correlate the user’s activity. 

Cheers 
Ole

v2.23.0 | Report a Bug | By Email