Return-Path: Received: (qmail 16478 invoked from network); 26 Jan 2001 21:05:27 -0000 Received: from unknown (HELO murphys-inbound.servers.plus.net) (212.159.14.225) by excalibur.plus.net with SMTP; 26 Jan 2001 21:05:27 -0000 Received: (qmail 27912 invoked from network); 26 Jan 2001 20:59:38 -0000 Received: from unknown (HELO post.thorcom.com) (212.172.148.70) by murphys with SMTP; 26 Jan 2001 20:59:38 -0000 Received: from majordom by post.thorcom.com with local (Exim 3.16 #1) id 14MFsc-0005yW-00 for rsgb_lf_group-outgoing@blacksheep.org; Fri, 26 Jan 2001 20:53:58 +0000 Received: from tomts7.bellnexxia.net ([209.226.175.40] helo=tomts7-srv.bellnexxia.net) by post.thorcom.com with esmtp (Exim 3.16 #1) id 14MFsb-0005yP-00 for rsgb_lf_group@blacksheep.org; Fri, 26 Jan 2001 20:53:57 +0000 Received: from server1 ([216.209.138.149]) by tomts7-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010126205308.XAIS6682.tomts7-srv.bellnexxia.net@server1> for ; Fri, 26 Jan 2001 15:53:08 -0500 Message-ID: <002901c087d9$d91467a0$0a00a8c0@ThreeLakes.ca> From: "Larry Kayser" To: rsgb_lf_group@blacksheep.org References: <3A71B3C1.11895.1102764@localhost> Subject: Re: LF: Minimalist QSO, a process Date: Fri, 26 Jan 2001 15:40:37 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group Sender: Mike: > However, the earlier part is a bit flawed. Are you assuming that this > type of communication can only be done on sked, or can there be a > random QSO? Flawed? Well that is the issue isn't it. We have to achieve a general acceptance in the peer community, disallowing for extremist positions. For my part I have no problems with your suggestions, there as good as others and they do shorten up the QSO overal time. Sked? Certainly a Schedule, I dont see this happening any other way, for my part if I am part of it, a random QSO has as much chance as 12 inches of snow in the Amazon. In general the "RO O" etc follows the EME convention, well tested and generally accepted, again minimize exposure to raising concerns in the peer community. Your proposals are excellent, I have no problems with them providing we can keep the noise down on the validity of the QSO when it occurs. Your thoughtful effort is appreciated, Mike. Larry VA3LK