On May 14, 2009, at 1:40 PM, Nate Duehr wrote: > > > (FIlters at the gateway could manage who could and could not use a > > given gateway - and callsign pattern matching, e.g. regex, could > > filter out most bogus callsigns) > > I don't like the idea of filtering "bogus" callsigns. What might be > "bogus" to you, might be my special event's tactical callsigns. > (There's nothing stopping anyone from registering "SAG1, SAG1, NET, > EVENT", etc.) >
Here is my thought on this. Radios should be identified by their official callsign (and optional designator character), tactical / special event callsigns can be put into the 4 char comment, on voice, or in the message field for SMS. Certainly, the local repeater could be allowed to pass tactical radio callsigns, but across the network you are just asking for routing errors if more than one station decides their callsign of the day is "TAC1" or "BASE" or "EOC" (mitigated by registration, but then only one station in the entire network can be "TAC1", in a dynamic addressed network it would be anarchy). I know you know it, but the callsign is the routing address in D-STAR. The filter would have to be pretty "loose" but keep it to looking something like a callsign and definitely could filter certain profane words. John Hays Amateur Radio: K7VE [email protected] [Non-text portions of this message have been removed]
