Debian Codegraph @

rfc1706.html

raw
1 <pre>Network Working Group B. Manning
2 Request for Comments: 1706 ISI
3 Obsoletes: <a href="./rfc1637">1637</a>, <a href="./rfc1348">1348</a> R. Colella
4 Category: Informational NIST
5 October 1994
6
7
8 <span class="h1">DNS NSAP Resource Records</span>
9
10
11 Status of this Memo
12
13 This memo provides information for the Internet community. This memo
14 does not specify an Internet standard of any kind. Distribution of
15 this memo is unlimited.
16
17 Abstract
18
19 OSI lower layer protocols, comprising the connectionless network
20 protocol (CLNP) and supporting routing protocols, are deployed in
21 some parts of the global Internet. Maintenance and debugging of CLNP
22 connectivity is greatly aided by support in the Domain Name System
23 (DNS) for mapping between names and NSAP addresses.
24
25 This document defines the format of one new Resource Record (RR) for
26 the DNS for domain name-to-NSAP mapping. The RR may be used with any
27 NSAP address format.
28
29 NSAP-to-name translation is accomplished through use of the PTR RR
30 (see STD 13, <a href="./rfc1035">RFC 1035</a> for a description of the PTR RR). This paper
31 describes how PTR RRs are used to support this translation.
32
33 This document obsoletes <a href="./rfc1348">RFC 1348</a> and <a href="./rfc1637">RFC 1637</a>.
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Manning &amp; Colella [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc1706">RFC 1706</a> DNS NSAP RRs October 1994</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
58
59 OSI lower layer protocols, comprising the connectionless network
60 protocol (CLNP) [<a href="#ref-5" title=" Switzerland">5</a>] and supporting routing protocols, are deployed in
61 some parts of the global Internet. Maintenance and debugging of CLNP
62 connectivity is greatly aided by support in the Domain Name System
63 (DNS) [<a href="#ref-7" title="&quot;Domain Names -- Concepts and Facilities&quot;">7</a>] [<a href="#ref-8" title="&quot;Domain Names -- Implementation and Specification&quot;">8</a>] for mapping between names and NSAP (network service
64 access point) addresses [<a href="#ref-6" title="Switzerland">6</a>] [Note: NSAP and NSAP address are used
65 interchangeably throughout this memo].
66
67 This document defines the format of one new Resource Record (RR) for
68 the DNS for domain name-to-NSAP mapping. The RR may be used with any
69 NSAP address format.
70
71 NSAP-to-name translation is accomplished through use of the PTR RR
72 (see <a href="./rfc1035">RFC 1035</a> for a description of the PTR RR). This paper describes
73 how PTR RRs are used to support this translation.
74
75 This memo assumes that the reader is familiar with the DNS. Some
76 familiarity with NSAPs is useful; see [<a href="#ref-1" title="&quot;Guidelines for OSI NSAP Allocation inh the Internet&quot;">1</a>] or Annex A of [<a href="#ref-6" title="Switzerland">6</a>] for
77 additional information.
78
79 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Background</span>
80
81 The reason for defining DNS mappings for NSAPs is to support the
82 existing CLNP deployment in the Internet. Debugging with CLNP ping
83 and traceroute has become more difficult with only numeric NSAPs as
84 the scale of deployment has increased. Current debugging is supported
85 by maintaining and exchanging a configuration file with name/NSAP
86 mappings similar in function to hosts.txt. This suffers from the lack
87 of a central coordinator for this file and also from the perspective
88 of scaling. The former describes the most serious short-term
89 problem. Scaling of a hosts.txt-like solution has well-known long-
90 term scaling difficiencies.
91
92 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Scope</span>
93
94 The methods defined in this paper are applicable to all NSAP formats.
95
96 As a point of reference, there is a distinction between registration
97 and publication of addresses. For IP addresses, the IANA is the root
98 registration authority and the DNS a publication method. For NSAPs,
99 Annex A of the network service definition, ISO8348 [<a href="#ref-6" title="Switzerland">6</a>], describes the
100 root registration authority and this memo defines how the DNS is used
101 as a publication method.
102
103
104
105
106
107
108 <span class="grey">Manning &amp; Colella [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc1706">RFC 1706</a> DNS NSAP RRs October 1994</span>
111
112
113 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Structure of NSAPs</span>
114
115 NSAPs are hierarchically structured to allow distributed
116 administration and efficient routing. Distributed administration
117 permits subdelegated addressing authorities to, as allowed by the
118 delegator, further structure the portion of the NSAP space under
119 their delegated control. Accomodating this distributed authority
120 requires that there be little or no a priori knowledge of the
121 structure of NSAPs built into DNS resolvers and servers.
122
123 For the purposes of this memo, NSAPs can be thought of as a tree of
124 identifiers. The root of the tree is ISO8348 [<a href="#ref-6" title="Switzerland">6</a>], and has as its
125 immediately registered subordinates the one-octet Authority and
126 Format Identifiers (AFIs) defined there. The size of subsequently-
127 defined fields depends on which branch of the tree is taken. The
128 depth of the tree varies according to the authority responsible for
129 defining subsequent fields.
130
131 An example is the authority under which U.S. GOSIP defines NSAPs [<a href="#ref-2" title="U.S. Department of Commerce">2</a>].
132 Under the AFI of 47, NIST (National Institute of Standards and
133 Technology) obtained a value of 0005 (the AFI of 47 defines the next
134 field as being two octets consisting of four BCD digits from the
135 International Code Designator space [<a href="#ref-3" title=" Switzerland">3</a>]). NIST defined the subsequent
136 fields in [<a href="#ref-2" title="U.S. Department of Commerce">2</a>], as shown in Figure 1. The field immediately following
137 0005 is a format identifier for the rest of the U.S. GOSIP NSAP
138 structure, with a hex value of 80. Following this is the three-octet
139 field, values for which are allocated to network operators; the
140 registration authority for this field is delegated to GSA (General
141 Services Administration).
142
143 The last octet of the NSAP is the NSelector (NSel). In practice, the
144 NSAP minus the NSel identifies the CLNP protocol machine on a given
145 system, and the NSel identifies the CLNP user. Since there can be
146 more than one CLNP user (meaning multiple NSel values for a given
147 "base" NSAP), the representation of the NSAP should be CLNP-user
148 independent. To achieve this, an NSel value of zero shall be used
149 with all NSAP values stored in the DNS. An NSAP with NSel=0
150 identifies the network layer itself. It is left to the application
151 retrieving the NSAP to determine the appropriate value to use in that
152 instance of communication.
153
154 When CLNP is used to support TCP and UDP services, the NSel value
155 used is the appropriate IP PROTO value as registered with the IANA.
156 For "standard" OSI, the selection of NSel values is left as a matter
157 of local administration. Administrators of systems that support the
158 OSI transport protocol [<a href="#ref-4" title="Switzerland">4</a>] in addition to TCP/UDP must select NSels
159 for use by OSI Transport that do not conflict with the IP PROTO
160 values.
161
162
163
164 <span class="grey">Manning &amp; Colella [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc1706">RFC 1706</a> DNS NSAP RRs October 1994</span>
167
168
169 |--------------|
170 | &lt;-- IDP --&gt; |
171 |--------------|-------------------------------------|
172 | AFI | IDI | &lt;-- DSP --&gt; |
173 |-----|--------|-------------------------------------|
174 | 47 | 0005 | DFI | AA |Rsvd | RD |Area | ID |Sel |
175 |-----|--------|-----|----|-----|----|-----|----|----|
176 octets | 1 | 2 | 1 | 3 | 2 | 2 | 2 | 6 | 1 |
177 |-----|--------|-----|----|-----|----|-----|----|----|
178
179 IDP Initial Domain Part
180 AFI Authority and Format Identifier
181 IDI Initial Domain Identifier
182 DSP Domain Specific Part
183 DFI DSP Format Identifier
184 AA Administrative Authority
185 Rsvd Reserved
186 RD Routing Domain Identifier
187 Area Area Identifier
188 ID System Identifier
189 SEL NSAP Selector
190
191 Figure 1: GOSIP Version 2 NSAP structure.
192
193
194 In the NSAP RRs in Master Files and in the printed text in this memo,
195 NSAPs are often represented as a string of "."-separated hex values.
196 The values correspond to convenient divisions of the NSAP to make it
197 more readable. For example, the "."-separated fields might correspond
198 to the NSAP fields as defined by the appropriate authority (RARE,
199 U.S. GOSIP, ANSI, etc.). The use of this notation is strictly for
200 readability. The "."s do not appear in DNS packets and DNS servers
201 can ignore them when reading Master Files. For example, a printable
202 representation of the first four fields of a U.S. GOSIP NSAP might
203 look like
204
205 47.0005.80.005a00
206
207 and a full U.S. GOSIP NSAP might appear as
208
209 47.0005.80.005a00.0000.1000.0020.00800a123456.00.
210
211 Other NSAP formats have different lengths and different
212 administratively defined field widths to accomodate different
213 requirements. For more information on NSAP formats in use see <a href="./rfc1629">RFC</a>
214 <a href="./rfc1629">1629</a> [<a href="#ref-1" title="&quot;Guidelines for OSI NSAP Allocation inh the Internet&quot;">1</a>].
215
216
217
218
219
220 <span class="grey">Manning &amp; Colella [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc1706">RFC 1706</a> DNS NSAP RRs October 1994</span>
223
224
225 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. The NSAP RR</span>
226
227 The NSAP RR is defined with mnemonic "NSAP" and TYPE code 22
228 (decimal) and is used to map from domain names to NSAPs. Name-to-NSAP
229 mapping in the DNS using the NSAP RR operates analogously to IP
230 address lookup. A query is generated by the resolver requesting an
231 NSAP RR for a provided domain name.
232
233 NSAP RRs conform to the top level RR format and semantics as defined
234 in <a href="./rfc1035#section-3.2.1">Section&nbsp;3.2.1 of RFC 1035</a>.
235
236 1 1 1 1 1 1
237 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
238 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
239 | |
240 / /
241 / NAME /
242 | |
243 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
244 | TYPE = NSAP |
245 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
246 | CLASS = IN |
247 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
248 | TTL |
249 | |
250 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
251 | RDLENGTH |
252 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
253 / RDATA /
254 / /
255 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
256
257 where:
258
259 * NAME: an owner name, i.e., the name of the node to which this
260 resource record pertains.
261
262 * TYPE: two octets containing the NSAP RR TYPE code of 22 (decimal).
263
264 * CLASS: two octets containing the RR IN CLASS code of 1.
265
266 * TTL: a 32 bit signed integer that specifies the time interval in
267 seconds that the resource record may be cached before the source
268 of the information should again be consulted. Zero values are
269 interpreted to mean that the RR can only be used for the
270 transaction in progress, and should not be cached. For example,
271 SOA records are always distributed with a zero TTL to prohibit
272 caching. Zero values can also be used for extremely volatile data.
273
274
275
276 <span class="grey">Manning &amp; Colella [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc1706">RFC 1706</a> DNS NSAP RRs October 1994</span>
279
280
281 * RDLENGTH: an unsigned 16 bit integer that specifies the length in
282 octets of the RDATA field.
283
284 * RDATA: a variable length string of octets containing the NSAP.
285 The value is the binary encoding of the NSAP as it would appear in
286 the CLNP source or destination address field. A typical example of
287 such an NSAP (in hex) is shown below. For this NSAP, RDLENGTH is
288 20 (decimal); "."s have been omitted to emphasize that they don't
289 appear in the DNS packets.
290
291 39840f80005a0000000001e13708002010726e00
292
293 NSAP RRs cause no additional section processing.
294
295 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. NSAP-to-name Mapping Using the PTR RR</span>
296
297 The PTR RR is defined in <a href="./rfc1035">RFC 1035</a>. This RR is typically used under
298 the "IN-ADDR.ARPA" domain to map from IPv4 addresses to domain names.
299
300 Similarly, the PTR RR is used to map from NSAPs to domain names under
301 the "NSAP.INT" domain. A domain name is generated from the NSAP
302 according to the rules described below. A query is sent by the
303 resolver requesting a PTR RR for the provided domain name.
304
305 A domain name is generated from an NSAP by reversing the hex nibbles
306 of the NSAP, treating each nibble as a separate subdomain, and
307 appending the top-level subdomain name "NSAP.INT" to it. For example,
308 the domain name used in the reverse lookup for the NSAP
309
310 47.0005.80.005a00.0000.0001.e133.ffffff000162.00
311
312 would appear as
313
314 0.0.2.6.1.0.0.0.f.f.f.f.f.f.3.3.1.e.1.0.0.0.0.0.0.0.0.0.a.5.0.0. \
315 0.8.5.0.0.0.7.4.NSAP.INT.
316
317 [Implementation note: For sanity's sake user interfaces should be
318 designed to allow users to enter NSAPs using their natural order,
319 i.e., as they are typically written on paper. Also, arbitrary "."s
320 should be allowed (and ignored) on input.]
321
322 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Master File Format</span>
323
324 The format of NSAP RRs (and NSAP-related PTR RRs) in Master Files
325 conforms to <a href="#section-5">Section 5</a>, "Master Files," of <a href="./rfc1035">RFC 1035</a>. Below are
326 examples of the use of these RRs in Master Files to support name-to-
327 NSAP and NSAP-to-name mapping.
328
329
330
331
332 <span class="grey">Manning &amp; Colella [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc1706">RFC 1706</a> DNS NSAP RRs October 1994</span>
335
336
337 The NSAP RR introduces a new hex string format for the RDATA field.
338 The format is "0x" (i.e., a zero followed by an 'x' character)
339 followed by a variable length string of hex characters (0 to 9, a to
340 f). The hex string is case-insensitive. "."s (i.e., periods) may be
341 inserted in the hex string anywhere after the "0x" for readability.
342 The "."s have no significance other than for readability and are not
343 propagated in the protocol (e.g., queries or zone transfers).
344
345
346 ;;;;;;
347 ;;;;;; Master File for domain nsap.nist.gov.
348 ;;;;;;
349
350
351 @ IN SOA emu.ncsl.nist.gov. root.emu.ncsl.nist.gov. (
352 1994041800 ; Serial - date
353 1800 ; Refresh - 30 minutes
354 300 ; Retry - 5 minutes
355 604800 ; Expire - 7 days
356 3600 ) ; Minimum - 1 hour
357 IN NS emu.ncsl.nist.gov.
358 IN NS tuba.nsap.lanl.gov.
359 ;
360 ;
361 $ORIGIN nsap.nist.gov.
362 ;
363 ; hosts
364 ;
365 bsdi1 IN NSAP 0x47.0005.80.005a00.0000.0001.e133.ffffff000161.00
366 IN A 129.6.224.161
367 IN HINFO PC_486 BSDi1.1
368 ;
369 bsdi2 IN NSAP 0x47.0005.80.005a00.0000.0001.e133.ffffff000162.00
370 IN A 129.6.224.162
371 IN HINFO PC_486 BSDi1.1
372 ;
373 cursive IN NSAP 0x47.0005.80.005a00.0000.0001.e133.ffffff000171.00
374 IN A 129.6.224.171
375 IN HINFO PC_386 DOS_5.0/NCSA_Telnet(TUBA)
376 ;
377 infidel IN NSAP 0x47.0005.80.005a00.0000.0001.e133.ffffff000164.00
378 IN A 129.6.55.164
379 IN HINFO PC/486 BSDi1.0(TUBA)
380 ;
381 ; routers
382 ;
383 cisco1 IN NSAP 0x47.0005.80.005a00.0000.0001.e133.aaaaaa000151.00
384 IN A 129.6.224.151
385
386
387
388 <span class="grey">Manning &amp; Colella [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc1706">RFC 1706</a> DNS NSAP RRs October 1994</span>
391
392
393 IN A 129.6.225.151
394 IN A 129.6.229.151
395 ;
396 3com1 IN NSAP 0x47.0005.80.005a00.0000.0001.e133.aaaaaa000111.00
397 IN A 129.6.224.111
398 IN A 129.6.225.111
399 IN A 129.6.228.111
400
401
402
403
404 ;;;;;;
405 ;;;;;; Master File for reverse mapping of NSAPs under the
406 ;;;;;; NSAP prefix:
407 ;;;;;;
408 ;;;;;; 47.0005.80.005a00.0000.0001.e133
409 ;;;;;;
410
411
412 @ IN SOA emu.ncsl.nist.gov. root.emu.ncsl.nist.gov. (
413 1994041800 ; Serial - date
414 1800 ; Refresh - 30 minutes
415 300 ; Retry - 5 minutes
416 604800 ; Expire - 7 days
417 3600 ) ; Minimum - 1 hour
418 IN NS emu.ncsl.nist.gov.
419 IN NS tuba.nsap.lanl.gov.
420 ;
421 ;
422 $ORIGIN 3.3.1.e.1.0.0.0.0.0.0.0.0.0.a.5.0.0.0.8.5.0.0.0.7.4.NSAP.INT.
423 ;
424 0.0.1.6.1.0.0.0.f.f.f.f.f.f IN PTR bsdi1.nsap.nist.gov.
425 ;
426 0.0.2.6.1.0.0.0.f.f.f.f.f.f IN PTR bsdi2.nsap.nist.gov.
427 ;
428 0.0.1.7.1.0.0.0.f.f.f.f.f.f IN PTR cursive.nsap.nist.gov.
429 ;
430 0.0.4.6.1.0.0.0.f.f.f.f.f.f IN PTR infidel.nsap.nist.gov.
431 ;
432 0.0.1.5.1.0.0.0.a.a.a.a.a.a IN PTR cisco1.nsap.nist.gov.
433 ;
434 0.0.1.1.1.0.0.0.a.a.a.a.a.a IN PTR 3com1.nsap.nist.gov.
435
436 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
437
438 Security issues are not discussed in this memo.
439
440
441
442
443
444 <span class="grey">Manning &amp; Colella [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc1706">RFC 1706</a> DNS NSAP RRs October 1994</span>
447
448
449 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Authors' Addresses</span>
450
451 Bill Manning
452 USC/Information Sciences Institute
453 4676 Admiralty Way
454 Marina del Rey, CA. 90292
455 USA
456
457 Phone: +1.310.822.1511
458 EMail: [email protected]
459
460
461 Richard Colella
462 National Institute of Standards and Technology
463 Technology/B217
464 Gaithersburg, MD 20899
465 USA
466
467 Phone: +1 301-975-3627
468 Fax: +1 301 590-0932
469 EMail: [email protected]
470
471 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
472
473 [<a id="ref-1">1</a>] Colella, R., Gardner, E., Callon, R., and Y. Rekhter, "Guidelines
474 for OSI NSAP Allocation inh the Internet", <a href="./rfc1629">RFC 1629</a>, NIST,
475 Wellfleet, Mitre, T.J. Watson Research Center, IBM Corp., May
476 1994.
477
478 [<a id="ref-2">2</a>] GOSIP Advanced Requirements Group. Government Open Systems
479 Interconnection Profile (GOSIP) Version 2. Federal Information
480 Processing Standard 146-1, U.S. Department of Commerce, National
481 Institute of Standards and Technology, Gaithersburg, MD, April
482 1991.
483
484 [<a id="ref-3">3</a>] ISO/IEC. Data interchange - structures for the identification of
485 organization. International Standard 6523, ISO/IEC JTC 1,
486 Switzerland, 1984.
487
488 [<a id="ref-4">4</a>] ISO/IEC. Connection oriented transport protocol specification.
489 International Standard 8073, ISO/IEC JTC 1, Switzerland, 1986.
490
491 [<a id="ref-5">5</a>] ISO/IEC. Protocol for Providing the Connectionless-mode Network
492 Service. International Standard 8473, ISO/IEC JTC 1,
493 Switzerland, 1986.
494
495
496
497
498
499
500 <span class="grey">Manning &amp; Colella [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc1706">RFC 1706</a> DNS NSAP RRs October 1994</span>
503
504
505 [<a id="ref-6">6</a>] ISO/IEC. Information Processing Systems -- Data Communications --
506 Network Service Definition. International Standard 8348, ISO/IEC
507 JTC 1, Switzerland, 1993.
508
509 [<a id="ref-7">7</a>] Mockapetris, P., "Domain Names -- Concepts and Facilities", STD
510 13, <a href="./rfc1034">RFC 1034</a>, USC/Information Sciences Institute, November 1987.
511
512 [<a id="ref-8">8</a>] Mockapetris, P., "Domain Names -- Implementation and
513 Specification", STD 13, <a href="./rfc1035">RFC 1035</a>, USC/Information Sciences
514 Institute, November 1987.
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556 Manning &amp; Colella [Page 10]
557 </pre>