Debian Codegraph @

rfc1085.html

raw
1 <pre>Network Working Group M. Rose
2 Request for Comments: 1085 TWG
3 December 1988
4
5
6 <span class="h1">ISO Presentation Services</span>
7 <span class="h1">on top of TCP/IP-based internets</span>
8
9 Status of this Memo
10
11 This memo proposes a standard for the Internet community.
12 Distribution of this memo is unlimited.
13
14 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
15
16 [<a id="ref-RFC1006">RFC1006</a>] describes a mechanism for providing the ISO transport
17 service on top of the Transmission Control Protocol (TCP) [<a href="./rfc793" title="&quot;Transmission Control Protocol - DARPA Internet Program Protocol Specification&quot;">RFC793</a>]
18 and Internet Protocol (IP) [<a href="./rfc791" title="&quot;Internet Protocol - DARPA Internet Program Protocol Specification&quot;">RFC791</a>]. Once this method is applied,
19 one may implement "real" ISO applications on top of TCP/IP-based
20 internets, by simply implementing OSI session, presentation, and
21 application services on top of the transport service access point
22 which is provided on top of the TCP. Although straight-forward,
23 there are some environments in which the richness provided by the OSI
24 application layer is desired, but it is nonetheless impractical to
25 implement the underlying OSI infrastructure (i.e., the presentation,
26 session, and transport services on top of the TCP). This memo
27 describes an approach for providing "stream-lined" support of OSI
28 application services on top of TCP/IP-based internets for such
29 constrained environments.
30
31 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
32
33 In as much as this memo is concerned primarily with concepts defined
34 in the framework of Open Systems Interconnection (OSI) as promulgated
35 by the International Organization for Standardization (ISO), the
36 terminology used herein is intended to be entirely consistent within
37 that domain of discourse. This perspective is being taken despite
38 the expressed intent of implementing the mechanism proposed by this
39 memo in the Internet and other TCP/IP-based internets. For those
40 more familiar with the terminology used in this latter domain, the
41 author is apologetic but unyielding.
42
43 Although no substitute for the "correct" definitions given in the
44 appropriate ISO documents, here is a short summary of the terms used
45 herein.
46
47
48
49
50
51
52 <span class="grey">Rose [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
55
56
57 Application Context:
58 The collection of application service elements which
59 cooperatively interact within an application-entity.
60
61 Application Service Element:
62 A standardized mechanism, defined by both a service and a
63 protocol, which provides a well-defined capability, e.g.,
64
65 ROSE - the Remote Operations Service Element,
66 which orchestrates the invocation of "total"
67 operations between application-entities [ISO9066/2].
68
69 ACSE - the Association Control Service Element,
70 which manages associations between application
71 entities [<a href="#ref-ISO8650" title="&quot; Protocol Specification for the Association Control Service Element (Final Text of DIS 8650)&quot;">ISO8650</a>].
72
73 Object Identifier:
74 An ordered set of integers, used for authoritative
75 identification.
76
77 Presentation Service:
78 A set of facilities used to manage a connection between two
79 application-entities. The fundamental responsibility of the
80 presentation service is to maintain transfer syntaxes which
81 are used to serialize application protocol data units for
82 transmission on the network and subsequent de-serialization
83 for reception.
84
85 Protocol Data Unit (PDU):
86 A data object exchanged between service providers.
87
88 Serialization:
89 The process of applying an abstract transfer notation to an
90 object described using abstract syntax notation one (ASN.1)
91 [<a href="#ref-ISO8824" title="&quot; Specification of Abstract Syntax Notation One (ASN.1)&quot;">ISO8824</a>] in order to produce a stream of octets.
92 De-serialization is the inverse process.
93
94 It is assumed that the reader is familiar with terminology
95 pertaining to the reference model [<a href="#ref-ISO7498" title="&quot;Basic Reference Model&quot;">ISO7498</a>], to the service
96 conventions in the model [<a href="#ref-ISO8509" title="&quot; Service Conventions&quot;">ISO8509</a>], and to the
97 connection-oriented presentation service [<a href="#ref-ISO8822" title="&quot; Connection Oriented Presentation Service Definition (Final Text of DIS 8822)&quot;">ISO8822</a>].
98
99 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Scope</span>
100
101 The mechanism proposed by this memo is targeted for a particular
102 class of OSI applications, namely those entities whose application
103 context contains only an Association Control Service Element (ACSE)
104 and a Remote Operations Service Element (ROSE). In addition, a
105
106
107
108 <span class="grey">Rose [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
111
112
113 Directory Services Element (DSE) is assumed for use by the
114 application-entity, but only in a very limited sense. The
115 organization of such an entity is as follows:
116
117
118 +------------------------------------------------------------+
119 | |
120 | Application-Entity |
121 | |
122 | +------+ +------+ +------+ |
123 | | ACSE | | ROSE | | DSE | |
124 | +------+ +------+ +------+ |
125 | |
126 +------------------------------------------------------------+
127 | |
128 | Presentation Services |
129 | |
130 | P-CONNECT P-RELEASE P-DATA |
131 | P-U-ABORT |
132 | P-P-ABORT |
133 | |
134 +------------------------------------------------------------+
135
136
137 The mechanism proposed by this memo is not applicable to entities
138 whose application context is more extensive (e.g., contains a
139 Reliable Transfer Service Element). The mechanism proposed by this
140 memo could be modified to support additional elements. However, such
141 extensions would, at this time, merely serve to defeat the purpose of
142 providing the minimal software infrastructure required to run the
143 majority of OSI applications.
144
145 The motivation for this memo was initially derived from a requirement
146 to run the ISO Common Management Information Protocol (CMIP) in
147 TCP/IP-based internets. In its current definition, CMIP uses
148 precisely the application service elements provided for herein. It
149 may be desirable to offer CMIP users a quality of service different
150 than the one offered by a connection with a high-quality level of
151 reliability. This would permit a reduced utilization of connection-
152 related resources. This memo proposes a mechanism to implement this
153 less robust -- and less costly -- quality of service.
154
155 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Approach</span>
156
157 The approach proposed by this memo relies on the following
158 architectural nuances:
159
160
161
162
163
164 <span class="grey">Rose [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
167
168
169 - the TCP is a stream-oriented transport protocol
170
171 - ASN.1 objects, when represented as a stream of octets are
172 self-delimiting
173
174 - The ISO presentation service permits the exchange of ASN.1
175 objects
176
177 - The ACSE and ROSE require the following presentation
178 facilities:
179
180 The Connection Establishment Facility
181
182 The Connection Termination Facility
183
184 The Information Transfer Facility (P-DATA
185 service only)
186
187 - The majority of the parameters used by the services which
188 provide these facilities can be "hard-wired" to avoid
189 negotiation
190
191 In principle, these nuances suggest that a "cheap" emulation of the
192 ISO presentation services could be implemented by simply serializing
193 ASN.1 objects over a TCP connection. This approach is precisely what
194 is proposed by this memo.
195
196 Given this perspective, this memo details how the essential features
197 of the ISO presentation service may be maintained while using a
198 protocol entirely different from the one given in [<a href="#ref-ISO8823" title="&quot; Connection Oriented Presentation Protocol Specification (Final Text of DIS 8822)&quot;">ISO8823</a>]. The
199 overall composition proposed by this memo is as follows:
200
201
202 +-----------+ +-----------+
203 | PS-user | | PS-user |
204 +-----------+ +-----------+
205 | |
206 | PS interface PS interface |
207 | [<a href="#ref-ISO8822" title="&quot; Connection Oriented Presentation Service Definition (Final Text of DIS 8822)&quot;">ISO8822</a>] |
208 | |
209 +----------+ ISO Presentation Services on the TCP +----------+
210 | client |-----------------------------------------| server |
211 +----------+ (this memo) +----------+
212 | |
213 | TCP interface TCP interface |
214 | [<a href="./rfc793" title="&quot;Transmission Control Protocol - DARPA Internet Program Protocol Specification&quot;">RFC793</a>] |
215 | |
216
217
218
219
220 <span class="grey">Rose [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
223
224
225 In greater detail, the "client" and "server" boxes implement the
226 protocol described in this memo. Each box contains three modules:
227
228 - a dispatch module, which provides the presentation services
229 interface,
230
231 - a serialization module, containing a serializer, which takes
232 an ASN.1 object and applies the encoding rules of [<a href="#ref-ISO8825" title="&quot;Specification of basic encoding rules for Abstract Syntax Notation One (ASN.1)&quot;">ISO8825</a>]
233 to produce a stream of octets, and a de-serializer, which
234 performs the inverse operation, and
235
236 - a network module, which manages a TCP connection.
237
238 The software architecture used to model a network entity using this
239 approach is as follows:
240
241
242 +---------+ +----------+ +-----+
243 | | | | output +---------------+ input | n |
244 | | | |&lt;--------| de-serializer |&lt;--------| e |
245 | | | | queue +---------------+ queue | t |
246 | PS-user |----| dispatch | | w |
247 | | | | input +---------------+ output | o |
248 | | | |--------&gt;| serializer |--------&gt;| r |
249 | | | | queue +---------------+ queue | k |
250 +---------+ +----------+ +-----+
251
252 |---- serialization module ----|
253
254
255 The ISO presentation layer is concerned primarily with the
256 negotiation of transfer syntaxes in addition to the transformation to
257 and from transfer syntax. However, using the mechanism proposed by
258 this memo, no negotiation component will be employed. This memo
259 specifies the fixed contexts which exist over each presentation
260 connection offered. This memo further specifies other constants
261 which are used in order to eliminate the need for presentation layer
262 negotiation.
263
264 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Fundamental Parameters</span>
265
266 There are certain parameters which are used by the presentation
267 service and are defined here.
268
269 1. Presentation address:
270
271 The structure of a presentation address is presented in Addendum 3
272 to [<a href="#ref-ISO7498" title="&quot;Basic Reference Model&quot;">ISO7498</a>]. This memo interprets a presentation address as an
273
274
275
276 <span class="grey">Rose [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
279
280
281 ordered-tuple containing:
282
283 - one or more network addresses
284 - a transport selector
285 - a session selector
286 - a presentation selector
287
288 Each selector is an uninterpreted octet string of possibly zero
289 length. The mechanism proposed in this memo completely ignores
290 the values of these selectors. Note however that the value of the
291 presentation selector is preserved by the provider.
292
293 A network address is interpreted as containing three components:
294
295 - a 32-bit IP address
296
297 - a set indicating which transport services are available
298 at the IP address (currently only two members are defined:
299 TCP and UDP; as experience is gained, other transport
300 services may be added); as a local matter, if a member is
301 present it may have an "intensity" associated with it:
302 either "possibly present" or "definitely present"
303
304 - a 16-bit port number
305
306 As a consequence of these interpretations, any application-entity
307 residing in the network can be identified by its network address.
308
309 2. Presentation context list
310
311 A list of one or more presentation contexts. Each presentation
312 context has three components:
313
314 - a presentation context identifier (PCI), an integer
315
316 - an abstract syntax name, an object identifier
317
318 - an abstract transfer name, an object identifier
319
320 The range of values these components may take is severely
321 restricted by this memo. In particular, exactly two contexts are
322 defined: one for association control and the other for the
323 specific application service element which is being carried as ROS
324 APDUs (see the section on connection establishment for the precise
325 values).
326
327 In addition, if the presentation context list appears in a
328 "result" list (e.g., the Presentation context result list
329
330
331
332 <span class="grey">Rose [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
335
336
337 parameter for the P-CONNECT service), a fourth component is
338 present:
339
340 - an acceptance indicator
341
342 which indicates if the context was accepted by both the service
343 provider and the remote peer. If the context was not accept, a
344 brief reason, such as "abstract syntax not supported" is given.
345
346 For the novice reader, one might think of the abstract syntax
347 notation as defining the vocabulary of some language, that is, it
348 lists the words which can be spoken. In contrast, the abstract
349 transfer notation defines the pronunciation of the language.
350
351 3. User data
352
353 User data passes through the presentation service interface as
354 ASN.1 objects (in a locally defined form). Associated with each
355 object is a presentation context identifier. The PCI
356 distinguishes the context for which the data is intended. The
357 range of values the PCI may take is severely restricted by this
358 memo. Exactly one of two contexts must always be used: either the
359 value for the ACSE presentation context or the value for the ROSE.
360
361 4. Quality of Service
362
363 Quality of service is a collection of "elements". Each element
364 denotes some characteristics of the communication, e.g., desired
365 throughput, and some value in an arbitrary unit of measure. For
366 our purposes, only one quality of service element is interpreted,
367 "transport-mapping". Currently, the "transport-mapping" element
368 takes on one of two values: "tcp-based" or "udp-based". At
369 present, the two values may also be referred to as "high-quality"
370 or "low-quality", respectively.
371
372 As experience is gained, other values may be added. These values
373 would correspond directly to the new transport services which are
374 listed in the network address.
375
376 5. Version of Session Service
377
378 Some application service elements (e.g., the ACSE) invoke
379 different procedures based on the (negotiated) version of the
380 session service available. Implementations of this memo always
381 indicate that session service version 2 has been negotiated.
382
383
384
385
386
387
388 <span class="grey">Rose [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
391
392
393 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Choice of Transport Service</span>
394
395 Discussion thus far has centered along the use of the TCP as the
396 underlying transport protocol. However, it has also been noted that
397 it may be desirable to permit a quality of service with less
398 reliability in order to take advantage of some other characteristic
399 of the transport service.
400
401 The introduction of this service has several profound impacts on the
402 model, and it is beyond the scope of this memo to enumerate these
403 impacts. However, this memo does propose a mechanism by which such a
404 facility is implemented.
405
406 To begin, we use the quality of service parameter for the P-CONNECT
407 service to select an underlying transport service. Only one element
408 is currently interpreted, "transport-mapping" which takes the value
409 "tcp-based" or "udp-based". If the value is "tcp-based", then the
410 presentation provider will use TCP as the underlying transport
411 service. If, however, the value of "transport-mapping" is "udp-
412 based", then the presentation provider will use the UDP instead.
413
414 The User Datagram Protocol (UDP) [<a href="./rfc768" title="&quot;User Datagram Protocol&quot;">RFC768</a>] is used to implement the
415 udp-based service. Very few transport-level facilities are placed on
416 top of the UDP service, i.e., it is not the intent of this memo to
417 "re-invent" the facilities in the TCP. Hence, It is critical to
418 understand that
419
420 low-quality means LOW-QUALITY!
421
422 Because the UDP is a packet-oriented protocol, it is necessary to
423 slightly redefine the role of the serialization module. For the
424 serializer, we say that each top-level ASN.1 object placed on the
425 input queue will form a single UDP datagram on the output queue which
426 is given to the network. Similarly, for the de-serializer, we say
427 that each UDP datagram placed on the input queue from the network
428 will form a single top-level ASN.1 object placed on the output queue.
429 The term "top-level ASN.1 object" refers, of course, to the protocol
430 data units being exchanged by the presentation providers.
431
432 It should be noted that in its current incarnation, this memo permits
433 the choice of two different transport protocols, e.g., the TCP or the
434 UDP. However, as experience is gained and as other transport
435 protocols are deployed (e.g., the VMTP), then future incarnations of
436 this memo will permit these transport protocols to be used. This is
437 a three step process: first, the set of transport services defined
438 for the network address is updated; second, a corresponding value is
439 added to the range of the quality of service element "transport-
440 mapping"; and, third, the following sections of this memo are
441
442
443
444 <span class="grey">Rose [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
447
448
449 modified accordingly.
450
451 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Connection Establishment</span>
452
453 The Connection Establishment facility consists of one service, the
454 P-CONNECT service.
455
456 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. The P-CONNECT Service</span>
457
458 This service is used to bring two identified application-entities
459 into communication. Its successful use results in a presentation
460 connection, with an initial defined context set, being established
461 between then. This connection is available for their subsequent
462 communication. This is a confirmed service whose effects are
463 sequenced and non-destructive.
464
465 If the udp-based service is selected, then a presentation connection
466 is formed which should be used infrequently and will have minimal
467 reliability characteristics.
468
469 For our purposes, the P-CONNECT service:
470
471 - requests TCP or UDP resources,
472
473 - builds a fixed defined context set, and
474
475 - exchanges initial user data.
476
477 Following are the interpretation of and the defaults assigned to the
478 parameters of the P-CONNECT service:
479
480 1. Calling Presentation Address
481
482 This is a presentation address. Although the ISO presentation
483 service states that this parameter is mandatory, in practice, a
484 local implementation rule may be used to determine an
485 "ephemeral" address to use.
486
487 2. Called Presentation Address
488
489 This is a presentation address. Note that when issuing the P-
490 CONNECT.REQUEST primitive, this parameter may contain more than
491 one network address. In the P-CONNECT.INDICATION primitive
492 however, only one network address, the one actually used to
493 establish the presentation connection, is present. (Appendix C
494 describes a strategy which might be used to determine the actual
495 network address).
496
497
498
499
500 <span class="grey">Rose [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
503
504
505 3. Responding Presentation Address
506
507 This parameter is identical to the value of the Called
508 Presentation Address parameter of the P-CONNECT.INDICATION
509 primitive.
510
511 4. Multiple defined Contexts
512
513 Always TRUE. Note that this parameter is present only in the
514 DIS version of the presentation service.
515
516 5. Presentation context definition list
517
518 Two contexts are defined:
519
520 PCI Abstract Syntax Name Abstract Transfer Name
521 --- -------------------- ----------------------
522 1 specific to the application "iso asn.1 abstract
523 transfer"
524 1.0.8825
525
526 3 "acse pci version 1" "iso asn.1 abstract
527 transfer"
528 2.2.1.0.0 1.0.8825
529
530 The abstract syntax and transfer names for the ACSE PCI are for
531 use with the DIS version of association control. If the IS
532 version is being used, then this PCI is used instead:
533
534 3 "acse pci version 1" "asn.1 basic encoding"
535 2.2.1.0.1 2.1.1
536
537 6. Presentation context result list
538
539 Identical to the Presentation context definition list with the
540 addition that the acceptance indicator for both contexts is
541 "accepted".
542
543 7. Default Context Name
544
545 None.
546
547 8. Default Context Result
548
549 Not applicable.
550
551
552
553
554
555
556 <span class="grey">Rose [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
559
560
561 9. Quality of Service
562
563 The element "transport-mapping" takes the value "tcp-based" or
564 "udp-based". In the future the range of values may be extended.
565
566 10. Presentation Requirements
567
568 None (the kernel functional unit is always used).
569
570 11. Session Requirements
571
572 Full duplex.
573
574 12. Initial synchronization point serial number
575
576 None.
577
578 13. Initial Assignment of tokens
579
580 None.
581
582 14. Session connection identifier
583
584 Unlike the "real" presentation service, depending on the quality
585 of service selected, this parameter may have great significance
586 to presentation provider. Hence, the following format of the
587 session connection identifier is mandated by this memo.
588
589 user data: a local string encoded as a T.61 string
590 using ASN.1, e.g., given string "gonzo":
591
592 14 05 67 6f 6e 7a 6f
593 tag length "g" "o" "n" "z" "o"
594
595 common data: a universal time encoding using ASN.1, e.g.,
596 given time "880109170845":
597
598 17 0c 38 38 30 31 30 ...
599 tag length "8" "8" "0" "1" "0" ...
600
601 additional data: any string encoded as a T.61 string using ASN.1
602 (optional)
603
604 As a local convention, the presentation provider may disregard
605 the first two octets of each data component for transmission on
606 the network as when the session connection identifier is
607 represented with ASN.1, the tag and length octets will be added
608 anyway.
609
610
611
612 <span class="grey">Rose [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
615
616
617 15. User Data
618
619 A single ASN.1 object is present, the appropriate A-ASSOCIATE
620 PDU, carried in presentation context 3.
621
622 16. Result
623
624 One of the following values: acceptance, user-rejection,
625 provider-rejection (transient), or provider-rejection
626 (permanent).
627
628 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Connection Termination</span>
629
630 The Connection Termination facility consists of three services, the
631 P-RELEASE, P-U-ABORT, and P-P-ABORT services.
632
633 <span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. The P-RELEASE Service</span>
634
635 This service provides the service user with access to a negotiated
636 release facility. This service has effects which are sequenced and
637 non-destructive. Either presentation user is permitted to request
638 this service. However, in the event of collision, a provider-
639 initiated abort procedure will be invoked.
640
641 If the udp-based service is selected, then any data in transit may be
642 discarded.
643
644 For our purposes, the P-RELEASE service:
645
646 - waits for the serialization module to drain,
647
648 - sends release user data, and
649
650 - releases TCP or UDP resources
651
652 Following are the interpretation of and the defaults assigned to the
653 parameters of the P-RELEASE service:
654
655 1. Result
656
657 Release accepted.
658
659 2. User data
660
661 A single ASN.1 object is present, the appropriate A-RELEASE PDU,
662
663
664
665
666
667
668 <span class="grey">Rose [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
671
672
673 <span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. The P-U-ABORT Service</span>
674
675 This service can be used by either presentation user to force the
676 release of a presentation connection at any time and have the
677 correspondent presentation user informed of this termination. This
678 service has effects which are not sequenced with respect to preceding
679 service invocations and may be destructive. It does not require the
680 agreement of both service users.
681
682 For our purposes, the P-U-ABORT service:
683
684 - flushes the serialization module,
685
686 - sends abort user data, and
687
688 - releases TCP or UDP resources
689
690 Following are the interpretation of and the defaults assigned to the
691 parameters of the P-U-ABORT service:
692
693 1. Presentation context identifier list
694
695 Contained in the ASN.1 objects, if any, that are delivered as
696 user data.
697
698 2. User data
699
700 A single ASN.1 object is present, an A-ABORT PDU, carried in
701 presentation context 3.
702
703 <span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. The P-P-ABORT Service</span>
704
705 This service is the means by which the service provider may indicate
706 the termination of the presentation connection for reasons internal
707 to the service provider. This service has effects which are not
708 sequenced with respect to preceding service invocations. The
709 execution of this service disrupts any other concurrently active
710 service and may thus be destructive.
711
712 For our purposes, the P-P-ABORT service:
713
714 - flushes the serialization module, and
715
716 - releases TCP or UDP resources
717
718 Following are the interpretation of and the defaults assigned to the
719 parameters of the P-P-ABORT service.
720
721
722
723
724 <span class="grey">Rose [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
727
728
729 1. Provider reason
730
731 An integer code detailing why the connection was aborted. Codes
732 include, but are not limited to: invalid PPDU parameter,
733 unexpected PPDU, unrecognized PPDU, and specified reason.
734
735 2. Abort data
736
737 None.
738
739 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Information Transfer</span>
740
741 Although the Information Transfer facility consists of many services,
742 only one, the P-DATA service, is provided by this memo.
743
744 <span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. The P-DATA Service</span>
745
746 This services provides the service user with a data transfer
747 capability. This service has effects which are sequenced and non-
748 destructive.
749
750 If the udp-based service is selected, then there is an upper-bound on
751 the size of the serialized ASN.1 objects which may be transmitted.
752 This limit, imposed by the UDP, is 65536 octets. As a practical
753 matter, it is probably a good idea to keep datagrams less than or
754 equal to 536 octets in size.
755
756 For our purposes, the P-DATA service:
757
758 - sends user data
759
760 Following are the interpretation of and the defaults assigned to the
761 parameters of the P-DATA service:
762
763 1. User data
764
765 A single ASN.1 object is present, a remote operations APDU,
766 carried in presentation context 1.
767
768 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Elements of Procedure</span>
769
770 The service provider is in one of the following states:
771
772 IDLE, WAIT1, WAIT2, DATA, WAIT3, or WAIT4
773
774 The possible events are:
775
776 PS-user P-CONNECT.REQUEST
777
778
779
780 <span class="grey">Rose [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
783
784
785 P-CONNECT.RESPONSE
786 P-RELEASE.REQUEST
787 P-RELEASE.RESPONSE
788 P-DATA.REQUEST
789 P-U-ABORT.REQUEST
790
791 network TCP closed or errored(*)
792 receive ConnectRequest PDU
793 receive ConnectResponse PDU
794 receive ReleaseRequest PDU
795 receive ReleaseResponse PDU
796 receive UserData(*) or CL-UserData(**) PDU
797 receive user-initiated Abort PDU
798 receive provider-initiated Abort PDU
799 timer expires(**)
800
801
802 The possible actions are:
803
804 PS-user P-CONNECT.INDICATION
805 P-CONNECT.CONFIRMATION
806 P-RELEASE.INDICATION
807 P-RELEASE.CONFIRMATION
808 P-DATA.INDICATION
809 P-U-ABORT.INDICATION
810 P-P-ABORT.INDICATION
811
812 network open TCP(*)
813 close TCP(*)
814 send ConnectRequest PDU
815 send ConnectResponse PDU
816 send ReleaseRequest PDU
817 send ReleaseResponse PDU
818 send UserData(*) or CL-UserData(**) PDU
819 send user-initiated Abort PDU
820 send provider-initiated Abort PDU
821 set timer(**)
822
823 (*) tcp-based service only
824 (**) udp-based service only
825
826 <span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Elements of Procedure specific to the tcp-based service</span>
827
828 The provider maintains the following information for each
829 presentation connection:
830
831 - a local designator for the PS-user
832
833
834
835
836 <span class="grey">Rose [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
839
840
841 - a local designator for a TCP connection
842
843 - the state of the connection (e.g., IDLE, WAIT1, and so on)
844
845 Upon receiving an event from the network, the provider finds the
846 associated presentation connection. Matching is done by simply
847 comparing local designators for the TCP connection. Whenever a
848 connection remains in or returns to the IDLE state, any associated
849 resources, such as an attachment to a local TCP port, are released.
850
851 In the procedures which follow, outgoing PDUs are "placed on the
852 input queue for the serializer". This has a different meaning
853 depending on the type of PDU being enqueued. If the PDU is not an
854 abort PDU (user-initiated or provider-initiated), then the PDU is
855 simply appended to the input queue regardless of the number of PDUs
856 present. If however, the PDU is an abort PDU, then the provider
857 checks the size of the input queue. If the input queue is non-empty
858 or if the serializer is busy transmitting to the network, then the
859 abort PDU is discarded, and the serializer is flushed, aborting any
860 output to the network in progress. However, if the input queue is
861 empty, then the Abort PDU is appended to the queue, and a small timer
862 started. If the timer expires before the PDU has been serialized and
863 transmitted, then the serializer is flushed, aborting any output to
864 the network in progress.
865
866 Further, in general, whenever the TCP connection is closed (either
867 locally by the provider, or remotely by the network) or has errored,
868 the serializer is flushed. The one exception to this is if a
869 ReleaseResponse PDU is being serialized and transmitted to the
870 network. In this case, the provider will not close the TCP
871 connection until after the serializer has finished.
872
873 <span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Elements of Procedure specific to the udp-based service</span>
874
875 The provider maintains the following information for each
876 presentation connection:
877
878 - a local designator for the PS-user
879
880 - the 32-bit IP address and 16-bit UDP port number of the
881 initiating host
882
883 - the 32-bit IP address and 16-bit UDP port number of the
884 responding host
885
886 - the session connection identifier used to establish the
887 presentation connection
888
889
890
891
892 <span class="grey">Rose [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
895
896
897 - a local designator for an UDP endpoint
898
899 - the state of the connection (e.g., IDLE, WAIT1, and so on)
900
901 - a retransmission counter
902
903 Upon receiving an event from the network, the provider finds the
904 associated presentation connection. Matching is done on the basis of
905 addresses, ports, and the session connection identifier (i.e., two
906 different presentation connections may differ only in their session
907 connection identifier). If no presentation connection can be found,
908 then for the purposes of discussion, it may be assumed that a
909 "vanilla" presentation connection is created and initialized to the
910 IDLE state. Further, whenever a connection remains in or returns to
911 the IDLE state, any associated resources, such as an attachment to a
912 local UDP port, are released.
913
914 In the procedures which follow, outgoing PDUs are "placed on the
915 input queue for the serializer". This means that the ASN.1 object is
916 serialized and the resulting sequence of octets is sent as a single
917 UDP datagram.
918
919 <span class="h3"><a class="selflink" id="section-10.3" href="#section-10.3">10.3</a>. State Transitions</span>
920
921 Following are the rules for transitioning states. If an event
922 associated with a user-generated primitive is omitted, then it is an
923 interface error for the user to issue that primitive in the given
924 state. Each state considers all possible incoming PDUs.
925
926 We assume that for the tcp-based service, that some entity starts a
927 passive TCP open. When the passive open completes, the entity, using
928 some local rule, locates a PS-user to be associated with the incoming
929 presentation connection. This presentation connection is then placed
930 in the IDLE state. The entity then continues listening for other
931 passive opens to complete. The mechanisms associated with this
932 entity are entirely a local matter, the concept of this listener is
933 introduced solely as a modeling artifact.
934
935 Finally, if the udp-based service is selected, then CL-UserData PDUs
936 are exchanged by the provider instead of UserData PDUs.
937
938
939 IDLE state
940
941 Event: P-CONNECT.REQUEST primitive issued
942
943 Based on the quality of service parameter and the list of network
944 addresses in the called presentation address parameter, the provider
945
946
947
948 <span class="grey">Rose [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
951
952
953 selects an address for the use of the presentation connection. The
954 method for making this determination is a local matter. (Appendix C
955 discusses a strategy which might be used.) For the discussion that
956 follows, we assume that a network address supporting the desired
957 quality of service has been determined.
958
959 Based on the network address chosen from the called presentation
960 address parameter, the provider selects a compatible network address
961 from the calling presentation address parameter. The provider
962 attaches itself to the port associated with this network address.
963 (By local determination, this address need not be used, and an
964 "ephemeral" port may be chosen by the provider.)
965
966 For the tcp-based service, the provider attempts to establish a TCP
967 connection to the network address listed in the called presentation
968 address. If the connection can not be established, the P-
969 CONNECT.CONFIRMATION(-) primitive is issued with a reason of
970 provider-rejection, and the provider remains in the IDLE state.
971
972 Regardless, the user data parameter is placed in a ConnectRequest
973 PDU, which is put on the input queue for the serializer.
974
975 For the udp-based service, the provider sets the retransmission
976 counter to a small value (e.g., 2), and now starts a small timer.
977
978 Regardless, the provider enters the WAIT1 state.
979
980
981 Event: ConnectRequest PDU received
982
983 The provider issues the P-CONNECT.INDICATION primitive and enters the
984 WAIT2 state.
985
986
987 Event: any other PDU received
988
989 If the PDU is not an Abort PDU, the provider constructs a provider-
990 initiated Abort PDU, which is put on the input queue for the
991 serializer. Regardless, the provider remains in the IDLE state.
992
993
994 WAIT1 state
995
996 Event: P-U-ABORT.REQUEST primitive issued
997
998 The user data parameter is placed in an Abort PDU, which is put on
999 the input queue for the serializer. The provider enters the IDLE
1000 state.
1001
1002
1003
1004 <span class="grey">Rose [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1007
1008
1009 Event: ConnectResponse PDU received
1010
1011 For the udp-based service, the timer is cancelled. If the PDU
1012 indicates rejection, the P-CONNECT.CONFIRMATION(-) primitive is
1013 issued and the provider enters the IDLE state. Otherwise, the P-
1014 CONNECT.CONFIRMATION(+) primitive is issued and the provider enters
1015 the DATA state.
1016
1017
1018 Event: user-initiated Abort PDU received
1019
1020 The provider issues the P-U-ABORT.INDICATION primitive and enters the
1021 IDLE state.
1022
1023
1024 Event: any other PDU received
1025
1026 If the PDU not an Abort PDU, the provider constructs a provider-
1027 initiated Abort PDU, which is put on the input queue for the
1028 serializer. Regardless, The provider issues the P-P-ABORT.INDICATION
1029 primitive and enters the the IDLE state.
1030
1031
1032 Event: timer expires
1033
1034 The provider decrements the retransmission counter. If the resulting
1035 value is less than or equal to zero, the provider issues the P-
1036 CONNECT.CONFIRMATION(-) primitive and enters the IDLE state.
1037 Otherwise, a ConnectRequest PDU is put on the input queue for the
1038 serializer, the small timer is started again, and the provider
1039 remains in the WAIT1 state.
1040
1041
1042 WAIT2 state
1043
1044 Event: P-CONNECT.RESPONSE primitive issued
1045
1046 The user data parameter is placed in a ConnectResponse PDU, which is
1047 put on the input queue for the serializer. If the result parameter
1048 had the value user-rejection, the provider enters the IDLE state.
1049 Otherwise if the parameter had the value acceptance, the provider
1050 enters the DATA state.
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Rose [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1063
1064
1065 Event: P-U-ABORT.REQUEST primitive issued
1066
1067 The user data parameter is placed in an Abort PDU, which is put on
1068 the input queue for the serializer. The provider enters the IDLE
1069 state.
1070
1071
1072 Event: user-initiated Abort PDU received
1073
1074 The provider issues the P-U-ABORT.INDICATION primitive and enters the
1075 IDLE state.
1076
1077
1078 Event: any other PDU received
1079
1080 If the PDU is not an Abort PDU, the provider constructs a provider-
1081 initiated Abort PDU, which is put on the input queue for the
1082 serializer. Regardless, The provider issues the P-P-ABORT.INDICATION
1083 primitive and enters the the IDLE state.
1084
1085
1086 DATA state
1087
1088 Event: P-DATA.REQUEST primitive issued
1089
1090 The user data parameter is placed in a UserData PDU, which is put on
1091 the input queue for the serializer. The provider remains in the DATA
1092 state.
1093
1094
1095 Event: P-RELEASE.REQUEST primitive issued
1096
1097 The user data parameter is placed in a ReleaseRequest PDU, which is
1098 put on the input queue for the serializer.
1099
1100 For the udp-based service, the provider sets the retransmission
1101 counter to a small value (e.g., 2), and now starts a small timer.
1102
1103 Regardless, the provider enters the WAIT3 state.
1104
1105
1106 Event: P-U-ABORT.REQUEST primitive issued
1107
1108 The user data parameter is placed in an Abort PDU, which is put on
1109 the input queue for the serializer. The provider enters the IDLE
1110 state.
1111
1112
1113
1114
1115
1116 <span class="grey">Rose [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1119
1120
1121 Event: UserData PDU received
1122
1123 The provider issues the P-DATA.INDICATION primitive and remains in
1124 the DATA state.
1125
1126
1127 Event: ReleaseRequest PDU received
1128
1129 The provider issues the P-RELEASE.INDICATION primitive, and enters
1130 the WAIT4 state.
1131
1132
1133 Event: user-initiated Abort PDU received
1134
1135 The provider issues the P-U-ABORT.INDICATION primitive and enters
1136 the IDLE state.
1137
1138
1139 Event: any other PDU received
1140
1141 If the PDU is not an Abort PDU, the provider constructs a provider-
1142 initiated Abort PDU, which is put on the input queue for the
1143 serializer. Regardless, the provider issues the P-P-ABORT.INDICATION
1144 primitive and enters the the IDLE state.
1145
1146
1147 WAIT3 state
1148
1149 Event: P-U-ABORT.REQUEST primitive issued
1150
1151 The user data parameter is placed in an Abort PDU, which is put on
1152 the input queue for the serializer. The provider enters the IDLE
1153 state.
1154
1155
1156 Event: ReleaseResponse PDU received
1157
1158 For the udp-based service, the timer is cancelled. The provider
1159 issues the P-RELEASE.CONFIRMATION primitive and enters the IDLE
1160 state.
1161
1162
1163 Event: user-initiated Abort PDU received
1164
1165 The provider issues the P-U-ABORT.INDICATION primitive and enters the
1166 IDLE state.
1167
1168
1169
1170
1171
1172 <span class="grey">Rose [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1175
1176
1177 Event: any other PDU received
1178
1179 If the PDU is not an Abort PDU, the provider constructs a provider-
1180 initiated Abort PDU, which is put on the input queue for the
1181 serializer. Regardless, the provider issues the P-P-ABORT.INDICATION
1182 primitive and enters the the IDLE state.
1183
1184
1185 Event: timer expires
1186
1187 The provider decrements the retransmission counter. If the resulting
1188 value is less than or equal to zero, the provider constructs a
1189 provider-initiated Abort PDU, which is put on the input queue for the
1190 serializer. It then issues the P-P-ABORT.INDICATION primitive and
1191 enters the IDLE state. Otherwise, a ReleaseRequest PDU is put on the
1192 input queue for the serializer, the small timer is started again, and
1193 the provider remains in the WAIT3 state.
1194
1195
1196 WAIT4 state
1197
1198 Event: P-RELEASE.RESPONSE primitive issued
1199
1200 The user data parameter is placed in a ReleaseResponse PDU, which is
1201 put on the input queue for the serializer. The provider now enters
1202 the IDLE state.
1203
1204 Event: P-U-ABORT.REQUEST primitive issued
1205
1206 The user data parameter is placed in an Abort PDU, which is put on
1207 the input queue for the serializer. The provider now enters the IDLE
1208 state.
1209
1210
1211 Event: user-initiated Abort PDU received
1212
1213 The provider issues the P-U-ABORT.INDICATION primitive and enters the
1214 IDLE state.
1215
1216
1217 Event: any other PDU received
1218
1219 If the PDU is not an Abort PDU, the provider constructs a provider-
1220 initiated Abort PDU, which is put on the input queue for the
1221 serializer. Regardless, the provider issues the P-P-ABORT.INDICATION
1222 primitive and enters the the IDLE state.
1223
1224
1225
1226
1227
1228 <span class="grey">Rose [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1231
1232
1233 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Directory Services</span>
1234
1235 Although not properly part of the presentation service, this memo
1236 assumes and specifies a minimal Directory service capability for use
1237 by the application-entity.
1238
1239 The function of the Directory Service Element is to provide two
1240 mappings: first, a service name is mapped into an application entity
1241 title, which is a global handle on the service; and, second, the
1242 application-entity title is mapped onto a presentation address.
1243
1244 The structure of presentation addresses were defined in <a href="#section-5">Section 5</a>.
1245
1246 The structure of application-entity titles is less solidly agreed
1247 upon at the present time. Since objects of this type are not
1248 interpreted by the presentation service, this memo does not specify
1249 their structure. If the DIS version of association control is being
1250 used, then use of an OBJECT IDENTIFIER will suffice. If the IS
1251 version is being employed, then application-entity titles consist of
1252 two parts: an application-process title and an application-entity
1253 qualifier. It is suggested that the AP-Title use an OBJECT
1254 IDENTIFIER and that the AE-Qualifier use NULL.
1255
1256 This memo requires the following mapping rules:
1257
1258 1. The service name for an OSI application-entity using the
1259 mechanisms proposed by this memo is:
1260
1261 &lt;designator&gt; "-" &lt;qualifier&gt;
1262
1263 where &lt;designator&gt; is a string denoting either domain name or a
1264 32-bit IP address, and &lt;qualifier&gt; is a string denoting the type
1265 of application-entity desired, e.g.,
1266
1267 "gonzo.twg.com-mgmtinfobase"
1268
1269 2. Any locally defined mapping rules may be used to map the
1270 service designation into an application-entity title.
1271
1272 3. The application-entity title is then mapped into a
1273 presentation address, with uninterpreted transport, session, and
1274 presentation selectors, and one or more network addresses, each
1275 containing:
1276
1277 -the 32-bit IP address resolved from the &lt;designator&gt; portion
1278 of the service name,
1279
1280 - a set indicating which transport services are available
1281
1282
1283
1284 <span class="grey">Rose [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1287
1288
1289 at the IP address,
1290
1291 - the 16-bit port number resolved from the &lt;qualifier&gt;
1292 portion of the service name (using the Assigned Numbers
1293 document), and
1294
1295 - optionally, a presentation selector, which is an
1296 uninterpreted sequence of octets.
1297
1298 The method by which the mappings are obtained are straight-forward.
1299 The directory services element employs the Domain Name System along
1300 with a local table which may be used to resolve the address employing
1301 local rules.
1302
1303 In the simplest of implementations, the DNS is used to map the
1304 &lt;designator&gt; to an IP address, and to fill-in the set of transport
1305 services available at the IP address. The port number is found in a
1306 local table derived from the current Assigned Numbers document.
1307 Finally, the presentation selector is empty.
1308
1309 A more ambitious implementation would use a local table to perhaps
1310 provide a presentation selector. This would be useful, e.g., in
1311 "proxy" connections. The network address would resolve to the proxy
1312 agent for the non-IP device, and the presentation selector would
1313 indicate to the proxy agent the particular non-IP device desired.
1314 This implies, of course, that the local table and the proxy agent
1315 bilaterally agree as to the interpretation of each presentation
1316 selector.
1317
1318 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Remarks</span>
1319
1320 To begin, if one really wanted to implement ISO applications in a
1321 TCP/IP-based network, then the method proposed by [<a href="./rfc1006" title="&quot;ISO Transport 1 on Top of the TCP Version: 3&quot;">RFC1006</a>] is the
1322 preferred method for achieving this. However, in a constrained
1323 environment, where it is necessary to host an application layer
1324 entity with a minimal amount of underlying OSI infrastructure, this
1325 memo proposes an alternative mechanism. It should be noted that an
1326 OSI application realized using this approach can be moved directly to
1327 an [<a href="./rfc1006" title="&quot;ISO Transport 1 on Top of the TCP Version: 3&quot;">RFC1006</a>]-based environment with no modifications.
1328
1329 A key motivation therefore is to minimize the size of the alternate
1330 underling infrastructure specified by this memo. As more and more
1331 presentation services functionality is added, the method proposed
1332 herein would begin to approximate the ISO presentation protocol.
1333 Since this in contrary to the key motivation, featurism must be
1334 avoided at all costs.
1335
1336
1337
1338
1339
1340 <span class="grey">Rose [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1343
1344
1345 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Acknowledgements</span>
1346
1347 Several individuals contributed to the technical quality of this
1348 memo:
1349
1350 Karl Auerbach, Epilogue Technologies
1351 Joseph Bannister, Unisys
1352 Amatzia Ben-Artzi, Sytek
1353 Stephen Dunford, Unisys
1354 Lee Labarre, MITRE
1355 Keith McCloghrie, The Wollongong Group
1356 Jim Robertson, Bridge Communications
1357 Glenn Trewitt, Stanford University
1358
1359 <span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. References</span>
1360
1361 [<a id="ref-ISO7498">ISO7498</a>] Information Processing Systems - Open Systems
1362 Interconnection, "Basic Reference Model", October, 1984.
1363
1364 [<a id="ref-ISO8509">ISO8509</a>] Information Processing Systems - Open Systems
1365 Interconnection, " Service Conventions".
1366
1367 [<a id="ref-ISO8650">ISO8650</a>] Information Processing Systems - Open Systems
1368 Interconnection, " Protocol Specification for the
1369 Association Control Service Element (Final Text
1370 of DIS 8650)", January, 1988.
1371
1372 [<a id="ref-ISO8822">ISO8822</a>] Information Processing Systems - Open Systems
1373 Interconnection, " Connection Oriented Presentation
1374 Service Definition (Final Text of DIS 8822)",
1375 April, 1988.
1376
1377 [<a id="ref-ISO8823">ISO8823</a>] Information Processing Systems - Open Systems
1378 Interconnection, " Connection Oriented Presentation
1379 Protocol Specification (Final Text of DIS 8822)",
1380 April, 1988.
1381
1382 [<a id="ref-ISO8824">ISO8824</a>] Information Processing Systems - Open Systems
1383 Interconnection, " Specification of Abstract Syntax
1384 Notation One (ASN.1)", December, 1987.
1385
1386 [<a id="ref-ISO8825">ISO8825</a>] Information Processing Systems - Open Systems
1387 Interconnection, "Specification of basic encoding rules
1388 for Abstract Syntax Notation One (ASN.1)",
1389 December, 1987.
1390
1391 [ISO9072/2] Information Processing Systems - Text Communication
1392 MOTIS, " Remote Operations Part 2: Protocol
1393
1394
1395
1396 <span class="grey">Rose [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1399
1400
1401 Specification (Working Document for DIS 9072/2)",
1402 November, 1987.
1403
1404 [<a id="ref-RFC768">RFC768</a>] Postel, J., "User Datagram Protocol", <a href="./rfc768">RFC 768</a>, USC/ISI,
1405 28 August 1980.
1406
1407 [<a id="ref-RFC791">RFC791</a>] Postel, J., "Internet Protocol - DARPA Internet Program
1408 Protocol Specification", <a href="./rfc791">RFC 791</a>, USC/ISI,
1409 September 1981.
1410
1411 [<a id="ref-RFC793">RFC793</a>] Postel, J., "Transmission Control Protocol - DARPA
1412 Internet Program Protocol Specification", <a href="./rfc793">RFC 793</a>,
1413 USC/ISI, September 1981.
1414
1415 [<a id="ref-RFC1006">RFC1006</a>] Rose, M., and D. Cass, "ISO Transport 1 on Top of the
1416 TCP Version: 3", Northrop Research and Technology
1417 Center, May 1987.
1418
1419 Appendix A:
1420
1421 Abstract Syntax Definitions
1422
1423 <a href="./rfc1085">RFC1085</a>-PS DEFINITIONS ::=
1424
1425 BEGIN
1426
1427 PDUs ::=
1428 CHOICE {
1429 connectRequest
1430 ConnectRequest-PDU,
1431
1432 connectResponse
1433 ConnectResponse-PDU,
1434
1435 releaseRequest
1436 ReleaseRequest-PDU,
1437
1438 releaseResponse
1439 ReleaseResponse-PDU,
1440
1441 abort
1442 Abort-PDU,
1443
1444 userData
1445 UserData-PDU,
1446
1447 cL-userData
1448 CL-UserData-PDU
1449
1450
1451
1452 <span class="grey">Rose [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1455
1456
1457 }
1458
1459
1460
1461 -- connect request PDU
1462
1463 ConnectRequest-PDU ::=
1464 [0]
1465 IMPLICIT SEQUENCE {
1466 version[0] -- version-1 corresponds to to this
1467 memo
1468 IMPLICIT INTEGER { version-1(0) },
1469
1470 reference
1471 SessionConnectionIdentifier,
1472
1473 calling
1474 PresentationSelector
1475 OPTIONAL,
1476
1477 called[2]
1478 IMPLICIT PresentationSelector
1479 OPTIONAL,
1480
1481 asn[3] -- the ASN for PCI #1
1482 IMPLICIT OBJECT IDENTIFIER,
1483
1484 user-data
1485 UserData-PDU
1486 }
1487
1488 SessionConnectionIdentifier ::=
1489 [0]
1490 SEQUENCE {
1491 callingSSUserReference
1492 T61String,
1493
1494 commonReference
1495 UTCTime,
1496
1497 additionalReferenceInformation[0]
1498 IMPLICIT T61String
1499 OPTIONAL
1500 }
1501
1502 PresentationSelector ::=
1503 [1]
1504 IMPLICIT OCTET STRING
1505
1506
1507
1508 <span class="grey">Rose [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1511
1512
1513 -- connect response PDU
1514
1515 ConnectResponse-PDU ::=
1516 [1]
1517 IMPLICIT SEQUENCE {
1518 reference -- present only in the udp-based
1519 -- service
1520 SessionConnectionIdentifier
1521 OPTIONAL,
1522
1523 responding
1524 PresentationSelector
1525 OPTIONAL,
1526
1527 reason[2] -- present only if the connection
1528 -- was rejected
1529 IMPLICIT Rejection-reason
1530 OPTIONAL,
1531
1532 user-data -- present only if reason is absent
1533 -- OR has the
1534 -- value rejected-by-responder
1535 UserData-PDU
1536 OPTIONAL
1537 }
1538
1539 Rejection-reason ::=
1540 INTEGER {
1541 rejected-by-responder(0)
1542 called-presentation-address-unknown(1),
1543 local-limit-exceeded(3),
1544 protocol-version-not-supported(4),
1545 }
1546
1547
1548 -- release request PDU
1549
1550 ReleaseRequest-PDU ::=
1551 [2]
1552 IMPLICIT SEQUENCE {
1553 reference -- present only in the udp-based
1554 -- service
1555 SessionConnectionIdentifier
1556 OPTIONAL,
1557
1558 user-data
1559 UserData-PDU
1560 }
1561
1562
1563
1564 <span class="grey">Rose [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1567
1568
1569 -- release response PDU
1570
1571 ReleaseResponse-PDU ::=
1572 [3]
1573 IMPLICIT SEQUENCE {
1574 reference -- present only in the udp-based
1575 -- service
1576 SessionConnectionIdentifier
1577 OPTIONAL,
1578
1579 user-data
1580 UserData-PDU
1581 }
1582
1583 -- abort PDU
1584
1585 Abort-PDU ::=
1586 [4]
1587 SEQUENCE {
1588 reference -- present only in the udp-based
1589 -- service
1590 SessionConnectionIdentifier
1591 OPTIONAL,
1592
1593 user-data -- MAY BE present on user-initiated abort
1594 UserData-PDU
1595 OPTIONAL,
1596
1597 reason[1] -- ALWAYS present on provider-initiated abort
1598 IMPLICIT Abort-reason
1599 OPTIONAL
1600 }
1601
1602 Abort-reason ::=
1603 INTEGER {
1604 unspecified(0),
1605 unrecognized-ppdu(1),
1606 unexpected-ppdu(2),
1607 unrecognized-ppdu-parameter(4),
1608 invalid-ppdu-parameter(5),
1609 reference-mismatch(9)
1610 }
1611
1612
1613 -- data PDU
1614
1615 UserData-PDU ::=
1616 [<a href="#ref-5" title=" 5">5</a>] -- this is the ASN.1 object
1617
1618
1619
1620 <span class="grey">Rose [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1623
1624
1625 ANY -- if it is a top-level PDU, it
1626 -- is in PCI #1, otherwise PCI #3
1627
1628
1629 -- data PDU for the udp-based service
1630
1631 CL-UserData-PDU ::=
1632 [6]
1633 IMPLICIT SEQUENCE {
1634 reference
1635 SessionConnectionIdentifier,
1636
1637 user-data[0] -- this is the ASN.1 object
1638 ANY -- it is always in PCI #1
1639 }
1640
1641 END
1642
1643 Appendix B:
1644
1645 Example of Serialization
1646
1647
1648 Consider the following call to ROSE:
1649
1650 RO-INVOKE (operation number = 5
1651 operation class = synchronous
1652 argument = NONE
1653 invocation identifier = 1
1654 linked invocation id. = NONE
1655 priority = 0)
1656 .REQUEST
1657
1658 Ultimately, ROSE will use the P-DATA service:
1659
1660 P-DATA (user data = {
1661 1, -- this is the PCI
1662 { -- this is the ASN.1 object
1663 invokeID 1,
1664 operation-value 5,
1665 argument {}
1666 }
1667 })
1668 .REQUEST
1669
1670 The presentation provider will construct a UserData PDU and send this
1671 via the transport connection:
1672
1673
1674
1675
1676 <span class="grey">Rose [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1679
1680
1681 [<a id="ref-5">5</a>] {
1682 {
1683 1,
1684 5,
1685 {}
1686 }
1687 }
1688
1689 Applying the basic encoding rules for ASN.1, we have an stream of 12
1690 octets.
1691
1692 a5 0a [<a href="#ref-5" title=" 5">5</a>]
1693 tag len
1694
1695 a0 08 [0]
1696 tag len
1697 02 01 01 invokeID 1
1698 tag len value
1699
1700 02 01 05 operation-value 5
1701 tag len value
1702
1703 30 00 argument NULL
1704 tag len
1705
1706 Of course, in actual use, the argument would not be NONE and this
1707 could be expected to dominate the size of the UserData PDU. However,
1708 it is worth nothing that the overhead of the encoding mechanism used
1709 is on the order of 10 octets, hardly a staggering amount!
1710
1711 Appendix C:
1712
1713 Determination of Network Called Address
1714
1715 As described in <a href="#section-10">Section 10</a>, when the P-CONNECT.REQUEST primitive is
1716 issued the presentation provider must determine which of the network
1717 addresses present in the called presentation address parameter to use
1718 for the presentation connection. The first step in this
1719 determination is to examine the quality of service parameter and
1720 consider only those network addresses which support the corresponding
1721 transport service. In practice, it is likely that each network
1722 address will support exactly the same transport services, so using
1723 quality of service as a discriminant will either permit all or none
1724 or the network addresses present to be selected. This appendix
1725 describes a local policy which might be employed when deciding which
1726 network address to use.
1727
1728 The policy distinguishes between "underlying failures" and
1729
1730
1731
1732 <span class="grey">Rose [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc1085">RFC 1085</a> ISO Presentation Services December 1988</span>
1735
1736
1737 "connection establishment failures". An "underlying failure" occurs
1738 when, using the desired transport service, the initiating
1739 presentation provider is unable to contact the responding
1740 presentation provider. For the tcp-based service, this means that a
1741 TCP connection could not be established for some reason. For the
1742 udp-based service, it means that a response was not received before
1743 final time-out. In contrast, a "connection establishment failure"
1744 occurs when the responding presentation provider can be contacted,
1745 but the presentation connection is rejected by either the
1746 presentation provider or the correspondent presentation user.
1747
1748 The policy is simple: starting with the first network address
1749 present, attempt the connection procedure. If the procedure fails
1750 due to an "underlying failure", then the next network address in the
1751 list is tried. This process is repeated until either an underlying
1752 connection is established or all network addresses are exhausted.
1753 If, however, a "connection establishment failure" occurs, then the
1754 presentation provider immediately indicates this failure to the
1755 presentation user and no further network addresses are considered.
1756
1757 Note that this is only one conformant policy of many. For example,
1758 the presentation provider may wish to order network addresses based
1759 on the "intensity" associated with the members present in the set of
1760 transport services for each network address.
1761
1762 Author's Address:
1763
1764 Marshall Rose
1765 The Wollongong Group
1766 1129 San Antonio Road
1767 Palo Alto, CA 94303
1768
1769 Phone: (415) 962-7100
1770
1771 EMail: [email protected]
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788 Rose [Page 32]
1789 </pre>