> There is a certain expectation among D-STAR RF users that if they are > in range of a D-STAR repeater, that provides gateway services, that > they should be able to do callsign routing to any other D-STAR RF user > that is in range of a gateway equipped D-STAR repeater. This means > that they all need to be on the same "trust server" in the current > architecture. As an RF user, I shouldn't need to find out which trust > server the local gateway uses (is it on K5TIT/USTRUST or another trust > server?). I should simply be able to put the callsign in the UR > field, along with the proper RPT1 and RPT2 entries, and make my call.
EXACTLY !!!! David - G4ULF --- In [email protected], John Hays <j...@...> wrote: > > I think the point KE5C and G4ULF are trying to make is this: > > There is a certain expectation among D-STAR RF users that if they are > in range of a D-STAR repeater, that provides gateway services, that > they should be able to do callsign routing to any other D-STAR RF user > that is in range of a gateway equipped D-STAR repeater. This means > that they all need to be on the same "trust server" in the current > architecture. As an RF user, I shouldn't need to find out which trust > server the local gateway uses (is it on K5TIT/USTRUST or another trust > server?). I should simply be able to put the callsign in the UR > field, along with the proper RPT1 and RPT2 entries, and make my call. > > Having other "trust servers" that don't sync with each other, segments > the D-STAR community into cliques -- most of us do not want that, we > want a unified D-STAR network. > > Personally, I would like to see an improved "trust server" with the > following changes: > > 1. RF users don't need to register to be added to the "routing" > tables. The gateway just reports who it hears on the air, and > requests routing information for those callsigns it does not know. > 2. Internet connected nodes have a strong authentication (gateways, > application servers (such as DPLUS and D-EXTRA), reflectors) -- Dongle > type users would come into the network through an application server, > rather than direct -- then they would be treated like other D-STAR > units with callsign routing, etc. > 3. A confederated trust server architecture so that regional trust > servers sync database entries so that a gateway or application server > could ask any trust server for routing information. > 4. A bridge to the Icom architecture and a new "short hand" capability > where "G" nodes don't need to be entered in RPT2 if the controller > sends all traffic to the local gateway. > > Until Scott can take the effort to work with K5TIT to get his code > tested on their test system and have it talk to the USTRUST it will > not be of interest to most repeater/gateway operators. G4ULF has gone > to that effort, so I think we will start saying a lot more homebrew > repeater/gateways coming on line using his code, once his production > beta is complete. > > > On Jul 23, 2009, at 11:24 AM, ham44865 wrote: > > > > > There are 4 European ICOM TRUST servers. > > You would need permission with them to register your > > home-made "ICOM compatible" G2 Gateway, same thing with the US. > > > > I also have instructions on how to create a NEW ICOM > > TRUST server. They have created their own ICOM TRUST server, > > just like K5TIT did. > > > > They are pretty active witrh their ICOM TRUST server > > and they allow registration from anyone that wants to learn. > > I do not believe that they would deny you registration > > if you asked them. > > The Europeans TRUST server groups are very friendly. > > > > My dstar "ICOM compatible" G2 Gateway KJ4NHF > > went live with the European TRUST server a couple of weeks ago. > > > > Scott/KI4LKF > > > > > > > > > > > > > > > > > > > > > > > > > > > John Hays > Amateur Radio: K7VE > j...@... >
