RFC 1637:DNS NSAP Resource Records
RFC-Ref

CLNP


Click on the red underlined text to get to the source

... infrastructure. This infrastructure comprises the connectionless network protocol (CLNP) [6] and supporting routing protocols. Also ...


... The reason for defining DNS mappings for NSAPs is to support CLNP in the Internet. Debugging with CLNP ...
... CLNP in the Internet. Debugging with CLNP ping and traceroute is becoming more difficult with only numeric NSAPs ...
... difficiencies. A second reason for this work is the proposal to use CLNP as an alternative to IP: "TCP ...
... 1]. For this to be practical, the DNS must be capable of supporting CLNP addresses. ...


... 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 user. Since there can be ...
... NSAP minus the NSel identifies the CLNP protocol machine on a given system, and the NSel identifies the CLNP user. Since there can be more than one CLNP user (meaning multiple NSel values for a given ...
... system, and the NSel identifies the CLNP user. Since there can be more than one CLNP user (meaning multiple NSel values for a given "base" NSAP), the representation of the NSAP ...
... "base" NSAP), the representation of the NSAP should be CLNP-user independent. To achieve this, an NSel value of zero shall be used with all NSAP ...
... NSAP structure. When CLNP is used to support TCP and UDP services ...


... binary encoding of the NSAP as it would appear in the CLNP source or destination address field. A typical example of such an NSAP ...
... ASP is required on type NSAP records to support servers and resolvers that use CLNP, either because of preference or because it is the only internetworking protocol available (i.e., in the absense of IPv4 ...



Google
Web
RFC-Ref