Re: [v6ops] Please review the No IPv4 draft

["George, Wes" <[e-mail]>]

From: Matthew Petach <[e-mail]<mailto:[e-mail]>>
Date: Monday, April 21, 2014 at 12:43 PM
To: Ted Lemon <[e-mail]<mailto:[e-mail]>>
Cc: "[e-mail]<mailto:[e-mail]> WG" <[e-mail]<mailto:[e-mail]>>
Subject: Re: [v6ops] Please review the No IPv4 draft

I would not expect any device
of mine to take advice from an IPv6 network about how to
operate on an IPv4 network.  Even if those networks happen
to be sharing the same physical piece of wire, or same range of
RF spectrum, they are independent and orthogonal networks.

WG] I think that there’s a need for clarification here. A lot of this discussion has focused almost exclusively on the full-on disabling of IPv4. Part of what the draft discusses is that there are differing things that can be signaled to the local devices from the network based on the bit set in the proposed option. There is an option that simply signals “there is no IPv4 support on this network” and makes attendant recommendations that the device decide on its own what to do for any local IPv4 traffic on the LAN, including doing nothing, configuring 169 addresses, etc. but that it should disable IPv4 on the upstream interface facing the network that provided the signal (I.e. Stop forwarding IPv4 traffic and stop sending DHCPv4).
I’m willing to go with consensus (if exist) that the more aggressive option of something like a full-on IPv4 killswitch that affects more than one interface and affects the local network is a bridge too far, both for security reasons (It’ll be hard to secure to a level that exploits aren’t likely) and because it gets into a question about autonomy and span of control. But I think it’s worth highlighting that there are also less aggressive options discussed in the draft, and I’d like to have some sense that those are mostly on the right track, and your statement is so broad that I wanted to get clarification on what you think of this.

Thanks,

Wes George

Anything below this line has been added by my company’s mail server, I have no control over it.
-----------

________________________________
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.