Message-ID: <33AA9FE0D62344A1A5D5A2F5D12F0697@White>
From: "Markus Vester" <markusvester@aol.com>
To: <rsgb_lf_group@blacksheep.org>
References: <4EA5AAF4.1010306@iup.uni-heidelberg.de>
Date: Mon, 24 Oct 2011 21:50:06 +0200
MIME-Version: 1.0
Importance: Normal
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 <rv3apm@gmail.com>=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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3Dtext/html;charset=3Dutf-8>
<META content=3D"MSHTML 6.00.6000.17104" name=3DGENERATOR></HEAD>
<BODY id=3DMailContainerBody=20
style=3D"PADDING-RIGHT: 10px; PADDING-LEFT: 10px; PADDING-TOP: 15px" =
text=3D#000000=20
bgColor=3D#ffffff leftMargin=3D0 topMargin=3D0 CanvasTabStop=3D"true"=20
name=3D"Compose message area">
<DIV><FONT face=3DArial size=3D2>oh yes Stefan, this has been debated =
before...=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I guess it should be each to his own, =
and&nbsp;I=20
would not like to engage in a discussion of what is required for a =
"valid=20
</FONT><FONT face=3DArial size=3D2>detection".</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Personally I often (but not always) =
prefer to send=20
just a suffix, because</FONT></DIV><FONT face=3DArial size=3D2>
<DIV>- longer intervals between shorter transmissions gives me more time =
to=20
receive, and saves power and potential QRM,<BR>- with QSB, its more =
likely to=20
detect a shorter string (especially from poor souls like me who are less =

equipped TX-wise ;</FONT><FONT face=3DArial size=3D2>-).</FONT><FONT =
face=3DArial=20
size=3D2><BR></FONT><FONT face=3DArial size=3D2>- suffixes are easy =
<FONT face=3DArial=20
size=3D2>to memorize and </FONT>fairly unique (the only exception I'm =
aware of are=20
the two AGC's). However single-letter strings have&nbsp;</FONT><FONT =
face=3DArial=20
size=3D2>often been confusing.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- sending suffixes is standard practice =
in the QRSS=20
QSO procedure (after the exchange of the full call), and they are easy=20
</FONT><FONT face=3DArial size=3D2>to memorize. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Just my 5 cent's worth.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Best 73,<BR>Markus (DF6NM)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV style=3D"FONT: 10pt Tahoma">
<DIV><FONT face=3DArial></FONT><FONT face=3DArial></FONT><BR></DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A=20
title=3D"mailto:Stefan.Schaefer@iup.uni-heidelberg.de&#10;STRG + =
Klicken, um Verkn=C3=BCpfung zu folgen"=20
href=3D"mailto:Stefan.Schaefer@iup.uni-heidelberg.de">Stefan =
Sch=C3=A4fer</A> </DIV>
<DIV><B>Sent:</B> Monday, October 24, 2011 8:14 PM</DIV>
<DIV><B>To:</B> <A title=3Drsgb_lf_group@blacksheep.org=20
href=3D"mailto:rsgb_lf_group@blacksheep.org">rsgb_lf_group@blacksheep.org=
</A>=20
</DIV>
<DIV><B>Subject:</B> LF: Full ID or just a suffix?</DIV></DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
size=3D2></FONT><BR></DIV>Dear LF group and QRSS-60 TXing =
stations,<BR><BR>I want=20
to start a discussion that may have been done before.<BR><BR>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. <BR>I find this is a=20
pity.<BR>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.<BR>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.<BR><BR>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).<BR><BR>Room for thought, =
as Mal=20
would say.<BR><BR>73, Stefan/DK7FC<BR><BR>(reduced the original =
screenshot in=20
size)<BR><BR><BR>-------- Original-Nachricht --------=20
<TABLE class=3Dmoz-email-headers-table cellSpacing=3D0 cellPadding=3D0 =
border=3D0>
  <TBODY>
  <TR>
    <TH vAlign=3Dbaseline noWrap align=3Dright>Betreff: </TH>
    <TD>Re: QRSS</TD></TR>
  <TR>
    <TH vAlign=3Dbaseline noWrap align=3Dright>Datum: </TH>
    <TD>Mon, 24 Oct 2011 05:20:44 +0400</TD></TR>
  <TR>
    <TH vAlign=3Dbaseline noWrap align=3Dright>Von: </TH>
    <TD>Serge K <A class=3Dmoz-txt-link-rfc2396E =
href=3D"mailto:rv3apm@gmail.com"=20
      moz-do-not-send=3D"true">&lt;rv3apm@gmail.com&gt;</A></TD></TR>
  <TR>
    <TH vAlign=3Dbaseline noWrap align=3Dright>CC: </TH>
    <TD><A class=3Dmoz-txt-link-abbreviated=20
      href=3D"mailto:schaefer@iup.uni-heidelberg.de"=20
      =
moz-do-not-send=3D"true">schaefer@iup.uni-heidelberg.de</A></TD></TR></TB=
ODY></TABLE><BR><BR>Also=20
please help<BR><BR>what it?<BR><BR>NM&nbsp;&nbsp; OE =
??&nbsp;&nbsp;&nbsp; I see=20
UR&nbsp; DK7FC&nbsp; but not understand another signals<BR><BR><PRE =
class=3Dmoz-signature cols=3D"72">73!  Serge =
RV3APM</PRE><BR><BR></BODY></HTML>

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