[SCCC] The EMAIL Robots are Coming to YOUR FREQUENCY!

[Art]

Hello
I'm forwarding links to the information you'll need. This appears to be 
REAL STUFF that WE NEED TO ATTEND TO. Note that the Imlay et al paper is 
dated 14 Feb 2007, last month. This is current.

http://mywebpages.comcast.net/hteller/11306-cont.pdf
http://www.zerobeat.net/bandplan-dissent.html
http://mywebpages.comcast.net/hteller/comment.htm

I invite all my DX'er/contester pals (please forward this or similar to 
YOUR list) to pay special attention to the ARRL proposed frequency 
assignments for

automatic HF data and rtty Winlink style transmissions:
160 entire band
80 entire band
7.0-7.125
30 entire band
20 14.0-14.15
17 All the cw and tty part
and so forth. Kiss your DXing goodbye.

Where's that ARRL survey of ALL its members? Let's hope coming soon.

All of us have fared poorly at the hands of automated digital messaging. 
Anyone on 20 RTTY or PSK knows current automated activity is without 
conscience, without regard to anything or anyone else. If this is the 
future we may as well either start running Winlink ourselves, or take 
our towers down. Gentlemen's agreements require ladies and gentlemen.

Notice the meeting took place just a week before the end of CW testing. 
Given the legal paper it can hardly be a cruel hoax. Much as we'd like 
to think.

73 Art
k6xt at arrl dot net




-------- Original Message --------
Subject: 	[dxlab] Fwd: [microHAM] FW: [ic706] Fwd: [RTTY] The Email
Robots are coming to RTTY!
Date: 	Thu, 22 Mar 2007 15:20:48 -0400
From: 	Richard B. Drake <rich at w3zj.com>
Reply-To: 	dxlab at yahoogroups.com
To: 	DXLAB <dxlab at yahoogroups.com>



I picked this up on the microHam reflector and thought it important
enough to forward here as well. I need to research it more but it
sure sounds to me like ARRL has finally flipped its lid. Whether or
not CW is required to obtain a ham license those of us who still love
CW and think it is important as the simplest and most reliable means
of communication during an emergency had better come down hard on this.

Having been caught in St. Maarten during hurricane Luis (a level 5
hurricane) in 1996, I can report first hand what happens in this kind
of natural emergency. Power is out, phones are out, satellite dishes
are reduced to rubble, commercial radio and TV stations are off the
air no power and antenna towers laying on the ground, airports are
strewn with rubble and closed, the Internet is out, roads are
impassable, food and water are scarce. Basically we are reduced to
surviving like cave men except for one thing. Emergency generators,
and skilled ham radio operators with the know how and equipment to
communicate long distances using makeshift antennas and the simplest
form of conveying intelligence - CW. We are the last line of defense
folks. Apparently ARRL has lost sight of this, lets make sure the FCC
hasn't.

73, Rich - W3ZJ

  > Sorry for the off topic post but I think this info needs
  >to be put before all Ham Radio operators.
  >73 de Tony, KD4K
  >
  > >
  > > ARRL is petitioning the FCC to allow Email Robots to
  > > take over the HF bands under 10m.
  > >
  > > You can read about the special meeting with the FCC
  > > here:
  > >
  > > http://mywebpages.comcast.net/hteller/11306-cont.pdf
<http://mywebpages.comcast.net/hteller/11306-cont.pdf>
  > >
  > > I urge all of you not to be complacent about this
  > > matter!
  > >
  > > As an invited member of the original ARRL committee
  > > from which the
  > > "bandwidth petition" sprang, I saw early on that the
  > > real intent of the
  > > committee, chaired by the originator of Winlink, was
  > > to turn control of the
  > > HF bands over to Winlink Email robots, and that
  > > "segmentation by bandwidth"
  > > was merely a guise for doing this. I even felt it
  > > necessary to issue a
  > > dissenting recommendation, which you may read here:
  > >
  > > http://www.zerobeat.net/bandplan-dissent.html
<http://www.zerobeat.net/bandplan-dissent.html>
  > >
  > > Now the ARRL is trying again, and in so doing,
  > > divulging the true purpose
  > > behind their original "bandwidth petition", by
  > > taking advantage of the fact
  > > that CW has been dropped as a requirement, basically
  > > leaving only RTTY and
  > > Data as important modes in the eyes of the ARRL. You
  > > may notice the complete
  > > absence of CW as a mode in the table of HF modes
  > > attached to the ARRL's
  > > Ex-parte attempted modification to RM-11306, which
  > > may or may not actually
  > > be allowed, since it basically scraps the concept of
  > > segmentation by
  > > bandwidth and preserves segmentation by mode for all
  > > bands under 10m. I
  > > don't see how the FCC can accept this magnitude of
  > > change to RM-11306
  > > without requiring a totally new petition and comment
  > > period.
  > >
  > > However, just in case they do, I have put together a
  > > simple explanation of
  > > how to file a comment and I strongly urge each one
  > > of you to file a comment
  > > NOW if you value your ability to enjoy RTTY and CW
  > > in the future. Please do not be
  > > complacent and assume everything will be OK! Just
  > > take a couple of minutes
  > > to file a comment. Here is a sample form to follow:
  > >
  > > http://mywebpages.comcast.net/hteller/comment.htm
<http://mywebpages.comcast.net/hteller/comment.htm>
  > >
  > > A flood of comments DOES influence the FCC. It
  > > worked to keep the robots off the
  > > phone bands, so now we must again work to keep them
  > > from taking over the
  > > RTTY and CW activity areas.
  > >
  > > If you want to enjoy RTTY contesting and DXing in
  > > the future, please help by simply clicking here:
  > > http://gullfoss2.fcc.gov/prod/ecfs/upload_v2.cgi
<http://gullfoss2.fcc.gov/prod/ecfs/upload_v2.cgi>
  > > and commenting NOW!
  > >
  > > 73, Skip KH6TY
  > >
  > > _______________________________________________
  > > RTTY mailing list
  > > RTTY at contesting.com <mailto:RTTY%40contesting.com>
  > > http://lists.contesting.com/mailman/listinfo/rtty
<http://lists.contesting.com/mailman/listinfo/rtty>