Central Area Plan



1.1 CENTRAL AREA ROUTING PLAN - In accordance with NTS Digital System Guidance, Section II, and Section IIIB, paragraphs 1 and 2, Central Area Digital (CAD) shall implement the "open system" approach for forwarding and coordination of inter-area and intra-area digital traffic. It is to be noted that the degree of flexibility with any routing plan shall always depend on the existing routing plans of the other areas involved. Therefore, CAD shall interface with EAD and PAD only to the extent allowed and/or dictated by their individual routing plans.

1.1.1 Central Area INTER-AREA traffic is defined as the inbound and outbound traffic that is RECEIVED FROM and/or SENT TO the Eastern and Pacific Areas. Basically: (a) Inter-area traffic TO the Eastern and Pacific areas may be sent by any CAD MBO or DRS station, but shall be routed only to designated EAD and PAD Regional MBO or HUB station(s) in accordance with the "Routing Plan" existing for the specific area. (b) EAD and PAD stations with Inter-area traffic for CAD may route directly to any applicable or available CAD Regional MBO station at their discretion, and depending on band conditions. (c) Coordination between SysOp's of applicable MBO/DRS stations shall be mandated and necessary to establish traffic flow and disposition.

1.1.2 Central Area INTRA-AREA digital traffic shall be defined as the traffic within the boundaries of CAD and subject to internal routing and disposition. (a) The preferred and desirable routing and disposition of CAD intra-area traffic shall be consistent to normal NTS traffic routing to the extent possible. (b) To implement, it shall be necessary for all CAD individual DRS stations coordinate with SysOp's of any or all applicable CAD Regional MBO/DRS stations to establish flow and disposition of applicable Section, Region, or Area traffic. (c) CAD SysOps are also requested to become familiar and knowledgeable, and apply all of the noted traffic handling issues of Section IV of referenced NTS Digital System Guidance.

1.2 MISCELLANEOUS - Related and recommended CAD SysOp do's and don'ts.

1.2.1 CAD SysOps are requested not to use the generic "NTS" command when connecting to Winlink MBO systems. The NTS command will do a listing of all pending non-forwarded NTS traffic on the board. The listing could result in a long listing of traffic destined for locations other than location being polled or interested in, or not authorized to remove. This could impose a problem or impact operation of the MBO, if it should have a long list of traffic, and if band conditions are marginal, and/or if other stations are waiting , etc. Using the NTS command shall not constitute an adverse useage of the MBO, but to avoid, would be in good judgement! The recommended alternative is to use the List command ...L@ NTSxx..., which will only list the traffic, destined for the specific Section(s) being polled. Keyboarder SysOps may also use the "FF" and "FS" commands when connecting to Winlink systems for retrieving traffic, but must be coordinated with the system SysOp. Any DRS station using AirMail or Winlink software to receive or transmit traffic by ARQ call/connect in the Auto-forward mode must also coordinate with applicable system SysOps.

1.2.2 CAD Winlink system SysOps are requested not to set daily board useage time limits for NTSD participating stations that are in compliance with issued CAD SOPs, and/or NTSD guidelines. When large volumes of traffic are being handled, and/or if adverse conditions are being experienced, limited daily time thresholds should not be a SysOp concern and/or restriction.

1.2.3 CAD SysOps are requested to lockout or reject any station that abuses and/or adversely affects the operation of their systems, and that do not comply with issued CAD SOPs and/or NTSD guidelines. Please follow up and coordinate with offenders to hopefully rectify the situation.

1.3 REPORTS: To expound on paragraph "G" of Section IV, all active and participating CAD stations are required to submit monthly traffic reports to the CADC. The traffic report is to account only for the messages that are RCVD and/or SENT via your digital system, i.e., total messages RCVD, total messages SENT, and then the TOTAL. All HF and/or VHF port configurations are to be accounted for. Monthly traffic reports are mandated regardless of how small or large the traffic activity, or even if there is no traffic to report. Cut off date for traffic reports shall be the 10th of the month. Early reports shall be appreciated.

R1: 05/04/2003, W4ZJY, CADC - Routing plan and generic changes.

.  Last modified:  April 06, 2013 06:20 AM  .