Australia has a long relationship with callsigns. Over time the regulator, today the ACMA, the Australian Communications and Media Authority, has seen fit to introduce different types of callsigns and restrictions associated with those callsigns.

The change that made the most waves most recently was the introduction of the so-called F-call. It's a callsign that looks like mine, VK6FLAB. It has a VK prefix for Australia, the number 6 indicating my state, Western Australia, then the letter F, followed by a suffix of three letters.

This type of callsign was introduced in 2005. To this day there are plenty of amateurs on-air who don't believe that this is a real callsign, to the point where some refuse to make contact, or worse, make inflammatory statements about getting a real callsign, and that's just the letters, let alone those who think that the callsign denotes a lack of skill or knowledge demanding that the amateur "upgrade" their license to a real one.

At the time of introduction, the apparent intent was to indicate that the holder was licensed as a Foundation or beginner. In 2020 this was changed, and existing F-call holders were able to apply for a new callsign if they desired. Some did, many did not. Currently there are 1,385 F-calls active and there are 3,748 Foundation class callsigns in the registry.

After this change, you might think that all callsigns in Australia are now either two or three letter suffixes, as-in VK6AA or VK6AAA. Actually, the F-call continues to exist and there are now also two by one calls, VK6A, intended for contesters.

A popular idea is that the F-call is for Foundation license class amateurs only. There are currently 10 Standard and 16 Advanced license classed holders with an F-call. There are also two special event callsigns that sport an F-call.

With the addition of contest callsigns, new prefixes, VJ and VL, were introduced which brought with it the notion that you could use those new prefixes for your callsign. Currently, only contest callsigns are allocated with VJ and VL prefixes.

An often repeated idea is that we're running out of callsigns. Well, there are 1,434,160 possible callsigns if we count each prefix, each state, single, double, triple and F-calls across all prefixes. As it happens, there are at present 15,859 assigned and 53 pending callsigns.

If not all, then surely, we're running out of real callsigns. Nope. If we look at the VK prefix alone, less than 10% of available callsigns have been allocated.

Okay, we've run out of contest callsigns. Nope. There are 1,040 possible contest callsigns and only 188 allocated.

Another popular notion is that we've run out of two-letter callsigns, that is, the suffix has only two letters. Again, no. There are 3,553 allocated out of 6,760, less than 53% has been assigned.

Surely, some states appear to have run out of two-letter callsigns. Well, maybe. Theoretically each state has 676 two-letter callsigns but none have all of those allocated. For example, VK3, with 675 allocated two-letter suffixes, is missing VK3NG for no discernible reason. More on the missing ones shortly. It's impossible to use the current register to determine how many amateurs hold more than one two letter callsign.

Another notion is that you can have a special event callsign as long as it starts with VI. As it happens there are currently special event callsigns registered with VI, VK and AX prefixes. Just over half of them have any online activity to promote the callsign for their event.

You might think that a callsign can only be "Assigned" or "Available". According to the register a callsign can be "Pending", it can also be "Reserved", more on that in a moment, and it can not be in the list at all, "Missing" if you like. Take for example JNW, it's assigned in VK2, it's available in all other states, except VK3 where it simply doesn't exist. This oddity doesn't restrict itself to VK3. Take XCA, available in all states, except VK4. TLC doesn't exist in VK2. Many more examples to go round.

And that's not looking at exclusions due to swear words and reserved words like PAN; but SOS is an assigned callsign. Combinations that you think might be unavailable, like QST, are fine, except in VK2 where it doesn't exist.

It's thought that reservations are only for repeaters. Nope. Suffixes with GG followed by a letter are reserved for the Girl Guides, those that start with S followed by two letters are reserved for Scouts, those starting with WI are for the Wireless Institute of Australia and those with IY are for the International Year of something. Interestingly there is no reference to repeaters or beacons at all in the callsign register since they fall under the old license regime, rather than the new amateur class. And you thought that the system was getting simpler and cheaper to run.

You might think that every state has the same number of callsigns. Ignoring F-calls, VK5 has the most callsigns available and VK3 the least. No doubt this is due to the callsigns that are "Missing" from the register.

This likely leaves you with plenty more questions, but next time someone asserts something about callsigns, perhaps it's time to have a think before you spout.

Note that this information is based on the ACMA callsign register as I found it on the 29th of June 2024. This started as an exploration of just how many different amateur calls were registered.

At the time there were 3,748 Foundation class, 2,079 Standard class and 9,946 Advanced class callsigns assigned or pending.

Without knowing how many callsigns each amateur has been assigned, it's impossible to know just how many amateurs those 15,773 callsigns represent. Perhaps it's time for the regulator to start publishing some data on our community, rather than relying on the likes of me to download 1,774 pages of data and two days analysing it.

I can tell you that I have been assigned two callsigns, one for day-to-day use and one I use for digital modes and contests, given that WSPR doesn't play nice with VK6FLAB and I really have no desire to give up my call.

Before I go, every VK callsign also has an AX equivalent on three days every year, 26 January, 25 April and 17 May and as I said, you can apply for a special event callsign with an AX prefix.

I'm Onno VK6FLAB

Over the past week I've been attempting to work out what the IARU, the International Amateur Radio Union, actually does and how it works. I started looking into this because the IARU is this year celebrating a century since its foundation in 1925. You might think of the IARU as one organisation, but behind the scenes there are actually four, one for each so-called "Region" as well a Global organisation called the International Secretariat, headquartered at the ARRL in Connecticut.

The Regions have been negotiated by members of the ITU, the International Telecommunications Union. As early as 1927 the ITU documented differences in frequency allocations between Europe and Other Regions. In Cairo in 1938 it defined boundaries for Europe. In Atlantic City in 1947, the ITU defined three Regions, with specific boundaries, essentially, Europe and Africa, the Americas and the rest of the world.

As a surprise to nobody, this is purely a political decision, especially since radio waves don't get to have a passport and pass border control. The impact of this continues today, generations later. We still have this patchwork of frequency allocations, we still have exclusions, different band-edges and other anachronisms.

The Regions are further divided into Zones. When you start looking at the ITU zone map in detail it gets weird. For example, Iraq is in Region 1, neighbouring Iran has been specifically excluded from Region 1 and moved to Region 3. In case you're curious, Iran has been represented at the ITU since 1938.

Antarctica is part of seven of the 90 ITU zones and all three Regions, because of course it is.

Zone 90, jammed between zones 35, 45, 61, 64, 65 and 76, almost as an afterthought, contains one landmass, Minamitorishima, an island that sticks 9 m above the water, has a 6 km coastline and is generally off-limits to the general public. The nearest land in any direction is over 1,000 km away. It's got an IOTA, Islands On The Air, designation, OC-073 and despite its isolation, has been activated by radio amateurs using JD1 prefix callsigns.

I live in Australia, ITU zone 58, part of Region 3, together with the two most populous countries on the planet, India and China and the rest of eastern Asia, but not the Former Soviet republics and most, but not all of Oceania, you know, because .. logic. From a population perspective Region 3 is the largest by several orders of magnitude, but you'd never know it if you went looking.

Why am I telling you all this?

Well, that's the international stage on which the IARU is representing amateur radio. In 1927 the underlying assumption was that each service, Amateur Radio included, had a global exclusive allocation. The reality was different. Spectrum was in such short supply that individual exceptions were carved out, which as I've said resulted in splitting up the world into regions, starting in 1938 and codified in 1947.

The IARU in 1925 is a different organisation from what it is today. In 1925 individual amateurs could become members. As soon as enough members from a country joined, they'd be grouped together. When there were enough groups, the IARU became a federation of national associations.

Over time, the IARU as a single body, evolved into the structure we have today. In 1950 in Paris, the IARU Region 1 organisation was formed. In 1964 in Mexico City, IARU Region 2 was created and in 1968 in Sydney, IARU Region 3 came to exist. You can see their online presence at the various iaru.org websites.

How it works is no clearer now than it was when I started. What it has achieved is equally unclear. I'm currently trolling through ITU World Radiocommunications Conference documentation going back to 1903 to discover references to Amateur Radio, but it's hard going. At least it's something. The IARU documentation is not nearly as extensive or up to date.

It appears that many, if not all, of the people working behind the scenes at the various IARU organisations are volunteers. If you feel inclined, there is an ongoing request for assistance, and before you ask, yes, I looked into helping out, but that will have to wait until funds permit.

If you have insights into the functioning of the IARU, don't be shy, get in touch. [email protected] is my address.

I'm Onno VK6FLAB

#ARDC

Australian Research Data Commons

meet

Amateur Radio Digital Communications

Gotta love acronyms..

My search has been without results.

My "new" model remote with a Siri button keeps needing to be reset to control my infrared amplifier. Press and hold the Volume Down and TV button works, but it's annoying when you want to change the volume whilst watching something and it doesn't respond.

Firmware version is 0x83.

Anyone got any ideas what might be causing this?

I've been using VMware for about two decades. I'm moving elsewhere. KVM appears to be the solution for me.

I cannot discover how a guest display is supposed to work.

On VMware workstation/Fusion the application provides the display interface and puts it into a window on the host. This can be resized to full screen. It's how I've been running my Debian desktop and probably hundreds of other virtual machines (mostly Linux) inside a guest on my MacOS iMac.

If I install Linux or BSD onto the bare metal iMac, how do KVM guests show their screen?

I really don't want to run VNC or RDP inside the guest.

I've been looking for documentation on this but Google search is now so bad that technical documents are completely hidden behind marketing blurbs or LLM generated rubbish.

Anyone?

So, I have a confession. I don't know everything. Shocking right?

Over the past too many months, actually, come to think of it, years, I have not been on-air with my station on HF using FT8 or Olivia, modes that use tools like "WSJT-X" and "fldigi". This has not always been the case. For a time I used a tiny computer running those tools. It had plenty of issues related to its size and capacity. Overwhelmingly it was slow, unsurprising since it was released in 2009. After one particularly frustrating session where I had to recompile WSJT-X on an older 32-bit operating system using an Atom processor, I decided that this was not helping me, and I put it away.

The idea was to use my main computer that could do all the heavy lifting without cracking a sweat. To make this happen the traditional way, I'd be expected to physically connect the radio to the computer. I'm not a fan of doing that, given the potential damage that RF could do to my computer, not to mention that I have a sit-stand desk on wheels that I move around my office as the mood or the light takes me, if you're interested, I found a mobile lectern that the computer is clamped to. Works great, been using it for years.

RF aside, moving around the office is not conducive to plugging in a radio that comes with power, coax, audio, control, microphone and expects to have some space around it to actually use it. No problem, I have a RemoteRig, a device that comes in two parts. You connect one unit to the radio, the other to the head, that is, the removable faceplate of the radio, and using a network connection, you can have the head in one place and the radio in another. The two units don't have to be in the same room, let alone the same country.

I figured that I could replace the second half of the system, the head and its unit, and instead use software on my computer to get the same functionality and be up and running in minutes. That was several years ago. Interestingly, whilst I'm putting this together I did a search for "RemoteRig protocols" and learnt a few things, so perhaps this path isn't quite as dead as I feared. I've reached out to Mikael SM2O and if that comes to anything I'll let you know.

In the meantime I've been trying to figure out how to operate my radio in software only. I can control the radio if I physically connect a computer like a Raspberry Pi to it and use "rigctld" to interact with it. This gives me access to all the standard CAT, or Computer Assisted Tuning commands. In other words, I can change band, mode, frequency, trigger the transmitter, all the stuff that you need to get on-air to make noise.

There's only one bit missing, the noise, as-in audio, either coming from the radio, or going to it. I suppose I could trigger a carrier and use it to send Morse, but that doesn't give me receive capability. I've tried using network audio using "pulseaudio" - it never worked right. I've made USB hot-plug scripts that allow you to connect a USB device into a computer and access it across the network on another computer - it mostly works for sound, but reliable is not a word I'd use. I've looked at using the USB sound card in the audio mixer on my desk, but it's subject to all manner of funky restrictions and random audio dropouts. I could use a virtual screen and connect to a Raspberry Pi that's physically connected to the radio, but that's leaving all the hard work on the Pi, rather than the computer that I'm currently using with several orders of magnitude more capability.

Whilst we're discussing this, one of the reasons I like the idea of a software defined radio like a PlutoSDR, is that the stuff coming out of the radio, and going into it for that matter, is already digital. It takes away a whole lot of complexity, admittedly replacing it with software, but that's where I feel more comfortable.

Which brings me to you.

As I said, I don't know everything.

What are you doing in this space? Are you actually on-air with your contraption, or is it still in the planning stages? Are you sending audio, or digital data across the network? Does your system have the ability to swap out a radio and replace it with something completely different? Do you rely on functions available on the radio, or could it be used for a 1950's valve radio, a twenty year old one, a current model, or any number of software defined radios without issues? Finally, is it Open Source?

I confess that I'm not holding my breath for an answer, but there is a chance that you're similarly intrigued by this collection of questions that you will poke your head above the fence and make yourself known.

I'm Onno VK6FLAB

The recent "incident" at the ARRL in which it disclosed that it was the "victim of a sophisticated network attack by a malicious international cyber group" brings into focus some serious questions around our community in relation to identity and privacy.

Let's start with your callsign. Right now in Australia you can use the official register to look for VK6FLAB. When you do, you'll discover that it's "Assigned to Foundation". That's it. No mention of who holds it, where it's registered or how to contact the holder, none of that.

In the case of my callsign, because I haven't surrendered my apparently now legally useless license, you can still search the previous system, the Register of Radiocommunications Licenses and discover that it's held by me, but as soon as it expires, that record will vanish and the relationship between me and my callsign will be lost to the public.

Also, there are no dates associated with any of this. You cannot use the current or previous system to discover if I held my callsign in November 2010 or not. In case you're wondering, no, I didn't, I was licensed a month later. Right now if you look for VK6EEN on QRZ.com, you'll see that it's linked to CT1EEN, but when was that information last updated? I know for a fact that I became the holder in November 2020. It appears that Sam CT1EEN used it around the turn of the century, about 24 years ago, but precisely when and for how long, is unclear.

So, from a public disclosure perspective, the links between me and my callsigns are tenuous at best.

Before I continue, I will point out that this is not unusual. For example, you can see the number plate on my car as I drive down the street, but most people don't have the ability to link it to me.

Similarly, Ofcom in the United Kingdom released a list of allocated amateur callsigns after a freedom of information request. It's unclear if this information is updated, or if it requires a new request each time. Like Australia, the dataset contains the callsign, the type of license and when the record was last updated. Nothing else.

In contrast, the United States has a full license search that returns name, address, issue and expiry dates. Japan offers both a search tool and downloads. Interestingly you can see if a callsign was previously licensed and when, but not by whom.

No doubt each country has their own interpretation in relation to how this is handled and as was the case in Australia, this is ever changing.

This leaves us with an interesting phenomenon.

We use callsigns on-air to identify ourselves, but the relationship between the callsign and our identity, let alone when, is not guaranteed for a significant proportion of the amateur community.

So, how does this relate to the ARRL incident?

Radio amateurs like to make contacts with each other and collect those contacts like you might collect stickers or postage stamps. For decades we've used QSL cards, essentially a postcard sent from one amateur to another to confirm a contact. When you collect enough cards, you can apply for an award, like the DXCC, showing that you made contact with one hundred different so-called DX entities.

In the era of computing, some organisations, like the ARRL, came up with the idea of using the internet to exchange these contacts instead of using a postcard. This reduced delays and was presented as a system to make the process more secure by requiring that people electronically sign their contacts, but could only do so after identifying themselves using traditional means, like providing copies of their license, their passport, etc. The ARRL called it Logbook of the World, or LoTW, and it was adopted by the amateur community around the globe.

While the ARRL continues to state that it only holds public information on its member database, it has made no such assurances about the LoTW system. There is personal and private information that the ARRL has and there is no indication at all what happened to it.

Other systems such as QRZ, eQSL, Clublog and Hamlog offer similar systems with various levels of authentication and verification. A new player, HQSL, is confusing the issue by offering cryptographically signed QSL cards, boasting that their system is decentralised and not restricted to any single service, but immediately requires that you sign-up with Hamlog to get going.

So, we have several organisations offering electronic logging, contact confirmation and security which claim to guarantee that this callsign contacted that callsign at a time and date, on a band, using a mode.

One problem.

None of this is real.

For starters, there is no guarantee that the station operating VK6FLAB was me. There is also no record guaranteeing that I'm the holder of VK6FLAB, or any proof that I am who I say I am. There is also no guarantee that the person confirming a contact between VK6FLAB and you is me. So, we're creating a phantom secure system that's attempting to fix the wrong problem.

In golf, when you start playing for rankings, rather than a round at the 19th hole, the process used to verify your score is dependent on peer review. You cannot mark your own score-card, someone else does.

In amateur radio we've built this electronic house of cards to track whom we've talked to and when, but it's a mirage when looked at closely.

While a DXCC award is worth nothing more than a personal achievement, we cannot go on pretending that identity verification services like LoTW are real, nor can we continue to accept that organisations like the ARRL should demand and store valuable identity information.

I'm Onno VK6FLAB

There is a growing trend where organisations are strictly limiting the amount of information that they disclose in relation to a data breach. Linked is an ongoing example of such a drip feed of PR friendly motherhood statements.

As an ICT professional with 40 years experience, I'm aware that there's a massive gap between disclosing how something was compromised, versus what data was exfiltrated.

For example, the fact that the linked organisation disclosed that their VoIP phone system was affected points to a significant breach, but there is no disclosure in relation to what personal information was affected.

For example, that particular organisation also has the global headquarters of a different organisation in their building, and has, at least in the past, had common office bearers. Was any data in that organisation affected?

My question is this:

What should be disclosed and what might come as a post mortem after systems have been secured restored?

If you've heard the phrase "shortwave listeners", you might have wondered what on earth that was all about.

It relates to the length of a radio wave used to transmit information. The length of a radio wave is tied to its frequency. The longer the wave, the lower the frequency.

When radio amateurs talk about bands, like for example the 40m band, we're talking about a range of frequencies where the wavelength is around 40m. From a frequency perspective, this is around 7 MHz. The 160m band, at about 1.8 MHz, or 1,800 kHz is considered the beginning of the short wave bands.

This implies that there are longer waves as well. If you've ever seen or owned a mid 1980's transistor radio, you'll have seen the notation MW, which stands for Medium Wave, today it's called the AM band. Older radios might have the notation LW, or Long Wave.

The medium wave band is a broadcast radio band that runs between about 500 and 1,700 kHz. The wave length is between 600 m and 170 m.

When radio was still in its infancy, there was also a popular long wave band, with wavelengths between 800 m and 2,000 m, or 150 to 375 kHz.

Today much of that has gone by the wayside. With the advent of digital radio, in Australia it's called DAB+, Digital Audio Broadcasting, the whole idea of "wave" has pretty much vanished.

Some countries like Japan and the United States are in the process of discussing the phasing out of the AM broadcast band. Much of that appears to be driven by car manufacturers who claim that the AM band is no longer useful or used, but forget to tell anyone that they really want to stop having to put AM radios in their cars because it's difficult to isolate the electrical noise from their modern contraptions in order to make it possible to actually listen to that band.

If you ask me, it's a good incentive to make electronics RF quiet, something which is increasingly important in our wirelessly connected world.

This might lead you to believe that all activity on air is moving to higher and higher frequencies, but that's not the case. The properties that made long wave and medium wave radio possible in the early 1900's are still valid today. For example, there are WSPR or Weak Signal Propagation Reporter beacons on the 2200m band, or at 136 kHz.

Whilst your RTL-SDR dongle might not quite get down that low, most of them start at 500 kHz, you don't need to spend big to start playing. My Yeasu FT-857d is capable of tuning to 100 kHz, plenty of space to start listening to the 2200m band, even if I cannot physically, or legally, transmit there.

If you want to build your own receiver, you can check out the weaksignals.com website by Alberto I2PHD where you'll find a project to build a receiver capable of 8 kHz to 900 kHz using a $50 circuit board.

If that's not enough, there's radio experimentation happening at even lower frequencies. Dedicated to listening to anything below 22 kHz, including natural RF, with a wavelength greater than 13 km, Renato IK1QFK runs the website vlf.it where you'll find receivers and antennas to build.

Given that most sound cards operate up to around 192 kHz, you can start by connecting an antenna to the microphone port of your sound card and use it to receive VLF or Very Low Frequencies. On your Linux computer you can use "Quisk" to tune.

There are VLF transmitters on air. For example, SAQ, the Grimeton Radio Station in Sweden opened on the 1st of December 1924. Capable of 200 kW, today it uses about 80 kW and transmits twice a year on 17.2 kHz.

While we search for higher and higher frequencies, there is still plenty of fun to be had at the other end of the radio spectrum. Consider for example that VLF or Very Low Frequency radio waves, between 3 and 30 kHz can penetrate seawater.

I'll leave you to explore.

I'm Onno VK6FLAB

Updated 6/4/2024

On or around May 12, 2024, ARRL was the victim of a sophisticated network attack by a malicious international cyber group. ARRL immediately involved the FBI and engaged with third party experts to investigate.

This serious incident was extensive and categorized by the FBI as “unique,” compromising network devices, servers, cloud-based systems, and PCs.

ARRL management quickly established an incident response team. This has led to an extensive effort to contain and remediate the networks, restore servers, and staff are beginning the testing of applications and interfaces to ensure proper operation.

Thank you for your patience and understanding as our staff continue to work through this with an outstanding team of experts to restore full functionality to our systems and services.

We will continue to update members as advised and to the extent we are able.

Today I want to talk about something that might feel only tangentially related to our hobby, but it likely affects you.

Recently the ARRL announced that it was "in the process of responding to a serious incident involving access to our network and headquarters-based systems". A day later it sought to assure the community that the "ARRL does not store credit card information" and they "do not collect social security numbers" and went on to say that their "member database only contains publicly available information". Five days after that it's "continuing to address a serious incident involving access to our network and systems" and that "Several services, such as Logbook of The World(R) and the ARRL Learning Center, are affected.", but "LoTW data is secure". Over a third of the latest announcement, more than a week ago, was to assure the community that the July QST magazine is on track but might be delayed for print subscribers.

Regardless of how this situation evolves, it's unwelcome news and much wider reaching than the ARRL.

LoTW, or Logbook of The World, is used globally by the amateur community to verify contacts between stations. The IARU, the International Amateur Radio Union, is headquartered at the ARRL office.

I've been told that I should have empathy and consider that the ARRL is only a small organisation that may not have the best of the best in technology staff due to budget constraints and finally, that LoTW being down for a few days is not going to kill anyone.

All those things might well be true and mistakes can and do happen.

The ARRL has been in existence for well over a century, bills itself as the answer to "When All Else Fails" and has even registered this as a trademark, but hasn't actually said anything useful about an incident that appears to have occurred on the 14th of May, now over two weeks ago. By the way, that date is based on the UptimeRobot service showing less than 100% up-time on that day, the ARRL hasn't told us when this all occurred, it didn't even acknowledge that anything was wrong until two days later.

This raises plenty of uncomfortable questions.

What information did you share with the ARRL when you activated your LoTW account? For me it was over a decade ago. I jumped through the hoops required and managed to create a certificate. What information I shared at the time I have no idea about. As I've said before, I do know that security was more extreme than required by my bank, even today, and the level of identification required was in my opinion disproportionate to the information being processed by the service, lists of amateur stations contacting each-other.

Something to take into account, on the 30th of October 2013, Norm W3IZ wrote in an email to me: "Data is never removed from LoTW." - I have no idea how much or which specific information that refers to.

If you used the ARRL Learning Center, what information did you share? If you're a member of the ARRL, or you purchased something from their online store, what data was required and stored? Is the data at the IARU affected? What infrastructure, other than the office, do they share?

While I've been talking about the ARRL, this same issue exists with all the other amateur services you use. QRZ.com, eQSL.cc, eham.net, clublog.org, your local regulator, your amateur club, your social media accounts, all of it.

What information have you shared?

Do you have an internet birthday, address and middle name?

Recently I received a meme. It shows two individuals talking about life, the universe and everything. They discuss their favourite books, the first movie they ever watched, the name of their pets, what car they learnt to drive in, their interests and other things you talk about when you meet someone new and interesting. The last image of the meme shows the heading: "Security Questions Answered, Welcome Amanda."

So, my question is this: What's your favourite colour and your mother's maiden name?

Seriously, next time you access a service online, have a look at what data that service has. When you sign up, consider the requirements for the service and how much information that's worth. Do you really need to send your birthday, your gender and your physical address with a copy of your passport or another government approved identity document? If you're being asked for the name of your first pet, consider answering something unique. In my case, I generate a random string of characters to use as an answer for each security question.

The ARRL "incident" is the tip of the iceberg. This problem is't going away, it's only going to get bigger and happen more often.

Final observation. With the potential of a global shopping list for thieves coming out of the database at the ARRL, will you be sharing your station address next time and if you're subject to the GDPR, the General Data Protection Regulation, perhaps it's time to ask your online service providers just exactly what they're doing to protect your information, and that includes the ARRL.

I have sent two emails to the ARRL in relation to these questions, but have yet to receive an acknowledgement, let alone answers.

By the time this reaches you, perhaps the ARRL has answers to my questions and more.

I'm Onno VK6FLAB