Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-de04.r1000.mx.aol.com (Internet Inbound) with ESMTP id B079738000098; Thu, 9 May 2013 09:27:50 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UaQs2-0001Yp-32 for rs_out_1@blacksheep.org; Thu, 09 May 2013 14:26:54 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UaQs1-0001Yg-JG for rsgb_lf_group@blacksheep.org; Thu, 09 May 2013 14:26:53 +0100 Received: from eterpe-smout.broadpark.no ([80.202.8.16]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1UaQrz-0006wM-OR for rsgb_lf_group@blacksheep.org; Thu, 09 May 2013 14:26:52 +0100 Received: from terra-smin.broadpark.no ([80.202.8.13]) by eterpe-smout.broadpark.no (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTP id <0MMJ00CJ19BU4H60@eterpe-smout.broadpark.no> for rsgb_lf_group@blacksheep.org; Thu, 09 May 2013 15:26:19 +0200 (CEST) Received: from [127.0.0.1] ([80.202.132.204]) by terra-smin.broadpark.no (Oracle Communications Messaging Server 7u4-27.01(7.0.4.27.0) 64bit (built Aug 30 2012)) with ESMTPA id <0MMJ003RV9BTKG90@terra-smin.broadpark.no> for rsgb_lf_group@blacksheep.org; Thu, 09 May 2013 15:26:18 +0200 (CEST) Date: Thu, 09 May 2013 15:26:17 +0200 From: Steinar Aanesland In-reply-to: <1368096290.60555.YahooMailNeo@web133205.mail.ir2.yahoo.com> To: rsgb_lf_group@blacksheep.org Cc: M0FMT Message-id: <518BA3F9.6030006@broadpark.no> MIME-version: 1.0 References: <7E7DFBB4D102A04DB5ADC88D66628A4A0FBCBDA1@ICTS-S-MBX5.luna.kuleuven.be> <518B7455.8000609@broadpark.no> <1368096290.60555.YahooMailNeo@web133205.mail.ir2.yahoo.com> User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 X-Spam-Score: -1.9 (-) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Yes i am 110% agree , and some people are extremely keen on regulating other people's behavior. LF/MF people are perfectly capable to take care of the band. The gentleman's agreement is working absolutely fine. [...] Content analysis details: (-1.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [80.202.8.16 listed in list.dnswl.org] -1.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Scan-Signature: 2ee80849a5d572dbc974bb207a527753 Subject: Re: LF: Re: [rsgb_lf_group] Proposed usage for the MF band Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: QUOTED-PRINTABLE 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: 3039ac1d40cc518ba4555ca5 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Yes i am 110% agree , and some people are extremely keen on regulatin= g other people's behavior. LF/MF people are perfectly capable to take c= are of the band. The gentleman's agreement is working absolutely fine. LA5VNA Steinar loc:JO59jq Den 09.05.2013 12:44, skrev M0FMT: > Hi all > =20 > It has been said before that to salami slice such a small allocatio= n as the MF/LF bands is nonsenses. > =20 > In any case how many of the "Slicers" use these frequencies? As usu= al it is those who feel they have the right, will thus be giving the = band "Policemen" a mission. > =20 > Why is it not possible to have these bands organised by the actual = users on a consensual basis rather than have it cast in "stone"? > =20 > Alterations in QRG usage would then be organic and by popular deman= d and meet the needs of developing modes and operating practise. It w= ill be messy but I think it's called Democracy which seems to be slip= ping through the fingers of the regular MF/LF users. After all we do = have a forum to air these issues.. > 73 es GL Pete M0FMT IO91UX >=20 >=20 >> ________________________________ >> From: Steinar Aanesland >> To: rsgb_lf_group@yahoogroups.co.uk; "rsgb_lf_group@blacksheep.org= " =20 >> Sent: Thursday, 9 May 2013, 11:03 >> Subject: LF: Re: [rsgb_lf_group] Proposed usage for the MF band >> =20 >> >> This has not been discussed in the Norwegian ham community, and be= cause >> of LA4LN's solo act, I am not a member of NRRL any more. >> >> LA5VNA Steinar >> loc:JO59jq >> >> >> Den 09.05.2013 10:36, skrev Rik Strobbe: >>> Dear all, >>> >>> >>> >>> those active on 630m might be interested in the outcome of the di= scussion of paper C4_06 (Bandplan for the 630 m band proposed by NRRL= ) at the Committee C4 (HF Matters) Interim Meeting (20-21 April 2013,= Vienna): >>> >>> >>> >>> 4.5 Paper C4_06 was presented by LA4LN >>> RSGB stated that they support the principle of a band plan, but t= hat it is too early to have a formal plan until the usage is better k= nown. >>> DARC stated that the usage of the band at the moment doesn=92t re= ally require a band plan. >>> DARC introduced a plan "proposed usage" (see Annex 1). >>> ZRS asked if the CW DX frequency could be moved a little higher u= p the band. >>> DARC noted that there are still 4 NDBs in the band. They also ask= ed if the QRSS CW segment could be moved out of the CW part of the ba= nd as it is decoded as a digimode. DARC also said there is currently = no need for a coordinated beacon segment as we can use the existing N= DBs. >>> OeVSV said we should observe the band usage for a while before de= ciding on a fixed band plan and suggested that centres of activity co= uld be used also. >>> UBA stated it is too early to propose a band plan. >>> It was agreed to show current plan as proposed usage and to revie= w at the next general conference. >>> CRC stated that we should not show a plan as the current users wo= uld not appreciate being told how to use the band. >>> The meeting agreed to change the wording to a =91proposed usage= =92 plan and that frequencies should be referred to as centre of acti= vities. >>> DARC introduced a plan "proposed usage". >>> >>> >>> >>> [cid:2bd9b952-2278-4148-b306-9c41271fd880] >>> >>> >>> >>> 73, Rik ON7YD - OR7T >>> >> >> >> >> >> =20