|
|
1.1 root 1: % run this through SLiTeX
2:
3: \documentstyle
4: [blackandwhite,landscape,oval,pagenumbers,plain,small,tgrind]{NRslides}
5:
6: \makeatletter
7: \def\@maketitle{%
8: \newpage
9: \null
10: \setbox\z@=\vbox{%
11: \ \vskip .75em
12: \begin{center}
13: {\huge\bf \@title \par}% %%% was \Large
14: \vskip .5em
15: {\Large\bf %%% was \large
16: \lineskip=.25em
17: \begin{tabular}[t]{c}
18: \@author
19: \end{tabular}
20: \par
21: }%
22: \vskip .25em %%% was .5em
23: {\Large\bf \@date}% %%% was \large
24: \end{center}
25: \par
26: \vskip .75em
27: }%
28: \if@ovaltitle
29: \title@ht=\ht\z@ \title@wd=\wd\z@
30: \title@@ht=\ht\z@ \title@@wd=\wd\z@
31: \divide\title@@ht by2 \divide\title@@wd by2
32: \unitlength=1sp
33: \fi
34: \box\z@
35: \if@ovaltitle
36: \vskip -\title@ht\unitlength
37: {\centering
38: \begin{picture}(\title@wd,\title@ht)
39: \put(\title@@wd,\title@@ht){\oval(\title@wd,\title@ht)}
40: \end{picture}
41: \par}
42: \fi
43: }
44: \makeatother
45:
46: \raggedright
47:
48: \begin{document}
49:
50: \title {FILE TRANSFER, ACCESS\\ AND MANAGEMENT}
51: \author {Marshall T.~Rose}
52: \date {September 1, 1987}
53: \maketitlepage
54:
55:
56: \begin{bwslide}
57: \ctitle {INTRODUCTION}
58:
59: \begin{nrtc}
60: \item FTAM - FILE TRANSFER, ACCESS AND MANAGEMENT
61:
62: \item THE OPEN SYSTEMS FILE SERVICE
63:
64: \item CURRENTLY A {\bf DRAFT INTERNATIONAL STANDARD}\\
65: SOON TO ACHIEVE FULL STANDARD STATUS
66: \end{nrtc}
67: \end{bwslide}
68:
69:
70: \begin{bwslide}
71: \ctitle {THE OPEN SYSTEMS FILE SERVICE}
72:
73: \begin{nrtc}
74: \item NOT ``JUST'' FILE TRANSFER
75:
76: \item THE BASIC BUILDING BLOCK FOR OSI
77: \begin{nrtc}
78: \item FILESTORE TO FILESTORE TRANSFER
79:
80: \item WORKSTATION FILE RETRIEVAL
81:
82: \item DISKLESS WORKSTATION PROTOCOL
83:
84: \item SPECIAL APPLICATIONS (e.g., PRINTING, SPOOLING)
85:
86: \item REMOTE DATABASE ACCESS
87: \end{nrtc}
88: \end{nrtc}
89: \end{bwslide}
90:
91:
92: \begin{note}\em
93: as one of the OSI applications,
94: FTAM is exciting
95: as we get to see how all of the lower layer services are used
96:
97: because of its scope,
98: FTAM is challenging
99: as it has a very large operating charter
100: (simple file transfer, database access, remote filesystems, and so on)
101:
102: it is a largish undertaking:
103: the spec is about 350~pages,
104: the ISODE implementation (which isn't complete) is about 40K~lines of C code
105: (about 25\% machine-generated, thank goodness)
106: \end{note}
107:
108:
109: \begin{note}\em
110: an audience survey, who has:
111:
112: heard of FTAM?
113:
114: read the FTAM specification?
115:
116: *understood* the FTAM specification?
117:
118: heard of association control (sometimes incorrectly called CASE)?
119:
120: heard of unix and the C programming language?
121: \end{note}
122:
123:
124: \begin{bwslide}
125: \part* {OUTLINE}
126:
127: \begin{nrtc}\bf
128: \item THE VIRTUAL FILESTORE
129:
130: \item THE FILE SERVICE
131:
132: \item THE FILE PROTOCOL
133:
134: \item ISSUES IN IMPLEMENTING THE VIRTUAL FILESTORE
135:
136: \item ISSUES IN IMPLEMENTING A CLIENT OF THE VIRTUAL FILESTORE
137:
138: \item FTAM STATUS
139: \end{nrtc}
140: \end{bwslide}
141:
142: \include {filestore}
143: \include {service}
144: \include {protocol}
145: \include {responder}
146: \include {initiator}
147: \include {status}
148:
149: \begin{bwslide}
150: \part* {ACKNOWLEDGEMENTS}
151:
152: \begin{quote}\em
153: this presentation is based on experiences in implementing the
154: ISO Development Environment (ISODE) at NRTC,
155: an openly available implementation of the upper-layers of OSI
156:
157: others have made significant contributions to the content and quality of this
158: presentation,
159: notably:
160: \end{quote}
161:
162: \begin{nrtc}\em
163: \item at UCL: Steve Kille
164:
165: \item at BRL: Mike Muuss
166:
167: \item at NPL: John Pavel
168:
169: \item at NRTC: John L.~Romine
170:
171: \item at NMA: Einar A.~Stefferud
172: \end{nrtc}
173:
174: also, UNIX is a trademark of at\&t bell laboratories
175: \end{bwslide}
176:
177: \end{document}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.