How CMIP services uses the directory definition file

The directory definition file contains names of other instances of CMIP services and of itself. When searching the directory definition file, CMIP services uses the most specific name it can find in the directory definition file. CMIP services searches the directory definition file for the attribute value for a particular name. Here is an example of a directory definition file, followed by some sample searches. (The line numbers are shown for reference only; they cannot appear in a valid directory definition file.)

 1 class aetitle
 2   name '*'
 3     timeSync 800
 4
 5 class aetitle
 6   name '1.3.18.0.2.4.6=SNANET1'
 7     associationKey 'd6c8f0d3e4F7c5c2'
 8     timeSync 17500
 9
10 class aetitle
11   name '1.3.18.0.2.4.6=SNANET1;2.9.3.2.7.4=(name SECURED)'
12     address USIBMNR.RALVMS
13     associationKey '*'
14
15 class aetitle
16   name '1.3.18.0.2.4.6=SNANET1;2.9.3.2.7.4=(name SECURED);&
17 1.3.18.0.2.4.12=BadSMASE'
18     associationKey '-'

CMIP services searches the directory definition file for a particular attribute for a given full name. Here are some sample searches:

• Search for the associationKey attribute for name

  1.3.18.0.2.4.6=SNANET1;2.9.3.2.7.4=(name SECURED);14 1.3.18.0.2.4.12=BadSMASE'

  In this example, line 18 is used (name matches exactly and associationKey exists for that specific name).
• Search for the associationKey attribute for name

  1.3.18.0.2.4.6=SNANET1;2.9.3.2.7.4=(name SECURED);14 1.3.18.0.2.4.12=OSISMASE'

  In this example, line 13 is used. The exact name is not in the directory definition file, so CMIP services searched for name '1.3.18.0.2.4.6=SNANET1;2.9.3.2.7.4=(name SECURED)' in the directory definition file and found it, and it had an associationKey.
• Search for the associationKey attribute for name

  1.3.18.0.2.4.6=SNANET1;2.9.3.2.7.4=(name UNSECURED);14 1.3.18.0.2.4.12=OSISMASE'

  In this example, line 7 is used. The exact name, and the first 2/3 name are not found, but name '1.3.18.0.2.4.6=SNANET1' is found, and it has an associationKey.
• Search for the associationKey attribute for name

  1.3.18.0.2.4.6=OTHERNET;2.9.3.2.7.4=(name GEORGE);14 1.3.18.0.2.4.12=OSISMASE'

  In this example, name is not found, which is equivalent to associationKey '*' (all associations allowed).
• Search for the timeSync attribute for name

  1.3.18.0.2.4.6=SNANET1;2.9.3.2.7.4=(name SECURED);14 1.3.18.0.2.4.12=OSISMASE'

  In this example, line 8 is used. Note that line 11 matches this name (the first 2/3 of this name, actually), but there is no timeSync for that name. So CMIP services keeps searching, and finds a match for the first 1/3 of the name and it does have a timeSync value.