Organization: NAVCOMTELSTA WASHINGTON DC (N91)
NAVY REQUIREMENTS IMPLEMENTATION MANUAL (RIM) DOCUMENTS
FORWARD (5/93)
ATTACHED ARE THE NAVY RIM DOCUMENT AND ASSOCIATED REGISTRATION
TEMPLATES. THE RIM SETS FORTH PROCEDURES ON HOW TO REGISTER DATA
REQUIREMENTS TO CONNECT TO THE DOD DEFENSE DATA NETWORK (DDN)
COMPRISED OF THE UNCLASSIFIED MILITARY NETWORK (MILNET) AND THE
DEFENSE SECURE NETWORKS (DSNET1, 2, AND 3).
THE DDN IS ONE OF NINE TIER 1 NETWORKS, IDENTIFIED AS A RESULT OF
DEFENSE MEMORANDUM REVIEW DECISION (DMRD) 968, TRANSITIONING TO
THE DEFENSE INFORMATION SYSTEM NETWORK (DISN).
AS A RESULT, DDN IS BEING DISMANTLED AND SUBSCRIBER REQUIREMENTS
WILL BE TRANSITIONED TO DISN INTERNET PROTOCOL ROUTERS.
FORMALIZED TRANSITION PLANS AND PROCEDURES HAVE NOT BEEN
PROMULGATED, AND UNTIL THEY ARE, NAVY RIM PROCEDURES WILL
CONTINUE TO BE USED TO TRACK SYSTEM, HOST AND TERMINAL
REQUIREMENTS.
THE FOLLOWING DOCUMENTS FOLLOW:
A. NAVY REQUIREMENTS IMPLEMENTATION MANUAL (RIM)
B. ADMINISTRATIVE (SYSTEM) POINT OF CONTACT TEMPLATE
C. SYSTEM QUESTIONNAIRE TEMPLATE
D. CONNECTION QUESTIONNAIRE AND POC TEMPLATES
E. HOST QUESTIONNAIRE TEMPLATE
F. TERMINAL QUESTIONNAIRE TEMPLATE
SUBSCRIBER REQUIREMENTS ON DDN AND DISN ARE BILLED TO THE SYSTEM,
HOST OR TERMINAL. THEREFORE, IT IS ADVISED THAT USERS SHOULD
CONTACT THEIR SYSTEM ADMINISTRATOR OR MAJOR CLAIMANT COMPTROLLER
TO ASCERTAIN FUNDING APPROVAL OF THEIR REQUIREMENTS AND USE OF
THE PROPER PROGRAM DESIGNATOR CODES TO BE USED.
NAVY REQUIREMENTS IMPLEMENTATION MANUAL (RIM)
SECTION A.1 SYSTEM QUESTIONNAIRE - S-1 FORM
A.1.1 PURPOSE. The two major purposes of this form are to
register a subscriber system in the Information Data Services -
Management Information System (IDS-MIS) and to provide a user
major command administrative or managerial POC for the subscriber
system being registered.
A.1.2 DEFINITION OF A SUBSCRIBER SYSTEM. As stated in Section
1.1, for purposes of this document, ADP subscriber systems and
data networks will be termed subscriber systems. A subscriber system
is a collection or community of hosts and/or terminals that
communicate based on some common activity or a group of hosts and
terminals that is used for a specific user-designated
application.
A.1.3 STATEMENT OF REQUIREMENT. Each subscriber system that is
added to the DDN must have a completed S-1 FORM filed for entry
of the data into the online IDS-MIS. This form usually is completed
at the user major command level. However, if it is not completed
at that level it must be forwarded to the user major command by
the person completing the form for review prior to being passed to
COMNAVCOMTELCOM N62. This form must be submitted prior to or at
the time of the initial registration of the first host for that
system. In order to maintain a current IDS-MIS, a subscriber or
POC must submit a revised S-1 FORM whenever there is a data item
change.
A.1.4 S-1 FORM. Figure A-1 is a blank S-1 FORM. Each of the
items on the form are numbered; e.g., (1). The descriptions,
definitions and actual lengths of these numbered items are
located in SECTION A.4, DEFINITION OF TERMS.
SECTION A.2 HOST QUESTIONNAIRE - H-1 FORM
A.2.1 PURPOSE. This form has two major purposes. The first
purpose is to provide information about the host and its
location, and the second is to provide an administrative or managerial POC
for that host.
A.2.2 STATEMENT OF REQUIREMENT. Each host that is added to the
DDN must have a completed H-1 FORM filed for entry of the data
into the online IDS-MIS. The H-1 FORM is originated at the user
level, processed through the chain of command to the user major command
level and then passed to COMNAVCOMTELCOM N62. COMNAVCOMTELCOM
N62 reviews the submission, updates the IDS-MIS and provides feedback
confirmation. The H-1 FORM is composed of four subsections, the
Host Site Information, the Host Information, the Host
Administrative POC Information and the Connection Requirement
Information. If any of the information pertaining to the host
changes prior to the Navy activity issuance of a Feeder TSR, the
changed information must be submitted to COMNAVCOMTELCOM N62.
Please complete the entire form when submitting a revision. Once
a TSR is issued by NAVTCO, COMNAVCOMTELCOM N62 is limited in the
fields that it can change in the IDS-MIS. The fields that it
cannot change MUST be changed through an Amended Feeder TSR. A
current list of the TSR sensitive fields is available from the
COMNAVCOMTELCOM N62 DDN personnel.
A.2.3 DEFINITION OF A HOST COMPUTER.
a. In the context of the DDN, a host computer is a
communications device or collection of devices that has
sufficient intelligence to execute the network protocols required to
directly connect to a DDN packet switch and that can properly execute an
"open connection" from the network, thus forming an active
useable connection.
b. For DDN planning purposes, a host must be viewed as
hardware, rather than applications software that may execute on
or be supported by that hardware. Therefore, host information is
to be collected on a hardware basis, not on an application
software basis.
c. A host may be: a single Central Processing Unit (CPU); a
CPU with its supporting front-end processor(s); multiple CPUs
sharing a front-end processor; a local area network (LAN) within
which the LAN serves as the long-haul communications gateway for
all devices attached to it; an intelligent terminal concentrator;
or a Packet Assembler/Disassembler (PAD).
d. A single-host is a device or collection of collocated
devices which share the same long-haul communications interface.
A.2.4 COLLOCATED HOST COMPUTERS.
a. At many sites, there exist multiple collocated computers.
In some cases, these computers will constitute a single host,
requiring only the completion of a single H-1 FORM. In other
cases, these computers will constitute multiple hosts, requiring
the completion of a separate H-1 FORM for each host.
b. If multiple collocated computers are already sharing or
will share a common long-haul communications interface device,
they should be considered a single host (requiring the completion of a
single H-1 FORM).
c. If multiple collocated computers do not or will not share
a common long-haul communications interface, they should be
considered to be separate hosts (requiring the completion of an
H-1 FORM for each host). If there is any doubt concerning this area,
contact COMNAVCOMTELCOM N62 for clarification.
d. EXAMPLES. The following examples should help clarify the
distinction between single and multiple hosts at sites with
multiple collocated host computers.
1. At a World Wide Military Command Control System
(WWMCCS) site, collocated Honeywell 6000 and/or DPS-8 mainframes and
Honeywell Level 6 minicomputers may both access the DDN through a
single Datanet 6000 front-end processor (just as they currently
access the WWMCCS Intercomputer Network). Because a single
interface from the Datanet to the DDN will serve both the
Honeywell 6000 and Level 6 computers, those computers and the Datanet
front-end constitute a single host. In other words, it is the
Datanet 6000, not the backside computers, that is registered in
the IDS-MIS.
2. In contrast, at a Navy Computer and Telecommunications
Center (NCTS) site a collection of heterogeneous mainframe
computers (i.e. IBM, UNISYS and Honeywell) are physically
collocated. Because of incompatibilities between these machines
from different vendors, it is not likely that these processors
will be able to share long-haul communications interfaces or access
lines. Thus, each processor and any associated front-end should
be considered a separate DDN host (requiring the completion of an
H-1 FORM).
3. As another example, consider a site with three
collocated IBM mainframe processors. If each of these machines
is configured using Systems Network Architecture (SNA) software, so
that all machines are interconnected and share the same long-haul
communications interface, then they will likely share a common
DDN network interface. These machines would then be considered to
constitute a single DDN host. If, however, each of these
machines uses less sophisticated networking software such that each
requires its own dedicated interface, they would be considered to be three
separate DDN hosts.
A.2.5 PACKET ASSEMBLER/DISASSEMBLER (PAD).
a. When a full-service host interface is not available,
synchronous terminals can use commercial X.25 PADs to communicate
with compatible X.25 hosts across the DDN.
b. The PAD is a device designed to provide access to public
data networks. PADs perform functions similar to those of a
terminal access controller (TAC) or mini-TAC by providing a user
interface, packetizing data, and concentrating terminals.
However, the user must understand that the PADs do not support the DDN
protocols above the X.25 network layer. This means that
electronic mail and file transfer are not supported. A PAD-implemented X.25
STANDARD protocol, defined by the CCITT X.3 Recommendation,
communicates with synchronous terminals according to the CCITT
X.28 Recommendation and with hosts according to the CCITT X.29
Recommendation. The PAD takes inputs from attached synchronous
terminals, forms them into X.25 packets, and transmits the
packets across the DDN to a remote host.
A.2.6 GATEWAY ACCESS. A "gateway" manages the communications
link between the DDN on one side and a local area network (LAN)
or a non-DDN network on the other side. A "gateway" allows multiple
host computers or terminals, which communicate with one another,
to communicate over the DDN using one communications link. A
"gateway" is considered for DDN purposes as a host, and is to be
registered in the IDS-MIS as one.
A.2.7 H-1 FORM. Figure A-2 is a blank H-1 FORM. Each of the
items on the form are numbered, i.e. '(1)'. The descriptions,
definitions and actual lengths of these numbered items are
located in SECTION A.4.
NOTE - The information listed under HOST SITE INFORMATION
pertains to the physical location of the equipment, not the postal
address, and must therefore be accurate.
SECTION A.3 TERMINAL QUESTIONNAIRE - T-1 FORM
A.3.1 PURPOSE. The major purpose of this form is to register a
direct-connect terminal to the DDN in the IDS-MIS. Do NOT
register dial-in terminals, terminals that will access the DDN through a
connection to a host or terminals that connect to a LAN.
A.3.2 STATEMENT OF REQUIREMENT. Each direct-connect terminal
that is added to the DDN must have a completed T-1 FORM filed for
entry of the data into the IDS-MIS. The T-1 FORM is originated
at the user level, processed through the chain of command to the
user major command level and then passed to COMNAVCOMTELCOM N62.
COMNAVCOMTELCOM N62 reviews the IDS-MIS submission, updates the
online database and provides feedback confirmation, in the form
of a letter and printout of the records. The T-1 FORM is composed of
four subsections, the Terminal Site Information, the Terminal
Information, the Terminal POC Information and the Connection
Requirement Information. If any of the information on the T-1
FORM changes prior to the Navy activity issuance of a Feeder TSR,
these changes must be submitted to COMNAVCOMTELCOM N62. Please
complete the entire form when submitting a revision. Once a TSR is
issued by NAVTCO, COMNAVCOMTELCOM N62 is limited in the fields that it
can change in the IDS-MIS.
The fields that it cannot change MUST be changed through an
Amended Feeder TSR. A current list of the fields which can and cannot
be changed is available from the COMNAVCOMTELCOM N62 DDN personnel.
A.3.3 TERMINAL DISCUSSION. The information provided on this
form should reflect the current configuration except where future
changes to the system have received procurement authority and
funding has been approved. Complete a T-1 FORM for each
direct-connect terminal that is to access the DDN, that is,
terminals which will be attached to the network via a
DDN-provided TAC or mini-TAC. A terminal that requires a dedicated "long
distance" link to access a host system (i.e., distances outside
of a host's local metropolitan calling area) is a candidate for
direct connection to the DDN and, therefore, requires the submission of
completed T-1 FORM.
A.3.4 TERMINAL CLUSTER CONTROLLERS. Some types of terminal
systems have a physically separate terminal cluster controller
which handles all communications for the system. For purposes of
this questionnaire, only the terminal cluster controller needs to
be listed on a T-1 FORM rather than those individual devices to
which it provides communications. It is expected that terminal
cluster data will only pertain to existing systems rather than
new systems being procured and/or implemented. Project Managers and
system designers should discuss plans to employ terminal cluster
controllers or similar equipment with their appropriate
service/agency DDN contact to insure compatibility and compliance
with DDN interface and protocol requirements.
A.3.5 T-1 FORM. Figure A-5 is a blank T-1 FORM. Each item on
the forms are numbered, i.e. '(1)'. The descriptions,
definitions and actual lengths of these numbered items are located in SECTION
A.4.
NOTE - The information listed under TERMINAL SITE INFORMATION
pertains to the physical location of the equipment, not the
postal address. This must be accurate.
SECTION A.4 DEFINITION OF TERMS.
A.4.1 PURPOSE - The items listed below correspond to the
numbered items on the three forms, S-1 FORM, H-1 FORM and T-1
FORM.
A.4.2 ITEMS.
1. DATE: This is an 8-character field containing the completion
date of the forms. The format is month, day and year. A slash,
"/", must separate the month from the day and the day from the
year.
2. FORM ACTION: This field indicates whether the form is a new
addition to the IDS-MIS (ADD), a change to an existing IDS-MIS
entry (CHANGE), or a deletion of an existing IDS-MIS entry
(DELETE). It is important to complete each item on the form,
this is true even for deletions or changes. It is requested that the
reason for the deletion be noted when submitting a form as a
DELETE. Place an "X" in the applicable area.
3. SYSTEM ACRONYM: This is a 20-character field containing the
abbreviated form of the full name of the subscriber system that
will run on the DDN. The acronym usually is derived from the
initial letters of a name or by combining initial letters or
parts of a series of words. The spelling of the SYSTEM ACRONYM is
important since this will be the name that is used on future
IDS-MIS forms and the Feeder Telecommunication Service Requests.
4. SYSTEM NAME: The field is 80 characters in length. It
contains the full name of the subscriber system acronym that is
listed above in Item #3 (SYSTEM ACRONYM).
5. NETWORK NAME: This six-character field defines the primary
DDN subnetwork upon which this subscriber system or connection will
operate. This field must be consistent with the SECURITY
CLASSIFICATION field, Item #7. The subnetwork entries are:
MILNET - Serves unclassified systems.
DSNET1 - Serves single-level classified systems
operating at the Secret security level.
This was formerly called DISNET.
DSNET2 - Serves single-level classified systems
operating at the Top Secret GENSER
security level. This was formerly called
WINCS.
DSNET3 - Serves single-level classified systems
operating at the Top Secret Special
Compartmented Information (Top Secret/SCI)
security level. This was formerly called
SCINET.
6. SERVICE CODE: This field is a two-letter code. It identifies
the military or civilian agency having responsibility for this
subscriber system. The codes for most Navy users are "DN" for
Department of the Navy or "CN" for Navy-sponsored academic or
commercial contractor systems. If there is any question
concerning the correct code, submit the complete name of the agency having
funding responsibility for the subscriber system.
COMNAVCOMTELCOM N62 will enter the correct code in the field during form
validation.
7. SECURITY CLASS: This field contains a one-character code
designating the security level of the subscriber system or the
classification of the data being passed over a connection. All
multi-level systems must register at the system high level of the
data being passed. NOTE - THIS IS NOT THE STANDARD CLASSIFICATION
REPRESENTATION. The classification and code representations are:
A = UNCLASSIFIED (APPLIES TO MILNET ONLY)
B = CONFIDENTIAL (DSNET1)
C = SECRET (DSNET1)
D = TOP SECRET - GENSER (DSNET2)
E = TOP SECRET - SIOP (DSNET2)
F = TOP SECRET - SCI (DSNET3)
If there is any question concerning the correct code, submit the
complete classification and COMNAVCOMTELCOM N62 will enter the
correct code in the field during form validation.
8. NO OF HOSTS: This is a three-character, non-zero numeric
field. It contains the number of host computers in this
subscriber system that is being proposed for connection to the network.
9. NO OF TERMINALS: This is a four-character field and contains
the number of direct-connect terminals being proposed for
connection to the subscriber system. Count only those terminals
which will access DDN through a leased line or a local hard cable
connection to a DDN Terminal Access Controller (TAC). Do NOT
count dial-in terminals, terminals that connect to a host, terminals
that connect to a Packet Assemblers/Disassembler (PAD) or terminals
that connect to a Local Area Network (LAN). If there are no direct-
connect terminals for this system, enter "N/A" in this field.
10. USER MAJOR COMMAND: The user major command is a 20-character
field containing the short title for the command having program
accountability or financial responsibility for the subscriber
system. Contractors need to obtain this information from the
agency they are supporting.
11. SUBSCRIBER PROGRAM DESIGNATOR CODE: The Program Designator
Code (PDC) is a six-character field which identifies the command
having program accountability or financial responsibility for the
subscriber system connecting to the DDN. This field is related
to the user major command and should be a code associated with that
particular user major command. If you do not know who has the
program accountability or financial responsibility for your
subscriber system, contact the comptroller or budget office of
your organization. The PDC for your system can be obtained by
contacting your major claimant or COMNAVCOMTELCOM, Code N62.
12. LAST NAME: This is a 25-character field containing the last
name of the administrative or managerial POC for the subscriber
system, host, terminal or connection being registered.
13. FIRST NAME: This is a 15-character field containing the
first name of the administrative or managerial POC for the subscriber
system, host, terminal or connection being registered.
14. MIDDLE INITIAL: This is a one-character field containing the
middle initial of the administrative or managerial POC for the
subscriber system, host, terminal or connection being registered.
15. POC TITLE: This is a 2O-character field containing the rank
or title of the administrative or managerial POC for the
subscriber system, host, terminal or connection being registered.
16. POC OFFICE SYMBOL: This 30-character field is also called
OFFICE SYMBOL identifies the organizational subcommand, code and
the office of the POC or command. This information should be
spelled out if possible. Please separate the fields by commas.
17. STREET: This is a 32-character field. This field and the
next three fields are used to either identify the postal address
of a POC or, in the subsections HOST SITE INFORMATION and TERMINAL
SITE INFORMATION, identifies the physical location of a piece of
equipment. STREET includes, if applicable, the number and
identifying street name, the postal box number and Naval or
Military base name. This field may also include the building
name or number and internal mail stop number, if this is necessary.
The field CANNOT be a post office box when identifying the
physical location.
18. BASE/CITY: This is a 25-character field. If it is being
used as the postal address, it contains the city or town of the
POC's mailing address. If the addressee is an OCONUS command,
this field could contain a FPO or APO address. If this is a physical
location, then this CANNOT be a FPO or APO address. If the
physical location is on a Naval or Military base, this field must
contain the community closest to that base.
19. STATE: This is the two-character abbreviation for the state
name. If it identifies the postal address of a POC, and the
field is an APO or FPO address, this field contains the state location
of the APO or FPO. If the address is in a foreign country, and
there is no APO or FPO address, enter the country code. In the case of
physical location, enter either the state name or country code.
If there is any question concerning the correct code, submit the
complete state or country name and COMNAVCOMTELCOM N62 will enter
the correct code in the field during form validation.
20. ZIP: This 10-character field contains the postal designator
for the address. Enter the complete ZIP code, a hyphen should
appear in the sixth position for CONUS addresses. Some OCONUS
locations have alphanumeric codes of varying lengths. For these
cases, complete the field from left to right leaving the
remainder of the field blank.
21. AUTOVON PHONE: This 20-character field contains the POC's
AUTOVON telephone number. The first three characters form the
AUTOVON theater code. The following codes are applicable:
313 = CARIBBEAN/SOUTH AMERICA
314 = EUROPE
315 = PACIFIC
317 = ALASKA
If there is any question concerning the correct code, submit the
geographic area for the POC responsible for the subscriber
system. COMNAVCOMTELCOM N62 will enter the correct code in the field
during form validation. If the POC does not have an AUTOVON number, enter an
"N/A" in this field.
22. COMMERCIAL PHONE: The commercial phone number is a
20-character field and contains the complete telephone number of
the POC. Include the area code in this field. For international
phone numbers, it is the international code, then country code,
then city code followed by the town or local number.
23. ELECTRONIC MAIL ADDRESS: This 30-character field contains
the POC's entire DDN electronic mail (E-MAIL) address, including the
domain name. If the POC does not have an E-MAIL address, enter
"N/A" in this field.
24. APO FPO: This 20-character field identifies whether this is
an Air Post Office or Fleet Post Office overseas mailing address
and the city where the post office is located.
25. IDS-MIS NUMBER: The host IDS-MIS number is a nine-character
field on the H-1 FORM and the terminal number is a
thirteen-character field on the T-1 FORM. This number uniquely
identifies a host or terminal on the DDN. The service or
agency representative assigns this number and it consists of the
following parts:
a. The first part of this field is a two-letter code. It
identifies the military or civilian department controlling this
host or terminal. Most Navy users will use the letters "DN",
Department of the Navy, or "CN", Navy-sponsored academic or
commercial contractor. If the correct code is in question,
submit the complete name of the agency having funding responsibility for
the terminal. COMNAVCOMTELCOM N62 will enter the correct code in
the field during form validation.
b. The second part is the four-character Data Processing
Installation (DPI) number. This number will uniquely identify an
activity and a location. It will not, however, distinguish
between different hosts or terminals located at the same site. Obtain
this number, if unknown, from the organization having funding
responsibility for the host or terminal. The Navy relates the
DPI number to the Unit Identification Code (UIC).
c. The third part of the IDS-MIS number is the
three-character host sequence number. The host administrative
POC specifically assigns a unique number to identify each host
computer at a site. The assignment of host IDS-MIS numbers is usually in
ascending sequence and based on the order of HOST QUESTIONNAIRE
FORM completion. For example, the first host would be 001, the
second would be 002. If this is a terminal being registered, it
must be registered relative to the host with which it
communicates.
Therefore this host number is that of the host to which the
terminal is assigned. The host must be registered in the IDS-MIS
before or at the same time as the terminal.
d. The fourth part of the IDS-MIS number is only used when
completing the T-1 FORM and it is a 4-digit terminal number
assigned by the administrative POC. This part of the IDS-MIS
number is only used when registering direct-connect terminals.
It uniquely identifies each direct-connect terminal and it is
customary to assign the numbers in ascending sequence as each T-1
FORM is completed. For example the first terminal would be 0001,
the second would be 0002.
26. SEQ NBR: Sequence Number is a two-character numeric field,
which in concert with the IDS-MIS number, uniquely identifies a
particular connection. The IDS-MIS number uniquely identifies
each host and terminal and the sequence number identifies the
connection from the host or terminal to the PSN. For example, a host
connected to more than one PSN or with more than one line to the
same PSN requires the submission of an H-1 FORM for EACH
connection. Each form would have a different sequence number
(01, 02, 03).
27. BASE MAJOR CMD: This is a 20-character field and it contains
the name of the POC's command. This name may be the same as USER
MAJOR COMMAND, if so enter the same name. Contractors need to
contact the agency they support for this information.
28. AGENCY NAME: This is a 20-character field. NOTE - This
field must contain the custodial unit or organization designator where
the HOST or TERMINAL EQUIPMENT is physically located.
29. GEOLOC: This is a 10-character field containing the
geographic location code where the host or terminal is physically
located. This is a DCA code and is contained in the DCA Circular
310-65-1. If there is any question concerning the correct code,
COMNAVCOMTELCOM N62 will enter the correct code in the field
during form validation. In order for COMNAVCOMTELCOM N62 to enter the
correct code, it is imperative that the CITY, STATE and ZIP CODE listed
under the HOST SITE INFORMATION or TERMINAL SITE INFORMATION be
correct and that these fields contain physical location
information. (GEOLOC is also required on the Feeder TSR.)
30. BLDG/ROOM: This 32-character field contains the building
name and room number of the host or terminal hardware's physical
location. A comma is used to separate the building name from the
room number.
31. AREA EXCHANGE: This seven-character field is a subset of the
local commercial telephone number. It identifies the host or
terminal equipment location by telephone area code and the local
telephone exchange code. The format is area code followed by the
exchange code. A hyphen, "-", will separate the area code from
the exchange code. For international telephone numbers use the
international code, "011", and the country code. If the country
code is less than three characters, use leading zeroes to pad the
field.
32. THEATER: This one-character code identifies the physical
location of the host or terminal equipment by geographic region
or theater. This is a DCA field and relates to their concept of a
theater. For example, Pacific does not include the San Diego
area or other CONUS locations. If there is any question concerning
the correct code, submit the geographic location of the piece of
equipment and COMNAVCOMTELCOM N62 will enter the correct code in
the field during form validation. The theater codes are:
C = Continental United States, Alaska,
South and Central America
E = Europe
P = Pacific
33. HOST NAME: This 64-character field contains the name
specified by the administrative POC and is the name used on the
DDN when addressing this host. This name is registered in the
Network Information Center (NIC) database. The first character of the
user portion must be alphabetic and the field must not have any
embedded blanks. If the host is also a GATEWAY, the last three characters
of the user portion of the name must be "-GW". If the host is a
gateway, it must be able to support at least one gateway
protocol, External Gateway Protocol (EGP) or Gateway To Gateway Protocol
(GGP).
34. MANUFACTURER CODE: This three-character field is the
Manufacturer Code. It is a DDN code which uniquely identifies
the manufacturing company of a host computer. COMNAVCOMTELCOM N62
normally supplies this code. However, a user with access to the
Manufacturer Code Table currently in use on the IDS-MIS system
can complete this field. If the user does not have access to the
Table, enter the full name of the host or terminal equipment
manufacturing company and COMNAVCOMTELCOM N62 will enter the
correct three-character code in the field during form validation.
35. MODEL: This 18-character field contains the name and model
number of the host or terminal equipment.
36. OPERATING SYSTEM: This 18-character field contains the name
and version number of the software operating system being used in
the host equipment.
37. TELEPROCESSING SOFTWARE: This 20-character field contains
the name of the protocol standard of the telecommunications software
application program being used in the host equipment. As of this
date the only two protocol standards are X.25 STANDARD and X.25
BASIC.
38. PROTOCOL: Protocol is a 12-character field that identifies
the type of network interface the host is using to connect to the
DDN. If the telecommunications software in the previous item is X.25
STANDARD, the protocol should be the "FULL SUITE" which includes
File Transfer Protocol (FTP), Simple Mail Transfer Protocol
(SMTP), Transmission Control/Internet Protocol (TCP/IP), and
Telecommunications Network Protocol (TELNET). Further, if this
host is to serve as a gateway to a backside local area network, a
LAN, added protocols are mandatory. The gateway will need either
External Gateway Protocol (EGP) or General Gateway Protocol
(GGP). Both are recommended. As the total network expands, we should
expect to communicate across net bounds. When this occurs,
domain processing will be necessary. For this reason, Uniform Domain
Protocol (UDP) is also suggested. Each of these is described in
DCA's DDN protocol handbook.
39. LAN NAME: This 20-character field is the name assigned to the
internet or Local Area Network (LAN) that is BEHIND the GATEWAY.
The LAN NAME will be registered in the NIC database. If the HOST
NAME field contains "-GW", the LAN NAME field must be completed
and the HOST TYPE must equal G. If this information is unknown,
enter "UNKNOWN". If there is no LAN, enter "N/A".
40. SECURITY CERTIFICATION CODE: This one-character code
indicates the level of security that is approved for the host.
As of this date, there are NO hosts certified to operate in a
multi-level secure mode of operation, therefore the only
acceptable code for this field is the letter "N".
41. DIAL UP TERMINALS: This four-character numeric field states
the number of dial up terminals that will access this host
THROUGH the DDN. (NOTE: This is not the number of terminals that will
access this host through a dedicated Terminal Access
Controller). Please estimate this number. Enter a number from
zero through 9999.
42. HOST TYPE: This one-character code identifies the type of
DDN connection for this host. The desired protocol suite is X.25
STANDARD. The codes for this field are:
A = AMPE
F = Front End Processor
G = Gateway to a backside LAN
P = General Computer
H = Host operating either of the X.25 protocols
U = UNKNOWN
43. PACKET SIZE: This is a four-character numeric field that
states how many 8-bit bytes will be transmitted as a unit from
the host to the network. The user can specify the size required,
however the default size is 128 bytes and the maximum is 1024.
44. PRIORITY CODE: NO LONGER USED (This is a one character
code.
It identifies the priority of this system for entry onto the DDN.
The valid codes are A-F, A is the highest priority and F is the
lowest. This code is assigned by CNO.)
45. SUBSCRIBER REQUEST OPERATIONAL DATE: This field is six
characters long. This is the date the service or agency would
like the host connection to be operational on DDN. The format of
this field is year, month and day (YYMMDD).
46. [SOFTWARE INTERFACE: This one-character code identifies the
software interface connecting a host or terminal to the DDN. The
software interface codes are:
A = X.25 BASIC
B = 1822 HDH
D = 1822 DH
E = 1822 LH
F = 1822 DH W/ECU
G = 1822 LH W/ECU
H = IMP TO IMP
I = TAC DIAL-IN
J = TAC DIRECT CONNECT
K = X.25 STANDARD
47. HARDWARE INTERFACE: This one-character code identifies the
hardware interface required to connect a host or terminal. The
hardware interface codes are:
A = RS-232
B = MILSTD 188-114
C = V.35
D = BELL 303
E = DH HOST IMP CABLE
H = IMP TO IMP
48. LINE SPEED: This one-character code indicates the line speed
at which the host or terminal interface operates. If the line
speed is equal to or less than 19.2 KBPS, then the Subscriber
Request Operational Date field must be at least 270 days away
from the date of entry. If the Line Speed is equal to 50 KBPS, 56
KBPS, 64 KBPS, 1.544 MBPS or 110 KBPS, then the Subscriber Request
Operational Date field must be at least 360 days away. This is
verified at the time of initial data entry. The line speed codes
are:
A = 1.2 KBPS
B = 2.4 KBPS
C = 4.8 KBPS
D = 9.6 KBPS
E = 19.2 KBPS
F = 50 KBPS ANALOG
G = 56 KBPS DDS
H = ASYNCH 0-100 KBPS
I = 0.3 - 1.2 KBPS
J = .3 KBPS
K = 110 KBPS
L = 14.4 KBPS
M = 16.8 KBPS
N = 64 KBPS
O = 128 KBPS
T = 1.544 MBPS
blank = UNKNOWN
49. PRECEDENCE CODE: This one-character numeric code represents
the precedence level of the requirement. As of 1 November 1987,
all requirements are being assigned a level of zero, "0", until
JCS determines the DDN precedence level requirement.
0 = ROUTINE
1 = PRIORITY
2 = IMMEDIATE
3 = FLASH
50. COMMENTS: This 60-character field is to be used for
additional notes and comments.
51. TERMINAL CONNECTIONS: This four-character numeric field
identifies the number of terminals connected to the terminal
concentrator. The number of terminals MUST be entered in this
field if "TERMINAL TYPE" is equal to "Y". If the field is not
"Y", enter "N/A".
52. PROTOCOL: This one-character field uniquely identifies the
data communication protocol implemented in the terminal. The
protocol codes are:
A = X.25 BASIC
B = X.25 STD TCP/IP AND VENDOR SPECIFIC
C = X.25 STD TCP/IP, TELNET, FTP, SMTP
D = X.25 STD IP, EGP (GW)
E = X.25 STD IP AND VENDOR SPECIFIC
F = X.25 STD OTHER
53. TERMINAL TYPE: This one-character field indicates whether
this terminal is a terminal concentrator or cluster controller.
The type codes are:
Y = YES
N = NO
U = UNKNOWN
54. CHARACTER SET: This one-character field uniquely identifies
the character code set implemented in the terminal. The terminal
character set codes are:
A = ASCII
B = EBCDIC
C = BCD
G = OTHER
ADMINISTRATIVE (SYSTEM) POINT OF CONTACT TEMPLATE
DATE(1): ________
**** IDS-MIS ADMINISTRATIVE POC FORM ****
FORM ACTION (SELECT ONE)(2): ADD: ___, CHANGE: ___, DELETE: ___
URDB(25): _____________ SEQ NBR(26): __
LAST NAME(12): ____________________ FIRST NAME(13):
_______________
POC MIDDLE INITIAL(14): __ POC TITLE(15):
__________________
POC OFFICE SYMBOL(16): ____________________________
STREET(17): ________________________________
CITY(18): ____________________ STATE(19): __ ZIP(20):_________
APO FPO(24): _________________ AUTOVON PHONE(21):
_________________
COMMERCIAL PHONE(22): ____________________
ELECTRONIC MAIL ADDRESS(23): ______________________________
SYSTEM QUESTIONNAIRE TEMPLATE
DATE(1): ________
IDS-MIS SYSTEM QUESTIONNAIRE FORM (S-1)
FORM ACTION (Select One)(2): ADD __, CHANGE __, or DELETE __
*** SYSTEM INFORMATION ***
SYSTEM ACRONYM(3): ____________________
SYSTEM NAME(4):
______________________________________________
_________________________________________________________________
_
PRIORITY CODE(44): _ SERVICE CODE(6): ___
SECURITY CLASS(7): _ NO OF HOSTS(8): ___ NO OF TERMINALS(9):
____
*** MAJOR CLAIMANT INFORMATION ***
MAJOR USER COMMAND(10): _________________________ PDC CODE(11):
______
LAST NAME(12): ____________________ FIRST NAME(13):
_______________
POC MIDDLE INITIAL(14): ___ POC TITLE(15) : ____________________
POC OFFICE SYMBOL(16): ____________________________
STREET(17): ________________________________
CITY(18): ____________________ STATE(19): __ ZIP(20): ________
AUTOVON PHONE(21): ___________________
COMMERCIAL PHONE(22): ____________________
ELECTRONIC MAIL ADDRESS(23): _______________________________
CONNECTION QUESTIONNAIRE AND POC TEMPLATES
DATE (1): ________
**** IDS-MIS CONNECTION QUESTIONNAIRE FORM ****
FORM ACTION (SELECT ONE) (2): ADD: ___, CHANGE: ___, DELETE: ___
URDB (25): _____________ SEQ NBR (26): __
SUBSCRIBER REQUEST OPERATIONAL DATE(45): ______ PRIORITY CODE
(44):___
SYSTEM ACRONYM (3): ______________________________________
SUBSCRIBER PROGRAM DESIGNATOR CODE(11): ______
NETWORK NAME(5): ______
SOFTWARE INTERFACE CODE (46) _ PRECEDENCE(49): _
HARDWARE INTERFACE CODE (47): _ LINE SPEED(48): _
SECURITY CLASSIFICATION(7): _
COMMENTS
(51):____________________________________________________________
____
_________________________________________________________________
_____________
**** CONNECTION POC FORM ****
FORM ACTION (SELECT ONE)(2): ADD: ___, CHANGE: ___, DELETE: ___
URDB(25): _____________ SEQ NBR(26): __
LAST NAME(12): ____________________ FIRST NAME(13):
_______________
POC MIDDLE INITIAL(14): __ POC TITLE(15):
__________________
POC OFFICE SYMBOL(16): ____________________________
STREET(17): ________________________________
CITY(18): ____________________ STATE(19): __ ZIP(20):_________
APO FPO(24): _________________ AUTOVON PHONE(21):
_________________
COMMERCIAL PHONE(22): ____________________
ELECTRONIC MAIL ADDRESS(23): ______________________________
HOST QUESTIONNAIRE TEMPLATE
DATE(1): ________
**** IDS-MIS HOST QUESTIONNAIRE FORM (H-1) ****
FORM ACTION (SELECT ONE)(2): ADD: ___, CHANGE: ___, DELETE: ___
URDB(25): _________ SEQ NBR (26): __
*** HOST SITE INFORMATION ***
AGENCY NAME(28): ____________________ AREA EXCHANGE(31): _______
BASE MAJOR CMD(27): _______________ MAJOR USER COMMAND(10)
:__________
OFFICE SYMBOL(16): ______________________________
BLDG/ROOM(30): _________________________ GEOLOC(29): __________
STREET(17): _________________________________THEATRE(32):___
BASE/CITY(18): ____________________ STATE(19): __ ZIP (20):
________
*** HOST INFORMATION ***
HOST NAME(33): ___________________________________________
HOST TYPE(42): ___ MODEL(35): _______________ LAN NAME(39):
_______________
PROTOCOL(38): __________________ PACKET SIZE(43): ____
OPERATING SYSTEM(36): __________________ MANUFACTURER CODE(34):
___
SECURITY CERTIFICATION CODE(40): __ DIAL UP TERMINALS(41):
___
TELEPROCESSING SOFTWARE(37): ____________________
COMMENTS(50):
____________________________________________________________
TERMINAL QUESTIONNAIRE TEMPLATE
DATE(1): ________
IDS-MIS TERMINAL QUESTIONNAIRE FORM (T-1)
FORM ACTION (Select One)(2): ADD ___, CHANGE ___, or DELETE ___
URDB NUMBER(25): _____________ SEQ NBR(26): ___
*** TERMINAL SITE INFORMATION ***
AGENCY NAME(28): ____________________ AREA EXCHANGE(31): _______
BASE MAJOR CMD(27): _______________ MAJOR USER COMMAND(10):
_______________
OFFICE SYMBOL(16):______________________________
BLDG/ROOM(30): _________________________ GEOLOC(29): __________
STREET(17): _______________________________THEATRE(32): ___
CITY(18): ____________________ STATE(19): __ ZIP (20): ________
*** TERMINAL INFORMATION ***
MODEL(35): __________________ MANUFACTURER CODE (34): ___
CHARACTER SET (54): ____ TERMINAL TYPE (53): ___
TERMINAL CONNECTIONS(51): ______ PROTOCOL (52):____
COMMENTS (50):
____________________________________________________________