<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>“Pig Latin” as I understand that particular coding is NOT encryption, as the cipher and key are widely publicly available for anyone to find and decode the message, thus Pig Latin cannot be used to obscure the meaning of the message any more than Morse Code does or the Finnish language does. Encryption is meant to obscure a message in a way to purposely hide the information using a secret key that’s needed to decode the message. The FCC does not ban the use of Finnish, Navajo, FT8, Morse Code, RTTY, etc, despite them possibly being a mild inconvenience for some hams to obtain the publicly available cipher and key needed for finding the meaning of those UNencrypted codings.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I just now went back to refer to the latest version of FCC CFR 47 Part 97 and found the most relevant sections to be 97.309(a)(4), and in particular 97.309(b) which contains this text: “data emissions using<o:p></o:p></p><p class=MsoNormal>unspecified digital codes must not be transmitted for the purpose of obscuring the *<b>meaning</b>* of any communication.” That text fits the definition of encryption as it is widely understood in the digital coding industry and military, regardless of whether the actual word “encryption” is used in the regulation. Could the Part 97 text be more expliciti and clear? Perhaps, but it is close enough to the problem we’re discussing that we need to be concerned. I had the opportunity to have a phone conversation with an FCC lawyer about another matter (having to do with importation of Part 90 & 97 radios used by hams) back in 2018 and while on the phone brought up this encryption topic (because of AMBE at the time), and it is clear to me that the FCC legally views encryption ciphers and their required keys like SSL to be illegal OTA on ham bands, as it is clear to them (and should be to everyone else) that the intent of encryption is to obscure communications with privately (not publicly) available means to decode/decrypt the communications (just as many commercial radio systems are doing, including the growing use of encryption in public safety systems); the grey area if any is whether a ham or anyone else in the public has to pay $ to get the cipher and/or key from a private source (such as for AMBE from DVSI) , but that is another story I believe unrelated to what we’re discussing here.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Stephen W9SK<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> PSDR <psdr-bounces@hamwan.org> <b>On Behalf Of </b>Kevin Walsh<br><b>Sent:</b> Tuesday, March 16, 2021 3:09 PM<br><b>To:</b> Puget Sound Data Ring <psdr@hamwan.org><br><b>Subject:</b> Re: [HamWAN PSDR] Newbie<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p></o:p></p><div><p class=MsoNormal>Hello,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The word encryption never appears in Part 97 rules, so its definition is irrelevant here. The key words in the rule are “intent” and “obscure”. So for instance, two people speaking pig-Latin with the intent of obscuring their conversation violate the same rule and the conversation is prohibited - even though it’s not encrypted.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>If I may, another option would be to get any of your associated Public Safety agencies to in part sponsor HamWan. Public Safety was granted access to the “special” Amateur Radio portion of 5.8GHz years ago and they CAN use (and in my state require) secure communication. Then you’re operating under Part 15 and the conversation is moot.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><a href="https://www.fcc.gov/public-safety/public-safety-and-homeland-security/policy-and-licensing-division/public-safety-spectrum">https://www.fcc.gov/public-safety/public-safety-and-homeland-security/policy-and-licensing-division/public-safety-spectrum</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Just food for thought, I’ll go back to lurking now :-).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>73, <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Kevin<o:p></o:p></p></div><div><p class=MsoNormal>W8KHW <o:p></o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-bottom:12.0pt'>On Mar 16, 2021, at 3:40 PM, Stephen Kangas <<a href="mailto:stephen@kangas.com">stephen@kangas.com</a>> wrote:<o:p></o:p></p></blockquote></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><o:p></o:p></p><p class=MsoNormal>John, it’s a good idea to investigate FW filtering to prevent encrypted protocols, and certainly the MikroTik RouterOS is quite capable of that. We should experiment with that to see if it breaks the Winlink Express connection with CMS. Hopefully, as Scott pointed out, it will not by simply forcing the CMS to fall back to pure telnet protocol…but he says that may not remain the case into the future. I’ll give it a try later this week when I have some time, others should, too.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Stephen W9SK<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> PSDR <<a href="mailto:psdr-bounces@hamwan.org">psdr-bounces@hamwan.org</a>> <b>On Behalf Of </b>John D. Hays<br><b>Sent:</b> Tuesday, March 16, 2021 11:22 AM<br><b>To:</b> Puget Sound Data Ring <<a href="mailto:psdr@hamwan.org">psdr@hamwan.org</a>><br><b>Subject:</b> Re: [HamWAN PSDR] Newbie<o:p></o:p></p></div><p class=MsoNormal> <o:p></o:p></p><div><div><p class=MsoNormal><span style='font-size:18.0pt'>The HamWAN client is a MikroTik device which has a robust IP tables implementation which could be used for filtering.</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><div><div><p class=MsoNormal>On Tue, Mar 16, 2021 at 10:22 AM Aaron Taggert <<a href="mailto:aaron.taggert@gmail.com">aaron.taggert@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal>I do not know what router you have but you could install squid (on the router or on a raspberry pi) on the ham wan connection and 'splice' the TLS Cipher to NULL: <a href="https://wiki.squid-cache.org/Features/SslPeekAndSplice" target="_blank">https://wiki.squid-cache.org/Features/SslPeekAndSplice</a><o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Also from HamWan.org:<o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><a href="https://hamwan.org/Administrative/Internet%20and%20Part%2097.html" target="_blank">https://hamwan.org/Administrative/Internet%20and%20Part%2097.html</a><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><a href="https://hamwan.org/Standards/Network%20Engineering/Authentication/SSL%20without%20Encryption.html" target="_blank">https://hamwan.org/Standards/Network%20Engineering/Authentication/SSL%20without%20Encryption.html</a><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><a href="https://hamwan.org/Standards/Network%20Engineering/Authentication.html" target="_blank">https://hamwan.org/Standards/Network%20Engineering/Authentication.html</a><o:p></o:p></p></div></div></div><p class=MsoNormal> <o:p></o:p></p><div><div><p class=MsoNormal>On Tue, Mar 16, 2021, 8:42 AM Steve - WA7PTM <<a href="mailto:psdr-list@aberle.net" target="_blank">psdr-list@aberle.net</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal>Thanks Aaron. I fully understand what SSL/TLS is, but am trying to zero <br>in on how to avoid it on my HamWAN connection. Unfortunately, the <br>sneaky protocol translations on the back end will only continue, and we <br>just need to be know which software to stop using when things are not <br>obvious on the front end.<br><br>Steve<br><br><br>Aaron Taggert wrote on 3/16/21 8:26 AM:<br>> On the authentication/integrity side... FCC says no encryption so we can<br>> all hear what you're on about. Ham would not be much fun if all you heard<br>> was encrypted pseudo noise. SSL/TLS authentication is a bit like me sending<br>> you a list of 100 words and asking you to tell me word 45. Everything is in<br>> the clear, but I can authenticate that whomever is at the other end at<br>> least has the right list. Another SSL/TLS feature is integrity, meaning the<br>> whole message is received. They would be like saying I sent 3421 characters<br>> CW 786 of them were vowels. Again everybody can hear what we're saying but<br>> it would be difficult to impersonate the sender (or receiver) or change the<br>> message.<br>> <br>> On Tue, Mar 16, 2021, 6:32 AM Steve - WA7PTM <<a href="mailto:psdr-list@aberle.net" target="_blank">psdr-list@aberle.net</a>> wrote:<br>> <br>>> If we separate Winlink (the system) from Winlink Express (the client<br>>> program), is a SSL connection also the case with the other six clients<br>>> listed on the <a href="https://winlink.org/ClientSoftware" target="_blank">https://winlink.org/ClientSoftware</a> page when used in<br>>> telnet mode?<br>>><br>>> Steve<br>>><br>>><br>>> Scott Currie wrote on 3/15/21 10:06 PM:<br>>>> Yeah, I discussed this with the WDT, and the issue with using HamWAN or<br>>>> ARDEN. I had asked if we could force a non-SSL connection to the CMS.<br>>> They<br>>>> have been under pressure from AWS to switch to all SSL connections, so<br>>> they<br>>>> had to make the change. They did commit to leaving the client or gateway<br>>>> connection to RMS Relay as non-SSL, so th>3.20.3.63-STEPHEN-ASUSLAP.2622f7cb-2c3a-4067-8ad6-3ad8d9119959
_nvstream_dbd_tcplocal ! Relay on HamWAN that the RMS Gateways and<br>>>> clients could point to. Backend of the RMS Relay would then connect to<br>>> the<br>>>> CMS over SSL on a hardened Internet connection (like at a county EOC or<br>>> the<br>>>> State EOC), or even HF forwarding if the Internet is down.<br>>>><br>>>> -Scott<br>>>><br>>>> On Mon, Mar 15, 2021 at 9:41 PM Stephen Kangas <<a href="mailto:stephen@kangas.com" target="_blank">stephen@kangas.com</a>><br>>> wrote:<br>>>><br>>>>> Scott, thanks for that update, interesting. “Telnet” is a misnomer in<br>>>>> this WinLink instance, as that port 22 protocol is historically and<br>>>>> normally unencrypted, and widely understood in the industry as such<br>>>>> (whereas SSH is encrypted). It looks like the email client is<br>>> connecting<br>>>>> locally to an RMS Relay in that mode, which then connects to the CMS on<br>>> the<br>>>>> internet.<br>>>>><br>>>>><br>>>>><br>>>>> --Stephen W9SK<br>>>>><br>>>>><br>>>>><br>>>>> *From:* PSDR <<a href="mailto:psdr-bounces@hamwan.org" target="_blank">psdr-bounces@hamwan.org</a>> *On Behalf Of *Scott Currie<br>>>>> *Sent:* Monday, March 15, 2021 5:56 PM<br>>>>> *To:* Puget Sound Data Ring <<a href="mailto:psdr@hamwan.org" target="_blank">psdr@hamwan.org</a>><br>>>>> *Subject:* Re: [HamWAN PSDR] Newbie<br>>>>><br>>>>><br>>>>><br>>>>> This is not entirely true. Winlink does use TLS/SSL connections for some<br>>>>> things. The normal telnet connection is now SSL (will fallback to<br>>> non-SSL<br>>>>> if the connection fails). Also, RMS Gateway to the CMS is now SSL.<br>>> Telnet<br>>>>> P2P and telnet to RMS Relay is not SSL. I believe updates are also SSL<br>>> now.<br>>>>><br>>>>><br>>>>><br>>>>> Winlink Express Link Test:<br>>>>><br>>>>> Test started 2021/03/16 00:52 UTC<br>>>>><br>>>>> Testing CMS telnet connection to <a href="http://cms.winlink.org" target="_blank">cms.winlink.org</a> through port 8772...<br>>>>> Successfully connected to a CMS through port 8772 in 253 Milliseconds<br>>>>><br>>>>> Testing CMS SSL telnet connection to <a href="http://cms.winlink.org" target="_blank">cms.winlink.org</a> through port<br>>> 8773...<br>>>>> Successfully connected to a CMS through port 8773 in 311 Milliseconds<br>>>>><br>>>>> Testing API service access through port 443 to api.winlink.org...<br>>>>> Successfully performed API service to <a href="http://api.winlink.org" target="_blank">api.winlink.org</a> through port<br>>> 443<br>>>>> in 756 Milliseconds<br>>>>><br>>>>> Testing Autoupdate server access through port 443 to<br>>>>> autoupdate2.winlink.org...<br>>>>> Successfully checked autoupdate server through port 443 in 439<br>>>>> Milliseconds<br>>>>><br>>>>> Testing connection to web site - <a href="http://www.winlink.org:443" target="_blank">www.winlink.org:443</a><br>>>>> Successfully connected to <a href="http://www.winlink.org" target="_blank">www.winlink.org</a> through port 443 in 47<br>>>>> Milliseconds<br>>>>><br>>>>> Testing FTP connection to SFI site -<br>>>>> <a href="ftp://ftp.swpc.noaa.gov/pub/latest/SGAS.txt" target="_blank">ftp://ftp.swpc.noaa.gov/pub/latest/SGAS.txt</a><br>>>>> Successfully connected to<br>>> <a href="ftp://ftp.swpc.noaa.gov/pub/latest/SGAS.txt" target="_blank">ftp://ftp.swpc.noaa.gov/pub/latest/SGAS.txt</a><br>>>>> through port 20/21 in 1522 Milliseconds<br>>>>><br>>>>> Test completed successfully.<br>>>>><br>>>>> -Scott, NS7C<br>>>>><br>>>>><br>>>>><br>>>>> On Mon, Mar 15, 2021 at 5:45 PM Stephen Kangas <<a href="mailto:stephen@kangas.com" target="_blank">stephen@kangas.com</a>><br>>> wrote:<br>>>>><br>>>>> Phil, an example of the ham band traffic that Kenny mentioned is not<br>>>>> permitted by the FCC is encrypted communications traffic…this means the<br>>>>> majority of websites your visit today and many email hosters, since<br>>>>> websites commonly use TLS/SSL encryption (indicated by “https” in front<br>>> of<br>>>>> the URL in your browser address bar) or encrypted settings in your email<br>>>>> hoster & client. Winlink does NOT use encryption, thus is legal, and is<br>>>>> the primary application for my ARES team using HamWAN. As Kenny points<br>>>>> out, certain routers (not inexpensive home models) can be used to split<br>>>>> that traffic appropriately, but it is not an easy setup unless you have<br>>> a<br>>>>> background in data networks or cybersecurity…so it’s far easier to<br>>> either<br>>>>> use HamWAN just for your dedicated ARES laptop use or switch a cable<br>>> back<br>>>>> and forth using one pipe at a time.<br>>>>><br>>>>><br>>>>><br>>>>> FWIW, Stephen W9SK<br>>>>><br>>>>><br>>>>><br>>>>><br>>>>><br>>>>> *From:* PSDR <<a href="mailto:psdr-bounces@hamwan.org" target="_blank">psdr-bounces@hamwan.org</a>> *On Behalf Of *Kenny Richards<br>>>>> *Sent:* Monday, March 15, 2021 12:49 PM<br>>>>> *To:* Puget Sound Data Ring <<a href="mailto:psdr@hamwan.org" target="_blank">psdr@hamwan.org</a>><br>>>>> *Subject:* Re: [HamWAN PSDR] Newbie<br>>>>><br>>>>><br>>>>><br>>>>> Just want to add two things to what Carl said already.<br>>>>><br>>>>><br>>>>><br>>>>> 1) Line of sight means you can actually 'see' the HamWAN node, or at<br>>> least<br>>>>> you can with something like a pair of binoculars.<br>>>>><br>>>>><br>>>>><br>>>>> 2) Remember that HamWAN is not meant to be a replacement for your home<br>>>>> internet. Be very conscious of what traffic you are putting over<br>>> HamWAN. I<br>>>>> don't recommend connecting it to your home network unless you are<br>>> familiar<br>>>>> enough with routing rules to limit what traffic goes out the HamWAN<br>>> link.<br>>>>><br>>>>><br>>>>><br>>>>> Good luck,<br>>>>><br>>>>> Kenny, KU7M<br>>>>><br>>>>><br>>>>><br>>>>><br>>>>><br>>>>> On Mon, Mar 15, 2021 at 12:40 PM <<a href="mailto:carl@n7kuw.com" target="_blank">carl@n7kuw.com</a>> wrote:<br>>>>><br>>>>> Hi Phil,<br>>>>><br>>>>> You can do all of the configuration while on the ground, but obviously<br>>> you<br>>>>> won’t have any signal. You don’t indicate what specific equipment you<br>>> have,<br>>>>> but if you have the mAnt30 dish and separate router/modem, make sure you<br>>>>> have the antenna connected before powering it up.<br>>>>><br>>>>><br>>>>><br>>>>> As to trees, they are an absolute show stopper. You must have clear,<br>>>>> visual, line of sight to the HamWAN site you are shooting to. Hopefully<br>>> you<br>>>>> will have that, or can achieve that, from where you plan to mount the<br>>>>> dish. As to “just over them”, a microwave shot consists of the direct,<br>>>>> pure line of sight, but also what is referred to as the Fresnel zone – a<br>>>>> cigar shaped “balloon” around the pure line of sight. Items in the<br>>> Fresnel<br>>>>> zone (including trees) can reduce the amount of signal you have, so you<br>>> may<br>>>>> not get optimum performance, but some.<br>>>>><br>>>>><br>>>>><br>>>>> In your initial post you commented about how to balance between your<br>>>>> regular internet and HamWAN for a Winlink node. My suggestion would be<br>>> to<br>>>>> just leave it on one (whichever one) as the norm, and only switch to the<br>>>>> other if the one goes down. You can also acquire routers that include<br>>>>> failover capability to automatically make that switch. You can go more<br>>>>> advanced with load sharing and such between multiple connections, but<br>>> that<br>>>>> requires much better understanding of internet routing, and for a<br>>> winlink<br>>>>> node basic failover will serve your purpose.<br>>>>><br>>>>><br>>>>><br>>>>> Good luck, let us know how things turn out.<br>>>>><br>>>>> Carl, N7KUW<br>>>>><br>>>>><br>>>>><br>>>>> *From:* PSDR <<a href="mailto:psdr-bounces@hamwan.org" target="_blank">psdr-bounces@hamwan.org</a>> *On Behalf Of *Phil Cornell via<br>>>>> PSDR<br>>>>> *Sent:* Monday, March 15, 2021 12:11 PM<br>>>>> *To:* <a href="mailto:psdr@hamwan.org" target="_blank">psdr@hamwan.org</a><br>>>>> *Subject:* [HamWAN PSDR] Newbie<br>>>>><br>>>>><br>>>>><br>>>>> OK, I figured out my problem and I now have Winbox talking to the radio<br>>>>> and reporting status. I's not linking to anything since the antenna is<br>>>>> still on the ground. How much configuration can I do before mounting<br>>> it on<br>>>>> my roof. The only question in my sight path may be some trees but I<br>>> think<br>>>>> I can aim just over them and get a signal. My friend Bruce/WA7BAM will<br>>> be<br>>>>> helping with the antenna installation on Wed afternoon. Making<br>>> progress...<br>>>>><br>>>>><br>>>>><br>>>>> *Phil Cornell *<br>>>>><br>>>>> *W7PLC *<br>>>>><br>>>>> *SHARES NCS590*<br>>>>><br>>>>> *Hybrid Gateway W7PLC*<br>>>>><br>>>>> *TCARES VP*<br>>>>><br>>>>><br>>>>><br>>>>><br>>>>><br>>>>><br>>>>><br>>>>><br>>>>><br>>>>> _______________________________________________<br>>>>> PSDR mailing list<br>>>>> <a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>>>>> <a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>>>>><br>>>>> _______________________________________________<br>>>>> PSDR mailing list<br>>>>> <a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>>>>> <a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>>>>><br>>>>><br>>>>><br>>>>><br>>>>> --<br>>>>><br>>>>> *-Scott*<br>>>>> _______________________________________________<br>>>>> PSDR mailing list<br>>>>> <a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>>>>> <a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>>>>><br>>>><br>>>><br>>>><br>>>> _______________________________________________<br>>>> PSDR mailing list<br>>>> <a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>>>> <a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>>>><br>>> _______________________________________________<br>>> PSDR mailing list<br>>> <a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>>> <a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>>><br>> <br>> <br>> _______________________________________________<br>> PSDR mailing list<br>> <a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>> <a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><br>> <br>_______________________________________________<br>PSDR mailing list<br><a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br><a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><o:p></o:p></p></blockquote></div><p class=MsoNormal>_______________________________________________<br>PSDR mailing list<br><a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br><a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><br clear=all><o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div><p class=MsoNormal>-- <o:p></o:p></p><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div><p class=MsoNormal><span style='color:blue'>John D. Hays</span><br><span style='color:black'>Kingston, WA</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='color:gray'>K7VE / WRJT-215</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='color:blue'> </span><o:p></o:p></p></div><div><p class=MsoNormal align=right style='text-align:right'> <o:p></o:p></p></div><div><p class=MsoNormal align=right style='text-align:right'> <o:p></o:p></p></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><p class=MsoNormal>_______________________________________________<br>PSDR mailing list<br><a href="mailto:PSDR@hamwan.org">PSDR@hamwan.org</a><br><a href="http://mail.hamwan.net/mailman/listinfo/psdr">http://mail.hamwan.net/mailman/listinfo/psdr</a><o:p></o:p></p></div></blockquote></div></div></body></html>