RFC 1637:DNS NSAP Resource Records
RFC-Ref

DNS


Click on the red underlined text to get to the source

... routing protocols. Also required as part of this infrastructure is support in the Domain Name System (DNS) [8] [9] for mapping between domain names ...
... Resource Record (RR) for the DNS for domain name-to-NSAP mapping. The RR ...
... RRs are used to support this translation. This memo assumes that the reader is familiar with the DNS. Some familiarity with NSAPs is useful; see [2 ...


... The reason for defining DNS mappings for NSAPs is to support CLNP in ...
... Routing" [1]. For this to be practical, the DNS must be capable of supporting CLNP addresses. ...


... registration authority and the DNS a publication method. For NSAPs, ...
... the root registration authority and this memo defines how the DNS is used as a publication method. ...


... requires that there be little or no a priori knowledge of the structure of NSAPs built into DNS resolvers and servers. For the purposes of this memo, NSAPs ...
... independent. To achieve this, an NSel value of zero shall be used with all NSAP values stored in the DNS. An NSAP with NSel=0 identifies the network ...
... RARE, U.S. GOSIP, ANSI, etc.). The use of this notation is strictly for readability. The "."s do not appear in DNS packets and DNS servers can ignore them when reading Master Files. For example, a printable representation of the first four fields of a U.S. GOSIP ...
... ANSI, etc.). The use of this notation is strictly for readability. The "."s do not appear in DNS packets and DNS servers can ignore them when reading Master Files. For example, a printable representation of the first four fields of a U.S. GOSIP NSAP ...


... NSAPs. Name-to-NSAP mapping in the DNS using the NSAP RR operates analogously to IP address ...
... NSAP, RDLENGTH is 20 (decimal); "."s have been omitted to emphasize that they don't appear in the DNS packets. 39840f80005a0000000001e13708002010726e00 ...



Google
Web
RFC-Ref