From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.lang.hm (rrcs-45-59-245-186.west.biz.rr.com [45.59.245.186]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 87FDE3CB38 for ; Wed, 11 Oct 2023 15:23:27 -0400 (EDT) Received: from dlang-mobile (unknown [10.2.2.69]) by mail.lang.hm (Postfix) with ESMTP id F10CC1B1D66; Wed, 11 Oct 2023 12:23:25 -0700 (PDT) Date: Wed, 11 Oct 2023 12:23:25 -0700 (PDT) From: David Lang To: "David Bray, PhD via Nnagain" In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="===============1877057784720178950==" Subject: Re: [NNagain] Internet Education for Non-technorati? X-BeenThere: nnagain@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: =?utf-8?q?Network_Neutrality_is_back!_Let=C2=B4s_make_the_technical_aspects_heard_this_time!?= List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Oct 2023 19:23:27 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --===============1877057784720178950== Content-Type: text/plain; format=flowed; charset=US-ASCII On Wed, 11 Oct 2023, David Bray, PhD via Nnagain wrote: > There's also the concern about how do startups roll-out such a label for > their tech in the early iteration phase? How do they afford to do the extra > work for the label vs. a big company (does this become a regulatory moat?) > > And let's say we have these labels. Will only consumers with the money to > purchase the more expensive equipment that has more privacy and security > features buy that one - leaving those who cannot afford privacy and > security bad alternatives? As far as security goes, I would argue that the easy answer is to ship a current version of openwrt instead of a forked, ancient version, and get their changes submitted upstream (or at least maintained against upstream). It's a different paradigm than they are used to, and right now the suppliers tend to also work with ancient versions of openwrt, but in all the companies that I have worked at, it's proven to be less ongoing work (and far less risk) to keep up with current versions than it is to stick with old versions and then do periodic 'big jump' upgrades. it's like car maintinance, it seems easier to ignore your tires, brakes, and oil changes, but the minimal cost of maintaining those systems pays off in a big way over time David Lang --===============1877057784720178950== Content-Type: text/plain; CHARSET=utf-8 Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: INLINE X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm5hZ2FpbiBt YWlsaW5nIGxpc3QKTm5hZ2FpbkBsaXN0cy5idWZmZXJibG9hdC5uZXQKaHR0cHM6Ly9saXN0cy5i dWZmZXJibG9hdC5uZXQvbGlzdGluZm8vbm5hZ2Fpbgo= --===============1877057784720178950==--