Re: Call for participation -- Is OSI really useful?

"Stover, Robert" <BOB@p01.uci.com> Fri, 03 June 1994 18:01 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09454; 3 Jun 94 14:01 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa09445; 3 Jun 94 14:01 EDT
Received: from sun2.nsfnet-relay.ac.uk by CNRI.Reston.VA.US id ab13822; 3 Jun 94 14:01 EDT
Via: uk.ac.ulcc.vmsfe; Fri, 3 Jun 1994 18:47:07 +0100
Via: UK.AC.NSFNET-RELAY; Fri, 3 Jun 94 18:42 GMT
Received: from kracken.uci.com by sun3.nsfnet-relay.ac.uk with Internet SMTP id <sg.19383-0@sun3.nsfnet-relay.ac.uk>; Fri, 3 Jun 1994 18:41:37 +0100
Received: by kracken.uci.com (/\==/\ Smail3.1.28.1 #28.3) id <m0q9c4E-0000dYC@kracken.uci.com>; Fri, 3 Jun 94 11:25 CDT
Received: by p01.uci.com with Microsoft Mail id <2DEF7742@p01.uci.com>; Fri, 03 Jun 94 11:32:34 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Stover, Robert" <BOB@p01.uci.com>
To: John Day <Day@bbn.com>, laurae <laurae@laurae.ar.telenex.com>
Cc: "73543.1077" <73543.1077@compuserve.com>, agrawala <agrawala@cs.umd.edu>, Baker <Baker@forty2.enet.dec.com>, baos <baos@oss.com>, bob <bob@uci.com>, conrad <conrad@oss.com>, cpd <cpd@one.com>, dallas <dallas@forty2.enet.dec.com>, DBRITT <DBRITT@nctsemh-npt.navy.mil>, dchoi <dchoi@vax2.cstp.umkc.edu>
PP-Warning: Parse error in original version of preceding line
Original-Cc: "73543.1077" <73543.1077@compuserve.com>, agrawala <agrawala@cs.umd.edu>, Baker <Baker@forty2.enet.dec.com>, baos <baos@oss.com>, bob <bob@uci.com>, colin%intelsat <colin%intelsat@uunet.uu.net>, conrad <conrad@oss.com>, cpd <cpd@one.com>, dallas <dallas@forty2.enet.dec.com>, DBRITT <DBRITT@nctsemh-npt.navy.mil>, dchoi <dchoi@vax2.cstp.umkc.edu>
Cc: ed-kelly <devon!ed-kelly@mhs.attmail.com>, dicksc <dicksc@uci.com>, dicksw <dicksw@uci.com>, dyons <dyons@arch4.att.com>, eric <eric@isci.com>, ews <ews@ctt.bellcore.com>, frank <frank@cos.com>, gray <gray@osi.ncsl.nist.gov>, heather <heather@tandem.com>, jmhunt <jmhunt@atlsita.org>, kk <kk@arinc.com>, kuiper <kuiper@osison.osiware.bc.ca>
Cc: lee <lee@huachuca-jitcosi.army.mil>, lee <lee@ntd.comsat.com>, lee <lee@vax2.cstp.umkc.edu>, lowe <lowe@osf.org>, lrajchel <lrajchel@attmail.com>, markh <markh@rsvl.unisys.com>, mkao <mkao@cup.hp.com>, "p.furniss" <p.furniss@ulcc.ac.uk>, quigley <quigley@cup.hp.com>, rdesjardins <rdesjardins@attmail.com>, ron11 <ron11@cc.bellcore.com>
Cc: rschilk <rschilk@huachuca-jitcosi.army.mil>, sjg <sjg@arch4.att.com>, THINOSI <THINOSI@ulcc.ac.uk>, troisi_brenda <troisi_brenda@tandem.com>, truoel <truoel@gmd.de>, truskows <truskows@cisco.com>, vantrees <vantrees@sed.stel.com>, wdavison <wdavison@rlg.stanford.edu>, X3T5 <X3T5@osf.org>
Subject: Re: Call for participation -- Is OSI really useful?
Date: Fri, 03 Jun 1994 11:24:00 -0700
Message-ID: <2DEF7742@p01.uci.com>
Encoding: 49 TEXT
X-Mailer: Microsoft Mail V3.0
X-Orig-Sender: THINOSI-request@ulcc.ac.uk
X-ULCC-Sequence: 196
X-ULCC-Recipient: ietf-archive%us.va.reston.cnri@uk.ac.nsfnet-relay

I think I have been "over quoted" a bit so maybe I should inject a few 
thoughts ( I never use the term backplane architecture in reference to OSI. 
Where did that come from?).  I certainly agree with John that many of the 
early contributors in the development of OSI had a good vision of where open 
network architectures were going, even a few who worked for large 
corporations.  Some major vendors had internal architecture work that 
paralleled OSI and influenced its development.  At the same time all of the 
major vendors had their own private communications / network architectures 
with large installed bases.  Some large vendors saw OSI as common structure 
that could be used to interface their private networks to other networks, 
thereby protecting their currently installed equipment and in the longer 
term providing a potential migration path to a native OSI capability.  It 
was in this environment of needing to interconnect these dissimilar systems 
that the work on OSI was started.  It would be incorrect to suggest that the 
ability to provide a basis for gateway capabilities was the only initial 
objective for OSI.  There were many objectives for OSI as well as many 
interests involved.  As in any large project, this sometimes led to 
additional complexity and not every decision perfectly satisfying everyone.

One of the objectives for the OSI architecture was the ability to 
accommodate changing technology.  It is natural to have some change of 
emphasis over the years to reflect the immense changes that have occurred in 
our industry, both in terms of the make up of the equipment vendors and in 
terms of the available technologies.  The interesting thing is that what 
precipitated this discussion was the call for an OIW BOFmeeting to work on 
accommodating precisely these requirements.  I don+t think anyone has lost 
track of the objectives.  Possibly, the language in the announcement could 
have been better stated.  The current direction in much of the OSI work (in 
which many of commentors are intimately involved) is toward providing more 
flexibility and efficiency, such as this meeting on Upper Layer Efficiency. 
 By providing more capability to select only the required functionality, OSI 
has the potential of being applicable to an expanded area of usage, i.e., 
providing efficient systems to support time critical applications in one 
case and yet still providing the full functionality when needed for complex 
applications.

A number of groups are considering ways to make the standards process more 
effective, e.g., faster, including wider participation, etc.  Any practical 
suggestions toward that end would be appreciated.  However, I would hope 
that the philosophical discussions would not detract from the primary reason 
for the meeting, Upper Layer efficiency.


Best Regards,

Bob Stover