On 1 Feb 2013, at 15:47, Rajiv Asati (rajiva) wrote:
>
> 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.
You can also of course just use tools that harvest data from
network/switch/router devices, and
I agree, Ted.
-Original Message-
From: Ted Lemon
Date: Friday, February 1, 2013 10:49 AM
To: Chuck Anderson
Cc: Rajiv Asati , "dh...@ietf.org" ,
Brian Hamacher , Philipp Kern ,
"ipv6@ietf.org"
Subject: Re: [dhcwg] MAC Address Tracking via DHCP6
>On Feb 1, 2
On Feb 1, 2013, at 10:42 AM, Chuck Anderson 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, thou
, "dh...@ietf.org"
, Brian Hamacher ,
"ipv6@ietf.org" , Philipp Kern
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 c
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 +, Rajiv Asati (rajiva) wrote:
> Hi Maglione,
>
> Thanks for your review and
