Hi Doug, On Thu, 26 May 2011 15:47:04 -0700 Doug Barton <[email protected]> wrote:
> On 05/26/2011 15:03, Mark Smith wrote: > > Exactly. That's the problem. If you know you can't or aren't very > > likely to be able to relay DHCP options to customer's end-nodes, you > > don't bother sending them. The myriad of DHCP(v4 and v6) options that > > exist that may be useful to an SP are currently of no or very little use > > because they can't be conveyed directly to customer's end-nodes across > > the CPE boundary. > > One could imagine a situation where the CPE makes configures itself with > those options, and by default then transmits them to clients it acts as > a server for. That is probably a different document though. > If the CPE doesn't understand the options, it can't pass them on. So if you look at the list of DHCPv6 options the are available - http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml#dhcpv6-parameters-2 currently, using a DHCPv6 server in the CPE, none of them can be provided to end-nodes if the CPE doesn't support them, despite the SP's DHCPv6 server supporting them and the SP's customer's end-nodes supporting them. Only a DHCPv6 relay can effectively convey (relay) options it doesn't understand because it doesn't actually try to understand them. Regards, Mark. -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
