On 3/12/2010 12:58 PM, John Hays wrote:
No, I'm saying we create a D-STAR router, a router that routes based
on D-STAR callsigns/addresses -- DD Ethernet packets are just a
payload and a D-STAR router need not concern itself with them at all.
No additional "mountain top" PC is required either; the networking
interface can be on the ro uter as well, or the D-STAR router can
route the DD payload to a Callsign (Address) at some other location
where it can be de-encapsulated and managed at a network level. Once
one quits trying to marry D-STAR to IP protocol (other than as a
transport between D-STAR routers) then it merely moves bits from one
Callsign/Address to another and allows those endpoints to deal with
the complexities of whether its AMBE (DV) or Ethernet (DD) - including
IP, IPX, XNS, DecNet, whatever. Those D-STAR endpoints can be radios
or services (DV Dongles, Network Servers, etc.), it just doesn't
matter to the router.
Ahhhh... I see. You'd prefer D-STAR quit trying to encapsulate in IP
until you hit the very end-points? That's not a bad idea at all. No
lookup tables to map things back and forth, just use the addressing
functionality (callsigns) already built into the on-air protocol.
That definitely follows the KISS principal.
Nate WY0X
