Re: [dhcwg] MAC Address Tracking via DHCP6

Ted Lemon <Ted.Lemon@nominum.com> Fri, 01 February 2013 15:49 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24CD71F0D05; Fri, 1 Feb 2013 07:49:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.511
X-Spam-Level:
X-Spam-Status: No, score=-106.511 tagged_above=-999 required=5 tests=[AWL=0.088, 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 IPz+jw41-kpM; Fri, 1 Feb 2013 07:49:08 -0800 (PST)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id CC7801F0CF8; Fri, 1 Feb 2013 07:49:03 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUQvj74WmNcpxHh+Vi/qCBUvU7DP0yCQf@postini.com; Fri, 01 Feb 2013 07:49:03 PST
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 6D715128008; Fri, 1 Feb 2013 07:49:03 -0800 (PST)
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 646CD190043; Fri, 1 Feb 2013 07:49:03 -0800 (PST) (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.0318.004; Fri, 1 Feb 2013 07:49:03 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Chuck Anderson <cra@WPI.EDU>
Thread-Topic: [dhcwg] MAC Address Tracking via DHCP6
Thread-Index: AQHN/9giM3WALPSOxEqXmVcvCQGGwZhkq+IggAB9qoCAAIJYAIAAAdgA
Date: Fri, 01 Feb 2013 15:49:03 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630747479218@mbx-01.win.nominum.com>
References: <282BBE8A501E1F4DA9C775F964BB21FE519D1A74F3@GRFMBX704BA020.griffon.local> <B14A62A57AB87D45BB6DD7D9D2B78F0B114EDEDF@xmb-rcd-x06.cisco.com> <20130201154226.GJ22295@angus.ind.WPI.EDU>
In-Reply-To: <20130201154226.GJ22295@angus.ind.WPI.EDU>
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="Windows-1252"
Content-ID: <C820B7F9D51CF14C94973CB4D42CAE9C@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Brian Hamacher <bhamacher@westianet.com>, "ipv6@ietf.org" <ipv6@ietf.org>, Philipp Kern <pkern@debian.org>, "Rajiv Asati (rajiva)" <rajiva@cisco.com>
Subject: Re: [dhcwg] MAC Address Tracking via DHCP6
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 15:49:15 -0000

On Feb 1, 2013, at 10:42 AM, Chuck Anderson <cra@WPI.EDU> wrote:
> There is also draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04
> which handles the case for DHCPv6 clients.  That also requires no
> changes to clients--only the DHCPv6 Relay Agent.

This document doesn't apply to SLAAC or CGA addresses, though—just stateful addresses acquired through DHCPv6.   Admittedly, we could also snoop DHCPINFORM traffic, but there's no guarantee that all devices on the network will do a DHCPINFORM, even if the O bit is set.