![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to X-STANDARDS CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / others / X|
Return to X-STANDARDS CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / others / X |
1.1 root 1: (Message inbox:39)
2: Replied: Thu, 23 Nov 89 11:49:43 +0000
3: Replied: John Dyer <[email protected]>
4: Replied: [email protected]
5: Replied: "x3h3.6" <x3h3.6%[email protected]>
6: Received: from vs6.cs.ucl.ac.uk by pyr1.Cs.Ucl.AC.UK via Ethernet with SMTP
7: id aa28231; 23 Nov 89 11:03 GMT
8: Received: from gec-b.rutherford.ac.uk by vs6.Cs.Ucl.AC.UK via Janet with NIFTP
9: id aa04229; 23 Nov 89 10:58 WET
10: Via: UK.AC.RUTHERFORD.GEC-B ; Thu, 23 Nov 89 10:58 GMT
11: (V39 at UK.AC.RUTHERFORD.GEC-B)
12: From: John Dyer <[email protected]>
13: To: [email protected],
14: "x3h3.6" <x3h3.6%[email protected]>
15: Date: Thu, 23 Nov 89 10:58 GMT
16: Subject: Proposed Transport Annex to X DSE
17: Message-Id: <23 NOV 1989 10:58:09 [email protected]>
18:
19:
20: Here is the revised Appendix to the X Window System DSE. This version is a
21: re write of the previuos version, but has been changed to accommodate the
22: use of any Transport Class (ie TP0 through to TP4).
23:
24: The major changes involve the NON use of user data fields in T-CONNECT
25: and T-DISCONNECT.
26:
27: John Dyer
28: Joint Network Team
29: --------------------------------------------------------------------------------
30:
31: DRAFT (v2.0) PROPOSED APPENDIX xx
32:
33: X Windows Mapping to OSI
34:
35:
36: This appendix should be treated as an integral part of (the ANSI
37: standard X3H3.6/yy-nnnn).
38:
39: This appendix defines the mapping of the X Windows protocol defined
40: in (the ANSI standard X3H3.6/yy-nnnn) onto the communication
41: services provided by the Open Systems Interconnection (OSI)
42: standards. (The OSI reference model is described in ISO 7498). It
43: shows not only the mappings onto the OSI communication primitives,
44: but also how the registration and addressing requirements of the X
45: Windows protocol are handled for OSI.
46:
47: This appendix consists of two sections, section A.1 for the mapping
48: of X Windows functions onto OSI service primitives and section A.2
49: for the X Windows registration requirements.
50:
51: This appendix references ISO 8072 (Transport Service Definition) and
52: uses the notation and conventions which are contained in sections 3,
53: 4 and 5 of that document.
54:
55:
56: A.1 Mapping X Windows Functions to OSI Service primitives
57:
58: This section specifies the OSI service primitives used to support
59: the X Windows functions.
60:
61: The X Windows requirements on the communication mechanism which have
62: been considered in choosing this OSI service are :
63:
64: a) the asynchronous nature of the way X Windows uses the
65: communication mechanism,
66:
67: b) connection oriented communication,
68:
69: c) reliable communication service,
70:
71: d) full duplex communication,
72:
73: e) process addressing, i.e. ability to select a particular X Windows
74: server,
75:
76: f) the supporting OSI functionality that most closely matches that
77: for which X Windows was written,
78:
79: g) efficiency,
80:
81: h) interworking with existing implementations.
82:
83:
84: These requirements are met using a connection oriented TWS (two way
85: simultaneous, i.e. full duplex) OSI Transport Layer connection
86: providing a service direct to client and server.
87:
88: A.1.1 Transport Connection Establishment and Termination
89:
90: A.1.1.1 Connection Establishment
91:
92: | The X Window function OPEN DISPLAY (see Part 1, section 7.6.1 of the
93: | ANSI standard X3H3.6/yy-nnnn) establishes a connection between the
94: | client and server. For operation over OSI, the transport service
95: | connection is made by T-CONNECT, however the X Windows OPEN DISPLAY
96: | function is not carried in the T-CONNECT User-Data parameter, but in
97: | the User-Data of the subsequent T-DATA.
98:
99:
100: The COTS T-CONNECT service is defined in section 12 and the
101: T-CONNECT parameters are listed in table 5 of ISO 8072.
102:
103:
104: A.1.1.1.1 COTS T-CONNECT parameters and OPEN DISPLAY
105:
106: | The T-CONNECT parameter values for support of OPEN DISPLAY are as
107: | specified in table 1. An explanation of the use of each parameter
108: | follows the table.
109:
110: | Table 1 -- T-CONNECT Parameter Values to support OPEN DISPLAY
111:
112: +-------------------------------------+-----+-----+-----+-----+
113: | T-CONNECT Parameter Name | Req | Ind | Rsp | Cnf |
114: | +-------------------------------------+-----+-----+-----+-----+
115: | | Called Address | X | X(=)| | |
116: | +-------------------------------------+-----+-----+-----+-----+
117: | | Calling Address | X | X(=)| | |
118: | +-------------------------------------+-----+-----+-----+-----+
119: | | Responding Address | | | X | X(=)|
120: | +-------------------------------------+-----+-----+-----+-----+
121: | | Expedited Data Option | N | N | N | N |
122: | +-------------------------------------+-----+-----+-----+-----+
123: | | Quality of Service | N | N | N | N |
124: | +-------------------------------------+-----+-----+-----+-----+
125: | | User-Data | N | N | N | N |
126: +-------------------------------------+-----+-----+-----+-----+
127:
128: | Key: X: Mandatory Parameter
129:
130: (=): The value of this parameter is indentical to the value
131: of the corresponding parameter of the preceding primitive.
132:
133: | N: Not used by X Windows - where the parameter needs a value
134: | as a mandatory requirement of the transport service it may
135: | take a default value.
136:
137:
138: | Addresses: The paramaters which take address values all refer to
139: | TSAPs. These addresses are unique within the scope of TSAP
140: | addresses.
141:
142: Called Address: This mandatory parameter identifies the application
143: process which is the X Windows server to which the T-CONNECT is
144: being sent. It conveys the address of the TSAP to which the
145: transport connection is to be established.
146:
147: Calling Address: This mandatory parameter identifies the application
148: process which is the X Windows client. It conveys the address of
149: the TSAP from which the transport connection has been requested.
150:
151: Responding Address: This mandatory parameter conveys the address of
152: the TSAP to which the transport connection has been established
153: and is identical to the Called Address parameter.
154:
155: Expedited Data Option: X Windows deals with all communication
156: requests serially and does not have the notion of urgent data.
157: The Expedited Data Option therefore always takes the value 'not
158: selected'.
159:
160: Quality of Service: This mandatory parameter consists of a list of
161: parameters specifying the quality of service for the transport
162: connection. The parameters are defined in section 10 of ISO
163: 8072.
164:
165: Note: This parameter is currently not widely used by OSI
166: applications and is not used by X Windows.
167:
168: | TS User-Data: This mandatory parameter is not used by X Windows OPEN
169: | DISPLAY.
170:
171:
172: A.1.1.2 Connection Release
173:
174: | A.1.1.2.1 COTS T-DISCONNECT and CLOSE DISPLAY
175:
176: The X Window function CLOSE DISPLAY is used to terminate the
177: | connection from the client in an orderly fashion. The X Windows
178: | function CLOSE DISPLAY is mapped to T-DATA User-Data and the
179: | transport connection terminated by a subsequent T-DISCONNECT.
180:
181: | Table 2 T-DISCONNECT Parameter Values to support CLOSE DISPLAY
182:
183: +----------------------------------+-----+-----+
184: | T-DISCONNECT Parameter Name | Req | Ind |
185: +----------------------------------+-----+-----+
186: | | Disconnect Reason | | X |
187: +----------------------------------+-----+-----+
188: | | User Data | N | N |
189: +----------------------------------+-----+-----+
190:
191: | Key: X: Mandatory Parameter
192:
193: | N: Not used by X Windows - where the parameter needs a value
194: | as a mandatory requirement of the transport service it may
195: | take a default value.
196:
197:
198: Reason: The disconnection reason parameter gives information
199: indicating the cause of the transport connection release. The
200: reason will be one of those listed in section 14.2.1 of ISO
201: 8072.
202:
203: | User data: This mandatory parameter is not used by X Windows CLOSE
204: | DISPLAY.
205:
206:
207: | A.1.1.2.2 COTS T-DISCONNECT and KILL CLIENT
208:
209: | The X Window function KILL CLIENT request from the server to
210: | terminate the client immediately is mapped to T-DATA User-Data. The
211: | transport service connection being terminated by a subsequent
212: | T-DISCONNECT. The T-DISCONNECT parameter values for support of KILL
213: | CLIENT are as specified in table 3.
214:
215:
216: | Table 3 T-DISCONNECT Parameter Values to support KILL CLIENT
217:
218:
219: +----------------------------------+-----+-----+
220: | T-DISCONNECT Parameter Name | Req | Ind |
221: +----------------------------------+-----+-----+
222: | | Disconnect Reason | | X |
223: +----------------------------------+-----+-----+
224: | | User Data | N | N |
225: +----------------------------------+-----+-----+
226:
227:
228: | Key: X: Mandatory Parameter
229:
230: | N: Not used by X Windows - where the parameter needs a value
231: | as a mandatory requirement of the transport service it may
232: | take a default value.
233:
234: Reason: The disconnection reason parameter gives information
235: indicating the cause of the transport connection release. The
236: reason will be one of those listed in section 14.2.1 of ISO
237: 8072.
238:
239: | User data: This mandatory parameter is not used by the X Windows
240: | KILL CLIENT function.
241:
242:
243: A.1.2 Data Transmission
244:
245: | All of the X Windows functions datstream is to be carried in the
246: | transport service T-DATA User-Data. This includes the functions OPEN
247: | DISPLAY, CLOSE DISPLAY and KILL CLIENT specifically mentioned above.
248:
249: T-DATA has only one parameter as shown in table 4. An explanation of
250: the use of this parameter follows the table.
251:
252: Table 4 T-DATA Parameter Values
253:
254: +-------------------------------------+-----+-----+
255: | T-DATA Parameter Name | Req | Ind |
256: +-------------------------------------+-----+-----+
257: | | User data | X | X(=)|
258: +-------------------------------------+-----+-----+
259:
260: | Key: X: Mandatory Parameter
261:
262: (=): The value of this parameter is indentical to the value
263: of the corresponding parameter of the preceding primitive.
264:
265:
266:
267: User data: This mandatory parameter passes all X Windows functions
268: and datastreams between X Windows clients and servers. For
269: support of X Windows, the ASN.1 type of this data is EXTERNAL
270: where the encoding is as specified in Part 2 of (the ANSI
271: standard X3H3.6/yy-nnnn).
272:
273:
274:
275: A.1.3 Lower Layer Requirements
276:
277: | Layers 1 to 3 may be any coordinated set of protocols, either
278: | connection oriented or connectionless, capable of supporting the
279: | Connection Oriented Transport Service.
280:
281: | This appendix defines a mapping onto a Transport service which is
282: | capable of supporting all of the five protocol classes specified in
283: | sections 7 to 12 of ISO 8073 (Connection Oriented Transport Protocol
284: | Specification). It is recommended that for a Connection Oriented
285: | Network the appropriate Transport Protocol Class is class 0, as
286: | specified in section 8 of ISO 8073.
287:
288: A.2 Registration, Names and Addresses
289:
290: A.2.1 Registration
291:
292: The registration requirements for X Windows consist of registering
293: the names of X Windows servers.
294:
295: The resolution of names to addresses may be handled using local
296: (e.g. non-standardized) mechanisms or by the use of the OSI
297: Directory service, see ISO 9594.
298:
299: | ***END OF PROPOSED TEXT (JD v2.0 24/10/89)***
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.