Return-Path: Received: from mtain-dc06.r1000.mx.aol.com (mtain-dc06.r1000.mx.aol.com [172.29.64.134]) by air-df07.mail.aol.com (v127_r1.1) with ESMTP id MAILINDF074-5efd4bb0ce9126b; Mon, 29 Mar 2010 12:00:17 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mtain-dc06.r1000.mx.aol.com (Internet Inbound) with ESMTP id 7CEC3380000BB; Mon, 29 Mar 2010 12:00:14 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1NwHMx-00076X-AF for rs_out_1@blacksheep.org; Mon, 29 Mar 2010 16:59:15 +0100 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1NwHMw-00076O-UY for rsgb_lf_group@blacksheep.org; Mon, 29 Mar 2010 16:59:14 +0100 Received: from mtaout01-winn.ispmail.ntl.com ([81.103.221.47]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1NwHMv-0000AX-8O for rsgb_lf_group@blacksheep.org; Mon, 29 Mar 2010 16:59:14 +0100 Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout01-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20100329155907.CLAU14666.mtaout01-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com> for ; Mon, 29 Mar 2010 16:59:07 +0100 Received: from [192.168.2.33] (really [82.22.244.28]) by aamtaout03-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20100329155907.NHEL2093.aamtaout03-winn.ispmail.ntl.com@[192.168.2.33]> for ; Mon, 29 Mar 2010 16:59:07 +0100 From: "Mike Dennison" To: rsgb_lf_group@blacksheep.org Date: Mon, 29 Mar 2010 16:58:59 +0100 MIME-Version: 1.0 Message-ID: <4BB0DC53.11486.1CDAEAC@mike.dennison.ntlworld.com> In-reply-to: <38A51B74B884D74083D7950AD0DD85E82A1BB6@File-Server-HST.hst.e-technik.tu-darmstadt.de> References: , <38A51B74B884D74083D7950AD0DD85E82A1BB6@File-Server-HST.hst.e-technik.tu-darmstadt.de> X-mailer: Pegasus Mail for Windows (4.41) Content-description: Mail message body X-Cloudmark-Analysis: v=1.1 cv=W3tOLUehizD4qj6VhtReFuw5MKb8d+XqjIxlDsIazEA= c=1 sm=0 a=MN6arlAjp7MA:10 a=9YlaCzn6_68A:10 a=kj9zAlcOel0A:10 a=4k0X21Rix_3L8Nw8O-8A:9 a=jooLSYtutr7PL6qph7sA:7 a=QdFKZijcKSXdg9Or4Wbk8FzKZ_EA:4 a=CjuIK1q_8ugA:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: Minimum content of a valid QRSS/DFCW QSO? Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-global-disposition: G x-aol-sid: 3039ac1d40864bb0ce8e0993 X-AOL-IP: 193.82.116.20 The requirement for the exchange of two complete callsigns makes extremely poor use of a limited time slot. Even HF DXers do not do this any more. I believe there are two minimum requirements: The first is to know for certain that the station you are listening to cannot be someone else (or something else). In this case a single letter (either pre-arranged or part of the callsign) should be adequate. The second is a piece of unknown information. Usually this would be a signal report (though again HF DXers have scrapped the unknown by sending 599 every time). The "unknown" can be chosen from a subset, such as the numbers in a report or the 'O', 'M' or 'T' used in QRSS- type modes. And of course the timing of the transmission will serve as confirmation that this is not a random reception. This may not please the purists, but it is certain proof of two-way communication, and (as I said) is better than a 20m DXpedition QSO accepted for DXCC will give you. Mike, G3XDV ========== > Recently i talked to Markus/DF6NM what has at least to be transmitted > within a valid QSO in very slow DFCW. I mean a 2way contact, not a > beacon reception report! > > Those of you (and others) who have done successful TA QSOs may give me > an example. Are there official rules/laws about that? > > If i would do a QSO with Markus like that, would it be valid?: > > Me: "dk7fc/p k" (the /p may be cancelled but it is "my label" ;-) ) > Markus: "fc df6nm O k" Me: "nm fc r M sk" Markus: "r sk" > > > 73, Stefan/DK7FC > > >