I'm replying to the main thread, as Rob still insists with posting using his broken MUA which breaks threading, making it impossible to follow his ramblings. Thanks Rob.

It is not convenient for me either! But I don't want to forward this list as separate mails as sometimes there are frantic discussions about topics that do not interest me at all (like RPKI) and I don't want my mail bell to ring all day (and load amsat.org with forwarding all those messages). So I am subscribed to the digest only, I sometimes watch the archives for quicker responses, and I cannot reply with the proper threading.

I think I have mentioned it before: this list should be a newsgroup on an NNTP server. If only to honor Brian Kantor. Accessing it via a usenet news reader would be so much more convenient, you can just read it when you like and kill uninteresting threads. Or otherwise just use a forum.

Having reverse DNS with a callsign in it doesn't meet identification requirements in the ITU or FCC rules, assuming the packet is traversing an RF link on amateur frequencies. Under FCC rules (and I'm aware you may be under a different legal authority), the control operator is the required ID, not the originator of the packet.

It is not only about regulatory ID requirements but also about identifying who is behind some traffic. Many places have "relaxed firewall rules" for traffic originating from within AMPRnet. This already requires revision due to the sale of the upper block (I think that lots of firewall rules still mention 44.0.0.0/8) but also with more and more blocks being routed directly and having no transparency about the actual use of that space, I would like to know if some address is really an amateur or if someone has lend it out to shodan.io or stretchoid.com. And if so, at least know who is responsible for that.

When that is not feasible, we will have to become more and more closed and more like the general internet (default drop everything).

Rob