From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <david@lang.hm>
Received: from bifrost.lang.hm (lang.hm [66.167.227.134])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id 7FEBE3B2BE;
 Mon, 14 Mar 2016 15:04:12 -0400 (EDT)
Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100])
 by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id u2EJ43Mv005524;
 Mon, 14 Mar 2016 11:04:03 -0800
Date: Mon, 14 Mar 2016 12:04:03 -0700 (PDT)
From: David Lang <david@lang.hm>
X-X-Sender: dlang@asgard.lang.hm
To: dpreed@reed.com
cc: Wayne Workman <wayne.workman2012@gmail.com>,
 bufferbloat-fcc-discuss <bufferbloat-fcc-discuss@lists.redbarn.org>,
 cerowrt-devel@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net
In-Reply-To: <1457977740.938414893@apps.rackspace.com>
Message-ID: <alpine.DEB.2.02.1603141202190.25586@nftneq.ynat.uz>
References: <1457964158.79616218@mobile.rackspace.com>
 <7E8F9D99-38F8-47CD-960E-45100844B161@gmail.com>
 <CAEfCu-oCfO+FfdLjpZDSwQmZ7-Mc+X4vDvzZMNrnp+p8ut8OKQ@mail.gmail.com>
 <1457977740.938414893@apps.rackspace.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [Cerowrt-devel] [Make-wifi-fast] [bufferbloat-fcc-discuss]
 arstechnica confirmstp-link router lockdown
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
 <cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
 <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
 <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2016 19:04:12 -0000

On Mon, 14 Mar 2016, dpreed@reed.com wrote:

> An external "limit-exceeding signal detector" could also be very inexpensive, 
> if it did not need to do ADC from the transmitted signal, but could get access 
> to the digital samples and do a simple power measurement.

I agree with this, but have concerns about how you can lock down part of the 
firmware and not all of it.

You still have the problem of telling the chip/algorithm which set of rules to 
enforce, and updating it when the requirements change.

David Lang