On Sep 28, 2014, at 10:24 PM, Brian E Carpenter <[email protected]> wrote: > I was thinking of the client side. I could be wrong though. It depends on > how the client side is implemented, I guess: it could just be a DHCPv6 > engine that is blind to the content of the options, which it passes > on to the softwire code.
Whether or not there is a special hack in the DHCP client, from the perspective of writing the standard it is simply a protocol engine that implements the spec, which I think can be done without reference to MAP or lw4over6. It shouldn't matter from the perspective of this draft whether the DHCP client and A+P tunneling/mapping agent are implemented as a monolithic hunk of code or as two distinct and logically separate agents. _______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
