[NLRS] Re: John Anderson <[email protected]>: Re: [Mw]
Clarification of ARRL 10GHz and Up contest rules
Donn Baker
[email protected]
Thu, 29 Aug 2002 13:04:28 +0100
Obviously, its a matter of interpetation. NOTHINMG IN DAN'S ANSWER NEGATES
THE SPECIFIC 3.9 RULE SAYING THAT PHONE AND INTERNET CANNOT BE USED.
Nothing says that repeaters can be used. "Scheduling is permitted and
encouraged" does NOT remove those restrictions.
Now, if that's what the "answer" is, OK, that's the answer. But this answer
greatly diminishes the INTENT of the rules, which is to level the playing
field, and make it reasonbly fair for everyone.
THE RULES NEED TO BE MODIFIED so the intent is clear, and NOT sujbect to
exparte "clairifications" such as in this thread. Anyone who was not a part
of this e-mail chain had/has NO KNOWLEDGE of this removal of the
restriction, and is at a distinct disadvantage because of it. Fair ?
WIthout fair treatment, why bother ?
Donn
WA2VOI/0
At 00:32 29-08-02 cdt, Gary M Danelius wrote:
>Here is another more recent e-mail. You probably have
>already read this one.
>
>Gary.
>
>--------- Begin forwarded message ----------
>From: John Anderson <[email protected]>
>To: [email protected], [email protected], [email protected]
>Cc: [email protected], [email protected]
>Subject: Re: [Mw] Clarification of ARRL 10GHz and Up contest rules
>Date: Mon, 10 Jun 2002 18:12:52 -0600
>
>
>An interesting (possibly new?) interpretation of the scheduling rule -
>particularly the portion stating:
>
>> The rules at this time do
>> not appear to allow use of a linked 440 repeater system, internet
>contacts,
>> or other means to coordinate completing the contacts.
>>
>
>I believe that a previous interpretation from the same source allowed
>(encouraged!) any method of scheduling contacts. To wit:
>
>> Subject: MicroWave: A Message from the ARRL regarding the 10G contest
>> Date: Tue, 17 Aug 1999 06:56:09 -0400
>> From: Tom Williams <[email protected]>
>> To: [email protected]
>>
>> Thanks for the query guys.
>>
>> 10 GHz rule 5.1 states "Scheduling contacts is permissible and
>encouraged."
>> The contest specific rules supercede the General rules in this case.
>>
>> Good luck this weekend!
>>
>> 73
>>
>> Dan Henderson, N1ND
>> Contest Branch Manager, ARRL
>
>
>And:
>
>> Subject: MicroWave: Forwarded message regarding 10 GHz contest scheds
>> Date: Tue, 17 Aug 1999 21:06:45 -0400
>> From: Tom Williams <[email protected]>
>> To: [email protected]
>>
>> THIS IS A MESSAGE FROM Dan Henderson, N1ND
>> Contest Branch Manager, ARRL
>> ---------------------------------------------------------
>> Gentlemen:
>>
>> My response of yesterday in regards to the scheduling of QSOs for the
>10 GHZ
>> and Up Contest has been questioned. Let me clarify the situation.
>>
>> I was approached several months ago and asked about the use of
>rescheduling
>> a missed schedule via an email or a phone call during the contest
>period. I
>> don't recall the exact contest, but it involved a microwave schedule
>during
>> either the January or June VHF contest. The party was told that under
>the
>> rules of the contest, the use of non-amateur means for scheduling a QSO
>> during the contest period was not allowed and was referred to the
>General
>> Rule 3.9, which I quoted yesterday. Since there is nothing in the
>specific
>> rules of either the January VHF Sweepstakes or the June VHF QSO party
>which
>> allows scheduling, the method which was suggested was not allowed under
>the
>> rules for that contest.
>>
>> The 10 GHZ rules specifically state that "Scheduling contacts is
>permissible
>> and encouraged." It is allowed for this contest. The very nature of
>the 10
>> GHZ and Up contest lends itself to utilizing these means - something
>which
>> can be accomplished on the other VHF/UHF contests without this
>assistance.
>>
>> So simply put: in the 10 GHz and Up Contest it is permissible to
>schedule
>> QSO's etc during the contest period. The answer given to several
>months ago
>> was correct in the context of the question which was asked in regards
>to
>> another contest. The answer which I gave yesterday is correct in the
>> context of this specific contest - the 10 GHz and Up Contest.
>>
>> Hope all of you have fun this weekend and during the September running
>of
>> this contest.
>>
>> 73
>>
>> Dan Henderson, N1ND
>> Contest Branch Manager, ARRL
>>
>>
>----------------------------------------------------------------------------
>> --
>> The following is the complete text of the email I received in regards
>to
>> this question. The identity of the sender has been deleted.
>>
>> 10 GHz rule 5.1 states "Scheduling contacts is permissible and
>encouraged."
>>>The contest specific rules supercede the General rules in this case.
>>
>>
>> Dan,
>>
>> Just a few short months ago, you informed me (via email) that any use
>of
>> the internet for scheduling or setting up schedules WAS A VIOLATION.
>When I
>> asked about
>> this, I was very specific and stated it was for vhf and microwaves
>where
>> antenna beamwidths were tight and therefor precluded DX contacts made
>> 'randomly'.
>>
>> Are you now saying that it IS NOT a violation of the rules to use
>> non-amateur means for scheduling? What exactly is the difference
>between
>> soliciting and scheduling?
>>
>> I can send you the copy of the message you sent to me previously if you
>> need it to jog your memory.
>>
>> I'll wait to hear from you before sending anything additional to the
>list.
>> It appears to me at this time that you are either contradicting
>yourself,
>> or that you are expecting me to abide by a different set of rules than
>> everyone else uses.
>>
>> Can we PLEASE clear this up?
>>
>> Thanks,
>
>73, John WD4MUO/0
>
>
>_______________________________________________
>Microwave mailing list
>[email protected]
>http://mbs.valinet.com/mailman/listinfo/microwave
>--------- End forwarded message ----------
>
>
>________________________________________________________________
>GET INTERNET ACCESS FROM JUNO!
>Juno offers FREE or PREMIUM Internet access for less!
>Join Juno today! For your FREE software, visit:
>http://dl.www.juno.com/get/web/.
>
>