On 21 May 2013, at 14:32, Marco Sommani <[email protected]> wrote:
> On 21/mag/2013, at 15:25, Tim Chown <[email protected]> wrote: > >> On 21 May 2013, at 13:26, Nick Hilliard <[email protected]> wrote: >> >>> On 21/05/2013 13:00, Liviu Pislaru wrote: >>>> With DHCPv6 i didn't find a way to do that (identify what IPv6 is allocated >>>> to which customer) without asking any additional information from the >>>> customer (like DUID). >>> >>> apparently this is a feature, not a bug. >> >> There is this, which allows a relay to insert the client hardware address: >> http://tools.ietf.org/html/draft-halwasia-dhc-dhcpv6-hardware-addr-opt-01 >> >> Seems to have expired though :/ >> >> Tim > > This one is still valid, though: > http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt/ > > The difference is that in the new draft the link-layer address is not an > option for clients, but just for relays. The idea is that servers located on > the same link as the client may find the link-layer address in the L2 header. Ah, right, sorry, that version slipped my mind :) I would suspect in a largeish enterprise that that approach would be appropriate, as it's likely that all DHCPv6 traffic would be forwarded by a relay. Tim
