🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.protocols.iso
Article #946

meeting announcement

#946
From: Dr. Alex Kuo
Date: Fri, 18 Sep 1992 20:37
94 lines
5027 bytes
***************** INVITATION *********************************************

ANNOUNCEMENT: JOINT IEEE/TCOS TROI MEETING at NIST
			  September 23-24 (Wed & Thu), 1992

SPONSOR     : IEEE/Technical Committee on Open Systems (TCOS)
CONVENOR    : J. J. Cinecoe, Boeing-BCS

You are invited to participate in the first meeting of the ad-hoc working
group on the specification of API for distributed computing for OSI.
This work will be undertaken under the rules for project authorization
request of the IEEE/Technical Committee on Open Systems (TCOS).
The current work plan of the ad-hoc group is named Transparent Remote
Operation Interface (TROI).

The Wednesday and Thursday meetings will be held from 9AM to 5PM in Room
B119 of Building 224 on the NIST campus in Gaithersburg Maryland during
the OIW workshop week.

The OIW registration desk is on the Administration Building (the only
high-rise building on the NIST campus) ground floor. Registration fees
for the entire week are around $250. A reduced registration exists for
those not attending the entire week.

****************** BACKGROUND *******************************************

The ad-hoc group was formed in response to North American MAP/TOP Users
Groups (NAMTUG) request who require distributed computing capability over
an OSI stack.  NAMTUG presented these requirement via presentations
(OSI Client/Server Profiles) to both the OIW and TCOS/DS. NAMTUG identified
the creation of APIs for OSI as a key component for the delivery of OSI
Services as a corporate utility (and a potential asset).
The current work plan of the ad-hoc group is named Transparent Remote
Operation Interface (TROI), but is not intended to preclude APIs for TP
and RPC.  This is just one aspect of providing the full set of functional
specification for distributed services over an OSI network.

The placement of the TROI API work under the Accredited Standards Committee
-IEEE is appropriate due to the ongoing work for OSI API undertaken by
Distributed Services Steering Committee (DSSC) under the auspices of TCOS.
TCOS has provided the POSIX specifications and more recently the standard
APIs for X.400, X.500, FTAM, and various levels of OSI protocols.

The IEEE PAR for the development of a ROSE API was submitted to TCOS
Distributed Services Steering Committee at their quarterly meeting on July
15 in Chicago, IL.  This officially kick starts the ad-hoc group formed to
define and contribute to the development of a set of APIs for OSI Distributed
Processing.  Although the PAR references a Transparent Remote Operation
Interface, it is up to the ad-hoc group to define the scope of the work and
the role of ROSE. The PAR API work may be split into several sub-project
which would facilitate the reconciliation with ISO/RPC and OSI TP which
are also considered essential in the distributed computing equation.
ROSE is an OSI standard (ISO/IEC 9072) and the intend of the proposal is
to specify an "Exposed ROS Services" for application program development.

The current Agenda includes:
	1) Introductions
	2) Agenda review and approval
	3) Presentation on TROI - IEEE Project Authorization Request
	4) Status of OSI API Standards
	5) Review of IEEE PAR for TROI
	6) Formulation of Scope and Agenda of work
	7) Membership and liaisons
	8) Base documents and Work plan
	9) Agenda and Work Items for next meeting.

The above topics are scheduled to be completed during the two days of work.
However the schedule is intended to maintain a level of flexibility to
answer all potential questions and resume with a viable plan for the
development of the API in cooperation with other PARs and the workshop SIGS.

****************** DIRECTION *******************************************

To get to NIST, you can fly into either of the two airports in the
Washington DC area: Washington National Airport and Dulles Airport.
Both are about 25 miles from NIST.

From either airport, get to the Beltway
(Route 495) that is north of Washington.

Then take Interstate 270 North to
Exit 10 (Clopper Rd.; Rt 117W).

Take the exit ramp to the end,
continue right to get onto Rt 117W,
go about a quarter mile to the first red light and
go left to enter the NIST campus.

At the end of the entrance road to the campus,
go left onto the perimeter road and
look for signs for OIW or look for the high-rise Admin. Bldg.

****************** END *******************************************
Technical Details
Message-ID: <346093000@pandora>
Path: arc1-ca.pugleaf.net!sparky!uunet!timbuk.cray.com!equalizer!sdcrsi!network.ucsd.edu!usc!wupost!gumby!destroyer!fmsrl7!lynx!news.cs.indiana.edu!noose.ecn.purdue.edu!sparkyfs.erg.sri.com!csl.sri.com!nntp1.radiomail.net!pandora!nntp1.radiomail.net!portal!uunet!dset!alex

Show Full Headers
Complete Article Headers
From: Dr. Alex Kuo <alex@dset.UUCP>
Path: arc1-ca.pugleaf.net!sparky!uunet!timbuk.cray.com!equalizer!sdcrsi!network.ucsd.edu!usc!wupost!gumby!destroyer!fmsrl7!lynx!news.cs.indiana.edu!noose.ecn.purdue.edu!sparkyfs.erg.sri.com!csl.sri.com!nntp1.radiomail.net!pandora!nntp1.radiomail.net!portal!uunet!dset!alex
Date: 18 Sep 92 20:37:21 GMT
Subject: meeting announcement
Newsgroups: comp.protocols.iso
Message-ID: <346093000@pandora>
Organization:  DSET Corporation, Lebanon, NJ
Keywords:  OSI ROSE API Async-messaging
Lines: 97