IPv7 (CLNP) a mistake

Brian Lloyd <brian@lloyd.com> Sat, 04 July 1992 13:55 UTC

Received: from NRI.NRI.Reston.Va.US by IETF.NRI.Reston.VA.US id aa00947; 4 Jul 92 9:55 EDT
Received: from venera.isi.edu by NRI.Reston.VA.US id aa08285; 4 Jul 92 9:56 EDT
Received: by venera.isi.edu (5.65c/5.65+local-6) id <AA22234>; Fri, 3 Jul 1992 13:41:22 -0700
Received: from ray.lloyd.COM by venera.isi.edu (5.65c/5.65+local-6) id <AA22190>; Fri, 3 Jul 1992 13:39:55 -0700
Received: by ray.lloyd.com (4.1/SMI-4.1/Brent-911016) id AA01877; Fri, 3 Jul 92 13:37:57 PDT
Date: Fri, 03 Jul 1992 13:37:57 -0700
From: Brian Lloyd <brian@lloyd.com>
Message-Id: <9207032037.AA01877@ray.lloyd.com>
To: craig@aland.bbn.com
Cc: big-internet@munnari.oz.au, iab@isi.edu, iesg@NRI.Reston.VA.US, ietf@isi.edu, road@lanl.gov
In-Reply-To: Craig Partridge's message of Fri, 03 Jul 92 11:35:21 -0700 <9207031835.AA02858@aland.bbn.com>
Subject: IPv7 (CLNP) a mistake
Reply-To: brian@lloyd.com

   Reply-To: Craig Partridge <craig@aland.bbn.com>
   From: Craig Partridge <craig@aland.bbn.com>
   Date: Fri, 03 Jul 92 11:35:21 -0700
   Sender: craig@aland.bbn.com


   Brian:

       See my note to Bob Braden of yesterday.  The goal is to adopt ISO CLNP
   and to keep in harmony (the exact words are "functionally compatible" and
   "convergent") with ISO CLNP.  IPv7 is CLNP by another name.

   Craig

I saw it after I made my posting.  I am not now quite as enamored of
the idea as I originally was.  Going with CLNP verbatim implies that
we go along with the braindamaged way that ISO wants to assign
addresses.  In that case I think that CLNP is a bad idea.  Rolling
something new that borrows from the good features of IP and CLNP but
does away with their respective warts is a good thing.  Going with
CLNP en toto just doesn't seem worth the pain.

Brian Lloyd, WB6RQN                                     Lloyd & Associates
Principal and Network Architect                         3420 Sudbury Road
brian@lloyd.com                                         Cameron Park, CA 95682
voice (916) 676-1147 -or- (415) 725-1392