IISP Networking Requirements WEB Page Ptr
bound@zk3.dec.com Thu, 21 March 1996 19:21 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa26186; 21 Mar 96 14:21 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa26182; 21 Mar 96 14:21 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa12362; 21 Mar 96 14:21 EST
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa26165; 21 Mar 96 14:21 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa26160; 21 Mar 96 14:21 EST
Received: from [192.208.46.10] by CNRI.Reston.VA.US id aa12352; 21 Mar 96 14:21 EST
Received: from wasted.zk3.dec.com by mail11.digital.com (5.65v3.2/1.0/WV) id AA03869; Thu, 21 Mar 1996 13:55:19 -0500
Received: from localhost by fwasted.zk3.dec.com; (5.65v3.2/1.1.8.2/18Feb95-1123AM) id AA25074; Thu, 21 Mar 1996 13:55:24 -0500
Message-Id: <9603211855.AA25074@fwasted.zk3.dec.com>
To: iesg@CNRI.Reston.VA.US, iab@isi.edu
Cc: deering@parc.xerox.com, perk@watson.ibm.com, hinden@ipsilon.com, bound@zk3.dec.com
Subject: IISP Networking Requirements WEB Page Ptr
Date: Thu, 21 Mar 1996 13:55:24 -0500
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: bound@zk3.dec.com
X-Mts: smtp
Just as a note I thought the IESG/IAB might want to check out the WEB page URL attached from the Information Infrastructure Standards Panel (IISP). As Jim Isaak says below there are many requirements and its amazing how many of them line up with our Areas and some of the strategic objectives I hear in the IETF. /jim ------- Forwarded Message Return-Path: daemon Received: from xirtlu.zk3.dec.com by fwasted.zk3.dec.com; (5.65v3.2/1.1.8.2/18Feb95-1123AM) id AA02681; Mon, 11 Mar 1996 23:39:42 -0500 Received: by xirtlu.zk3.dec.com; id AA16485; Mon, 11 Mar 1996 23:39:41 -0500 Date: Mon, 11 Mar 1996 23:39:41 -0500 Message-Id: <9603120439.AA16485@xirtlu.zk3.dec.com> From: isaak@csac.ENET.dec.com (JimIsaak) To: bound@xirtlu.ENET.dec.com Subject: ANSI IISP requirements Jim, I would encourage IETF to review the 35 or so IISP identified requirements and provide responses to those where IETF has work or specifications. For example, one calls for Universal Identifiers to locate data ... (like URL's maybe??) ... The list is on the web at: http://www.ansi.org/iisp/needlist.html The one I've refered to here is #29 Thanks, jim ------- End of Forwarded Message
- IISP Networking Requirements WEB Page Ptr bound
- Re: IISP Networking Requirements WEB Page Ptr Scott Bradner
- Re: IISP Networking Requirements WEB Page Ptr Brian Carpenter CERN-CN
- Re: IISP Networking Requirements WEB Page Ptr bound