Re: Disabling temporary addresses by default?

Tom Herbert <tom@herbertland.com> Wed, 29 January 2020 22:57 UTC

Return-Path: <tom@herbertland.com>
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 6075E120047 for <ipv6@ietfa.amsl.com>; Wed, 29 Jan 2020 14:57:01 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 iWx4nwTWJBsn for <ipv6@ietfa.amsl.com>; Wed, 29 Jan 2020 14:56:58 -0800 (PST)
Received: from mail-ed1-x52b.google.com (mail-ed1-x52b.google.com [IPv6:2a00:1450:4864:20::52b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90E28120044 for <ipv6@ietf.org>; Wed, 29 Jan 2020 14:56:58 -0800 (PST)
Received: by mail-ed1-x52b.google.com with SMTP id r21so1675175edq.0 for <ipv6@ietf.org>; Wed, 29 Jan 2020 14:56:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SXFiIPuC6vK7blZ1RdPqIj+jVFtuT34LrjhR2XQS4co=; b=jot/hmyuUOZOG6y+ONPzy16ztT4rzppSgGfThvR+Xf9yrxyq72kumyULs/ZMCOfrRl HRb202eI1oBjfZaTweU9KVn9HSnvJgxjqQiVwlqzSVbIyT4yDhmMfxGQkjpWqJW24rFF /6UN2oGYyBvxHliv01FWkml+kKR3R46gGs8h75HY7zlfA7mxw+3GUwMZrxcsjfwW1fhJ 65DeNP2VuHORi+GHmJIMZGHXLZiu1ThzQ3NLJZV7pY99E58ucinQXgZlrvYuQa1bEVGn TeWdmKD0C+bxovhlb4tUXqfl2O+rPo0efje2lgyWmVeCV/dLH8bXL7fY06wfOu1RkZwM wpeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SXFiIPuC6vK7blZ1RdPqIj+jVFtuT34LrjhR2XQS4co=; b=o7LpLTK1wBHEWGA6Zj481jQDrDT7/H8tmX43p8AAbGJfCqFHcTEwC4II8zB9gwuxrQ O7JefhxBmd27L87oXIi9RGovaxQPsX1l51goTFKYIL18pSkprTnr3LCB69jZiO3SqUoO J9fTMrshAjhwLIRwnS1zblLdjqgp1yGGfNAfoGPCByq5ig7MeHr9MkINd3qZuU5ZNLnL XUBIYZJK+/9oF6ByX5qxHq/RFRH9ae6eeyY4B/sJaEavAj1eFuoP2QtzZtYPxtBL06/s ZhYK6DBSZ3fMrxWX8CDzlZe9/kbbFC0osEs4PJOBKRSy3x5hjQ501yo5/2AZq+tiSBJg HkLg==
X-Gm-Message-State: APjAAAUYnml8tQ8d3i8B0Zrm1P93haE8pdAMlaMmJTYrjrH/L5fN5IL0 wKGFiH1xsUuOhF6pqw/nuWepgnjiNL40VOLHFmFWI2f7
X-Google-Smtp-Source: APXvYqwfITJFQKM44msTbl/KOKa0N7pIaf14+ezsE54FA3aevHDOjsEtafCuwZXqoSRCgo4h+UXf59+eiZUhrsE4stQ=
X-Received: by 2002:a17:906:55d3:: with SMTP id z19mr1538591ejp.304.1580338616877; Wed, 29 Jan 2020 14:56:56 -0800 (PST)
MIME-Version: 1.0
References: <56BD2286-D761-44EF-812B-82BAFB380992@employees.org> <0163A2F7-7874-43BF-B0CE-E83D62A92123@puck.nether.net> <B72F96B6-9B19-4832-8636-B86A6ED01402@employees.org>
In-Reply-To: <B72F96B6-9B19-4832-8636-B86A6ED01402@employees.org>
From: Tom Herbert <tom@herbertland.com>
Date: Wed, 29 Jan 2020 14:56:45 -0800
Message-ID: <CALx6S368GQ=RskeDfFLJ+6jOArZ6EKGP1qE=sTFejFhmt9RjOA@mail.gmail.com>
Subject: Re: Disabling temporary addresses by default?
To: Ole Troan <otroan@employees.org>
Cc: 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pvcqkQg16x5GUre8F2nT7AVbd3s>
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: Wed, 29 Jan 2020 22:57:01 -0000

On Wed, Jan 29, 2020 at 3:49 AM <otroan@employees.org> wrote:
>
> >> Enterprises use web proxies and SSL intercepting gateways anyway, don't they (sigh).
> >
> > Some do. I've worked places that did for non-SSL. Keep in mind the operator of that network tends to only allow devices managed by them so they are not user devices. A user generally has no right to privacy on equipment they do not own.
> >
> > (This is a controversial position to state in the IETF but is still valid).
>
> And just to be clear. I am not against a document specifying temporary addresses.
> The IETF published RFC3041 back in 2001, as a response to information leakage caused by EUI-64 based IIDs.
> Quite a lot has changed since then. I am trying to get some answers to the following questions:
>
>  - what are the operational consequences of temporary addresses
>  - how effective are temporary addresses in making correlation harder?
>  - are applications clever enough to not re-use tainted addresses for example?
>  - do protocols like ICE, MPTCP, QUIC bundle together stable and temporary addresses?
>  - implementations that allow for the use of many addresses might get into trouble with the network,
>    can they deal with those failure cases in an acceptable way?
>
> 4941bis is being demoted to proposed standard. Which means we might live with these questions being unanswered, but I think we need to have some of the discussion around these in the deployment considerations.
> And the issues with temporary addresses might still warrant that we keep the general recommendation of off by default. TBD.

Ole,

I agree these are important questions, I would also add that there
should be more discussion and analysis as to the real effect that
temporary addresses has had on privacy in addressing-- specifically,
whether temporary addresses as defined in RFC4941 has sufficiently
addressed the problem posed in the Problem Statement (section 1.2 of
that RFC).

Tom

>
> Best regards,
> Ole
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------