7
Network Working Group B. Manning
8
Request for Comments: 1348 Rice University
9
Updates: RFCs 1034, 1035 July 1992
16
This memo defines an Experimental Protocol for the Internet
17
community. Discussion and suggestions for improvement are requested.
18
Please refer to the current edition of the "IAB Official Protocol
19
Standards" for the standardization state and status of this protocol.
20
Distribution of this memo is unlimited.
24
Introduction ..................................................... 1
25
Background ....................................................... 1
26
NSAP RR .......................................................... 2
27
NSAP-PTR RR ...................................................... 2
28
REFERENCES and BIBLIOGRAPHY ...................................... 3
29
Security Considerations .......................................... 4
30
Author's Address ................................................. 4
34
This RFC defines the format of two new Resource Records (RRs) for the
35
Domain Name System (DNS), and reserves corresponding DNS type
36
mnemonic and numerical codes. This format may be used with the any
37
proposal that has variable length addresses, but is targeted for CLNP
40
This memo assumes that the reader is familiar with the DNS [3,4].
44
This section describes an experimental representation of NSAP
45
addresses in the DNS. There are several reasons to take this approch.
46
First, it provides simple documentation of the correct addresses to
47
use in static configurations of CLNP compliant hosts and routers.
49
NSAP support requires that a new DNS resource record entry type
50
("NSAP") be defined, to store longer Internet (i.e., NSAP) addresses.
51
This resource record allows mapping from DNS names to NSAP addresses,
52
and will contain entries for systems which are able to run Internet
53
applications, over TCP or UDP, over CLNP.
60
RFC 1348 DNS NSAP RRs July 1992
63
The backward translation (from NSAP address to DNS name) is
64
facilitated by definition of an associated resource record. This
65
resource record is known as "NSAP-PTR", and is used in a manner
66
analogous to the existing "in-addr.arpa".
68
These RRs are intended for use in a proposal [6] by one of the
69
members of the NOOP WG to address the next-generation internet.
73
The NSAP RR is defined with mnemonic NSAP and type code 22 (decimal).
75
An NSAP (Network Service Access Protocol) number is a unique string
76
to OSI transport service.
78
The numbering plan follows RFC 1237 and associated OSI definitions
81
NSAP has the following format:
83
<owner> <ttl> <class> NSAP <length> <NSAP-address>
85
All fields are required.
87
<length> identifies the number of octets in the <NSAP-address> as
88
defined by the various national and international authorities.
90
<NSAP-address> enumerates the actual octet values assigned by the
91
assigning authority. Its format in master files is a <character-
92
string> syntactically identical to that used in TXT and HINFO.
94
The format of NSAP is class insensitive. NSAP RR causes no
95
additional section processing.
99
foo.bar.com. IN NSAP 21 47000580ffff000000321099991111222233334444
100
host.school.de IN NSAP 17 39276f3100111100002222333344449876
102
The RR data is the ASCII representation of the digits. It is encoded
103
as two <character-strings>, i.e., count followed by characters.
107
The NSAP-PTR RR is defined with mnemonic NSAP-PTR and a type code 23
110
Its function is analogous to the PTR record used for IP addresses
116
RFC 1348 DNS NSAP RRs July 1992
121
NSAP-PTR has the following format:
123
<NSAP-suffix> <ttl> <class> NSAP-PTR <owner>
125
All fields are required.
127
<NSAP-suffix> enumerates the actual octet values assigned by the
128
assigning authority for the LOCAL network. Its format in master
129
files is a <character-string> syntactically identical to that used in
132
The format of NSAP-PTR is class insensitive. NSAP-PTR RR causes no
133
additional section processing.
137
In net ff08000574.nsap-in-addr.arpa:
139
444433332222111199990123000000ff NSAP-PTR foo.bar.com.
141
Or in net 11110031f67293.nsap-in-addr.arpa:
143
67894444333322220000 NSAP-PTR host.school.de.
145
The RR data is the ASCII representation of the digits. It is encoded
146
as a <character-string>.
148
REFERENCES and BIBLIOGRAPHY
150
[1] Stahl, M., "Domain Administrators Guide", RFC 1032, Network
151
Information Center, SRI International, November 1987.
153
[2] Lottor, M., "Domain Administrators Operations Guide", RFC 1033,
154
Network Information Center, SRI International, November, 1987.
156
[3] Mockapetris, P., "Domain Names - Concepts and Facilities", RFC
157
1034, USC/Information Sciences Institute, November 1987.
159
[4] Mockapetris, P., "Domain Names - Implementation and
160
Specification", RFC 1035, USC/Information Sciences Institute,
163
[5] Colella, R., Gardner, E., and R. Callon, "Guidelines for OSI
164
NSAP Allocation in the Internet", RFC 1237, NIST, Mitre, DEC,
172
RFC 1348 DNS NSAP RRs July 1992
175
[6] Callon, R., "TCP and UDP with Bigger Addresses (TUBA),
176
A Simple Proposal for Internet Addressing and Routing",
177
Digital Equipment Corporation, RFC 1347, June 1992.
179
[7] Mockapetris, P., "DNS Encoding of Network Names and Other Types",
180
RFC 1101, USC/Information Sciences Institute, April 1989.
182
[8] ISO/IEC. Information Processing Systems -- Data Communications
183
-- Network Service Definition Addendum 2: Network Layer Address-
184
ing. International Standard 8348/Addendum 2, ISO/IEC JTC 1,
187
[9] Bryant, P., "NSAPs", PB660, IPTAG/92/23, SCIENCE AND ENGINEERING
188
RESEARCH COUNCIL, RUTHERFORD APPLETON LABORATORY May 1992.
190
Security Considerations
192
Security issues are not addressed in this memo.
197
Rice University - ONCS
200
Houston, Texas 77251-1892
202
Phone: +1.713.285.5415
203
EMail: bmanning@rice.edu
b'\\ No newline at end of file'