SAS Net

Rules of
Engagement

 

 

 

These rules are necessary to clearly demonstrate that there will never be
any communications intentionally hidden.    By ensuring transparency of all communications on the SAS Net, there can be no grounds for complaint.
Unnecessary and time-wasting involvement of national authorities is avoided.

Listeners are invited to decrypt any encrypted traffic they wish by simply
following the instructions.

 

 

1

The SAS Net is for efficient handling of traffic in Morse Code,  primarily encrypted but may also be in clear.     It provides a channel for encryption enthusiasts to share their systems.   Casual chat in any mode is not in the remit; discussion needs to be via email, echolink, forums, etc.  

2

The SAS Net Control Station (NCS) may be subject to a rota.  It will call for check-ins on Thursdays at 0840Z on 7.0257 MHz   ±   2 kHz     No time is limit.

3

Check-ins are invited from operators with traffic to pass, and from operators who hear during check-ins that traffic is waiting for them.  No QRU check-ins please.

4

The SAS Net will be conducted under traditional Traffic Net rules, wherein Q-codes and prosigns are used wherever possible in the interest of efficiency, also to help stations listening understand the state-of-play.

5

Two well documented encryption methods may be freely used on the SAS Net.  These are WWII German Enigma M3 and M4, and the well-known Cold War Number Stations' One Time Pad,  both the manual method or with Python error detection.  Each item of traffic must include a URL in clear which links to its respective decryption instructions.      Generic URLs for use in OPNOTES for the two methods already documented are:    BIT.LY/DECRNS  (Number Station OTP)  and  BIT.LY/DECREN  (ENigma)

 Please do not EVER send encrypted traffic or variations on these two methods, without providing a reference to its own decrypt instructions.

6

Any other encryption method may be used but must have been previously documented including ad hoc and easily implemented decryption instructions,  as described in Rule 7 and Rule 8.     No exceptions.    The BIT.LY/THP  (temporary help page index) may be used to point to your decrypt information by arrangement with the webmaster, in advance of transmitting any new methodology or unusually encrypted traffic.

7

The responsibility for providing full and understandable decryption instructions, and/or to provide a URL pointing to those instructions, lies squarely with the sender of encrypted traffic.   The SAS Net webmaster, the holder of call sign ZL3TK, and any other party participating party on the SAS Net,  does not accept any responsibility for the activity of any amateur operator who chooses to breaches these common-sense rules. 

8

A decryption facility may be accessed by a URL (the preferable option),  or by sending decryption instructions in clear.  Decryption instructions must be transmitted immediately following, but separate from, the encrypted message text.  The second option is strongly discouraged due to inherent inability to present clarification via screen shots and the length of time needed to convey such detailed  information.   

9

Decryption instructions may be hosted on any web server,  or by arrangement with the SAS Net webmaster on the SAS website in advance of any transmission requiring dependent upon those decrypt instructions.