Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 05 Aug 2003 03:43:43 -0700
From:      Terry Lambert <tlambert2@mindspring.com>
To:        Craig Rodrigues <rodrigc@crodrigues.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: INET6 in world
Message-ID:  <3F2F8A5F.A17CABCA@mindspring.com>
References:  <3F2D1713.9060806@liwing.de> <20030803181735.GC6331@cicely12.cicely.de> <3F2EA5AD.E4C73C6@mindspring.com> <20030804184248.GA41334@crodrigues.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Craig Rodrigues wrote:
> On Mon, Aug 04, 2003 at 11:27:57AM -0700, Terry Lambert wrote:
> > > That's chicken/egg - IPv6 never will be widely used if everyone thinks
> > > that way.
> >
> > The problem, as I see it, is that it doesn't come enabled by
> > default on Windows systems.  Until it does, it's never going
> > to get any traction.
> >
> > I wouldn't be surprised if the government has asked Microsoft
> > to not deploy it, or to deploy it without encryption support,
> > given world events.
> 
> The government is pushing IPv6, but from a different direction:
> 
> http://www.fcw.com/fcw/articles/2003/0609/web-dodip-06-13-03.asp

13 Jun 2003:

	"He added that either the Secret Internet Protocol Router
	 Network (SIPRNET) or the Non-Classified Internet Protocol
	 Router Network (NIPRNET) might be one of the programs
	 switched over to IPv6, and that the Navy Marine Corps
	 Intranet also is being considered.  Definitive choices
	 will be made within 30 days."

...so... what was the decision, over 3 weeks ago?  8-) 8-).

> http://www.defenselink.mil/transcripts/2003/tr20030613-0274.html

	"...major development activities, that are going to come
	 online in the 2008, 2009, and 2010 time frame..."

	"So I think the actual push to move from IP 4 to IP 6 will
	 not be driven by us."

	"...as I say, we're taking a target date of 2008, so it's
	 not like we're thinking about it tomorrow."

He also talks about Microsoft and IBM embodying it into products (which
is what I said was the barrier).

> In the U.S., this will probably push many vendors to
> become "IPv6-compatible".

In 5 years.

He's not planning on deploying until it's depoloyed commercially.

He apparently doesn't understand that v6/v4 NATs and proxy servers
would let him deploy today ...assuming that the Windows stack was
there.

He doesn't seem to be a very technical person, for being the chief
information officer; he had to ask his assistant for the name of
the "IETF", for example.

If you're looking for him to push the move to IPv6, you probably
want to look to the other Washington (the one where Redmond is
located).

-- Terry



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F2F8A5F.A17CABCA>