HX 19.2.001 - Net Intex Messaging System

NIMS: The Net Intex Messaging System

Off and on for the past year or so I have been tinkering with a "modern" telegraphic messaging network called Net Intex. The concept was that a virtual telex-style network would be overlayed across multiple communications technology, with the internet being the primary mode of carrying traffic. Under ITU-T recommendations, a telex-style network using the ITA2 character set is called gentex, while one that uses the IA5 character set (ASCII) is called intex. There are a large number of problems to solve in such a network, and the solutions aren't all that simple. A key capability of a telex-style network is that it provides a circuit-switched keyboard-to-keyboard connection, while the ultimate end goal is to deliver a telegraphic message from one endpoint to the other. As telex calls were charged by the minute, it was important to reduce the time spent on a call. It was common for messages to be prepared offline and then transmitted using something like a paper tape reader, and then disconnect at the end of the message. Throw on a few additional procedures and you end up with something like old Western Union's routing system, or ACP-128 ALTERS. In other words, a store-and-forward message network.

As I have a AN/UGC-129(V)1 teleprinter that understands messages in the ACP-style 16-line message format, laziness dictates I must use that format for everything. As of early September 2019, various details have been hammered out. Documentation regarding the interpretation and variations on ACP-128 and USMTF are mostly written. The SAME project has been transformed into a feature of NIMS, instead of NIMS being an adaptation for SAME. Code to understand message addresses and to perform routing is mostly complete. As routing will be automatic, provisions for stopping message loops have been devised. The host-side monitor to provide service to teleprinters is mostly functioning.