17 Apr
2014
17 Apr
'14
8:36 p.m.
More interesting to the discussion of part 97 referencing encryption is not
the definition of communication but the meaning of "meaning" as it applies
to the packet I'm handed to pass along further down the network. If I
get a packet composed of a string of 1's & 0's, say
0011001101001011110011010010...... it means to me exactly
0011001101001011110011010010..... and so long as I have done nothing to
obscure the meaning of that string of bits I don't know that I ought need
care what the upper 4 layers of the osi stack do with such upon recipt or
transmission. Ultimately what does "meaning" mean. that seems to me to be
where the meat is in this.
Eric
On Thu, Apr 17, 2014 at 4:37 PM, <lleachii(a)aol.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Actually, the point of the topic was to inform me if the application
worked as I described.
Since I noted that I'm of the opinion that encryption (in some cases) is
allowed on Ham Radio, that was a non-issue.
US Part 97 never says "encryption is prohibited," it says:
"RTTY and data emissions using unspecified digital codes must not be
transmitted for the purpose of obscuring the meaning of any communication."
What is a communication???
47 U.S. Code ยง 153(40) Radio communication:
'The term "radio communication" or "communication by radio" means
the
transmission by radio of writing, signs, signals, pictures, and sounds of
all kinds, including all instrumentalities, facilities, apparatus, and
services (among other things, the receipt, forwarding, and delivery of
communications) incidental to such transmission.'
You may wish to look through the list of digital codes specified in Part
97 and use Wireshark to sniff SSL packets...you may find you can read the
HTTP GET command, source, destination, requests, requests to exchange, etc.
in plain English, ASCII is exempt the last time I checked. Even on the
802.11 level, source, destination and acknowledgments can be read. I don't
want to enter a large debate, but I wouldn't suggest seeking a rule-making
on it either.
:)
-KB3VWG
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net