George, Wes
2014-04-16 17:38:24 UTC
Simon Perreault (and to some lesser extent,I ) has been involved in a fairly animated discussion across Homenet and V6Ops about draft-ietf-sunset4-noipv4 after requesting those WGâs feedback on the draft.
Hereâs a quote from one of Ted Lemonâs posts that might help to summarize the discussion:
"We've gotten some good feedback that the document isn't clear enough, particularly with respect to how multiple interfaces are handled, and we've gotten some good feedback about how to handle validity of the assertion that IPv4 shouldn't be used, and about how to deal with various attacks that could be launched by shutting down IPv4.
...
there's also been a lot of discussion about whether to use DHCPv4 or IPv6 configuration protocols for signaling,"
Additionally there were questions about whether or not the scope should be limited to shutting down DHCPv4, or still include shutting IPv4 off altogether, and whether there should be guidance on things like lifetimes, back off behavior in clients, etc.
This link should pull up the relevant threads all in one place via the new mail archive search tool.
https://mailarchive.ietf.org/arch/search/?qdr=a&start_date=&end_date=&email_list=v6ops%2Chomenet&q=text%3A%28%22the+no+ipv4+draft%22%29&as=1
Iâd encourage folks to take a look and provide input on this list, so that the authors have good guidance from the WG on how this WG draft should evolve to address the feedback provided.
Thanks,
Wes
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.
Hereâs a quote from one of Ted Lemonâs posts that might help to summarize the discussion:
"We've gotten some good feedback that the document isn't clear enough, particularly with respect to how multiple interfaces are handled, and we've gotten some good feedback about how to handle validity of the assertion that IPv4 shouldn't be used, and about how to deal with various attacks that could be launched by shutting down IPv4.
...
there's also been a lot of discussion about whether to use DHCPv4 or IPv6 configuration protocols for signaling,"
Additionally there were questions about whether or not the scope should be limited to shutting down DHCPv4, or still include shutting IPv4 off altogether, and whether there should be guidance on things like lifetimes, back off behavior in clients, etc.
This link should pull up the relevant threads all in one place via the new mail archive search tool.
https://mailarchive.ietf.org/arch/search/?qdr=a&start_date=&end_date=&email_list=v6ops%2Chomenet&q=text%3A%28%22the+no+ipv4+draft%22%29&as=1
Iâd encourage folks to take a look and provide input on this list, so that the authors have good guidance from the WG on how this WG draft should evolve to address the feedback provided.
Thanks,
Wes
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.