Installing and Administering OSI Transport Services

Chapter 2 79
Planning Your Network
Determine the Network Structure
After you have done the partition into domains and areas, you can then
assign an appropriate network address prefix for each node, and the full
address can be completed by using each node’s End System address.
Application Addresses
You may also want to dictate the selector values to be used for the upper
layer addresses. (Note that HP OSI services use default addresses. For
instance, FTAM uses 0x0001 (hex) for P-, S-, and T- selectors. X.400 uses
blank (null) P- and S- selectors and 4D4853 (hex) as the T-selector. Refer
to the appropriate product manuals to see what, if any, default addresses
are used.)
If you wish to change the default addresses, you might assign all FTAM
responders to have the P-, S- and T-selectors of 0x0010. For an XTI
application you are developing, you may want all initiators to use
T-selectors 0x0020 and all responders to use T-selectors of 0x0021.
You have a wide array of addresses to choose from. The selectors may fall
in the following range:
P-selector: 0 to 16 bytes
S-selector: 0 to 16 bytes
T-selector: 0 to 32 bytes
Remember that the longer or more complicated you make your selector
values, the more room you leave for error during configuration.
NOTE Some government profiles may dictate the selector values for certain
services (for example, U.S. GOSIP for FTAM and X.400).
Naming Hierarchies
If you are using FTAM o r X.500, you will use Directory Distinguished
Names (DDNs) in some capacity. These are hierarchical names, for
example, “/C=us/O=hp/OU=hpnode1/AP=mms/AE=demo_prog”.
At this time, you should define what components of the naming
hierarchy you plan to use and define conventions for assigning values to
each component.