Conference azur::mcc

3601.0. "private vs dec: namespace" by ROYALS::D_BEAUREGARD (Freewheeler) Fri Aug 21 1992 09:48

I am implementing DECmcc for internal use and would like to know if other 
internal sites are using a private namespace or the DEC: namespace. It appears
from a note in the DNS_PROGRAM notesfile that their are problems using the 
DEC: namespace with mcc v1.1 that were to be fixed in v1.2. Has this all been
resolved?


						Doug



Note 192.1                   DECmcc & namespace DEC:                      1 of 4
GVA01::BUCLIN "Bertrand Buclin @ GEO | DTN: 821-495" 36 lines  30-SEP-1991 09:32
                    -< You'd better run your own namespace >-

>               We are working in the implementation of DECmcc for internal
>       use and we want to use DEC: namespace, but before to put hands on
>       we would like to know if there are restrictions, guidelines ,
>       recomendations... about this, can you give me any pointer. Thanks in
>       advance.

There is no official European policy regarding the use of DEC: namespace with
DECmcc. However, here is the current situation (and the constraints
derivating from it) :

- DECmcc V1.1 requires write access to the root nameserver (to create
  for example backtranslation directories for managed entities). Current
  operating rules of DEC: namespace won't allow you to have write access
  on the root.

- A couple of backtranslation directories already exists. You will need to
  share them with other sites willing also to use DECmcc along with the
  DEC: namespace. Setting up the access control lists for these directories
  is not an easy task ... DECmcc V1.2 will remove this need of root level
  directories, so you'd better wait for it.

- You will have only read access to the node objects. DECmcc requires to
  have DELETE access to fully manage a node. This function will not be granted
  to you.

I would encourage you to set up your DECmcc in a separate private namespace
that you can totally control (as do most of the MCC users).

Maybe some guideline will be issued when DECmcc V1.2 will be out.
 

   

    We are using DECmcc T1.2.7 with the MCC_KERNEL_SHR.EXE from X1.2.15
    (a logical name points to it) in the DEC: DNS namespace.
    This conforms to the Digital namespace security guidelines - you 
    can manage your own nodes (that were put into DECdns by the authorities)
    and can register objects in your own sub-directory with the privs that
    they are willing to give you. V1.2 should work as well, I'll be
    installing it shortly.
    
    You will find the DEC: namespace slow and unreliable.  Also, if you are
    using the common agent (aka VMS/DMS, etc.) to manage your own entities,
    they will be CMIP speaking children of the NODE entity. You will
    discover that you can't have a NODE and a NODE4 with the same name
    registered in DECmcc at the same time (because they share DNS
    back-links)  So you can't do, for example
    
    MCC> show node mynode myentity characteristics
    if mynode is already registered as a phase4 node in DECmcc

RE:
>>    MCC> show node mynode myentity characteristics
>>    if mynode is already registered as a phase4 node in DECmcc

Not true!  From FCL you can do that just fine...  FCL does not really care
about the node being registered at all.  You cannot do the same function
from the iconic interfacem however, as it does require that the system
be registered as a phase 5 node.