Order Tray | Contact Us | Home | SIG Lists

[linux] Callsign coding (was Take a Stand)

Jeff King jeff at aerodata.net
Thu Oct 14 18:03:52 UTC 2004

I was just pointing out the fact that you don't need to imbed a callsign in 
an IP address to use it over the air. You just need to identify on RF once 
every 10 minutes in the U.S.

I also was commenting, on someone's suggestion "TAPR take a stand", that I'd 
rather see it directly involve amateurs getting on the air, rather then 
devising a "callsign coding" method. Now, if the current RF 44 net amprnet 
was busting at the seams, I might feel different. Bottom line, you don't need 
callsign IP address coding to get on the air and I rather see TAPR focus its 
limited resources on problems that needs solutions.

That much being said, I commend your private efforts.

On Thu, 14 Oct 2004 08:13:04 -0500, Gerry Creager N5JXS wrote:
>My though is that this offers a mechanism for on-air addressing that
> incorporates readable, or readily decodable, callsigns within the
>IP address.  It allows interoperability with the Internet, but it's
>not exclusive to the Internet.  It *can* be used on RF.  The use of
>IPv6 addressing with modified EUI64 callsign encoding was what made
>me present this originally.  It looks like a 'natural' to me.
>We can incorporate a registration and subsequent address assignment
>with the embedded callsign using DHCP6.  This allows the users who
>don't want to learn to code up their own addresses to have 'em auto-
>generated, and, when someone goes to another area and registers with
>THAT network, they get a consistent address, can register with their
>home network, and have data/packets auto-rerouted to them at their
>mobility location.
>73, gerry
>jeff at aerodata.net wrote:
>>I think you all are wasting your time. Just grab a block for
>>amateur radio, if you must, but it is nonsense to try and embedded
>>a callsign in it. The best analogy for the "callsign" would be a
>>MAC address (the transport layer) and, AFAIK, a IP address could
>>care less about the MAC address (except in things like DHCP, and
>>then only to assign the same IP address). The FCC only requires we
>>ident what we actually transmit, not what we send on the internet.
>>Me, I just like radio, and I think amateur radio should be working
>>towards convergence with the real world, not continually trying to
>>set ourselves apart.
>>If TAPR wants to focus on anything, let it be radio, which has
>>(almost) been forgotten, is the key part of our hobby.
>>_______________________________________________ linux mailing list
>>linux at lists.tapr.org https://lists.tapr.org/cgi-

More information about the linux mailing list