Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mb02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 5622638000089; Mon, 24 Oct 2011 15:51:20 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1RIQXc-0008K6-SY for rs_out_1@blacksheep.org; Mon, 24 Oct 2011 20:50:36 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1RIQXc-0008Jx-BS for rsgb_lf_group@blacksheep.org; Mon, 24 Oct 2011 20:50:36 +0100 Received: from imr-da02.mx.aol.com ([205.188.105.144]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1RIQXa-0003kw-5e for rsgb_lf_group@blacksheep.org; Mon, 24 Oct 2011 20:50:36 +0100 Received: from mtaout-ma05.r1000.mx.aol.com (mtaout-ma05.r1000.mx.aol.com [172.29.41.5]) by imr-da02.mx.aol.com (8.14.1/8.14.1) with ESMTP id p9OJoRwe017291 for ; Mon, 24 Oct 2011 15:50:27 -0400 Received: from White (nrbg-4dbfbbf9.pool.mediaWays.net [77.191.187.249]) by mtaout-ma05.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id A42C2E00008A for ; Mon, 24 Oct 2011 15:50:24 -0400 (EDT) Message-ID: <33AA9FE0D62344A1A5D5A2F5D12F0697@White> From: "Markus Vester" To: References: <4EA5AAF4.1010306@iup.uni-heidelberg.de> Date: Mon, 24 Oct 2011 21:50:06 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 X-AOL-SCOLL-SCORE: 0:2:440601472:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-Spam-Score: 0.1 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001,HTML_TAG_EXIST_TBODY=0.126 Subject: Re: LF: Full ID or just a suffix? Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01CC9296.E45E5980" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.0 required=5.0 tests=HTML_30_40,HTML_MESSAGE, HTML_TAG_EXISTS_TBODY,MISSING_OUTLOOK_NAME 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-SCORE: 0:2:468811040:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d60164ea5c1b8511a X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0008_01CC9296.E45E5980 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable oh yes Stefan, this has been debated before...=20 I guess it should be each to his own, and I would not like to engage in = a discussion of what is required for a "valid detection". Personally I often (but not always) prefer to send just a suffix, = because - longer intervals between shorter transmissions gives me more time to = receive, and saves power and potential QRM, - with QSB, its more likely to detect a shorter string (especially from = poor souls like me who are less equipped TX-wise ;-). - suffixes are easy to memorize and fairly unique (the only exception = I'm aware of are the two AGC's). However single-letter strings have = often been confusing. - sending suffixes is standard practice in the QRSS QSO procedure (after = the exchange of the full call), and they are easy to memorize.=20 Just my 5 cent's worth. Best 73, Markus (DF6NM) From: Stefan Sch=C3=A4fer=20 Sent: Monday, October 24, 2011 8:14 PM To: rsgb_lf_group@blacksheep.org=20 Subject: LF: Full ID or just a suffix? Dear LF group and QRSS-60 TXing stations, I want to start a discussion that may have been done before. This is a forwarded message, showing the typical problem of newcomers = who do not know what they receive if a station just transmitts a suffix. = I find this is a pity. Maybe someone can expain me why just the suffix is sent? There is a lack = of information as long as the receiving station is not a member of this = reflector. It is not the only example. I got at least 4 mails within the last = months, where new stations asked what station that is. Usually there are plenty of grabbers available which make ID clear. Even = if a full callsign is lost in the QSB, there is a chance to verify who = it must have been. Frequency and time can help to identify the traces. = So why transmitting 8x GH instead of 3x GM3GH (an example) which could = help to find an ID? I one receive a full call and is not a member of the = reflector, there is a chance to find further informations in the web = (qrz.com, and so on). Room for thought, as Mal would say. 73, Stefan/DK7FC (reduced the original screenshot in size) -------- Original-Nachricht -------- Betreff: Re: QRSS=20 Datum: Mon, 24 Oct 2011 05:20:44 +0400=20 Von: Serge K =20 CC: schaefer@iup.uni-heidelberg.de=20 Also please help what it? NM OE ?? I see UR DK7FC but not understand another signals 73! Serge RV3APM ------=_NextPart_000_0008_01CC9296.E45E5980 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
oh yes Stefan, this has been debated = before...=20
 
I guess it should be each to his own, = and I=20 would not like to engage in a discussion of what is required for a = "valid=20 detection".
 
Personally I often (but not always) = prefer to send=20 just a suffix, because
- longer intervals between shorter transmissions gives me more time = to=20 receive, and saves power and potential QRM,
- with QSB, its more = likely to=20 detect a shorter string (especially from poor souls like me who are less = equipped TX-wise ;-).
- suffixes are easy = to memorize and fairly unique (the only exception I'm = aware of are=20 the two AGC's). However single-letter strings have often been confusing.
- sending suffixes is standard practice = in the QRSS=20 QSO procedure (after the exchange of the full call), and they are easy=20 to memorize.
 
Just my 5 cent's worth.
 
Best 73,
Markus (DF6NM)
 

From: Stefan = Sch=C3=A4fer
Sent: Monday, October 24, 2011 8:14 PM
Subject: LF: Full ID or just a suffix?

Dear LF group and QRSS-60 TXing = stations,

I want=20 to start a discussion that may have been done before.

This is a = forwarded=20 message, showing the typical problem of newcomers who do not know what = they=20 receive if a station just transmitts a suffix.
I find this is a=20 pity.
Maybe someone can expain me why just the suffix is sent? There = is a=20 lack of information as long as the receiving station is not a member of = this=20 reflector.
It is not the only example. I got at least 4 mails within = the last=20 months, where new stations asked what station that is.

Usually = there are=20 plenty of grabbers available which make ID clear. Even if a full = callsign is=20 lost in the QSB, there is a chance to verify who it must have been. = Frequency=20 and time can help to identify the traces. So why transmitting 8x GH = instead of=20 3x GM3GH (an example) which could help to find an ID? I one receive a = full call=20 and is not a member of the reflector, there is a chance to find further=20 informations in the web (qrz.com, and so on).

Room for thought, = as Mal=20 would say.

73, Stefan/DK7FC

(reduced the original = screenshot in=20 size)


-------- Original-Nachricht --------=20
Betreff: Re: QRSS
Datum: Mon, 24 Oct 2011 05:20:44 +0400
Von: Serge K <rv3apm@gmail.com>
CC: schaefer@iup.uni-heidelberg.de


Also=20 please help

what it?

NM   OE = ??    I see=20 UR  DK7FC  but not understand another signals

73!  Serge =
RV3APM


------=_NextPart_000_0008_01CC9296.E45E5980--