Re: [homenet] homenet: what now? ... next?

Michael Thomas <mike@mtcc.com> Sat, 02 March 2019 00:24 UTC

Return-Path: <mike@mtcc.com>
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 84F7312D7EA for <homenet@ietfa.amsl.com>; Fri, 1 Mar 2019 16:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 of0JPEP5js4z for <homenet@ietfa.amsl.com>; Fri, 1 Mar 2019 16:24:38 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) (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 40768130E7A for <homenet@ietf.org>; Fri, 1 Mar 2019 16:24:38 -0800 (PST)
Received: from Michaels-MacBook.local (170-75-133-42.volcanocom.com [170.75.133.42] (may be forged)) (authenticated bits=0) by mtcc.com (8.15.2/8.15.2/Debian-3) with ESMTPSA id x220OaZf009787 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <homenet@ietf.org>; Fri, 1 Mar 2019 16:24:37 -0800
To: homenet@ietf.org
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>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <41e6a363-2bb6-2789-e671-078d999d7819@mtcc.com>
Date: Fri, 01 Mar 2019 16:24:31 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <4803.1551485670@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/w_8CXJwelF4OW6-Ax3ejjnKalYw>
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: Sat, 02 Mar 2019 00:24:39 -0000

On 3/1/19 4:14 PM, Michael Richardson wrote:
>
> When we started this effort we heard of real situations such as Fred's
> original FUN BOF slides on how dual-geek households are forced not to share
> printers due to corporate home firewall requirements.  And that we should
> expect the situation to get worse.  Those slides are close to ten years old.
> I'd like to know if they are still at relevant.  Maybe they aren't.
> If not, why not?
>
I've been in startup land the last several years where everything is in 
the cloud and everybody brings their own device. At the office, it was 
just business cable. We got asked by a customer what our firewall was 
and we sort of looked puzzled. Where do you mean? There was no corporate 
network and no need for one. We outsourced all of the typical things 
that corpro IT does which was fine by us because who wants to spend time 
and money on reinventing wheels?

My point here is that companies who are started in the cloud -- which is 
just about everybody these days -- don't even understand the 
requirement. Maybe they do when they get big enough, but I'm not sure.

Mike