On Wed, Feb 6, 2013 at 2:38 PM, Jay Nugent <jjn@nuge.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Greetings,


On Wed, 6 Feb 2013, Rob Janssen wrote:

(Please trim inclusions from previous messages)
_______________________________________________
44net-request@hamradio.ucsd.edu wrote:
 the DNS functionality is a separate module and is not tied to the name of
 the IP/subnet, not everyone uses their callsign as the DNS name

But that is a license requirement!   We need a mapping between IP address and callsign for legal use of IP on amateur radio....
(ID requirement)

   Not that I am aware of.  The IP traffic has NEVER required any callsign identification.  Nor has the TCP traffic.  Transmissions over the air are always carried atop layer 2, which is the AX.25 Link Layer protocol.  The transmitters on each end of every radio link use the callsign to identify each and every frame sent over the air.  Our callsigns are used in AX.25 Link Layer in the same way that MAC addresses are used in the 802.3 ethernet layer 2 / link layer protocol. Take a look at your ARP table to confirm this.

   The "transmitters" must be identified, and they may identify *within* the published protocol (in this case AX.25).  This is all that the FCC requires.

      --- Jay Nugent  WB8TKL
          Michigan IP coordinator (44.102/16)


This is fine if you are using AX.25  for link layer media, but I don't see AX.25 being the only link layer used on AMPRNET by a long shot.  802.11 is growing in use and other link layer technologies exist.  While info from DNS may not meet a requirement for Identification requirement, having the callsign of the party responsible (either directly as in the case of a gateway, or indirectly as in the case of an ISP) for the host required as part of the FQDN is helpful in tracing network issues.

AF6EP