Dear Michael, all, Please see inline.
Cheers, Med >-----Message d'origine----- >De : homenet [mailto:homenet-boun...@ietf.org] De la part de Michael >Richardson >Envoyé : mercredi 16 avril 2014 15:08 >À : homenet@ietf.org >Objet : Re: [homenet] Please review the No IPv4 draft > > >{I would love a description from Apple and Microsoft of how their >layer-2/layer-3 address discovery/configurartion systems already interact} > >Philip Homburg <pch-homene...@u-1.phicoh.com> wrote: > > Does that include all edge cases and the user interface? > > > I.e. DHCPv4 has configured an address and by mistake a RA orders IPv4 > > to be > > shutdown. Do you just shutdown IPv4? Does your code parse the output >of > > ifconfig to figure out if the interface was configured? > >No, and no. > >The order is not to shutdown v4. The suggestion is to stop DHCPv4, if it >hasn't succeeded, and assume that there isn't any IPv4 for any downstream >devices. > >Ideally the device will not announce an IPv4 default route if it hasn't got >one itself. [Med] This is not a valid generic statement. Consider the DS-Lite model (RFC6333): there is no dhcpv4 client in the CPE at all + no assigned IPv4 address in the wan side, but still IPv4 connectivity is offered to connected hosts. DHCPv4 client is disabled when the CPE detects it is attaching the network using DS-Lite. The no-dhcpv4 explicit signal is not required for this case for example. _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
