Re: [address-policy-wg] Re: [ppml] Is the time for conservation over?

[Jeff Williams <]

Leo and all,

  I also am in agreement with Leo on this point as well.  IPv8 is already
in significant deployment asia and elsewhere and is in some folks
opinion, though I am sure not Michael's, a superior IP Protocol to
IPv6, which has known Privacy problems.

Leo Bicknell wrote:

> In a message written on Mon, Oct 27, 2003 at 01:54:45PM +0000, Michael.Dillon@localhost wrote:
> > Therefore, I believe that all the RIRs should jointly do some research
> > to establish a prudent date at which IPv6 will be considered to have
> > reached critical mass so that there will be a significant migration of
> > users from IPv4 to IPv6. Once we set our sights on this date we should
>
> I am going to strongly disagree on this point at this time.  We
> don't know that there will /ever/ be a strong migration of users
> to IPv6.  IPv6 may yet flop completely, be replaced by IPv8 or
> something before it ever reaches full deployment, or even always
> live side by side with IPv4.
>
> Even if we assume everything migrates to IPv6, I see no reason why
> we should change IPv4 policy at all.  First, if people are migrating
> IPv4 policy becomes irrevelant anyway.  Second, if the IPv4 policy
> is hinderng things we should fix it in IPv6 policy to more quickly
> encourage cut over.
>
> --
>        Leo Bicknell - bicknell@localhost - CCIE 3440
>         PGP keys at http://www.ufp.org/~bicknell/
> Read TMBG List - tmbg-list-request@localhost, www.tmbg.org
>
>   ------------------------------------------------------------------------
>
>    Part 1.2   Type: application/pgp-signature

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 134k members/stakeholders strong!)
"Be precise in the use of words and expect precision from others" -
    Pierre Abelard
===============================================================
CEO/DIR. Internet Network Eng. SR. Eng. Network data security
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@localhost
Contact Number: 214-244-4827 or 214-244-3801