W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: HTTP 2.0 mandatory security vs. Amateur Radio

From: (wrong string) 陈智昌 <willchan@chromium.org>
Date: Wed, 13 Nov 2013 21:13:50 -0800
Message-ID: <CAA4WUYjkjTniUbDbffJ4Yd=03kc_Xd6gfo5AGG=fVAnbedB=fQ@mail.gmail.com>
To: Bruce Perens <bruce@perens.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Can you just use unencrypted HTTP/1.X?


On Wed, Nov 13, 2013 at 9:07 PM, Bruce Perens <bruce@perens.com> wrote:

>  Amateur radio, commonly referred to as "ham radio", is prohibited from
> using encryption to obscure the message content by both international law
> (an ITU treaty) and its implementations in the national law of most
> nations. However, we can use encryption that *doesn't* obscure message
> content for the purposes of authentication. Use of an https URL over an
> Amateur Radio connection would be a rule violation.
>
> Although I am well able to discuss the rationale for the prohibition of
> encryption, that's probably off-topic for this list. Please take it as a
> given that it's necessary and we like it this way. Anyone who wishes to
> know more can email me directly.
>
> Radio Amateurs use wifi-like networks, using 802.11 equipment on its usual
> frequencies or transverting it to other frequencies, and sometimes with a
> lot more power than non-licensed users are allowed.
>
> Although our routers often run OpenWRT or something similar so that we can
> add ham-specific protcols, we  use off-the-shelf computing equipment,
> operating systems, and web browsers.
>
> It would cause us some significant pain if web browsers stopped enabling
> unencrypted http connections. We'd have to proxy https to http before we
> allowed the signal on to Amateur frequencies, in order to remain in legal
> compliance.
>
> I doubt we're the only people in the world who must, or would rather, have
> their communications in the clear.
>
>     Thanks
>
>     Bruce Perens K6BP
>
Received on Thursday, 14 November 2013 05:14:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:19 UTC