IETF Logo Mail Archive

Re: Status of IPng

Mark Knopper <mak@aads.net> Tue, 19 July 1994 03:44 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22811; 18 Jul 94 23:44 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa22807; 18 Jul 94 23:44 EDT
Received: from mailhost.lanl.gov by CNRI.Reston.VA.US id aa27092; 18 Jul 94 23:44 EDT
Received: from noc-gw.lanl.gov by mailhost.lanl.gov (8.6.8.1/1.2) id VAA03090; Mon, 18 Jul 1994 21:42:59 -0600
Received: by noc-gw.lanl.gov (8.6.8.1/SMI-4.1) id VAA00299; Mon, 18 Jul 1994 21:41:59 -0600
Received: from mailhost.lanl.gov by noc-gw.lanl.gov (8.6.8.1/SMI-4.1) id VAA00296; Mon, 18 Jul 1994 21:41:59 -0600
Received: from aads.net by mailhost.lanl.gov (8.6.8.1/1.2) id VAA03080; Mon, 18 Jul 1994 21:42:01 -0600
Received: (mak@localhost) by aads.net (8.6.9/aads1.1) id XAA07074; Mon, 18 Jul 1994 23:08:21 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Knopper <mak@aads.net>
Message-Id: <199407190308.XAA07074@aads.net>
Subject: Re: Status of IPng
To: Keith Sklower <sklower@vangogh.cs.berkeley.edu>
Date: Mon, 18 Jul 1994 23:08:21 -0400
Cc: tuba@lanl.gov
In-Reply-To: <199407190234.TAA14548@vangogh.CS.Berkeley.EDU> from "Keith Sklower" at Jul 18, 94 07:34:03 pm
Reply-To: mak@aads.net
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Content-Length: 662 

Keith,
  The IESG is acknowledging that the TUBA (and SIPP and CATNIP) groups
can continue if there is interest in doing so. This is apart from the
IPng working group.
	Mark

> 
> Mark Knopper writes: 
> 
> 	The IPng directorate has decided to recommend SIPP 16
> 	as a starting point for IPng.
> 
> Well, that was accomplished with remarkably little hoopla.  What does
> that say about TUBA?  Would anybody in the IESG support the notion
> that even though CLNP is not the fair-haired child of IPv4, that there
> is still value in improving CLNP to the point where it can carry any
> traffic that the other IP can, and that this work may occur in the IETF?
>

v2.23.0 | Report a Bug | By Email