NSAP
Click on the red underlined text to get to the source
... NSAP) addresses [7] [Note: NSAP and NSAP
address are used interchangeably throughout this memo].
...
... addresses [7] [Note: NSAP and NSAP
address are used interchangeably throughout this memo].
This document defines the format of one new Resource Record ...
... NSAP address format.
NSAP-to-name translation is accomplished through use of the PTR RR
(see RFC 1035std13 ...
... This memo assumes that the reader is familiar with the DNS. Some
familiarity with NSAPs is useful; see [2] or [7] for additional
...
... CLNP ping and traceroute is becoming
more difficult with only numeric NSAPs as the scale of deployment
increases. Current debugging is supported by maintaining and
...
... increases. Current debugging is supported by maintaining and
exchanging a configuration file with name/NSAP mappings similar in
function to hosts.txt. This suffers from the lack of a central
...
...
The methods defined in this paper are applicable to all NSAP formats.
This includes support for the notion of a custom-defined NSAP format
...
... methods defined in this paper are applicable to all NSAP formats.
This includes support for the notion of a custom-defined NSAP format
based on an AFI obtained by the IAB ...
... registration authority and the DNS a publication method. For NSAPs,
addendum two of the network service definition, ISO8348/Ad2 [7 ...
... Structure of NSAPs ...
...
NSAPs are hierarchically structured to allow distributed
administration and efficient routing. Distributed administration
...
... addressing authorities to, as allowed by the
delegator, further structure the portion of the NSAP space under
their delegated control. Accomodating this distributed authority
...
... authority
requires that there be little or no a priori knowledge of the
structure of NSAPs built into DNS resolvers and servers.
...
... DNS resolvers and servers.
For the purposes of this memo, NSAPs can be thought of as a tree of
identifiers ...
... 3], as shown in Figure 1. The field immediately following
0005 is a format identifier for the rest of the U.S. GOSIP NSAP
structure, with a hex value of 80. Following this is the three-octet
field, values for which are allocated to network operators ...
... Services Administration).
The last octet of the NSAP is the NSelector (NSel). In practice, the
NSAP minus the NSel identifies the CLNP ...
... The last octet of the NSAP is the NSelector (NSel). In practice, the
NSAP minus the NSel identifies the CLNP protocol machine on a given
system, and the NSel identifies the CLNP ...
... more than one CLNP user (meaning multiple NSel values for a given
"base" NSAP), the representation of the NSAP should be CLNP-user
...
... CLNP user (meaning multiple NSel values for a given
"base" NSAP), the representation of the NSAP should be CLNP-user
independent. To achieve this, an NSel value of zero shall be used
...
... CLNP-user
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
...
... network layer itself. It is left to the application
retrieving the NSAP to determine the appropriate value to use in that
instance of communication.
...
... NSAP RRs in Master Files and in the printed text in this memo,
NSAPs are often represented as a string of "."-separated hex values.
The values correspond to convenient divisions of the NSAP to make it
...
... NSAPs are often represented as a string of "."-separated hex values.
The values correspond to convenient divisions of the NSAP to make it
more readable. For example, the "."-separated fields might correspond
to the NSAP ...
... NSAP to make it
more readable. For example, the "."-separated fields might correspond
to the NSAP fields as defined by the appropriate authority (ISOC,
...
... 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 might look like
47.0005.80.005a00
...
... 47.0005.80.005a00
and a full U.S. GOSIP NSAP might appear as
47.0005.80.005a00.0000.1000.0020.00800a123456.00.
...
... 47.0005.80.005a00.0000.1000.0020.00800a123456.00.
Other NSAP formats have different lengths and different
administratively defined field widths to accomodate different
requirements ...
... administratively defined field widths to accomodate different
requirements. For more information on NSAP formats in use see RFC
1629draft [2 ...
... NSAP RR is defined with mnemonic "NSAP" and TYPE code 22
(decimal) and is used to map from domain names ...
... TYPE code 22
(decimal) and is used to map from domain names to NSAPs. Name-to-NSAP
mapping in the DNS ...
... (decimal) and is used to map from domain names to NSAPs. Name-to-NSAP
mapping in the DNS using the NSAP ...
... lookup. A query is generated by the resolver requesting an
NSAP RR for a provided domain name.
...
... | |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| TYPE = NSAP |
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| CLASS ...
... resource record pertains.
* TYPE: two octets containing the NSAP RR TYPE code of 22 (decimal).
...
...
* RDATA: a variable length string of octets containing the NSAP.
The value is the binary encoding of the NSAP ...
... NSAP.
The value is the binary encoding of the NSAP as it would appear in
the CLNP source or destination address field ...
... CLNP source or destination address field. A typical example of
such an NSAP (in hex) is shown below. For this NSAP, RDLENGTH is
20 (decimal); "."s have been omitted to emphasize that they don't
...
... destination address field. A typical example of
such an NSAP (in hex) is shown below. For this NSAP, RDLENGTH is
20 (decimal); "."s have been omitted to emphasize that they don't
appear in the DNS packets ...
... For TUBA, identical ASP is required on type NSAP records to support
servers and resolvers that use CLNP, either because of preference or
...
... NS records cause ASP which locates a type
NSAP record in addition to a type A record. Both type A and NSAP
...
... NSAP record in addition to a type A record. Both type A and NSAP
records should be returned, if available.
...
... NSAP.INT" domain. A domain name is generated from the NSAP
according to the rules described below. A query is sent by the
...
...
A domain name is generated from an NSAP by reversing the hex nibbles
of the NSAP, treating each nibble as a separate subdomain, and
...
... domain name is generated from an NSAP by reversing the hex nibbles
of the NSAP, treating each nibble as a separate subdomain, and
appending the top-level subdomain name "NSAP ...
... NSAP, treating each nibble as a separate subdomain, and
appending the top-level subdomain name "NSAP.INT" to it. For example,
the domain name used in the reverse lookup ...
... the domain name used in the reverse lookup for the NSAP
47.0005.80.005a00.0000.0001.e133.ffffff000162.00
...
...
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. \
0.8.5.0.0.0.7.4.NSAP.INT.
[Implementation note: For sanity's sake user interfaces ...
... [Implementation note: For sanity's sake user interfaces should be
designed to allow users to enter NSAPs using their natural order,
i.e., as they are typically written on paper. Also, arbitrary "."s
should be allowed (and ignored) on input.]
...
... The format of NSAP RRs (and NSAP-related PTR RRs) in Master Files
conforms to Section 5, "Master Files," of RFC 1035std13 ...
... examples of the use of these RRs in Master Files to support name-to-
NSAP and NSAP-to-name mapping.
...
... ;
$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.
;
0.0.1.6.1.0.0.0.f.f.f.f.f.f IN ...
... Colella, R., Gardner, E., Callon, R., and Y. Rekhter, "Guidelines for OSI NSAP Allocation inh the Internet", RFC 1629draft, NIST ...