Re: [v6ops] Please review the No IPv4 draft

Yeah, but we survived the transition away from these older networks without significant issues and special messages on IPv4 to tell clients "don't try IPX or AppleTalk or ...".

- Bernie

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

Le 2014-04-15 10:21, Dale W. Carder a écrit :
> I guess I am still confused by your use cases.  In looking at our 
> dhcpv4 servers, I don't have No-IPX nor No-AppleTalk options sent to 
> clients, so I am confused why this is needed for IPv4.

IPv4 has billions of deployed devices. IPX and AppleTalk, not so much.

> 3.1:  Turn off the dhcpv4 relay feature per router (sub)interface.  No 
> more load on the dhcpv4 server.

Not possible if the L2 link is shared with devices to which you do want to provide IPv4 service.

> 3.2:  At the edge of your network, filter packets containing 
> ethertypes you do not support.

Not possible if the L2 link is shared with devices to which you do want to provide IPv4 service.

> 3.3:  Mobile device vendors have an incentive in fixing their code so 
> they do not chew up their battery more than their competitors.

Yet the problem has not been fixed.

> 3.4:  At the edge of your network, filter packets containing 
> ethertypes you do not support.

Not possible if the L2 link is shared with devices to which you do want to provide IPv4 service.

Plus, that only works for ISPs. We need a way to propagate this 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