Return-Path: Received: from mtain-df12.r1000.mx.aol.com (mtain-df12.r1000.mx.aol.com [172.29.64.224]) by air-de06.mail.aol.com (v127_r1.1) with ESMTP id MAILINDE064-5eb94bb0b9dd1f8; Mon, 29 Mar 2010 10:31:57 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mtain-df12.r1000.mx.aol.com (Internet Inbound) with ESMTP id 13DB9380000AF; Mon, 29 Mar 2010 10:31:43 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1NwFz9-0005cO-0X for rs_out_1@blacksheep.org; Mon, 29 Mar 2010 15:30:35 +0100 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1NwFz8-0005cF-Hh for rsgb_lf_group@blacksheep.org; Mon, 29 Mar 2010 15:30:34 +0100 Received: from smtp823.mail.ukl.yahoo.com ([217.12.12.19]) by relay1.thorcom.net with smtp (Exim 4.63) (envelope-from ) id 1NwFz6-0007fD-P4 for rsgb_lf_group@blacksheep.org; Mon, 29 Mar 2010 15:30:34 +0100 Received: (qmail 77909 invoked from network); 29 Mar 2010 14:30:26 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=DKIM-Signature:Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=Ga7mLWBSjo5T58P7hn8pJBl2YNNF8aapQXAQBTG54fAfbj0cj3lSFvCn2jphfmvIVo3Djq9fyx4Wa4XhuA6MxUwASU9+ab/PKXvf1pkjwldkPf92mSzy+P9eid/0UpI4DSeq/4S+A+DLAdshhhZ39I28WPOSd8JZbeJTYRcZ4xg= ; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=s1024; t=1269873026; bh=fsA4V/bmwZdBkLUf3AvBdsfvqAWqR0/k22cxW1u9NUA=; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE; b=pqxqY6gn9+KFd+vpnYXZnyx+y+GvJWiElZZmrmfoaEiq4CYYg0ZbLgpJ5x/rsJUZ+fRcEZp0SNq7KhCj2utw8P98t+hTkVRmCmtrM4iko99O0EK4izjBUZ8nx2bp4ePIMg4xmuDXv5OC/x877kJx4rFtrU2mLGfzvc3n+7OdUTA= Received: from lark (alan.melia@81.131.8.55 with login) by smtp823.mail.ukl.yahoo.com with SMTP; 29 Mar 2010 14:30:25 +0000 GMT X-Yahoo-SMTP: fpz.2VeswBBs59bVshRPmMN51lcO2lgFRIvE4XTqE8dRwOxd70E- X-YMail-OSG: Ap.HmmUVM1l4Qf.vNKgI_ZcS1UAHJQafDFAqIpmgR64r_vQj7vLCX1jFoApB1JRt0uOjimYFyAggdZLacu.F9FG.2XNBX9ZbSkWBga.DzOY.Wg7gdphKcahoa2ccUUtO0EFC2IW92w1Pg1MN2Mm3hxyVi_aREBMNavbxxdRbd8i4TAL2511.ni_vevKvEiHdSFKPl1arRvNSh0hZ5qhGMLLvWYJ6EDsTK6UpKrkDk8OVZLjDUv00gBtOWEUIefzm0B7k5_HTaWpB.wI.HKf29nDp7R0nrUQSO6ZqXFdmcJF_HEQRha3VzBC7A8JLA8FZaRE- X-Yahoo-Newman-Property: ymail-3 Message-ID: <001301cacf4c$67d1d770$0901a8c0@lark> From: "Alan Melia" To: References: <38A51B74B884D74083D7950AD0DD85E82A1BB6@File-Server-HST.hst.e-technik.tu-darmstadt.de> Date: Mon, 29 Mar 2010 15:30:30 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1983 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1983 DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,UNPARSEABLE_RELAY=0.001 Subject: LF: Re: Minimum content of a valid QRSS/DFCW QSO? Content-Type: text/plain; charset="iso-8859-1" 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-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-d306.2 ; domain : btinternet.com DKIM : fail x-aol-sid: 3039ac1d40e04bb0b9cf1b5f X-AOL-IP: 193.82.116.20 Content-Transfer-Encoding: quoted-printable Hi Stefan that would align with what was done in the TA contacts (as= far as I remember) unlike other modes it is also useful to capture the waterf= all and store for posterity. There can always be a question about recognis= ing a smudge on the waterfall when you do actually know who is calling. and= though some do not realise having a local post a clean picture may be conside= red by some to compromise the QSO. I was always in favour of the trasfer of= an unknown to the receiver element of information. This used to be done= on ATV. Markus did devise a way of validating very weak traces with reference= to the locally received element timing. It is legitimate to lay a timing temp= late against the waterfall and chech the edge positions to define the chara= cter when you somtimes get a fade or interference in the middle of a long= dash, for instance. I dont expect itwill count for DXCC :-)) Alan G3NYK ----- Original Message -----=20 From: "Stefan Sch=E4fer" To: Sent: Monday, March 29, 2010 2:52 PM Subject: LF: Minimum content of a valid QRSS/DFCW QSO? Dear Group, 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 rec= eption 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