Re: [Fwd] ISO wants Collaboration with Internet Community

don provan <sgiblab!novell.com!troi!donp@uucp-gw-2.pa.dec.com> Wed, 17 February 1993 00:19 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16658; 16 Feb 93 19:19 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa16654; 16 Feb 93 19:19 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa06238; 16 Feb 93 19:19 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16647; 16 Feb 93 19:19 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa16641; 16 Feb 93 19:19 EST
Received: from venera.isi.edu by CNRI.Reston.VA.US id aa06233; 16 Feb 93 19:19 EST
Received: from uucp-gw-2.pa.dec.com by venera.isi.edu (5.65c/5.65+local-7) id <AA26637>; Tue, 16 Feb 1993 16:19:38 -0800
Received: by uucp-gw-2.pa.dec.com; id AA20493; Tue, 16 Feb 93 16:12:01 -0800
Received: from troi by sgiblab.sgi.com via UUCP (920330.SGI/911001.SGI) id AA15693; Tue, 16 Feb 93 16:10:54 -0800
Received: by troi.dbaccess.com (AIX 3.1/UCB 5.61/4.03) id AA24295; Tue, 16 Feb 93 15:35:50 -0800
To: sgiblab!decwrl!info-ietf@uucp-gw-2.pa.dec.com
Path: troi!sgiblab!newsun!donp
X-Orig-Sender: ietf-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: don provan <sgiblab!novell.com!troi!donp@uucp-gw-2.pa.dec.com>
Newsgroups: info.ietf
Subject: Re: [Fwd] ISO wants Collaboration with Internet Community
Message-Id: <1993Feb16.184223.10935@novell.com>
Date: Tue, 16 Feb 1993 18:42:23 +0000
References: <9302161713.AA13413@ftp.com>
X-Orig-Sender: The Netnews Manager <sgiblab!novell.com!troi!news@uucp-gw-2.pa.dec.com>
Organization: Novell, Inc., San Jose, California
Lines: 13
Nntp-Posting-Host: na.sjf.novell.com

In article <9302161713.AA13413@ftp.com> kasten@ftp.com writes:
>Let's suppose that we decide that CLNP is the next IPv7. What this
>means is that there will be some RFC, the product of the TUBA w.g.
>most likely, that is titled "IP Version 7" (or something like that)
>and it would _amazingly_ similar to the ISO CLNP spec.

I assume this means that it wouldn't use the same media layer protocol
identifier (such as the 802.2 SAP value) as CLNP, right?  To me,
that's the one thing that would distinguish CLNP from "something just
like CLNP but different".  (Offhand, i don't think this is really what
the CLNP people have in mind...)
						don provan
						donp@novell.com