1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
|
<pre>Network Working Group S.E. Hardcastle-Kille
Requests for Comments 1278 University College London
November 1991
<span class="h1">A string encoding of Presentation Address</span>
Status of this Memo
This memo provides information for the Internet community. It
does not specify an Internet standard. Distribution of this memo
is unlimited.
Abstract
There are a number of environments where a simple string encoding
of Presentation Address is desirable. This specification defines
such a representation.</pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1278">RFC 1278</a> String encoded P-Address November 1991
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a> Introduction</span>
OSI Application Entities use presentation addresses to address other
Application Entities. The model for this is defined in [<a href="#ref-ISO87b">ISO87b</a>].
Presentation addresses are stored in the OSI Directory using an ASN.1
representation defined by the OSI Directory [<a href="#ref-CCI88" title="models and services">CCI88</a>]. Logically, a
presentation address consists of:
o A presentation selector
o A session selector
o A transport selector
o A set of network addresses
The selectors are all octet strings, but often have IA5 character
representations. The format of network addresses is defined in
[<a href="#ref-ISO87a">ISO87a</a>].
There is a need to represent presentation addresses as strings in a
number of different contexts. This Internet Draft defines a format
for use on the Internet. It is for display to human users, and its
use is recommended whenever this needs to be done. Typically, this
will be for system managers rather than for end users. It is not
intended for internal storage.
This Internet Draft was originally published as UCL Research Note
RN/89/14 [<a href="#ref-Kil89" title=" University College London">Kil89</a>]. It was agreed as a unified syntax for the THORN and
ISODE projects. It is used throughout ISODE.
Christian Huitema of Inria and Marshall Rose of PSI Inc. gave much
useful input to this document.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> Requirements</span>
The main requirements are:
o Must be able to specify any legal value.
o Should be clean in the common case of the presentation address
containing network addresses and no selectors.
Hardcastle-Kille Page 1</pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1278">RFC 1278</a> String encoded P-Address November 1991
o Must deal with selectors in the following encodings:
-- IA5
-- Decimal digits encoded as IA5 (this is the most common syntax
in Europe, as it is required by X.400(84) and should receive a
straightforward encoding)
-- Numeric encoded as a 16 bit unsigned integer (US GOSIP). This
is mapped onto two octets, with the first octet being the high
order byte of the integer.
-- General Hexadecimal
o Should give special encodings for the ad hoc encoding proposed in
``An interim approach to use of Network Addresses'' [<a href="#ref-HK91" title="Department of Computer Science">HK91</a>].
-- X.25(80) Networks
-- TCP/IP Networks
o Should be extensible for additional forms.
o Should provide a reasonably compact representation .
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a> Format</span>
The_BNF_is_given_in_figure_1.__________________________________________
<digit> ::= [0-9]
<other> ::= [0-9a-zA-Z+-.]
<domainchar> ::= [0-9a-zA-Z-.]
<hexdigit> ::= [0-9a-fA-F]
<hexoctet> ::= <hexdigit> <hexdigit>
<decimaloctet> ::= <digit> | <digit> <digit>
| <digit> <digit> <digit>
<digitstring> ::= <digit> <digitstring> 10
| <digit>
<otherstring> ::= <other> <otherstring>
| <other>
Hardcastle-Kille Page 2</pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1278">RFC 1278</a> String encoded P-Address November 1991
<domainstring> ::= <domainchar> <otherstring>
| <domainchar>
<hexstring> ::= <hexoctet> <hexstring> | <hexoctet>
<dotstring> ::= <decimaloctet> "." <dotstring>
| <decimaloctet> "." <decimaloctet>
20
<dothexstring> ::= <dotstring> | <hexstring>
<presentation-address> ::=
[[[ <psel> "/" ] <ssel> "/" ] <tsel> "/" ]
<network-address-list>
<network-address-list> ::= <network-address> "_" <network-address-list>30
| <network-address>
<psel> ::= <selector>
<ssel> ::= <selector>
<tsel> ::= <selector>
<selector> ::= '"' <otherstring> '"' -- IA5
-- For chars not in this
-- string use hex
| "#" <digitstring> -- US GOSIP 40
| "'" <hexstring> "'H" -- Hex
| "" -- Empty but present
<network-address> ::= "NS" "+" <dothexstring>
-- Concrete Binary Representation
-- This is the compact encoding
| <afi> "+" <idi> [ "+" <dsp> ]
-- A user oriented form
| <idp> "+" <hexstring>
-- ISO 8348 Compatability 50
<idp> ::= <digitstring> -
<dsp> ::=
| "d" <digitstring> -- Abstract Decimal
| "x" <dothexstring> -- Abstract Binary
| "l" <otherstring> -- IA5: local form only
Hardcastle-Kille Page 3</pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1278">RFC 1278</a> String encoded P-Address November 1991
| "<a href="./rfc1006">RFC-1006</a>" "+" <prefix> "+" <ip>
[ "+" <port> [ "+" <tset> ]]
| "X.25(80)" "+" <prefix> "+" <dte> 60
[ "+" <cudf-or-pid> "+" <hexstring> ]
| "ECMA-117-Binary" "+" <hexstring> "+" <hexstring>
"+" <hexstring>
| "ECMA-117-Decimal" "+" <digitstring> "+"
<digitstring> "+" <digitstring>
<idi> ::= <digitstring>
<afi> ::= "X121" | "DCC" | "TELEX" | "PSTN" | "ISDN"
| "ICD" | "LOCAL"
70
<prefix> ::= <digit> <digit>
<ip> ::= <domainstring>
-- dotted decimal form (e.g., 10.0.0.6)
-- or domain (e.g., twg.com)
<port> ::= <digitstring>
<tset> ::= <digitstring>
<dte> ::= <digitstring>
<cudf-or-pid> ::= "CUDF" | "PID" 80
________________________Figure_1:__String_BNF__________________________
Four examples:
"256"/NS+a433bb93c1_NS+aa3106
#63/#41/#12/X121+234219200300
'3a'H/TELEX+00728722+X.25(80)+02+00002340555+CUDF+"892796"
TELEX+00728722+<a href="./rfc1006">RFC-1006</a>+03+10.0.0.6
Note that the <a href="./rfc1006">RFC 1006</a> encoding permits use of either a DNS Domain
Name or an IP address. The former is primarily for ease of entry. If
this DNS Domain Name maps onto multiple IP addresses, then multiple
network addresses should be generated. The DNS Domain Name form is
Hardcastle-Kille Page 4</pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1278">RFC 1278</a> String encoded P-Address November 1991
for convenient input. When mapping from an encoded address to string
form, the IP address form should always be used.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a> Encoding</span>
Selectors are represented in a manner which can be easily encoded. In
the NS notation, the concrete binary form of network address is given.
Otherwise, this string notation provides a mechanism for representing
the Abstract Syntax of a Network Address. This must be encoded
according to Addendum 2 of ISO 8348 [<a href="#ref-ISO87a">ISO87a</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a> Macros</span>
There are often common addresses, for which a cleaner representation
is desired. This is achieved by use of Macros. If a
<network-address> can be parsed as:
<otherstring> "=" *( any )
Then the leading string is taken as a Macro, which is substituted.
This may be applied recursively. When presenting Network Address to
humans, the longest available substitution should be used. For
example:
________________________
|_Macro_|Value__________ |
| UK.AC |DCC+826+d110000 |
|_Leeds_|UK.AC=120______ |
Then ``Leeds=22'' would be expanded to ``DCC+826+d11000012022''.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> Standard Macros</span>
No Macros should ever be relied on. However, the following are
suggested as standard.
Hardcastle-Kille Page 5</pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1278">RFC 1278</a> String encoded P-Address November 1991
________________________________________________
|_Macro_____________|Value______________________ |
| Int-X25(80) |TELEX+00728722+X25(80)+01+ |
| Janet-X25(80) |TELEX+00728722+X25(80)+02+ |
| Internet-RFC-1006 |TELEX+00728722+<a href="./rfc1006">RFC-1006</a>+03+ |
|_IXI_______________|TELEX+00728722+<a href="./rfc1006">RFC-1006</a>+06+_|
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a> References</span>
References
[<a id="ref-CCI88">CCI88</a>] The Directory --- overview of concepts, models and services,
December 1988. CCITT X.500 Series Recommendations.
[<a id="ref-HK91">HK91</a>] S.E. Hardcastle-Kille. Encoding network addresses to support
operation over non-osi lower layers. Request for Comments
<a href="./rfc1277">RFC 1277</a>, Department of Computer Science, University College
London, November 1991.
[<a id="ref-ISO87a">ISO87a</a>] Information processing systems - data communications -
network services definition: Addendum 2 - network layer
addressing, March 1987. ISO TC 97/SC 6.
[<a id="ref-ISO87b">ISO87b</a>] ISO DIS 7498-3 on naming and addressing, May 1987.
ISO/IEC/JTC-1/SC 21.
[<a id="ref-Kil89">Kil89</a>] S.E. Kille. A string encoding of presentation address.
Research Note RN/89/14, Department of Computer Science,
University College London, February 1989.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a> Security Considerations</span>
Security considerations are not discussed in this memo.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a> Author's Address</span>
Steve Hardcastle-Kille
Department of Computer Science
University College London
Gower Street
WC1E 6BT
Hardcastle-Kille Page 6</pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><a href="./rfc1278">RFC 1278</a> String encoded P-Address November 1991
England
Phone: +44-71-380-7294
EMail: S.Kille@CS.UCL.AC.UK
Hardcastle-Kille Page 7
</pre>
|
