On Mar 12, 2010, at 11:28 AM, Nate Duehr wrote:
On 3/12/2010 11:08 AM, John Hays wrote:
I would avoid the complexity of domain names as you outline here.
The bandwidth of the D-STAR DD stream doesn't bode well for
supporting "server" applications at the "last mile" ID-1.
If you mean putting the server application at the ID-1 end of
things, absolutely right. That'd suck.
I was speaking of putting that functionality in the Gateway/Router/
whatever you want to call it.
(You're saying you're "creating" the concept of a DD Router, when
that's exactly what the Gateway is doing with DD packets already --
just a very poor implementation. I would NOT want an ADDITIONAL
fragile PC up at the repeater site to handle DV and DD separately.
That's a poor use of both hardware resources (two machines where one
can easily do this job) and human resources (two machines will break
twice as often, and require site visits commensurately - doesn't
follow the KISS principal.)...
...
Nate WY0X
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 router 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.
John D. Hays
Amateur Radio Station K7VE
PO Box 1223
Edmonds, WA 98020-1223 VOIP/SIP: [email protected]
Phone: 206-801-0820
801-790-0950
Fax: 866-309-6077
Email: [email protected]
