While everything you say may be true, it has absolutely no impact on securing
the system from anonymous abuse.
As simple as it is for DNS to be controlled by root servers and replicated
worldwide, a database of authorized users could as easily be implemented and
replicated to all node, leaving the connectivity architecture intact.
Organizations such as ARRL DARC and other volunteers could easily take on the
task of verifying amateurs for access.
Once completed, it will be a simple task to identify abusers.
It seems to me, the only people who would desire the system to remain open to
anonymous abuse would be those wishing to abuse the system or support those
that already do abuse it.
You won't ever sell me on a position that it can't be done or it's too hard or
to challenging.
KY1V
Sincerely,
David Kopacz, CTO
Rational Certified Developer, MCSE+I
ASPwebhosting.com, LLC
Microsoft Certified Partner
4044 Fort Campbell Blvd, #308, Hopkinsville, Kentucky 42240 1.888.277.9320 U.S.
& Canada
1.502.410.2922 International
SIP: dial@freecall.aspwebhosting.com
CONFIDENTIALITY NOTE:
The information contained in this electronic transmission is PRIVILEGED and
CONFIDENTIAL information intended only to be viewed by the individual, entity
or entities named as recipient(s). You are hereby notified that any
dissemination, distribution or copy of this communication is strictly
prohibited and a violation of your service agreement. If you have received this
communication in error, please notify ASPwebhosting.com, LLC immediately by
electronic mail or by telephone and permanently delete this message from your
computer.
-----Original Message-----
From: cq-contest-bounces@contesting.com
[mailto:cq-contest-bounces@contesting.com] On Behalf Of K1TTT
Sent: Friday, March 05, 2010 9:00 AM
To: 'Luc PY8AZT'; CQ-Contest@contesting.com
Subject: Re: [CQ-Contest] Cluster network update - was: Reverse Beacon Network-
too much success?
A central server system has been discussed in the past, but has always been
rejected as being a single point of failure, removing local control, relying on
someone to provide the service for a long period, etc. While things like sms,
twitter, aol-im, msn-im, irc, aprs, and other services may seem like a nice way
to do it I would worry about the long term viability and our use being
disrupted by business decisions or changes in other services for security or
other reasons. When ar-cluster came out there was a move to organize into
regional sub-nets which would connect via one hub... that fairly quickly fell
apart when everyone realized that a single failure could split the world into a
bunch of disconnected islands. The software was modified to allow more
redundant connections and automatic failovers. This is similar to how other
cluster software works now, most nodes have many redundant connections so a
single failure affects only the local node.
David Robbins K1TTT
e-mail: mailto:k1ttt@arrl.net
web: http://www.k1ttt.net
AR-Cluster node: 145.69MHz or telnet://dxc.k1ttt.net
> -----Original Message-----
> From: Luc PY8AZT [mailto:py8azt@dxbrasil.net]
> Sent: Friday, March 05, 2010 14:25
> To: K1TTT; CQ-Contest@contesting.com
> Subject: Re: [CQ-Contest] Cluster network update - was: Reverse Beacon
> Network- too much success?
>
> Dave,
>
> You put DXCluster future in perspective. Yes, I agree, This 40 years
> old tecnology developed to run over packet radio has no fixing fo
> nowadays.
>
> > The only way I can see the existing network going away is to design
> > a
> new
> > system from the ground up that includes strong backbone security,
> > not
> too
> > complicated but secure user identification, and all the other
> > features
> that
> > everyone wants to enable opting in/out of spotting, filters, larger
> volumes
> > of spots, elimination of bottlenecks and loops, must run on various
> versions
> > of windows, linux, mac's, must include telnet, rf, web, and some
> > kind of
> new
> > secure user access for future expansion, must include localized
> > language capabilities and built in translation of
> > talk/announce/comments, use the
> new
> > non-ascii url system, accommodate skimmer spots automatically, allow
> Unicode
> > character sets, email and bulletin distribution, emergency disaster
> > overrides, etc, etc, etc. And then of course all the user logging
> > and
> other
> > access programs will have to update to handle whatever the
> authentication
> > system is. This is obviously not a simple project... and it won't
> > make
> the
>
> I'm not a Geek (ah, I'm ham radio anyway), but reading this
> requirements for the new network, it looks like something that has
> been arround for while: Twitter network.
>
> So, I wonder if we can use a Twitter API to setup a parallel network
> to transport DX Spots. It is very well docummentaded and integrated it
> to log software won't be hard.
> 140 caracters is just enough to send a spot, just like it is now.
>
> 73, Luc
> __
> ZY7C Team member
> PT7AG (also PY8AZT, PX8C, ZZ8Z)
> LABRE, ARRL, Uirapuru DX Club & ADXG Member __
> Prefil: http://www.google.com/profiles/lmoreira
> Participe da Lista DXBrasil: dxbrasil+subscribe@googlegroups.com
> Website: http://www.dxbrasil.net
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|