Browse Prior Art Database

Technique for Naming Resources that Span Network Name Spaces

IP.com Disclosure Number: IPCOM000111928D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 81K

Publishing Venue

IBM

Related People

Allen, MO: AUTHOR [+5]

Abstract

Disclosed is a method for naming OSI-managed objects representing network resources when the resources span network name spaces.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Technique for Naming Resources that Span Network Name Spaces

      Disclosed is a method for naming OSI-managed objects
representing network resources when the resources span network name
spaces.

      SNA resources such as control points and logical units are
members of an SNA subnetwork identified by a network identifier or
netID.  The complete SNA network consists of any number of
interconnected netid subnetworks.  The connections between these SNA
resources may span networks, however, so they cannot obviously be
named in either subnetwork.  SNA avoids this difficulty by simply
establishing some relative name for the connection that is meaningful
to the partners participating in the connection, but which would not
be meaningful outside that context.  For example, a transmission
group (a path control level connection) is established between two
nodes participating in an Advanced Peer to Peer Networking (APPN*)
network.  When the transmission group connection is established, the
two nodes agree to refer to the connection via a simple number.
Thus, if the number for a given TG between NET1.NODE1 and NET2.NODE2
is 7, at NET1.NODE1 the TG will be referred to as TG 7 to NET2.NODE2;
at NET2.NODE2, the same TG will be referred to as TG 7 to NET1.NODE1.
Refer to Fig. 1 for an illustration of this naming concept.

      Since SNA does not provide an unambiguous name for the TG
resource, the construction of a distinguished name for an OSI managed
object representing the TG resource is not obvious.  The TG resource
is place-indendent, that is, it exists in both the NET1 and the NET2
subnetworks, so even the network name of the managed object was not
obvious.

      The solution is an algorithm that can be applied at either end
of a connectio...