Conference azur::mcc

381.0. "EASYNET DIRECTION ON NAMING OF MCC MANAGED OBJECTS" by RELEE::KILLIAN () Thu Oct 04 1990 18:00

		EASYNET NAMING OF MCC MANAGED OBJECTS

							EASYnet Geographies
							Tools Group
							9/07/90



GENERAL

	MCC will be used to manage many different classes of device. These
include NODES, ROUTERS, BRIDGES, STATIONS, TERMINAL SERVERS and more. 
MCC cannot manage a class of device until each device has an associated object
in the EASYnet DNS (Distributed Name Service) namespace. MCC is only one of many
users of the EASYnet DNS namespace. Because of the diversity and volume of 
objects that will be placed in the EASYnet DNS namespace; careful thought 
should be given to the naming of these objects. 

AUDIENCE

	This memo is directed to site based MCC operations groups.

SCOPE

	This memo discusses naming of MCC managed objects only. Specific
direction is given for BRIDGE objects, which should also be applied to all site
based MCC managed devices(except NODES and ROUTERS).

MCC AND EASYNET DNS NAMESPACE

	Site based MCC operations groups will REGISTER objects with MCC, to make
objects visible to MCC. As part of this REGISTER operation MCC will add the 
objects into the EASYnet DNS namespace.
	Two classes of objects are predefined and already exist in the EASYnet 
DNS namespace, NODES and ROUTERS. Site based MCC operations must REGISTER NODES
and ROUTERS with MCC, to make these objects visible to MCC. When doing so, the
name of the NODE/ROUTER used must be exactly as it appears in the EASYnet DNS
namespace !

EASYNET NAMING STANDARD

	The DNS MC (Management Committee) which is responsible for EASYnet
naming policy, have developed a standard for naming of NODE and ROUTER objects 
in the EASYnet DNS namespace. This document is available at	
"IAMOK::DNS_PROGRAM:NAMESPACE_STANDARD.LIS".

	The namespace standard specifies a site bases NODE/ROUTER naming scheme.
For example:
		Current name	Location	EASYnet DNS namespace name

		TOOK		LKG		DEC:.LKG.TOOK
		STAR		ZKO		DEC:.ZKO.STAR
		DISSRV		VRO		DEC:.VRO.DISSRV

MCC MANAGED OBJECTS NAMING RECOMMENDATION

	The above site based naming scheme could easily be applied to BRIDGE
objects and other MCC managed objects. However, due to the importance of 
NODE/ROUTER objects in the functioning of EASYnet there is a restriction on
what objects can be placed in the <site> directory (NODE/ROUTER objects in
the EASYnet DNS namespace are needed for connection establishment). The EASYnet
naming standard allows only three object classes to exist in the <site>
directory; NODE, ROUTER and SUBSCRIBER NAME. All other site based objects must
be placed deeper in the namespace.

	The namespace standard recommends that all other site based objects be
placed in the subdirectory "S" of the site directory. 

For example : 	Bridge	21LABLAT_A	   becomes	DEC:.LKG.S.21LABLAT_A
	
		Bridge  BS11FDDI	   becomes	DEC:.LKG.S.BS11FDDI


	The Geographies Tools Group recommends that all MCC managed objects
(except NODES and ROUTERS) be placed in the subdirectory "S" of the site 
directory. E.g DEC:.LKG.S.BS11FDDI . 

QUESTIONS/ANSWERS

Q	Explain EASYnet DNS namespace access control as it applies to MCC and 
	the objects it manages.
	
A	MCC managed objects are located in the <site> directory and the
	<site>.S directory of the EASYnet DNS namespace. The granularity of
	MCC partitioned access is by site ! The DNS access control group 
	DEC:.<site>.NODE_ADMIN has the necessary access for the MCC operations
	at a particular site (<site>).
	One or more account (from where MCC is executed) is included in this
	group.
	A single MCC operations group can control MCC for more than one site
	by placing the same account(s) in the respective DEC:.<site>.NODE_ADMIN
	groups of each site ( eg DEC:.VRO.NODE_ADMIN & DEC:.CFO.NODE_ADMIN ).

	More information on EASYnet DNS nodename access control can be found
	in "DEC: Namespace Security Standard" document located at
	"IAMOK::DNS_PROGRAM:DEC_NAMESPACE_SECURITY.PS".

Q	I want to put BRIDGES and other MCC managed objects in the following
	directory :	DEC:.<site>.S.MCC.<bridge>

A	You have made a subdirectory assignment based on partitioning all MCC
	managed objects into this directory. NODE and ROUTER objects will 
	never be moved from the site directory (DEC:.<site>)! Thus the 
	MCC subdirectory does NOT partition MCC managed objects. The MCC
	subdirectory only confuses things. 

    Q:	Why should nodes, routers and people be the only things in the site
    directories? This is stated but not justified. It's not clear that it
    makes sense to have nodes, routers and people in .LKG, but bridges
    terminal servers and modems in .LKG.S
    Also, where would conferences and DFS access points go?
    
    Colin

    What's the difference between "nodes" and "routers"? Arn't they both
    ususally NODE4 entities?
    
    s/rob

    Rob,
    
    You can ask this Of Jim Carey, but if I understand you what your
    asking has to do with variants. A phase4 node can operate as either
    an end node or a routing node. In the 1.1 updates we will start
    the introduction of variant support form the iconic map. I do not
    have the details regarding what the dna4 teams is doing in this
    space, if this is what your looking for please post an additional
    request for the data and I will see what I can do about getting
    it for you.
    
    jill