DHCPv6 and MAC Address inclusion

[Ted Lemon]

On Jan 26, 2012, at 12:58 PM, "perl-list" <perl-list at network1.net<mailto:perl-list at network1.net>> wrote:
Don't know how one would do that.  At best, potentially we could cause the web browser to immediately connect to the IPv6 address of the web portal transmitting the same information (so that the web portal had the IPv6 address).  This would cause a nice failure error message in clients that don't have IPv6 enabled, or aren't even capable of IPv6.

It's a trivial JavaScript hack using XmlHttpRequest. There's no problem trapping the error message.

They are necessary for DHCP to function in conformance with the standard.
So they need to exist so that they can exist?  Sounds like a circular argument.

The standard says "do X".  If your implementation does Y, you have not implemented the standard.   How is this circular?   The DUID identifies the client; without it, you can't differentiate between clients.

Whether they are layer 3 or layer 2 doesn't really matter.  The simple fact is that varying manufacturers implement useful features to varying degrees or not at all.  Much like the MAC address in the DHCPv6 packet, it cannot be counted upon that a particular DSLAM will have some certain functionality available that will make your life easier.

You are the customer.  Why are you buying DSLAMs that don't do what you need?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20120126/3cf79ea2/attachment.html>