IPv4, IPv8, and IPv16
"Jim Fleming" <JimFleming@prodigy.net> Sat, 13 March 1999 07:20 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id CAA02258 for ietf-outbound.10@ietf.org; Sat, 13 Mar 1999 02:20:02 -0500 (EST)
Received: from virtualmaster3-int.prodigy.net (virtualmaster3-ext.prodigy.net [207.115.59.137]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02226 for <ietf@ietf.org>; Sat, 13 Mar 1999 02:16:29 -0500 (EST)
Received: from technocat (CHCGB111-31.splitrock.net [209.156.11.192]) by virtualmaster3-int.prodigy.net (8.8.5/8.8.5) with SMTP id CAA407134 for <ietf@ietf.org>; Sat, 13 Mar 1999 02:16:29 -0500
Message-ID: <000501be6d21$980279c0$c00b9cd1@technocat.unir.com>
From: Jim Fleming <JimFleming@prodigy.net>
To: ietf@ietf.org
Subject: IPv4, IPv8, and IPv16
Date: Sat, 13 Mar 1999 01:17:44 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3155.0
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
IPv4, IPv8 and IPv16 are being developed to work together. This requires architecture. A "flat-network" view of the world, such as IPv6, does not require any architecture. That makes life simple, and allows the IETF to avoid the hard problems, which eventually have to be solved. In my opinion, the IETF is largely the equivalent of a "street-gang" of technical "thugs" who think they control the playground. Fortunately, more and more people are seeing what they are all about, and just route around them to and from other more interesting activities. I suggest that people just route around the IETF...and maybe they will all end up on Mars...those of us on planet Earth still have a lot of work to do...and are not distracted by the noise from Mars...or other parts of the IETF outerspace... JF
- IPv4, IPv8, and IPv16 Jim Fleming
- Re: IPv4, IPv8, and IPv16 Fred Baker