Re: [dhcwg] MAC Address Tracking via DHCP6

["Rajiv Asati (rajiva)" <[e-mail]>]

Hi Chuck,

Yah, but draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt is for DHCPv6
clients, as you rightly pointed out, and not for SLAAC/static hosts.

Cheers,
Rajiv

-----Original Message-----
From: Chuck Anderson <[e-mail]>
Date: Friday, February 1, 2013 10:42 AM
To: Rajiv Asati <[e-mail]>
Cc: Maglione Roberta <[e-mail]>, "[e-mail]"
<[e-mail]>, Brian Hamacher <[e-mail]>,
"[e-mail]" <[e-mail]>, Philipp Kern <[e-mail]>
Subject: Re: [dhcwg] MAC Address Tracking via DHCP6

>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.
>
>On Fri, Feb 01, 2013 at 02:56:03PM +0000, Rajiv Asati (rajiva) wrote:
>> Hi Maglione, 
>> 
>> Thanks for your review and a good question.
>> 
>> draft-ietf-dhc-addr-registration introduces a new IPv6 Neighbor
>>Discovery
>> option and a
>>    new DHCPv6 option to propagate the address registration information
>> from the hosts to the network.  It requires the changes on the host.
>> 
>> 
>> 
>> draft-asati-dhc-ipv6-autoconfig-address-tracking, on the other hand,
>> requires no changes to IPv6 Neighbor Discovery and no changes to the
>> hosts. It introduces changes in DHCPv6 specific to the last hop router
>>and
>> the DHCP server, thereby keeping the changes within the network (and
>>DHCP
>> server).
>> 
>> 
>> Cheers,
>> Rajiv
>> 
>> -----Original Message-----
>> From: Maglione Roberta <[e-mail]>
>> Date: Friday, February 1, 2013 3:26 AM
>> To: Rajiv Asati <[e-mail]>
>> Cc: "[e-mail]" <[e-mail]>, Philipp Kern <[e-mail]>,
>> Brian Hamacher <[e-mail]>
>> Subject: RE: MAC Address Tracking via DHCP6
>> 
>> >Hello Rajiv,
>> > is there any relation between your draft and
>> >draft-ietf-dhc-addr-registration-00?
>> >
>> >Thanks
>> >Regards,
>> >Roberta
>> >
>> >
>> >-----Original Message-----
>> >From: [e-mail] [mailto:[e-mail]] On Behalf Of
>> >Rajiv Asati (rajiva)
>> >Sent: Thursday, January 31, 2013 6:27 PM
>> >To: Philipp Kern; Brian Hamacher
>> >Cc: [e-mail]
>> >Subject: Re: MAC Address Tracking via DHCP6
>> >
>> >
>> >There is a better way out to track the IPv6 addresses used by the hosts
>> >(via SLAAC or static) -
>> >
>> 
>>>http://tools.ietf.org/html/draft-asati-dhc-ipv6-autoconfig-address-track
>>>in
>> >g
>> >
>> >Cheers,
>> >Rajiv
>> >
>> >-----Original Message-----
>> >From: Philipp Kern <[e-mail]>
>> >Organization: The Debian Project (http://www.debian.org)
>> >Date: Wednesday, December 12, 2012 10:37 AM
>> >To: Brian Hamacher <[e-mail]>
>> >Cc: "[e-mail]" <[e-mail]>
>> >Subject: Re: MAC Address Tracking
>> >
>> >>On Tue, Dec 11, 2012 at 04:04:14PM -0600, Brian Hamacher wrote:
>> >>> I am looking for a good way to track my users MAC Addresses.  I
>>have a
>> >>> test DHCPv6 server up and running ISC 4.1.1-P1.  When I look
>>through my
>> >>> DHCP logs as well as my leases file I do not see the client MAC
>>Address
>> >>> anywhere.  Do I need to enable an option to allow this to be
>>logged?  I
>> >>> am looking to figure out how I can track what user had what IP
>>Address
>> >>> at any given time.  The MAC Address is traditionally how I have done
>> >>> this.
>> >>
>> >>One way would be to poll your routers' ND tables (like fetching ARP
>> >>tables
>> >>in IPv4). As soon as you use relaying you most certainly won't get a
>> >>useable MAC address from your client, even though it might be
>>possible in
>> >>the same network segment. (The MAC address is not copied from the wire
>> >>into the new relayed packet sent by the router to your server.)
>> >>
>> >>DHCPv6 uses the so-called client identifier extensively and not the
>>MAC
>> >>address anymore. So you cannot do any static assignment based on MAC
>> >>addresses.
>> >>
>> >>Kind regards
>> >>Philipp Kern