Re: [v6ops] Please review the No IPv4 draft

> This doesn't work when the L2 link is shared with clients to which you do want to provide IPv4 service.

So, why can't other devices use IPv4 then?

> That is true, but there's no way to propagate this information to more hosts in the home. So you end up with DHCP requests eating battery life in the home.

That might require some tweaks in those devices (they probably already limit what discovery they do if they aren't getting DHCPv4 service to start with -- and that would benefit the device everywhere).

- Bernie

-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Simon Perreault
Sent: Tuesday, April 15, 2014 9:37 AM
To: v6ops@ietf.org
Subject: Re: [v6ops] Please review the No IPv4 draft

Le 2014-04-14 16:44, Bernie Volz (volz) a écrit :
> BTW: How significant is the problem anyway? Has this been analyzed by anyone?
> 
> Sure, the clients broadcast these packets but this is the "good" direction in Wifi - the Wifi 'switch' can be told to drop them. Other switches can to?
> 
> Seems to me that this would be far better to leave to the networking infrastructure to just 'block' the DHCPv4 packets if IPv4 isn't enabled?

This doesn't work when the L2 link is shared with clients to which you do want to provide IPv4 service.

> I suspect many access networks (i.e. DOCSIS - the IP Provisioning Mode TLV) already provide some information about whether v4, v6, or both are available?

That is true, but there's no way to propagate this information to more hosts in the home. So you end up with DHCP requests eating battery life in the home. Our draft describes how to propagate the No-IPv4 knowledge inside the home.

Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops