KB3VWG et al,
The FCC disagrees with your statements on encryption. The concern is
regarding the ability of others to receive your transmission's content. A
PL tone does not block the ability for an external party to receive the
message. Quoted from FCC DA13-1918, released on 18 September 2013: "Section
97.113 is intended to help maintain the non-commercial character of the
amateur radio service by prohibiting certain types of transmissions. The
primary protection against exploitation of the amateur service and the
enforcement mechanism in the amateur service is its self-regulating
character. [...] amateur stations must be capable of understanding the
communications of other amateur stations. The content of messages that are
encoded, however, are known only to those stations that have the code used
to encode the message. In the case of encrypted messages, the message
content is known only to stations having the encryption algorithm or key."
It is reasonable to believe that if a third party cannot reasonably
determine the contents of a message (eg, more than just metadata), that
transmission is in violation.
Also a few posts prior, KB3VWG stated "US Part 97 never says 'encryption is
prohibited'". While this is true, it is unwise to interpret that loosely.
The phrase "prohibition on encryption" is used multiple times in FCC order
DA13-1918. While this is not as unequivocal as a statement in CFRs, it does
provide insight to their intent of part 97, and we should act accordingly.
Note that authentication mechanisms are not part of the identifying
character of a transmission's nature. In the same petition, the ARRL
submitted comments that stated "the ARRL has previously advised members,
following discussions with Commission Enforcement Bureau and Wireless
Bureau staff, that encoding exclusively for authentication purposes does
not violate Section 97.113(a)(4)". These remarks were not addressed in the
FCC's order, but other parts of the comment were referenced and quoted
directly. We should continue to operate with the understanding that the use
of encryption for the purpose of authentication is permissible and
certainly not a gray area.
Luckily the FCC recognizes that this ban on encryption (and other
"impediment"s to hams) is an issue suitable to be resolved in
administration rather than legislation. I remain hopeful that this may be
resolved in petitions. As always, I am not a lawyer, you should not act on
my opinion, and you are wise to completely ignore my message.
Cheers,
K0RET
On Thu, Apr 17, 2014 at 10:38 PM, <lleachii(a)aol.com> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Don,
You mentioned a sernario where 802.11 itself is encrypted, I disagree
that's legal (see below). I'm also under the impression that, in some
cases, the return packet may be a 3rd party communication (if you want to
discuss this from Layer 3); but I won't get into that, since I purposely
stuck to Layer 1 to formulate my theory.
The "communication" here is an 802.11 frame (which happens to contain an
Ethernet [802.3] frame, which contains an TCP/IP packet). So, at the
'nitty-gritty' of RF, I'm sending you an 802.11 frame by DSSS or OFDM - by
Part 97, I can't obfuscate the 802.11 WLAN frames (so encrypted access
points may be a no-no here, but ARRL even says that the code can be
'published' and they believe that solves the closed access point issue - I
suppose analogous to someone not knowing the PL tone to transmit, if you
will; but I don't 100% agree).
I'm 100% aware some stations may disagree with that notion; but as far as
I'm concerned, I can sniff 802.11 frames all day, if I can determine the
callsign somewhere, tell if it's 802.11, tell the device MACs and that it's
an Ethernet frame (even even more, that it's ICMP/TCP/UDP/GRE/IPENCAP/etc.),
we're within the scope of the Part 97.
-KB3VWG
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
--
Ryan Turner