Proceedings of the Fourth

LAN-Transport Workshop

Report of the Fourth Workshop for Local Area Network

Implementors of the NBS Specifications of the

International Standards Organization Transport

Class 4 Protocol

U S. DEPARTMENT OF COMMERCE

National Bureau of Standards

Institute for Computer Sciences and Technology

Systems and Network Architecture Division

Washington, DC 20234

October 27 - 28, 1983

QC

100

. U56

33-2796

1933

U S DEPARTMENT OF COMMERCE

NATIONAL BUREAU OF STANDARDS

national bureau

' Cf STANDARDS

\ LIBRARY

NBSIR 83-2796

'TUC.

QC

l OO

PROCEEDINGS OF THE FOURTH

LAN-TRANSPORT WORKSHOP

> U6 (o

1

Report of the Fourth Workshop for Local Area Network

Implementors of the NBS Specifications of the

International Standards Organization Transport

Class 4 Protocol

U S. DEPARTMENT OF COMMERCE

National Bureau of Standards

Institute for Computer Sciences and Technology

Systems and Network Architecture Division

Washington, DC 20234

October 27 - 28, 1983

U.S. DEPARTMENT OF COMMERCE, Malcolm Baldrige, Secretary

NATIONAL BUREAU OF STANDARDS, Ernest Ambler, Director

ABSTRACT

The National Bureau of Standards Institute for

Computer Sciences and Technology (ICST) has

prepared specifications for the International

Organization for Standardization's (ISO) Class 4

Transport Protocol. At the request of a number of

companies, ICST organized a workshop series for

implementors of these specifications using local

area networking technology. The first workshop

focused on implementation techniques and

strategies so that a multivendor demonstration of

these protocols can occur at a major computer

conference in 1984 targeted for the NCC 1984.

Primarily the details of CSMA/CD and Transport

Class 4 were discussed and parameters were

selected. A second workshop focused on token bus

LANS and file transfer applications to be run at

the targeted 1984 demonstration. Agreements on

the specifics of the file transfer protocol were

reached at the third workshop. This report

documents the fourth workshop in the series of

LAN-Transport workshops. The fourth workshop

covered further refinements to the file transfer

protocol, testing procedures, and demonstration

details

Keywords: communication protocols, computer networks,

transfer protocol, local area networks.

SUMMARY

This report documents the fourth workshop of the

LAN-Transport Workshop Series for implementors of

the ICST specification of the ISO Class 4

Transport Protocol over IEEE 802 compatible LANs

using local area networking technology.

At the fourth workshop, agreements to date were

reviewed and further refinements to the file

transfer protocol were made. FTP testing was

discussed and a base set of criteria for FTP tests

was developed. In addition, a number of

demonstration details were discussed including

booth etiquette, advertising, staffing, and so on.

The participants agreed to the need for a fifth

workshop, to be held as earlier planned in

February, in Gaithersburg, Maryland. An

announcement will be mailed to the current

LAN-Transport Workshop Series distribution list in

the near future.

file
CONTENTS

Abstract

Summary

1. Participants in the Fourth Workshop

2. Introduction and Opening Remarks

3. File Transfer Protocol

4. Demonstration Particulars

5. Testing

6. FTP Testing

7. Technical Session at NCC

8. Newcomers

9. After NCC

10. Follow-on Meetings

Attachments

1. File Types

2. NCC Booth Overview

3. Token Bus Booth

4. CSMA/CD Booth

5. Tentative Agenda for CSMA/CD Meeting

6. Base Set of Documents Relating to Testing

7. Suggested Demonstration FTP Test Procedures

8. FTP Testing Issues (to Resolve)

9. Updated Mailing List

Bibliography
Page 3

1. participants

The fourth workshop, chaired by

was attended by the following.

Kenneth Aird

Hewlett Packard

3404 E. Harmony Road

Ft. Collins, CO 80525

(303) -226-3800

Pat Amaranth

General Motors

GM Tech Center-ME&D

Dept. 69 EA-BLD9

Warren, MI 48090

(315 ) -575-0808

Gary Baczkowski

Allen-Bradley

747 Alpha Drive

Highland Hts., OH 44118

(216) -449-6700 X4218

James Berets

Bolt, Beranek, & Newman

10 Moulton Street

Cambridge, MA 02238

(617 ) -497-2593

Bob Blanc

National Bureau of Standards

Technology Building Room A231

Washington, DC 20234

(301) -921-3317

Gerald Brinda

NCR Comten

2700 Snelling Ave N

Roseville, MN 55113

(612) -638-7685

Laurie Bride

Boeing Computer Services

P O Box 24346 MS 7F-01

Seattle, WA 98124

(206) -763-5744

Allen Brown

Gould, Inc., CSD

6901 W. Sunrise Blvd.

Ft. Lauderdale, FL

(305) -587-2900 X5198

Mr. Maris Graube, Tektronix,

Roy Cadwallader

ICL

West Avenue/Kinsgrove

Stoke-on-Trent ST7 1TL UK

44 782 29681 X3806

A. Lyman Chapin

Data General Corp.

4400 Computer Drive

Westborough, MA 01746

(617) -366-8911 X3056

Michael Chernick

National Bureau of Standards

Technology Building

Washington, DC 20234

(301) -921-3516

John Davidson

Ungermann-Bass Inc.

2560 Mission College Blvd.

Santa Clara, CA 95050

(408) -496-0111

Ed Deenihan

General Motors

GM Technical Center B/MD-66

Warren, MI 48090-9040

(313) -575-0892

Emmanuel G. Delahostria

Allen-Bradley

747 Alpha Drive

Highland Hts., OH 44143

(216) -449-6700

Edward Efron

Able Computer

1732 Reynolds Avenue

Irvine, CA 92714

(714 ) -979-7030

Robert W. Franklin

Motorola Microsystems

2900 South Diablo Way

Tempe, AZ 85282

(602) -829-3013
Page 4

John Heafner

National Bureau of Standards

Technology Building Room B218

Washington, D.C. 20234

(301) -921-3537

Rebecca Hutchings

Honeywell

7900 Westpark Drive

McLean, VA 22066

(703) -827-3982

Maris Graube

Tektronix

Box 500, MS 50-473

Beaverton, OR 97077

Navindra Jain

Excelan

2180 Fortune Drive

San Jose, CA 95131

( 408 ) -945-9526

D. Janetzky

Siemens

P O Box 211080

7500 Karlsruhe

West Germany

721 595 2350

Vadivelu Jeyabalan

Ford Motor Company

Room E-1174 Scientific Res. Lab

P O Box 2053

Dearborn, MI 48121

(313) -322-3952

Ken Kanaby

General Motors, APMES

GM Technical Ctr MD-57

Warren, MI 48090-9040

( 313 ) -575-0899

Mr. Kreppel

Siemens

Guenther-Scharowsky-Str

D-8520 Erlangen

West Germany

9131 7 31759

Chak Lai

Digital Equipment Corporation

21333 Haggerty

Novi, MI 48050

( 313) -348-8900

Aldrin Leung

Integrated Microcomputer Systems

5320 Marinelli Road

Rockville, MD 20852

(301) -984-3343

Jerry Linn

National Bureau of Standards

Technology Building Room B212

Washington, DC 20234

(301) -921-2601

Andy Luque

Tektronix

131 SE Salmon

Redmond, OR 97756

( 503 ) -923-0333

Joseph R. Maixner

Advanced Computer Consultants (ACC)

2901 Park Avenue

Santa Cruz, CA 95073

(408) -425-0937

Ronald M. Martin

Industrial Technology Inst.

P O Box 1485

Ann Arbor, MI 48106

(313) -763-9482

Douglas McCallum

NBI , Inc.

P 0 Box 9001

Boulder, CO 80301

(303) -444-5710

Kevin Mills

National Bureau of Standards

Technology Building Room B212

Washington, DC 20234

(301) -921-2601
Jose Ramiro Montealegre

Carleton University

180 Argyle Street Rm 1524

Ottawa, Ontario, CANADA K2P-1B7

( 613 ) -237-1320 X542

James Moulton

National Bureau of Standards

Technology Building Room B212

Washington, DC 20234

(301) -921-2601

Pat Mulvey

IBM > 21Q/B231-1

P. O. Box 1328

Boca Raton, FL 33432

(305) -998-1561

Fran Nielsen

National Bureau of Standards

Technology Building Room B212

Washington, DC 20234

301-921-2601

D. J. Power

ICL

Arndale Centre

Manchester, UK

James Quigley

IBM

P 0 Box 10500

Palo Alto, CA 94304

(415) -855-7124

Don Rippy

National Bureau of Standards

Technology Building Room A231

Washington, DC 20234

(301) -921-2948

Allen Rochkind

Intel Corporation

3065 Bowers Avenue

Santa Clara, CA 95051

( 408 ) -987-7817

Rob Rosenthal

National Bureau of Standards

Technology Building Room B226

Washington, DC 20234

(301) -921-3516

Robert L. Sangroniz

Tektronix, Inc.

Box 1000 MS 63-489

Wilsonville, OR 97070

(503) -685-3816

Alan Sciacca

The Foxboro Co.

Dept 341

38 Newponset Avenue

Foxboro, MA 02035

(617) -549-3190

Inder M. Singh

Excelan

2180 Fortune Drive

San Jose, CA 95131

(408) -945-9526

Rita J. Stubler

Digital Equipment Corp.

21333 Haggerty Road

Novi, MI 48050

(313) -348-8900

Dick Swee

Charles River Data Systems

983 Concord Street

Framingham, MA 01701

(617) -626-1101

Ken Swenson

Boeing Computer Services

P 0 Box 24346 MS 7A-05

Seattle, WA 98124

(206 ) -763-5385

Roger F. Thompson

IBM

1501 California Avenue

Palo Alto, CA 94306

(415) -855-7235
Shack Toms

Allen-Bradley

747 Alpha Drive

Highland Hts., OH 44143

( 216 ) -449-6700 X4652

Lyle Weiman

Hewlett Packard - IND

19446 Pruneridge Avenue

Cupertion, CA 95014

(408 ) -725-8111

Ronald Yara

Intel Corporation

3200 Lakeside Drive

Santa Clara, CA 95051

(408 ) -496-7703

Prentiss Yates

Cincinnati Milacrom

Route 48 & Mason Road

Lebanon, OH 45236

( 513 ) -494-5426
2. Introduction and Opening Remarks

Mr. Rob Rosenthal, NBS , welcomed the attendees to the fourth

LAN-Transport workshop and introduced Dr. John Heafner, NBS,

temporary stand-in for Mr. Maris Graube, workshop chairperson.

The agenda was reviewed and two additions were made to Fr idav*"5"

schedule - a presentation bv National Trade Productions and a discussion of booth etiquette.

2.1 Agreements to Date

The following agreements about the NCC demo were reviewed:

i. IEEE 802.3 CSMA/CD and 802.4 Token Bus will be used,

XID and TEST will not be sent.

ii. No internet will be used.

iii. Transport agreements -

- Volume 3 of NBS Transport Specification

(February 1983) will be used.

- 31 bit sequence space will be used.

- Expedited will not be used.

- Unit data will not be used.

- Expedited will not be used.

The base document will be modified to allow a service

without expedited. If expedited is unsupported, the

requestor should propose no expedited service in the CR,

following ISO rules for negotiation; it will be a protocol error to use expedited.

- TSAP (transport suffix) will be two octets.

- Application TSAPs defined in the Proceedings

of the Second LAN-Transport Workshop are

still valid

00FF file transfer,

00FE file transfer/NAPLPS data,

00FD programmable control applications,

00FC messaging.

iv. File Transfer

The following agreements, reached at the third workshop were

incorporated into the August 1983 file transfer protocol

document:

- maximum size of files to be transferred will be 64K,

by te s

;

larger files may be transferred by mutual agreement of

more than one vendor,

- even number of PCI octets was eliminated,

- file type supported by all vendors will be ASCII data,

with carrriage return <cr> and line feed <lf>
contained in the file,

- applications not supporting lower case ASCII

should expect to see and convert lower case,

- other file types (such as NAPLPS graphics, 3270,

binary, Regis graphics) may be transferred by

mutual agreement of more than one vendor,

- receiving entity will abort on receipt of

protocol errors,

- least significant octet will be presented first, and

- receipt of ABORT, CANCEL, or DISCONNECT will result

in data loss.

3. File Transfer Protocol

After discussion, it was agreed that only two file types will be

supported for the demo: binary and public ASCII. The only

control characters to be recognized in public ASCII will be <cr>

and <lf> and these characters must appear together. Attachment 1

is a copy of the vugraph detailing this agreement. It was agreed

not to use mixed data types for the NCC demo.

Proposal for file management services -

Mr. Allen Rochkind, Intel, presented a proposal for file

management services needed for the intervendor demo. Allen

described the FILEDIR directory, which will contain the list of

all files on the server accessible by other nodes; NETDIR, which

will contain the filestore narae/48 bit host address translation

table for each node recognized by the consumer; and the FCOPY

and NETDIR Maintenance utilities. FCOPY will facilitate copying

remote vendors' files onto the server for later access by other

nodes and will update the FILEDIR. The NETDIR Maintenance

utility, whose name at each consumer node is implementation

dependent, will update the NETDIR directory file when new nodes

are added to the network. In answer to a question on the need

for local pathnames in the FILEDIR, it was suggested that these

pathnames be deleted from the FILEDIR.

Write /Create -

Discussion of write/create centered on whether these services

should be mandatory or optional. Four service primitives have

been added to the specification to include write/ create. These

primitives, in addition to those contained in the original

specification, comprise the extended file transfer service

subset. Consensus was reached that write/create would be

negotiated as pictured:
connect with

extended subset

wr ite/create

Page 9

< A "agrees" basic subset

to basic

subset

write request

| A | >| B | < A violates T_disconnect

agreement

connect with

extended subset

write/create

| A | >| B | <_

extended subset

write request transmission of the

| A | >| B | write request is not

< a protocol violation

write response

The FTP document will be revised to reflect the above agreement

and will be sent to attendees. Several vendors indicated they

may implement write/create for the NCC demo.

The following list of protocol issues was defined:

i. File type vs. data type,

ii. Deadlock,

iii. Encoding Questions,

iv. Subset IDs,

v. Formal Description and Miscellaneous Questions,

i. File type vs. data type -

Mr. Allen Rochkind, Intel, reviewed his File Management Services

document in which the FILEDIR service lists the type of data

contained in the file. He suggested that, since the FILEDIR

contains the data type of the file, the information is not needed

in the protocol. The FILEDIR will be an ASCII text file. Since

the local pathname field will be optional, knowing the local

pathname cannot be a constraint. Local pathnames would be useful

for allowing users to create files on one system and view the

files on other systems. An incomplete strawvote showed that

seven vendors wanted to remove file type/data type from the file

transfer protocol; there was no indication of how many wanted to

retain the information in the protocol.

transmission of the

write request is a protocol violation
Page 10

Discussion of file type frequently became a discussion of

applications. For example, the question arose as to whether

creating files would be dynamic (at the NCC demo) or static, and,

therefore, whether the FILEDIR would be used at NCC or just for

system development. These issues, along with the file type

discussion, was postponed until the applications meetings in

November and December.

ii. Deadlock -

Since there are states within the protocol which cannot be exited

until responses are received, it was questioned whether timeout

functions should be included to handle possible deadlocks if

responses are not received. Consensus was that this is an

implementation issue, that the FTP can send an F_abort if a response is not received when expected.

iii. Encoding Questions -

Mr. Jim Berets, BBN, clarified some encoding questions as

follows

— the length field includes the header length, and — there are two octets for the header length because

under certain circumstances the header may exceed

255 octets. (For example, a diagnostic string alone

may be 255 octets long.)

It was decided that no further modifications should be made to

the file transfer protocols since there are time constraints.

Vendors will use the NBS problem/failure report form to report

problems with the FTP specification and NBS will circulate copies

of the reports.

iv. Subset IDs -

There was a request to include a transaction service subset which

could be used with a messaging application, but since there is a different TSAP for messaging, this service subset was deemed

unnecessary.

v. Formal Description and Miscellaneous Questions -

Mr. Jim Berets, BBN, fielded several questions on the formal

description of the file transfer protocol, including

clarification of a typographical error in the comments describing

transition 22. Another question concerned the behavior of the

protocol if a T_disconnect was received on a connection which had

already been disconnected. The behavior of the protocol, in that

case, would be a local implementation issue. A new version of

the FTP document will be sent to participants.
Page 11

4. Demonstration Particulars

4.1 Trade Show Support -

Mr. Ron Yara, Intel, gave an overview of vendor and

participating company responsibilities for the NCC booth for

CSMA/CD. A copy of his vugraphs is attachment 2. He also showed

a booth rendering as an example of how the NCC demo booth for

CSMA/CD could be designed.

4.2 GM Status Report -

Ed Deenihan, GM, presented a status report of GM's efforts to

date on their NCC booth. A copy of his vugraphs is attachment 3.

GM proposed that each of the six vendors have two terminals in

the booth. GM has scheduled a meeting, November 15, to finalize

the messaging protocol for the programmable controller

application. Each vendor must have successfully tested a set of

test scenarios, currently being selected, prior to testing

on-site at the GM Technical Center.

4.3 NBS Status Report -

Mr. Rob Rosenthal, NBS, presented a status report of the CSMA/CD

demo (attachment 4). Several vendors have made commitments to

particpate. In order to participate, vendors roust submit a purchase order, not to exceed $20,000, to NBS. Costs of the demo

will be charged against this purchase order. The booth will be

built and displayed at NBS prior to the NCC. To coordinate both

booths and have commonality of design and motifs, it was

suggested that, if possible, GM work with the organization chosen

by the NBS to provide the CSMA/CD booth.

4.4 Connections to Foreign Booths -

Connections to foreign booths will not be allowed in the GM demo.

As for the CSMA/CD booth, some vendors expressed a desire to

interconnect their booth with the common intervendor booth.

There was a consensus vote (14 yes, 3 no) to allow, if any

foreign connections, only those having point-to-point repeaters

over standard cable, whose equipment has gone through full

verification at NBS, and which can be switched off from the main

demo booth. The pros and cons of allowing foreign booths were

stated as follows:

PRO - More participants,

- More equipment interconnection,

- Greater public relation,

CON - Uncertainty of network security,

- Increase in testing effort,

- Increase in financial obligation.

Those participants interested in having foreign booths connected

to the raultivendor booth must convince other participants, at the
Page 12

December 1 CSMA/CD meeting, that foreign booths should be

allowed

4.5 Booth Etiquette -

Mr. Ron Yara, Intel, led the discussion of booth etiquette. He

stated the importance of having a marketing person available for

the December CSMA/CD group meeting to provide inputs. Concerns

will be:

- fairness in the booth (equal space, no product

specific discussions or literature, and so on)

,

- consistent responses from personnel staffing

the booth,

- continued emphasis on standards. (Visitors

should be directed to particular vendors

booths, if questions or discussion

becomes unrelated to standards activities.)

4.6 Advertising -

NBS will schedule an open press day for token bus and CSMA/CD

participants. Trade editors will be notified prior to the NCC to

show editors what to expect; press packages will be prepared.

4.7 Able Announcement -

Mr. Ed Efron, Able, announced the Easyway Ethernet Port which i3

a board containing protocols of layers one through four.

4.8 Parallel Discussions on Demo Details

4.8.1 GM/Token Bus Demo - Transport Testing

General Motors will test its transport implementation remotely

with NBS Transport over Telenet. GM's transport package will be

used to test test transports against a subset of the NBS

scenarios, locally at the GM Technical Center. Vendors must

validate their transport implementations with NBS prior to coming

on-site at GM; no remote testing will be provided to vendors by

GM. GM should have further definition of on-site testing

procedures and the scenario subset at the multi-vendor demo

meeting to be held at the GM Technical Center on November 15,

1983 . FTP

Preliminary discussions on a mechanism for vendor FTP testing

indicated a need for definite procedures and central arbitration.

Concern was expressed that consistency in this area be maintained

between the CSMA/CD and token bus demonstrations.

Ideas for the "attendee” interface to FTP were discussed; GM
Page 13

requested that the vendors develop lists of desirable "user"

functions, to be discussed at the November 15 meeting.

Programmable Controller Protocol

The programmable controller data format, known as the "GM

standard message,” is firm for the NCC demo. A transaction

oriented protocol has been proposed by Allen-Bradley which is

being distributed for review by participants. Final decision on

this proposal will be made at the November 15, multivendor

meeting

.

4.8.2 CSMA/CD Demo -

Mr. Rob Rosenthal, NBS , presented the NCC time schedule

(attachment 4). The LAN-Transport group will allow NBS to accept

vendors' contributions and offers of service in return for NBS

assurance of being fair and equitable in acceptance of such

offers. Each vendor will supply a contact person whom NBS will

poll on major decisions; names of contact persons should be

submitted to Rob Rosenthal by c.o.b. Monday, October 31. NBS

will submit timely reports of progress and status of the contract

to contact persons. NBS must have vendors' letters of commitment

(or purchase orders not to exceed $20,000) by November 15, 1983.

These should be sent to Ms. JoAnn Brooks, National Bureau of

Standards, Technology Building Room A231, Washington, D.C.

20234. If a company "drops out," it is still committed to paying

a share (not to exceed $20,000) of the expenses associated with

the NCC booth. Vendors will be billed for their share in the

second or third quarter of 1984.

The following organizations indicated their interest in adding

their names to the list of participants in the CSMA/CD demo:

Able

Assoc. Computer Consultants

Charles River Data Systems

Codenoll

Data General

Excelan

Joe Devita

Joseph Maixner

Dick Swee

John Balen

A. Lyman Chapin

Inder Singh

Ms. Laurie Bride will investigate the possibility that Boeing

Computer Services can expedite a contract to provide the booth

for the NCC. NBS will continue the RFP process in parallel with

Ms. Bride's investigation. If Boeing can offer a contract

earlier than NBS, then Boeing will do the contracting for the NCC

booth

.

There will be a meeting December 1 and 2 in Seattle, hosted by

Boeing Computer Services, to discuss themes and coordination of

the booth; a tentative agenda is attachment 5.

5. Testing

Jerry Linn reviewed the base set of documents, attachment 6,
Page 14

relating to testing. Vendors should inform NBS if testing with

other vendors is desired.

6. FTP Testing

NBS will not implement or test FTP prior to the NCC; NBS will be

a measurment node in the CSMA/CD booth.

Ms. Pat Amaranth, GM, presented some FTP testing issues to be

resolved (attachment 8). The central issue, as yet unresolved,

is whether FTP should be tested via a formally defined scenario

set (as is the case with Transport) or whether a combined FTP and

application test constitutes sufficient testing. Proponents of

testing FTP simply by exercising the applications cite expediency

as justification. Proponents of formal, separate FTP tests

believe that the combined testing will be inadequate. Mr. Maris

Graube, Tektronics, suggested the DEC implementation as a possible FTP reference implementation; DEC will investigate that

poss ibility

.

Mr. Jim Berets, BBN , presented a set of FTP test procedures,

attachment 7, for each vendor to perform at the vendor's site.

The token bus group is developing a common set of functions that

the user would see; it was suggested that the CSMA/CD group

should take the same approach. All participants are asked to

write two lists of functions, specific and common, for the demo.

All FTP applications and lists of user functions should be sent

to Ms. Vicki Howard, National Bureau of Standards, Technology

Building Room B218, Washington, D.C. 20234, by November 15. NBS

will extract information from these inputs, will exchange

information with GM, and will then distribute this information to

the mailing list.

It was agreed to work from the BBN test suggestion as a base and

augment the base with a test of the transfer of binary

information.

7. Technical Session at NCC

Mr. Rob Rosenthal, NBS, reported that NBS has offered NCC a technical panel session. The panel will discuss multivendor

protocols and, in particular, what standards can and cannot cover

and what experiences vendors had with the multivendor

demonstration. The panel is thus far composed of Mr. Tony

Lauck, DEC, Mr. Jim Quigley, IBM, and Mr. Allen Rochkind,

Intel. If other vendors wish to participate, they should contact

Mr. Bob Blanc, NBS.

8. Newcomers

Mechanisms for allowing new participants are needed. Constraints

on adding these newcomers would be that their participation must

be "standards oriented," that they submit a purchase order (not

to exceed $20,000), and that a limited number of participants can

be accommodated in the booth.
Page 15

9. After NCC

9.1 National Trade Productions -

Mr. Sam Smith and Mr. Joe Rupple, both from National Trade

Productions, gave a brief overview of INTEC and requested that

the LAN-Transport group consider bringing the NCC demo to the

INTEC conference in October, 1984. Participants in the NCC demo

were asked to contact their marketing people to determine whether

there is interest in taking the LAN-Transport demo to other

shows.

9.2 Follow-on Demonstration of IP -

Dr. John Heafner gave a brief overview of the status of the

draft proposed ISO internetwork protocol (IP). He expressed the

NBS interest in a follow-on global demonstration using internet

to show the interconnection of networks. A show of hands

indicated that vendors were also interested in internet;

therefore, there will be follow-on meetings to discuss this

protocol after the NCC demo.

9.3 Additional High Level Protocols -

In addition to internet, the complete ISO file transfer protocol

will be a candidate for a follow-on demonstration. (The file

transfer protocol being used at the 1984 NCC demo is a subset of

the current, as yet incomplete, ISO protocol.) Dr. John Heafner,

NBS, stated that NBS has specifications for message handling

facilities and will have specifications for file transfer after

the protocol stablizes within ISO. Mr. Jim Moulton, NBS,

informed the group that an ISO draft proposed basic class virtual

terminal protocol is expected by the end of 1984. GM mentioned

their need for a transaction protocol to be used for device

control; Dr. Heafner suggested that GM check the NBS messaging

format standard, FIPS 98. It was also suggested that those

vendors who are interested in high level protocols exchange

information among themselves and investigate what other vendors

are doing. After January, GM will make available their MAP

protocol specifications, which include specifications for file

transfer, virtual terminal, management, and directory services.

Mr. Moulton announced that ISO session has progressed to the

draft international standard stage and that most likely NBS will

issue session as a guideline rather than as a standard. It is

hoped that some functions now in the session layer will be pushed

upward to the common application sublayer as that is developed.

He stated that the ISO presentation layer group is working

towards a language to describe a common syntax, targeted for

draft proposed standard status in early 1985. Groups interested

in presentation layer protocols should make their needs known to

ANSI X3T5.5, the national committee working on layer 6 protocols

for open systems interconnection.
Page 16

9.4 Gateway CSMA/CD - Token Bus

f

The discussion of gateways evolved into a discussion of

addressing. Mr. James Moulton, NBS , announced that addressing,

designed to accommodate subnetworks in place today, will become a draft proposed standard after the March 1984 SC6 WG2 meeting. He

also volunteered to give a status report of ISO and NBS standards

at the next LAN-Transport workshop.

10. Follow-on Meetings

The token bus meeting will be held at the GM Technical Center,

November 15. Boeing will host a meeting of the CSMA/CD group in

Seattle, December 1 and 2. A tentative agenda of that meeting is

attachment 5. The next LAN-Transport workshop will be held in

mid-February; NBS will send meeting details to all participants.
ATTACHMENT 1

presented by John Heafne

CONSENSUS ON FILE TYPES

TWO FILE TYPES

- PUBLIC ASCII

- BINARY

PUBLIC ASCII

EXPECTED

- UPPER/LOWER CASE ALPH

- SPACES

~ NUMBERS/MATH OPERATORS

- ENGLISH PUNCTUATION

- CR/LF (must appear together)

UNEXPECTED

ACTION TAKEN IS AT THE RECEIVER'S DISCRETION.

I

Z iN3..H3Vll\?

[0^.uj; ‘cutx uo^ Aq paquasauu

OEM

COMMUNICATIONS

OPERATION
AGENDA

u_

i

cc

1 " i CC

CCQ_

CC

LU

cn cc LU

>-

1— cc. i—

•c:

1 Q_ *—

5T cc o

UC cc uz cc t—

cc * f—

cc Lc

CU < 1 1— Lc

LT. 1 U_' <c Lc

CL. cc 1 oo

<a; Cc cc cc

c; > ' - cc cc }— 1— cc.

~~ cc fc—~T u_ *=c cc LU > cc C_) >

e • • •

(}uod) 2 iuaimpeqq\/

[aq.ui ‘eaex uo^ Aq paquasaud

OEM

COMMUNICATIONS

OPERATION
l.aq.u x ‘ejex uo a Aq paquesaua

OEM

COMMUNICATIONS

OPERATION
(}U0D)2 lwB^HOVllV

[aq.uj; uo 0 /\q paiuasauu

OEM

COMMUNICATIONS

OPERATION
PARTICIPATING

CWPAHY

RFSPPNS

IBILIT

IES

(luoo) 2 in3hHjV11\/

ID

[a^uj ‘eu ex uo u Aq pa^uasauu

OEM

COMMUNICATIONS

OPERATION
eq.ii i ‘euex uo u A'q peq.ueseju

OEM

COMMUNICATIONS

OPERATION
Laq.u x ‘euex uo<j Aq paxuasauo

OEM

COMMUNICATIONS

OPERATION
(JZ

Oc CL

LL d

LU d

GO CL LU —

<

d > d DC •SC •—

<

LU LU

LU a_ 1

"" ~~~

1

c; . CL

1

d. >- d

<S. 1

1i •—i DC — d

<L l

1

d Lu uc CO ~~

1 oc >- CL d 1— L2

cl LU CO

DC d LU d LU «—

i

d CO

c L 1

CL •— ~ DC CL 1

1

CL LU c. d

LU •—

>

1

DC

LU 1

LU LU

i <C d DC

UJ d d

co \— *— LU LU

co d ac d CL ac DC i— Lu1 cl 5" CL i

C~ OC d CL CL DC ac

<z LU d LU CO 31

LU d h— 1 o_ > uz LU C Lu • co

CL LU d LU <c 1

1

1

1 Dc 1

CO CO LU LU •—

c: d <L 1

(— d LU d — *—

CO d \ d CL DC CL «x C LU

Lu Cl. LU LU cu 1

> - - > 1

•— CL 1 LU i— 1 LU d DC <c

LU 1 DC i—

i

LU < CO

LU LD d 1— LU CL — "

t— DC DC LU CL

> — d LU <X. d d CL

CL CO CL *=C Q_ cC 1— DC

LU N—

CU

co 1

1 LU 1 1 d

1 Lu 1

1 1 CL

LU CL

LU CO DC

e • •

/

(qilOD)Z lU0UilpBqq\,

l.aqui ‘eje A uoQ Aq paquasaua

OEM

COMMUNICATIONS

OPERATION
ATTACHMENT 3

Presented by Ed Deenihan,

TOKEN BUS DEMO

Schedule for NCC *84 GM LAN DEMO

WK Oct 17 1983 Install CDS Testbed Modems at GM

(was late September 1983)

WK Oct 24 1983 Begin Acceptance Test of CDS Modens at GM

(was October 1, 1983)

Nov 14 1983 Install UNIX at Tech Center

Begin NBS Transport Testing at Tech Center

Nov 15 1983 Third Multi-vendor Workshop at GM Tech Center

Nov 16 1983 (Tentative) Concord Data System's Workshop

at Tech Center

Nov 1983 Final FTP Specification Published by NBS

Dec 1983 Host-802 Interface Testing at Vendor Site

Dec 12 1983 Receive and Install VAX 11/780, Move UNIX to

New System

Feb-Apr 1984 Transport Testing at GM (Individual Testing)

(Was Jan-Mar 1984)

Apr-Jun 1984 Multi-vendor FTP and Demo Testing at GM

June 20 1984 Package and Ship Hardware to NCC

WK Jul 2 1984 Install Network and Test at Las Vegas

Jul 9-12 1984 1984 National Computer Conference
I

V:*: '?>•;.,

tf&ji.iTr &$»$ Silt

L *v.». .m?v/r#M;?^.y-^. %

•' '•*-;>:* -viIi;v' gftw

iSilipp

8

“

«

•V.' v.-^.::k\ »§St|

rli^,^‘v- .'

itesiwr

_;• .-v

>f^v.

'^00* ; 5: v ,r-V; < 1

iBimm)

Cy) 1

T«a-iv\>

-.itSOW:

«r««Ssr^

-*•> to - A'.',;

- •

1 pi1

' ^

,?.'^ ~

;

; V .!,v v’_

. 'i^'i;,'. 'j£‘i*/: 2

ry' V*.-^v’."'^,^' 2’v^ ;V' .

[• C'yij :'“% _ : ^

r >- ~ •;

'

;. .'^-Y-> .

'"'

; ^r’k"-''-'-

^'r>'J*

'

-- V^ff. ><V^ yv-’X tR.Sfr V- v&bt.l-j£r *wi’; XS^i&wVi

.

X&U~*&*~?y£>LV

‘uvuLUd^fi ui- Au ppiuaseju ( ^ u0 'j) £ 1N3 mHPv1I\/
ATTACHMENT a nresented by Pob Posenthal

,

NBS

CSMA/CD Booth — Status Report

• Booth Reservation Confirmed Late December

• Vendor Commitments and Specifications

DEC, Honeywell, ICL, INTEL, NBS, Tektronix

• MBS Contract

Concept, Rendering

Design, Fabrication

• Printing
ATTACHMENT 4(cont.)

NCC '84 TIME SCHEDULE

presented by Rob n osenthal

MBS

Receipt of specifications from vendors 09-30-83

Followup on request for specifications from vendors 10-07-83

Telephone calls to vendors requesting purchase orders

NTE $20,000 based on proportionate amount of total

costs of exhibit

10-07-83

LAN Workshop with vendors at Marriott 10-27/28-83

RFP for both design & fabrication issued for 30 days 11-01-83

Award of booth design <5c fabrication contract 02-01-84

Preliminary booth design concept from contractor to

NBS for review and approval 02-22-84

Meeting in Washington with vendors participating in

NCC '84 to approve booth design concept 03-14-84

One-page writeups for NCC '84 brochure received from

vendors 03-30-84

Delivery of booth on-site (NBS) of exhibit at Booth

Mock-up location 05-30-84

Press Release issued on exhibit at NCC '84 06-08-84

Booth and vendor equipment shipped to Las Vegas 06-25-84

Begin setting up vendor equipment and arranging for

electrical and cable hook-ups of all equipment 07-03-84

Opening day of exhibit at NCC '84 07-09-84

Last day of exhibit at NCC '84 07-13-84

Arrangements for shipment of NBS equipment and booth

to NBS Gaithersburg facility 07-14-84
ATTACHMENT 5

Tentative Agenda for CSMA/CD Group Meeting

December 1-2, 1983

Seattle, Washington

I. Agenda Approval

II. Review November 15 Token Passing Meeting

III. Booth Theme

- application

- key messages

IV. Booth Merchandising

- logo

- literature (brochures)

- press release

- follow-on p. r.

- common literature request form

with participants names

- availability of IEEE 802 and

ISO Specifications

V. Remote Booth Proposals

- guidelines

VI. Booth Staffing

- guidelines

VII. FTP

- typing recommendation

- testing
ATTACHMENT 6 presented by .lerry Linn, MBS

BASE SET OF DOCUMENTS PELATlNG TO TESTING

Transport Spec i f i c at i on J 6 volumes, Pet. No, ICST/HLNP 83-1 # 2# 3# 4# 5#

6

r-fjTF.j Volumes 1# 3# 5 are base level for testing cTqss 4

T ® s 1 1 n 3 of r 3.I Protocols: A Compendium of Papers# p ef. No. ICST/SNA 83-1

Users : ju1de to the Testing System for I mp 1 ement e 1 ons of the 1CST

Transport Protocol# Pef. No. ICST/SNA 65-2

A Test Suite for Implementations of the ICST Transport Protocols#

Pef. No. ICST/SNA 83-3

NOTE: Seven scenarios have been added that use disconnect rather

than graceful close for the purposes of this workshop.

Specification of a Remote Scenario Interprter for the

Implementation of the ICST Transport Protocols, Ref, No, ICST/SNA 83-4
ATTACHMENT 7

Dresented by Jim Berets, BBN

Suggested Demonstration FTP Test Procedures

Tests of normal operation.

1. Transfer file between like machines.

1. Transfer file from machine A2 <- A1

.

1. Establish connection.

2. Establish file selection.

3. Open file.

4. Read file contents.

5. Close file.

6. Deselect file.

7. Disconnect.

2. Transfer file from machine A1 <- A2

.

1. Establish connection.

2. Establish file selection.

3. Open file.

4. Read file contents.

5. Close file.

6. Deselect file.

7. Disconnect.

3. Compare the original file on A1 with the new file on A1

4. Compare the original file on A1 with the new file on A2

2. Transfer file between different machines.

1. Transfer file from machine B1 <- A1

.

1

.

Establish connection.

2. Establish file selection

3. Open file.

4. Read file contents.

5. Close file.

6. Deselect file.

7. Disconnect

.

Transfer file from machine A1 <-

1 . Establish connection.

2. Establish file selection

3. Open file.

4. Read file contents.

5. Close file.

6. Deselect file.

7. Disconnect

.

3. Compare the original file on A1 with the new file on A1

4. Compare the original file on A1 with the new file on B1

- 1 -
ATTACHMENT 7 (cont)

presented hv Tim Berets, BBN

2. Suggested Test Files

These files use ASCII representation with the parity bit set to

zero. An explicit <cr><nl> should appear in the file at the end

of each line.

1 . The ASCII character set:

<nul><soh><stx><etx><eot><enq><ackXbel>

<bsXhtXnlXvtXnpXcrXsoXsi>

<dleXdc1Xdc2Xdc3Xdc4XnakXsynXetb>

<canXemXsubXescXfsXgs><rsXus>

<sp> ! "#$%&'

()*+,-./

01234567

89: ;<=>?

@ABCDEFG

HIJKLMNO

PQRSTUVW

XYZ[ ]"_

' abcdefg

hi jklmno

pqrstuvw

xyz { ! } ~<del>

2. A slightly larger file:

112

123

1234

1 2345

123456

1234567

12345678

1 23456789

1 234567890

12345678901

123456789012

1234567890123

12345678901234

1 23456789012345

1234567890123456

12345678901234567

123456789012345678

1 234567890123456789

1 2345678901234567890

1 23456789012345678901

1234567890123456789012

12345678901234567890123

123456789012345678901234

1234567890123456789012345

2 -
nresented by dim Berets, BBN

ATTACHMENT 7 (cont)

12345678901234567890123456

123456789012345678901234567

1234567890123456789012345678

12345678901234567890123456789

123456789012345678901234567890

1234567890123456789012345678901

12345678901234567890123456789012

123456789012345678901234567890123

1234567890123456789012345678901234

12345678901234567890123456789012345

123456789012345678901234567890123456

1234567890123456789012345678901234567

12345678901234567890123456789012345678

123456789012345678901234567890123456789

1234567890123456789012345678901234567890

12345678901234567890123456789012345678901

123456789012345678901234567890123456789012

1234567890123456789012345678901234567890123

12345678901234567890123456789012345678901234

123456789012345678901234567890123456789012345

1234567890123456789012345678901234567890123456

12345678901234567890123456789012345678901234567

123456789012345678901234567890123456789012345678

1234567890123456789012345678901234567890123456789

12345678901234567890123456789012345678901234567890

123456789012345678901234567890123456789012345678901

1234567890123456789012345678901234567890123456789012

12345678901234567890123456789012345678901234567890123

123456789012345678901234567890123456789012345678901234

1234567890123456789012345678901234567890123456789012345

12345678901234567890123456789012345678901234567890123456

123456789012345678901234567890123456789012345678901234567

1234567890123456789012345678901234567890123456789012345678

12345678901234567890123456789012345678901234567890123456789

123456789012345678901234567890123456789012345678901234567890

1234567890123456789012345678901234567890123456789012345678901

12345678901234567890123456789012345678901234567890123456789012

123456789012345678901234567890123456789012345678901234567890123

1234567890123456789012345678901234567890123456789012345678901234

12345678901234567890123456789012345678901234567890123456789012345

123456789012345678901234567890123456789012345678901234567890123456

1234567890123456789012345678901234567890123456789012345678901234567

12345678901234567890123456789012345678901234567890123456789012345678

123456789012345678901234567890123456789012345678901234567890123456789

1234567890123456789012345678901234567890123456789012345678901234567890

12345678901234567890123456789012345678901234567890123456789012345678901

123456789012345678901234567890123456789012345678901234567890123456789012

1234567890123456789012345678901234567890123456789012345678901234567890123

12345678901234567890123456789012345678901234567890123456789012345678901234

123456789012345678901234567890123456789012345678901234567890123456789012345

1234567890123456789012345678901234567890123456789012345678901234567890123456

- 3 -
nresented by Jin Berets, BBN

ATTACHMENT 7 (cont)

123 4567 8901 234567 8901234567 89012345678901234567890123456789012345678901234567

1234567 8901234567 890123456789012345678901 234567 8901234567890123456789012345678

12345678901234567 8901234567 8901234567890123456789012345678901234567890123456789

1234567 890123456789012345678901234567890123456789012345678901234567 8901234567 890

3. Tests of robustness.

1

.

Robustmess tests between 1 ike machines.

1 . Attempt connection to a non-existant machine.

2. Attempt connection to an inoperative machine.

3. Attempt selection of a non-existant file.

4. Attempt to open a file already in use.

5. Cancel a pa rtially completed transfer.

6 . Abort a pa rti al ly completed transaction.

7. Send an out-of-ord er PDU.

2. Robustn ess tests between d ifferent machines.

1 . Attempt connection to a non-existant machine.

2. Attempt connection to an inoperative machine.

3. Attempt selection of a non-existant file.

4. Attempt to open a file already in use.

5. Cancel s1 partially completed transfer.

6. Abort a partially completed transaction.

7. Send an out-of-ord er PDU.

Additional Sugg estions

1 . To f ac i litate de‘bugging, i nclude in the implementation

ability to log incoming and outgoi ng PDUs and parameters.

2. To f ac i litate de:bugging , i nclude in the implementation

ability to send or recei.ve a PDU, then display the contents of

the variables of the protocol machine.

- 4 -
ATTACHMENT 8

Presented by Pat Amaranth, GM

FTP TESTING ISSUES

(TO RESOLVE)

UNIFORMITY ACROSS DEMOS

1) ARBITRATION DECISIONS APPLY TO BOTH

2) TEST PROCEDURES ARE UNIFORM

3) NO CURRENT COMMITMENT TO DEVELOP A

"STANDARD" FTP IMPLEMENTATION

*****

INTER-VENDOR TESTING

1) ALL MUST TEST TO ALL

- TIMING

2) FULL TESTING >

- "ATTENDEE" INTERFACE

- FILE UTILITIES

- LOADING

- PRIVATE VENDOR AGREEMENTS
CURRENT LAN/TRANSPORT SERIES MAILING LIST

Able Computer

Edward Efron

1732 Reynolds Avenue

Irvine, California 92714

Advanced Computer Consultants (ACC)

Joseph R. Maixner

2901 Park Ave.

Santa Cruz, California 95073

Allen-Bradley Company

E. Delahostria

747 Alpha Drive

Highland Heights, Ohio 44143

Gary Baczkowski

747 Alpha Drive

Highland Heights, Ohio 44143

Bob Jones

747 Alpha Drive

Highland Heights, Ohio 44143

David C. Sweeton

747 Alpha Drive

Highland Heights, Ohio 44143

Shack Toms

747 Alpha Drive

Highland Heights, Ohio 44143

American Bell

A. A. Akiwpelu

307 Middletown/Lincroft Road

Lincroft, New Jersey 07738

Michael Herrick

307 Middletown/Lincroft Road

Lincroft, New Jersey 07738

Associated Computer Consultants

Joseph Maixner

Local Area Network Center

2901 Park Avenue

Sequel, California 95073

BDM Corporation

John Long

International Support

7915 Jones Branch Drive

McLean, Virginia 22102

Roger S. Novack

7915 Jones Branch Drive

McLean, Virginia 22102

Boeing Computer Services Company

Sheldon Blauman

P.O. Box 24346

Seattle, Washington 98124

Lorie Bride

P.O. Box 24336 MS 7F-01

Seattle, Washington 98124

Chris Dunlap

7980-90 Gallows Road

Vienna, Virginia 22180

Ken Swenson

P.O. Box 24346 MS 7A-05

Seattle, Washington 98124

Bolt, Beranek, & Newman

James Berets

10 Moulton Street

Cambridge, Massachussetts 02238

John Burruss

50 Moulton Street

Cambridge, Massachussetts 02238

Ross Callon

50 Moulton Street

Cambridge, Massachusetts 02238
Burroughs Corporation

3Com Corporation

Scott A. Stein

CNG/Tredyffrin Plan

P.O. Box 203 . Paoli, Pennsylvania 19301

Carleton University

Jose Ramiro Montealegre

180 Argyle Street

Room 1524

Ottawa, Ontario Canada K2P-1B7

Charles River Data Systems

Pamela Lawson

1390 Shorebird Way

Mountain View, California 94043

Greg Shaw

1390 Shorebird Way

Mountain View, California 94043

Data General

Lyman Chapin

4400 Computer Drive

Westborough, Massachusetts 01746

Digital Equipment Corporation

Dick Swee

983 Concord Street

Framingham, Massachusetts 01701

Cincinnati Milacrom

Prentiss Yates

Route 48 & Mason Road

Lebanon, Ohio 45236

Contel Information Systems

Samuel E. Clopper, Jr.

Government Systems Division

11781 Lee Jackson Highway

Fairfax, Virginia 22033

Concord Data Systems

Ross Seider

303 Bear Hill Road

Waltham, Massachusetts 02154

Control Data Corporation

J. L. Nading

4201 N. Lexington Avenue

Arden Hills, Minnesota 55112

B. S. Sekhon

4201 N. Lexington Avenue

Arden Hills, Minnesota 55112

Chak Lai

21333 Haggerty Road

Novi, Michigan 48050

Anthony G. Lauck

1925 Andover Street

Tewksbury, Massachusetts 01876

Jeff Schriesheim

1925 Andover Street

Tewksbury, Massachusetts 01876

Rita Stubler

21333 Haggerty Road

Novi, Michigan 48050

E-Systems

Marvin Jenkel

7700 Arlington Blvd.

Falls Church, Virginia 22046

William Livingston

7700 Arlington Blvd.

Falls Church, Virginia 22046

William Miller

7700 Arlington Blvd.

Falls Church, Virginia 22046
Excelan Foxboro Company, The

Navindar Jain

2180 Fortune Drive

San Jose, California 95131

Inder M. Singh

2180 Fortune Drive

San Jose, California 95131

Federal Bureau of Investigation

Jerry Smith

Room 8391, TL-245

10th & Pennsylvania Avenue, NW

Washington, D. C. 20535

Fisher Body

Charles D. Groff

30001 Van Dyke Avenue

Warrent, Michigan 48090

Ford Motor Company

Richard Batty

Room 890 WHQ

The American Road

Dearbord, Michigan 48121-1899

Shaun Devlin

Room S-2097, Scientific Research Lab

P.O. Box 2053

Dearborn, Michigan 48121-1899

Melvin Gable

Room E-1174, Scientific Research Lab

P.O. Box 2053

Dearborn, Michigan 48121-1899

Vadivelu Jeyabalan

Room E-1174 Scientific Res. Lab.

P.O. Box 2053

Dearborn, Michigan 48121

Alan Sciacca

Department 341

38 Newpost Ave.

Foxboro, Massachusetts 02035

General Motors Corporation

Pat Amaranth

GM Tech. Center-ME<5cD

Department 69 EA-BLD9

Warren, Michigan 48090

Ed Deenihan

GM Tech. Center B/MD-66

Warren, Michigan 48090

Ronald Floyd

GMME<5cD-MD/66

GM Technical Center

Warren, Michigan 48090-9040

Ken Kanaby

Technical Center, MD-66

Warren, Michigan 48090-9040

Mike Kaminski

Manufacturing Development

Technical Center

Warren, Michigan 48090-9040

Dale F. Larson

GM Technical Center

12 MI&MOUND-N2-GMECC

Warren, Michigan 48080-9040
Gould, Inc.

Rao Cherukuri

6901 Sunrise Blvd.

Ft. Lauderdale, Florida 33310

Allen Brown

6901 W. Sunrise Blvd.

Ft. Lauderale, FL

Hewlett Packard

Ken Aird

3404 E. Harmony Road

Ft. Collins, Colorado 80525

Atul Garg

19420 Homestead Road

Cupertino, California 95014

June Nishimoto

246 Edlee Avenue

Palo Alto, California 94306

Lyle Weiman

19446 Pruneridge Ave.

Cupertino, California 95014

Honeywell Information Systems

Rebecca Hutchings

7900 Westprak Drive

McLean, Virgina 22066

William Stallings

7900 Westpark Drive

McLean, Virginia 22102

IBM Corporation

G. A. Deaton, Jr. IBM Communications Products Division

E87/651

P.O. Box 12195

Research Triangle Park, North Carolina

J. J. Quigley

IBM Systems Products Division

24E/037

P.O. Box 10500

Palo Alto, California 94304

Pat Mulvey

24V B231-1

P.O. Box 1328

Boca Raton, Florida

Perry Taylor

2747 Franklin Road

Bloomfield Hills, Michigan 48013

Roger Thompson

1501 California Avenue

Palo Alto, California 94304

ICL

J. R. Cadwallader

West Avenue

Kidsgrove

Stoke-on-Trent ST7 1TL

United Kingdom

John Salter

West Avenue

Kidsgrove

Stoke-on-Trent ST7 1TL

United Kingdom

D.J. Power

Arndale Center

Manchester, United Kingdom

K. J. Turner

West Avenue

Kidsgrove

Stoke-on-Trent ST7 1TL

Inco. Inc.

Paul Styger

C3I Systems Division

8260 Greensboro Drive

McLean, Virginia 22102

Thomas Trump

C3I Systems Division

8260 Greensboro Drive

McLean,Virginia 22102

Industrial Technology Institute

P. David Fisher

2901 Baxter Road

Ann Arbor, Michigan 48109

Ronald M. Martin

P.O. Box 1485

Ann Arbor, Michigan 48109
Integrated Microcomputer Systems, Inc. Mitre Corporation

Aldrin Leung

5320 Marinelli Road

Rockville, Maryland 20852

Kenneth Lindsay

1235 Jefferson Davis Highway

Suite 1408

Arlington, Virginia 22202

Howell Mei

1235 Jefferson Davis Highway

Suite 1408

Arington, Virginia 22202

Intel Corporation

Allen Rochkind

SC6-056

3200 Lakeside Drive

Santa Clara, California 95051

Ronald Yara

3200 Lakeside Dr.

Santa Clara, California 95014

INTERLAN, Inc.

David Potter

3 Lyberty Way

Westford, Massachusetts 01886

Jonathan Taylor

3 Lyberty Way

Westford, Massachusetts 01886

InterSil Systems

Dr. Ted Britton

1275 Hammerwood Ave.

Sunnyvale, California 94086

Los Alamos National Laboratory

Don Tolmie

Los Alamos, New Mexico 87545

Paul J. Brusil

P.O. Box 208

Bedford, Massachusetts 01730

David Oppenheim

P.O. Box 208

Bedford, Massachusetts 01730

Motorola

Robert Franklin

South Diablo Way

Tempe, Arizona 85282

Bruce Loyer

P.O. Box 2953

Phoenix, Arizona 85062

NBI, Inc.

Douglas McCallum

P.O. Box 9001

Boulder, Colorado 80301

Conrad Geiger

P.O. Box 9001

Boulder, Colorado 80301

National Bureau of Standards

Robert Blanc

Institute for Computer

Sciences & Technology

Room A231, Building 225

Washington, D. C. 20234

Dennis Branstad

Institute for Computer

Sciences <5c Technology

Room A219, Building 225

Washington, D. C. 20234

Robert Carpenter

Institute for Computer

Sciences & Technology

Room A219, Building 225

Washington, D. C. 20234
Michael Chermck

Institute for Computer

Sciences 5c Technology

Room B226, Building 225

Washington, DC 20234

Robert Rosenthal

Institute for Computer

Sciences 5c Technology

Room B226, Building 225

Washington, D. C. 20234

John Heafner

Institute for Computer

Sciences <5c Technology

Room B218, Building 225

Washington, D. C. 20234

Shirley Watkins

Institute for Computer

Sciences 5c Technology

Room B226, Building 225

Washington, D. C. 20234

Jerry Linn

Institute for Computer

NCR Comten

Sciences 5c Technology

Room B212, Building 225

Washington, D. C. 20234

Gerald Brinda

2700 Snelling Ave. N.

Roseville, Minnesota 55113

William Majurski

Institute for Computer

Sciences 5c Technology

Room A219, Building 225

David W. Tillman

2700 Snelling Avenue North

St. P$ul, Minnesota 55113

Washington, D. C. 20234 North Carolina State University

Kevin Mills

Institute for Computer

Sciences 5c Technology

Room B212, Building 225

Washington, D. C. 20234

Bill Chimiak

School of Physical and Mathematic

Sciences 5c School of Engineering

Box 5490

Raliegh, North Carolina 27650

James Moulton

Institute for Computer

Phillips Information Systems

Sciences 5c Technology

Room B212, Building 225

Washington, D. C. 20234

Rene Archambault

5250 Ferrier

Montreal, Canada H4B1L4

Seimens AG

Fran Nielsen

Institute for Computer

Sciences 5c Technology

Room B212, Buliding 225

Washington, DC 20234

Dittmar Janetzky

P.O. Box 211080

7500 Karlsfuhe, Germany

Don Rippy

Institute for Computer

Sciences 5c Technology

Room A231

Washington, DC 20234

Mr. Kreppel

Guenther-Scharowsky-Str.

D-8520 Erlangen

West Germany

9131 7 31759
Tektronix, Inc. Solosystems

Maris Graube

P.O. Box 500

Beaverton, Oregon 97077

Andy Luque

P.O. Box 500

Beaverton, Oregon 97077

Robert L. Sangroniz

Box 1000 MS/63-489

Wilsonville, Oregon 97070

University of Michigan <5c Industrial Technology

Institute

Douglas B. Smith

Ann Arbor, Michigan 48109

Ungerm an-Bass

John M. Davidson

2560 Mission College Blvd.

Santa Clara, CA 95050

Xerox Corporation

Juan Bulnes

OPD Office Systems Business Unit

3450 Hillview Avenue

Palo Alto, California 94304

Der-Hwa Gan

670 Gail Avenue #E-27

Sunnyvale, California 94086

Source Telecomputing

Leslie Spira

1616 Anderson Road

McLean, Virginia

Sperry Univac

Jim McNulty

P.O. Box 500

Blue Bell, Pennsylvania 19124

Mike Wolfersperger

P.O. Box 500

Blue Bell, Pennsylvania 19124

Sytek, Inc.

William C. Taylor

6000 Executive Blvd.

Suite 205A

Rockville, Maryland 20852

Systems Architects, Inc.

Ashok Kuthyar

510 W. Annandale Road

Falls Church, Virginia 22046
BIBLIOGRAPHY

"Multi-Vendor Demonstration File Transfer Protocol," National

Bureau of Standards, August, 1983.

"Multi-Vendor Demonstration File Transfer Protocol Formal

Description," National Bureau of Standards, September, 1983.

"Multi-Vendor Demonstration File Transfer Protocol Supplement,"

National Bureau of Standards, September, 1983.

Proceedings of the First LAN -Transport Workshop , NBSIR 83-2673,

National Bureau of Standards, Washington, D.C., February 1-2,

1983.

Proceedings of the Second LAN -Transport Workshop , NBSIR 83-2717,

National Bureau of Standards, Washington, D.C., May 5-6, 1983

Proceedings of the Third LAN -Transport Workshop , NBSIR 83-2757,

National Bureau of Standardly Washington, D.C., July 18 - 20,

1983

Rochkind, Allen B. "Proposal for File Management Services Used

for the Intervendor Demo," Intel, August, 1983.
NBS-114A (REV. 2-80

U.s. DEPT. OF COMM.

BIBLIOGRAPHIC DATA

1. PUBLICATION OR

REPORT NO.

2. Performing Organ. Report No. 3. Publication Date

SHEET (See instructions) NBSIR 83-2796 November 1983

4. TITLE AND SUBTITLE

Proceedings of the Fourth LAN/Transport Workshop

5. AUTHOR(S)

Fran Nielsen

6. PERFORMING ORGANIZATION (If joint or other than NBS. see instructions) 7. Contract/Grant No. NATIONAL BUREAU OF STANDARDS

DEPARTMENT OF COMMERCE 8. Type of Report & Period Covered

WASHINGTON, D.C. 20234

9.

SPONSORING ORGANIZATION NAME AND COMPLETE ADDRESS (Street. City. Stote, ZIP)

National Bureau of Standards

Institute for Computer Sciences and Technology (651)

Washington, D. C. 20234

10.

SUPPLEMENTARY NOTES

3 Document describes a computer program; SF-185, FlPS Software Summary, is attached.

11.

ABSTRACT (A 200-word or less factual summary of most significant information. If document includes a significant

bi bl iography or literature survey, mention it here) The National Bureau of Standards Institute for Computer Sciences and Technology (ICST)

has prepared specifications for the International Organization for Standardization's

(ISO) Class 4 Transport Protocol. At the request of a number of companies, ICST

organized a workshop series for implementors of these specifications using local area networking technology. The first workshop focused on implementation techniques and

strategies so that a multivendor demonstration of these protocols can occur at a major

computer conference in 1984 targeted for the NCC 1984. Primarily the details of

CSMA/CD and Transport Class 4 were discussed and parameters were selected. A second

workshop focused on token bus LANs and file transfer applications to be run at the

targeted 1984 demonstration. Agreements on the specifics of the file transfer protocol were reached at the third workshop. This report documents the fourth workshop in the

series of LAN-Transport workshops. The fourth workshop covered further refinements

to the file transfer protocol, testing procedures, and demonstration details.

12. KEY WORDS (Six to twelve entries; alphabetical order; capitalize only proper names; and separate key words by semicolon s) communication protocols; computer networks; file transfer protocol; local area networks

.

13. AVAILABILITY 14. NO. OF

PRINTED PAGES

[X] Uni i mi ted

| | For Official Distribution. Do Not Release to NTIS 46

~J Order From Superintendent of Documents, U.S. Government Printing Office, Washington, D.C. 20402. 15. Price

[~X] Order From National Technical Information Service (NTIS), Springfield, VA. 22161 $8.50

USCOMM-DC 6043-P80