Re: [homenet] homenet: what now? ... next?
Mikael Abrahamsson <swmike@swm.pp.se> Wed, 13 March 2019 21:01 UTC
Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 307331311C6 for <homenet@ietfa.amsl.com>; Wed, 13 Mar 2019 14:01:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XbMpHie4Eo73 for <homenet@ietfa.amsl.com>; Wed, 13 Mar 2019 14:01:22 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABE9B1311CC for <homenet@ietf.org>; Wed, 13 Mar 2019 14:01:19 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 77A96B2; Wed, 13 Mar 2019 22:01:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1552510877; bh=EnHwCZljmbF6aqQxFTV0A+cCc8A+NQK7KE7cSiHFKVo=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=SNPgu+alQ/sp+LnxXoKdConCnpERP4XHsw2fO2s6SljU+EWI+gejzxSavbl5a/Svm B0hU5kLYzgDqKimTLXTyEP5oGVc61CUN5Ug+rw7YZRJekwV/bIyrZoStGQ4VBpMKoP /bu7l9u+oKIcxyC8ucBcKVYU68pesMcCayYfAaJw=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 756B8B0; Wed, 13 Mar 2019 22:01:17 +0100 (CET)
Date: Wed, 13 Mar 2019 22:01:17 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Michael Richardson <mcr+ietf@sandelman.ca>
cc: homenet@ietf.org
In-Reply-To: <4803.1551485670@localhost>
Message-ID: <alpine.DEB.2.20.1903132150430.3161@uplift.swm.pp.se>
References: <894b4181-c4ca-5cf1-adba-1c5fcab0d355@cs.tcd.ie> <90A48EC1-C13D-4B9B-9F04-252C0CC87084@fugue.com> <dbe6e19f-84c2-f2eb-b9ab-d085de7c299c@mtcc.com> <4803.1551485670@localhost>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/rYlC2rEIVxiTSAs8xlDTr0OszRg>
Subject: Re: [homenet] homenet: what now? ... next?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2019 21:01:24 -0000
On Fri, 1 Mar 2019, Michael Richardson wrote: > For the last 10 to 15 years the ISP-provided home router has come to dominate > the market, with the belief by the ISPs that this is a MUST that they control > the device. Many (but not all) at the IETF do not share this view, but most > non-technical users see the ISP provided router is simply saving the trip to > BestBuy, rather than an abdication of control over their home. If this > trend continues, then I believe that ISPs (residential IAPs) will come to > want to control all IoT devices in the home -- because security -- telling > residential customers what they can and not connect. I have data from some ISPs here pointing to 1% of the customers setting the media converter/router into bridge mode and providing their own HGW. Most people just keep whatever the ISP provided them with. Looking at the SSIDs I see, typically people don't even change the SSIDs/passwords from what came out of the box. A multi-router home isn't on the product managers radar. Their biggest issue right now, is customers complaining about bad service and most of the time this is related to bad wifi for the last 0-30 meters of access to the end-user device. If HOMENET somehow could help solve that problem (diagnosing bad wifi and helping the ISP/customer figure out what's wrong and what needs to be done) then HOMENET might get onto the radar and be of interest. The good thing is that the HGW is going from an unloved cost-cut necessity into a more important device that is a lot higher end device. It's gone from a 2-4MB flash / 16 MB RAM device, to nowadays often having 128-512MB RAM and 32-128MB flash (or even more). It now also is more likely to have aN ARM processor which is several times faster than the devices of 5-10 years ago. A negative though, is that it's also very likely to contain a packet accelerator that is quite constrained in what it can and can't do acceleration of. This might make some use-cases harder to achieve. Speeds have gone up and nowadays having 4x4 wifi chips in there that'll in practice support actual transport payload speeds of upwards of 1 gigabit/s on wifi isn't uncommon. We're also now seeing devices with even higher port speeds than 1GE, but that might take a bit longer to reach wider adoption. -- Mikael Abrahamsson email: swmike@swm.pp.se
- [homenet] homenet: what now? ... next? Stephen Farrell
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Michael Thomas
- Re: [homenet] homenet: what now? ... next? STARK, BARBARA H
- Re: [homenet] homenet: what now? ... next? Michael Thomas
- Re: [homenet] homenet: what now? ... next? Michael Richardson
- Re: [homenet] homenet: what now? ... next? Michael Thomas
- Re: [homenet] homenet: what now? ... next? STARK, BARBARA H
- Re: [homenet] homenet: what now? ... next? Ralf Weber
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Michael Thomas
- Re: [homenet] homenet: what now? ... next? Michael Richardson
- Re: [homenet] homenet: what now? ... next? STARK, BARBARA H
- Re: [homenet] homenet: what now? ... next? STARK, BARBARA H
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Stephen Farrell
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Stephen Farrell
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Ted Lemon
- Re: [homenet] homenet: what now? ... next? Mikael Abrahamsson
- Re: [homenet] homenet: what now? ... next? Toke Høiland-Jørgensen
- Re: [homenet] homenet: what now? ... next? Mikael Abrahamsson
- Re: [homenet] homenet: what now? ... next? Toke Høiland-Jørgensen
- Re: [homenet] homenet: what now? ... next? Mikael Abrahamsson
- Re: [homenet] homenet: what now? ... next? Toke Høiland-Jørgensen
- Re: [homenet] homenet: what now? ... next? Juliusz Chroboczek
- Re: [homenet] homenet: what now? ... next? Mikael Abrahamsson
- Re: [homenet] homenet: what now? ... next? Toke Høiland-Jørgensen
- [homenet] -CoDel David R. Oran
- Re: [homenet] -CoDel Toke Høiland-Jørgensen
- Re: [homenet] homenet: what now? ... next? Michael Richardson
- Re: [homenet] homenet: what now? ... next? Stephen Farrell
- Re: [homenet] homenet: what now? ... next? Michael Richardson