On 15 Mar 2016, at 3:09, Lee Howard wrote:

As noted below, I¹ve posted a draft. I thought I¹d start a thread for
discussing it.

starting the discussion ;-)
- courageous you are.

«  The IETF does not update Historic RFCs. Therefore, the IETF will no longer work on IPv4 technologies, including transition technologies. »

I think this needs clarification. For example:
- what does that mean for current protocols specifications that are already dual-stacked, when they are updated? If there is a field with IPv4 address in the update specification, what does that really mean? It might just break the protocol if we avoid the IPv4 address in the update. SIP/WebRTC comes to mind… - transition technologies. you meant I guess IPv4 to IPv6 transition technologies. Might be good to be more explicit. - transition technologies: there are a few that are « helping » IPv6 deployment, one in mind is NAT64/DNS64. Does this mean we can not work on augmenting/making NAT64/DNS64 better?

Marc.


PLEASE Please please read the draft before commenting. It¹s very short, less than 500 words, and I anticipate a lot of people having strong feelings
about it. I would really rather not waste time arguing about things it
doesn¹t say.

To that end, I¹ve also written a blog post, explaining in a level of detail
I thought inappropriate for the draft:
http://www.wleecoyote.com/blog/ipv4-historic.htm

Thank you,

Lee

From:  sunset4 <[email protected]> on behalf of Wesley George
<[email protected]>
Date:  Monday, March 14, 2016 at 6:28 PM
To:  "[email protected]" <[email protected]>
Subject:  [sunset4] Agenda items?

As you can see, we have a meeting scheduled for BA.
As of right now, we have a single agenda item:

https://tools.ietf.org/html/draft-howard-sunset4-v4historic-00

While I fully expect that this item can expand to fill all available time, if there are other things that the WG wishes to discuss, please respond ASAP to
request agenda time.

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.
_______________________________________________ sunset4 mailing list
[email protected] https://www.ietf.org/mailman/listinfo/sunset4


_______________________________________________
sunset4 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sunset4
_______________________________________________
sunset4 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sunset4

Reply via email to