Op 13 nov. 2012, om 21:19 heeft Simon Kelley het volgende geschreven: > On 13/11/12 19:04, Jim Gettys wrote: > >> >> So the recursive DHCP-PD scheme strikes me as something possibly very >> fragile. I really, really don't want to repeat the experience I had with >> having extra DHCP servers, and I would guess few ISP's do either. >> >> It seems to me much more robust to flood the key configuration information >> (prefixes, DNS, NTP, and the like) via a protocol that is really designed >> for the job (whether specifically for configuration, ie. ahcp >> http://www.pps.univ-paris-diderot.fr/~jch/software/ahcp/, or via the hacks >> on routing protocols like Ari has done with OSPF). > > Given that hosts are going to want to talk RA or DHCPv6, at least initially, > one option down this route has the flood include the unicast address of a > single, centralised DHCPv6 server, and routers run DHCP-relay agents which > forward to that address. That gives you DHCPv6 functionality without > recursive-PD complications. It also eliminates the problems of distributing > the available prefixes as they traverse PD chains. Right.
> The one-and-only DHCP server knows about all the prefixes delegated from the > ISP and the relays know which particular prefix has been given to the local > router by the routing protocol or AHCP. I don't like a single DHCP server for multi-homed sites. This introduces unneeded complexity, it needs merging of information from multiple sources. This is completely incompatible with what MIF is doing (multiple provisioning domains). It also introduces an unneeded single point of failure. Multi-homing could be used for redundancy. Let's use a DHCP server for each ISP. In cases where a single CPE router connects to multiple ISPs, it can take two approaches: running multiple DHCP server instances, one for each ISP. Or perform the problematic integration. BRDP takes the "per provisioning domain" approach, where each provisioning domain is presented with a border router address (generated form provided prefix), with prefix length. Problem solved :-). Teco > > Simon. > > > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
