| |
ZL3AI > APRDIG 17.04.03 10:07l 140 Lines 5937 Bytes #999 (0) @ WW
BID : 1168-ZL3AI
Read: GUEST
Subj: TAPR Digest, Apr 14, 3/3
Path: DB0FHN<DB0RGB<DB0MRW<OK0PKL<OK0PPL<RZ6HXA<SP7MGD<VK7AX<ZL2BAU<ZL3VML
Sent: 030416/1111Z @:ZL3VML.#80.NZL.OC #:64024 [Chch-NZ] FBB7.00i $:1168-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Opening up the proverbial can o' worms
From: "John Zantek" <john@zantek.net>
Date: Mon, 14 Apr 2003 19:50:59 -0700
X-Message-Number: 22
Not sure about that. HIPAA has particularly language that holds
emergent services absolvent of the Act when dealing with life actions,
e.g, first responders are not required to have the security (on line
encryption) engaged on the radio. If the Act didn't exempt them, many
police and fire departments could not afford an infrastructure to meet
the Act.
Privacy is different than security in the Act, however, and holds
different requirements and penalties.
Regardless, I think the paradigm for the use of the amateur radio
service as an adjunct to 'conventional' emergency services'
communications support is shifting...
John K3JZ
----------------------------------------------------------------------
Subject: Re: Opening up the proverbial can o' worms
From: "Mike Yetsko" <myetsko@insydesw.com>
Date: Mon, 14 Apr 2003 22:52:27 -0400
X-Message-Number: 23
I think the rule is pretty simple. I don't have the wording handy, but
I feel the flavor of the rule can be summed up as 'intent to obscure'.
In direct contrast to what you are trying to do with 'health and
welfare'. And of course you would be called to task to show that
the immediacy of the message was relevant to health and welfare,
not just the fact that you were passing juicy bits.
But where there's a rule there's a way...
Just like the rules about what call sign you use when you hop in your
friends car and grab his mic. Or reach over on his bench when you're
sharing a cold one... How many people DON'T use their own call?
Hey, you're breaking the rules! Or are you? All you need to be NOT
breaking the rules is for your friend to say he 'loaned' you the station.
Now you can legally use your own call. (Assuming all else is legal,
of course!)
As to the 'intent to obscure' issue... You could argue that data packets
are data packets, and have meaning in and of themselves. You can
argue that repeater or satellite control packets are data packets in and
of themselves. So if you sent a 'zip' file... You could argue (I'm not
saying you would successfully hold off a fine or other punishment)
that the data packet was the data packet. And that the data IN the
packet was 'end to end' for 'health and welfare'.
If nothing else, you would be forcing the issue of what you did to be
evaluated by TWO standards. One being the 'intentional obscurity'
of what you were sending, the other being the most judicious way of
handling 'health and welfare' as a public service. Hopefully, the two
would somewhat counter each other, and cool heads will prevail.
Mike
----------------------------------------------------------------------
Subject: APRS+SA v2.21 Patch File for EchoLink Tab
From: "The Hildebrands" <bhildebrand@earthlink.net>
Date: Mon, 14 Apr 2003 19:57:17 -0700
X-Message-Number: 24
I have uploaded an APRS+SA patch file that adds a new text substitution
tag for EchoLink. When using the tag, APRS+SA will search for running
programs on the system and if it finds one with "EchoLink - CALLSIGN"
where CALLSIGN is the callsign of your APRS+SA station, it will change
the <ECHOLINK> tab to "Yes", otherwise, it will be "No". Example of
use, station text of "EchoLink=<ECHOLINK>" would be change to
"EchoLink=Yes" on transmit if EchoLink is running. The file is
SubText.P221 at the FTP site below. The patch works with APRS+SA v2.21.
It might work with prior versions, but I have not tested it. To use it
with prior version, change the name of the file to SubText.Pxxx where
xxx is the version number (xxx for v2.21 is 221). Copy the file to your
APRS+SA directory, and either restart the program, or File menu, click
"Load Patch Files" to update the program without restarting. Note,
APRS+SA automatically loads patch files when restarting that program.
Again, the new text substitution tag is: <ECHOLINK>
Brent Hildebrand, KH2Z
APRS+SA
http://www.tapr.org/~kh2z/aprsplus
ftp://ftp.tapr.org/aprssig/winstuff/aprsplus
----------------------------------------------------------------------
Subject: Re: Opening up the proverbial can o' worms
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Tue, 15 Apr 2003 03:11:27 -0000
X-Message-Number: 25
I wonder what they consider acceptable encryption. I was playing around
with my scanner the other day and came across a channel in the 460 MHz band
that sounded like inverted sideband. I piped it through my soundcard and
fiddle around with the inversion point and had intelligible audio within a
minute or so. Listened to someone (local PD, maybe) conducting surveilance
on a couple of targets, coordinating tails. Not exactly a 'secure' channel.
----------------------------------------------------------------------
Subject: Re: Opening up the proverbial can o' worms
From: "Gregg G. Wonderly" <gregg@skymaster.cytetech.com>
Date: Mon, 14 Apr 2003 22:23:04 -0500
X-Message-Number: 26
>If I am sending health and welfare traffic during some storm or other
>catastrophe over a packet channel. I want to obsure the names of , say,
>recently deceased people before the families can be notified.... and I
>obscure the name with a well known code such as ROT13, does that violate the
>FCC rules about cyphers on the ham bands?
Two issues:
1. You are obscuring, so I'd say it would be a violation.
2. I'd just use connected mode packet on a simplex frequency so that
others wouldn't be as likely to hear.
Need more distance, then you might need to plan ahead to have a frequency
agile digi that you can borrow for this use. In particular, it would be nice
to have it along side a voice repeater, and use that repeaters controller to
manipulate the freq on the Digi.
-----
gregg@cytetech.com (Cyte Technologies Inc)
---
END OF DIGEST
Read previous mail | Read next mail
| |
