Appendix 1: Communications Control
Tab A: Communications Control Diagram
This diagram reflects the communications control that the MCCC has established over the network. It is a quick reference that MCCC/SYSCON/TECHCON watch standers can ref- erence as an aid in reporting significant network-related events and includes the following:
• Unit POCs can be listed on the diagram, or may be included as an exhibit to the tab.
• Include unit names on the diagram.
• Grid coordinates for the MCCC and subordinate SYSCONs may be included.
Tab B: Required Reports
Include a required reports matrix or a simple list with required reports with examples as necessary, to include the following information:
• To what unit/agency reports must be submitted.
• Required time for report submission.
• Transmission media reports are to be submitted via means such as e-mail, telephone, or radio net.
Tab C: Master System Link Designator List
A master system link designator (SLD) list is required to ensure that all links are prop- erly identified, and not used more than once. Consider the following when creating a master SLD:
• The most efficient means to create the SLD list is to use the export tool within the tactical network analysis and planning system (TNAPS).
• A TNAPS can export information to a Microsoft Excel spreadsheet that can be inserted into a Microsoft Word document and placed as a tab within the appendix. This process can also be used to port the SLD to a Web page.
• The SLD list will change over the period of a given exercise or operation and will require continuous update. This can be accomplished efficiently with Web page updates and alerts to subscribers via an e-mail distribution list.
• Links for FRAGOs can be quickly created for an operation using TNAPS, updated within the FRAGO matrix, and ported to the SLD Web page for quick reference.
Tab D: Master Command Communications Service Designator
The process explained on page F-9 for the SLD list also applies to the command com- munications service designator (CCSD) list.
Appendix 2: Communications Security
This appendix defines the COMSEC plan for the exercise or operation. The communica- tions network planner is responsible for preparing and planning COMSEC requirements (such as keying materials, codes, or equipment) for the communications network, and must work closely with the EKMS manager(s) to accomplish this. For example, the communica- tions network planner will identify the COMSEC keying materials for the MAGTF switched network and the COMSEC and alternate COMSEC parent circuit switches. This appendix will also—
• Define how COMSEC keying material will be distributed throughout the AO.
• Define what unit/agency is responsible for distribution.
• Provide effective and supersession date information for keying materials to be used.
• Provide amplifying guidance and direction for submission of COMSEC incident reports.
• Provide coordinating instructions that might reference what actions are to be taken in event of a compromise.
• Provide POC information for EKMS manager(s).
Tab A: Intent to Use Message
Once the “Intent to Use” message is published, place it in this appendix for easy reference.
Tab B: Communications Security Callout Message
Once the “COMSEC Callout” message is published, place it in this appendix for easy reference.
Tab C: Emergency Action Plan
This is the command’s EKMS emergency action plan. If an SOP exists, reference it here or provide the location of the electronic copy.
Appendix 3: Information Security
This appendix identifies general INFOSEC requirements and procedures. The references should identify the commander’s policies and procedures. The following information (not a complete list) should be outlined in this appendix:
• Types of reports that are to be used. Note: These reports should also be listed in appendix 1: Communications Control, tab B.
• Coordinating instructions which should reference items such as firewall procedures and IA POCs.
Tab A: SIPRNET DSID Diagram
A diagram of the DSID network that identifies SLD/CCSD and IPs used. Exhibits in this tab should list all firewall settings for initial implementation. Specific guidance for how DSIDs are managed should also be included in this appendix.
Tab B: SIPRNET Antivirus Architecture Diagram
A diagram of the antivirus server architecture identifying SLD/CCSD and IPs used.
Tab C: NIPRNET DSID Diagram
Similar to tab A.
Tab D: Information Assurance Vulnerability Alert Process Diagram
This diagram should highlight the IA vulnerability alert process that was outlined previously.
Tab E: Interim Authority to Operate
Once the interim authority to operate package is completed, place it in this appendix for reference.
Tab F: Systems Security Accreditation Authorization
Once the systems security accreditation authorization is published, place it in this appen- dix for reference.
Tab G: Example End User Agreement
This is a reference that should have been discussed in the appendix. Every Marine that accesses the network must sign one of these agreements.
Appendix 4: Spectrum (Frequency) Management Plan
This appendix defines how spectrum (frequency) management is conducted and, most importantly, how frequencies are requested and deconflicted. Reference to the CEOI and where it can be located will be included. Spectrum management POC information will also be included.
Tab B: Master Net List
Appendix 5: Radio Network Plan
The appendix will provide necessary guidance and diagrams required to install, operate, and maintain the radio network, including SCR, MCR, and satellite radio. The satellite access request and gateway access request will be included in this appendix. This will be particularly important information while conducting a relief in place (RIP).
Tab A: Radio Guard Chart
Tab B: HF Radio Network Diagram Tab C: VHF Radio Network Diagram
Tab D: LOS Radio Network Diagram
Tab E: UHF (LOS) Multichannel TACSAT Radio Network Diagram Tab F: Gateway Access
Once the gateway access request is published, place it in this appendix for easy reference. This will be particularly useful during a RIP of communications units.
Tab G: SHF (LOS) Multichannel Radio Network Diagram/Gateway Access Authorization
Once the gateway access authorization is released by the STEP site, place it in this appendix for easy reference. This will be particularly useful during a RIP of communications units.
Tab H: UHF SATCOM Radio Network Diagram Tab I: UHF SATCOM MCR Network Diagram Tab J: EHF SATCOM MCR Network Diagram Tab K: EHF SATCOM Orderwire Network Diagram Tab L: Satellite Access Request (US military) Tab M: Satellite Access Request (Commercial) Tab N: Satellite Access Authorization (US military)
Tab O: Satellite Access Authorization (Commercial)
Appendix 6: Multiplexing Network Plan
This appendix will provide necessary guidance and diagrams, and will include any spe- cial considerations or restrictions, required to install, operate, and maintain the multiplex- ing network. Tabs are used to amplify this information.
Tab A: Multiplexing Network Diagram
Tab B: TRITAC Levels One and Two Multiplexing Network Diagram Tab C: FCC 100 Level One Multiplexing Network Diagram
Tab D: PROMINA Level One Multiplexing Network Diagram Tab E: Primary Network Timing Diagram
Tab F: Cut Sheet
Appendix 7: Telephone Network Plan
This appendix discusses elements that a network planner should take into account when designing a telephone system. Within the tabs, you will find examples of some of the fol- lowing topics and other pertinent information.
Tab A: Circuit Switch Diagram
Tab B: Defense Switch Network/Defense Red Switch Network Diagram Tab C: Dialing Instructions
Tab D: Information Systems Directory Format Tab E: Generation of Traffic Reports
Tab F: Naming Standard
Tab G: Global Block Numbering Plan
The global block numbering plan (GBNP) is managed by DISA. The GBNP predesig- nates a range of PRSL to each of the Uniformed Services to avoid conflict in switchboard
identifier codes. Marine Corps Systems Command is the GBNP manager for the Marine Corps designated range, providing a breakdown for each of the four MEFs and MCTSSA.
Tab H: Leased Line Emulation
This feature, commonly referred to as yellow alarm busyout, is available on the primary rate card in the Promina 400/800. When yellow alarm busyout is enabled, it overrides the regular busyout features and all parameters pertaining to regular busyout are no longer displayed in the operator interface of the Promina. When a busyout condition occurs, the digroup will bring down the whole digroup; hence, the emulated leased line, rather than busyout, an individual port, or a group of ports in the digroup, forces the REDCOM to use a secondary route (if available). Yellow alarm busyout is applied in response to the following conditions:
• No bandwidth.
• Primary call path not available.
• Slow response (if enabled).
• Destination Promina failure.
• No echo canceller channel available.
• No compression/decompression channel available.