IETF Logo Mail Archive

Re: [Iotops] Automatically connecting to stub networks...

Ted Lemon <mellon@fugue.com> Fri, 04 December 2020 21:27 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: iotops@ietfa.amsl.com
Delivered-To: iotops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AEFF3A0CD8 for <iotops@ietfa.amsl.com>; Fri, 4 Dec 2020 13:27:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.886
X-Spam-Level:
X-Spam-Status: No, score=-1.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, NO_DNS_FOR_FROM=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 94t1Dberwupr for <iotops@ietfa.amsl.com>; Fri, 4 Dec 2020 13:27:35 -0800 (PST)
Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47ECB3A0C17 for <iotops@ietf.org>; Fri, 4 Dec 2020 13:27:35 -0800 (PST)
Received: by mail-qk1-x730.google.com with SMTP id z188so6875374qke.9 for <iotops@ietf.org>; Fri, 04 Dec 2020 13:27:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=VNvcFvBKhtQxoq7eOZlAOn4ltVkrsZPVsZB1zY8vNFM=; b=WCj/eWiuW8Uu0S16ABsG7sEcnpYv23HcV0yAzMAYxCguHDB11LfDvvId09OBFz9Dkc DNzJTixWbop6TlYLkrKKZdCqRTKtsCIjYU32iZjfixd5RLV7THDTyzcJek340Y36Uy0b SRXiEWRCrj5C+4xjHSrnvpxchB/qV8Jak305qiF5Yk+GyIz9iqMnTTMP6CEIycyXKtDA MK6j+ngCBK/NbwkTG0TErCkuR/Jbk2KSWbsRsBI4dINFH/IuPsxx3mD/1vF/b3MTUSQm ry5INzveK1zhkXjHu9YlTnmJFcXbqDozr4nYAzLAjbQ9+NYtppIUtfQTdt7rPiWQQ1R/ /ntQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=VNvcFvBKhtQxoq7eOZlAOn4ltVkrsZPVsZB1zY8vNFM=; b=Oly6v9Lc0tUxrRPsspxAiP9c5MvH0u9R+DqatjCQhRtBsohGr2o7ffpPY11vf9GQP5 n4mQZlxwaZEllt+nQh4zvIbQisflGlKoQ7AJboO/BhbfxWvcPby+NX5WuE0j632s1SMN LszV4M7SV4ePlD8T1vAfbyFMw/9H07ATXnY8TMMBvRu8jV128FWTjXJqM+hm72w8cxN8 OFoASrFAMFBC0mSnruGXOH9rtFmqUXXsLrfziPswmqBvIHRTbeIUCUdA4Weik56RptHX qVt6SvA3tKzBLzu1hQVSZRAsyjgJ2pDEDcnn+BEvOhr+lkMBqGNjNSTCBJvyhgbFao5Q w4AA==
X-Gm-Message-State: AOAM531+BxywqKpEvHzV3BTf63pTKyUjEuNZqDIKDYsXm7o877chhdC5 xsFuXKQTIl8AwHvJ2zC2lM2Mhg==
X-Google-Smtp-Source: ABdhPJxWBgk/JJHOAAjIh5FVYVjCBcTyYI1TiZ0ucJm0dJyvN4cvocIQmHiC+FkiPyArsvz1piyAew==
X-Received: by 2002:a37:6892:: with SMTP id d140mr11734812qkc.200.1607117254148; Fri, 04 Dec 2020 13:27:34 -0800 (PST)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id o13sm5758814qkm.78.2020.12.04.13.27.33 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 Dec 2020 13:27:33 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <25EB2B8B-2C16-4E79-9BC1-2654634FBD68@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8910F496-728F-4A0B-B3B3-05BE8170D1A7"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Fri, 04 Dec 2020 16:27:30 -0500
In-Reply-To: <784BB35E-D9A3-413B-912D-46D12CCB34B8@employees.org>
Cc: Toerless Eckert <tte@cs.fau.de>, 6MAN <6man@ietf.org>, iotops@ietf.org
To: Ole Troan <otroan@employees.org>
References: <695953.1606952552@dooku> <B989299A-ED3C-4205-A4E2-DA080F574B33@fugue.com> <20201203174901.GW44833@faui48f.informatik.uni-erlangen.de> <36EA3F9D-A79D-4BC0-B894-54B7D3054476@fugue.com> <20201204064930.GY44833@faui48f.informatik.uni-erlangen.de> <B9DC56CD-E2A7-469C-9E8F-596554DA1A80@employees.org> <20201204085738.GZ44833@faui48f.informatik.uni-erlangen.de> <784BB35E-D9A3-413B-912D-46D12CCB34B8@employees.org>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iotops/SvqApfCJrK0VVi8PGNLvfbcdgF8>
Subject: Re: [Iotops] Automatically connecting to stub networks...
X-BeenThere: iotops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IOT Operations <iotops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iotops>, <mailto:iotops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iotops/>
List-Post: <mailto:iotops@ietf.org>
List-Help: <mailto:iotops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iotops>, <mailto:iotops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Dec 2020 21:27:37 -0000

On Dec 4, 2020, at 4:19 AM, otroan@employees.org wrote:
> Yes, I believe this was also discussed in homenet.
> In Ted's case as well as many others devices are controlled with umbilical cords to other administrative domains.
> They should in theory not be more trusted inside the network than a host from the outside.
> This is a hard one.

I think generally for IoT devices controlled by the cloud reach out to the cloud rather than the cloud reaching in. I think James Woodyatt years ago said that Nest did this with an IPv6 tunnel, but in any case I think these are provider-specific solutions and not really something the IETF needs to work on.

My goal in documenting our stub router solution is (1) so that people can point out issues they see with what we’ve done. Real issues, please. And (2) because it can serve as a base specification that various specific documents can reference. I think it has general utility, although my current use case is 802.15.4 mesh (Thread).

v2.23.0 | Report a Bug | By Email