Re: [mif] New Version Notification for draft-reddy-mif-dhcpv6-precedence-ops-02.txt

Ted Lemon <Ted.Lemon@nominum.com> Tue, 23 October 2012 15:52 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E79B311E80CC for <mif@ietfa.amsl.com>; Tue, 23 Oct 2012 08:52:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.504
X-Spam-Level:
X-Spam-Status: No, score=-106.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gTiN1cBo0Nhb for <mif@ietfa.amsl.com>; Tue, 23 Oct 2012 08:52:41 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8750A11E80D1 for <mif@ietf.org>; Tue, 23 Oct 2012 08:52:33 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKUIa9Qcjp68woi0NoMFTcg57LYVAxwjhq@postini.com; Tue, 23 Oct 2012 08:52:40 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B50D41B82F4 for <mif@ietf.org>; Tue, 23 Oct 2012 08:52:32 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A921219005C; Tue, 23 Oct 2012 08:52:32 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0247.003; Tue, 23 Oct 2012 08:52:27 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [mif] New Version Notification for draft-reddy-mif-dhcpv6-precedence-ops-02.txt
Thread-Index: AQHNrS3iW6gFvmNkqUiZ8bkm+bpnwpfB+fWAgAATB4CAAXzwgIAAAbKAgAOP3wCAAGxKgA==
Date: Tue, 23 Oct 2012 15:52:25 +0000
Message-ID: <896E858D-BF41-4100-9E63-EE07B0D74DA6@nominum.com>
References: <913383AAA69FF945B8F946018B75898A1480EDFA@xmb-rcd-x10.cisco.com> <7E99AA25-66C2-4A4D-B251-0E71F31FBA26@nominum.com> <913383AAA69FF945B8F946018B75898A148124F2@xmb-rcd-x10.cisco.com> <09806E4D-E6BA-431A-9BB4-F59AD64885A7@nominum.com> <913383AAA69FF945B8F946018B75898A14812900@xmb-rcd-x10.cisco.com> <CD611B92-16E5-4836-BF43-DEB9706155CD@nominum.com> <50866262.3050500@gmail.com>
In-Reply-To: <50866262.3050500@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1D96C8967FB42943B2394B5D239C038B@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mif@ietf.org" <mif@ietf.org>, "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Subject: Re: [mif] New Version Notification for draft-reddy-mif-dhcpv6-precedence-ops-02.txt
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 15:52:42 -0000

On Oct 23, 2012, at 5:24 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> It makes sense, but the draft doesn't explain that it is only
> intended for use in managed networks where the suppression of
> privacy is considered acceptable. I think this needs to be stated
> in the Introduction, and the issue of (loss of) privacy needs to
> be discussed in the Security Considerations.

It might be worth mentioning in the security considerations section, but it's worth noting that this option increases the user's privacy, rather than decreasing it; users who are known to the local network get temporary addresses; only those users who haven't yet registered do not.

This would only occur on a network with a security policy that forbade privacy addresses in general.   It's already possible to do that with existing DHCP servers, routers and DHCP clients.

The incremental additional privacy may seem trivial, since the user is still being tracked by the local service provider whether they get privacy addresses or not on this network.   However, the user would at least in principle have real and meaningful privacy from being tracked by their IP address by service providers outside the administrative domain of the local network.