On Tue, Mar 15, 2016 at 11:57 AM, George, Wes <[email protected]> wrote:
> > > On 3/15/16, 12:47 PM, "sunset4 on behalf of Philip Homburg" > <[email protected] on behalf of [email protected]> wrote: > > >If you can't develop new > >standards that involve the protocol that carries more than 50% of the > >world > >internet traffic, then you are doing something wrong. > > </chair hat> > WG] I don't think that's what this draft is suggesting. The vast majority > of IETF standards are wholly agnostic to the version number in the IP > packet, and as such will continue regardless of whether IPv4 is declared > historic. What changes is that it is no longer strictly necessary (or > permitted) to make concessions in the standard to ensure that it works > properly over the now historic IP version in cases where the IP version > matters to the protocol or standard being developed. > As an example: if I as a software developer have a program that was > originally developed to work on Windows XP, and I deprecate support for > that OS, the downrev version that I wrote before I deprecated support for > XP will keep working, and while it's possible that the new version I > optimized to run on Windows 8 and 10 might mostly still work on XP, if you > file a bug complaining that something, especially a feature that I > newly-introduced on the current version of software, doesn't work on XP, > I'll ignore you. > > Additionally, consider the time scale at which IETF operates - 2-3 years > for significant deployment of new standards is usually fairly aggressive, > and this draft is going to take some time to achieve consensus, in > addition to it being dependent on IPv6 being elevated to full Standard. > I'm not convinced that by then IPv4 will still be the majority given its > current burn rate and IPv6's growth rate. > > Thanks > Wes George > > +1 to Wes and the I-D being good as is. It is crisp and clear statement of how we as the IETF are moving forward. CB 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
