Re: [T2TRG] T2TRG discovery session notes

Ralph Droms <rdroms.ietf@gmail.com> Fri, 14 April 2017 13:28 UTC

Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 497EB12EC9B for <t2trg@ietfa.amsl.com>; Fri, 14 Apr 2017 06:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 7LnZU76071RQ for <t2trg@ietfa.amsl.com>; Fri, 14 Apr 2017 06:28:45 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (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 AA246129422 for <t2trg@irtf.org>; Fri, 14 Apr 2017 06:28:45 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id v3so65154797qtd.3 for <t2trg@irtf.org>; Fri, 14 Apr 2017 06:28:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QzeFdcCo3aekDY/ihc6O634JmWTauKH8dIwjse/eYAo=; b=YAk+VY2U8Bk46UaONwderWTm1sELj2dPSI+IbDJgIEV92qXBxo4rDbrxM7duQCUqpW MTF9qx5c20kZJ20+xXsguv/mfhYAzw3tcExTQsJJ71KREDXmqOvFQP0nBOReoVD5VTXz 3QYO2uRk8a8NDBKje1kBdSO15p06IPt7I0qCrCLiSGSBLe15QygJLUZ5GnjpiUw4AjqC Gb1Vi8emxIcnKFnJhNxW94whm/2JW4oNXXX8LksMv4F0s1pTQezXEzGe68SOewAyslKT UbZDk1U0QH2NMSjnwx31bIH7Dnr978vTvZqEh3W6Z+wY/v4fSUivUZHCR+cvl6M+v1V8 AaPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QzeFdcCo3aekDY/ihc6O634JmWTauKH8dIwjse/eYAo=; b=gQOBSj4RtDzyjzkB2wMsBE13+Yfvz8uuGnlxeyLyrS4cTV4WBm/on2v+TLnABKEtoR wH0Mq5zQPdAiLxK1eHXlD+kLYWH13V6dZeespCppVSKwdQF6XaOerMDUnncmU/j/N6Nr EYXpCIY79nL91AuY4LsEJzPtRwPhwNEWLmnuf6ZhI0Pyf3Le+HQa3gAX3KGwsFGgbd+R 4PwzmhqHUHZmBcskrLZP2ruB6uvL6oNIL4kJ4SwwtktXjM2SHqo000w5gumpRoqFmDkg xaF2k7O80uctwSJmPxybp1neeIqtG5wwgbbAlE/J5wQPY69qGKIC4eX6n+hWs2wM2zmm 6u+A==
X-Gm-Message-State: AN3rC/5oCgUqcPTR9Hub/b3yuJolnAaoym3KdcBYUDeUJimVglIoQ/ag DWsTBqzbR9NHcMA7DSo=
X-Received: by 10.237.47.194 with SMTP id m60mr8331682qtd.9.1492176524718; Fri, 14 Apr 2017 06:28:44 -0700 (PDT)
Received: from ?IPv6:2601:18f:801:600:50fd:e2b2:8482:1d0b? ([2601:18f:801:600:50fd:e2b2:8482:1d0b]) by smtp.gmail.com with ESMTPSA id 1sm1239408qtb.40.2017.04.14.06.28.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Apr 2017 06:28:44 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <9413AFB5-F562-4F72-8C04-1F8792AADC40@ericsson.com>
Date: Fri, 14 Apr 2017 09:28:42 -0400
Cc: Ari Keränen <ari.keranen@ericsson.com>
Content-Transfer-Encoding: 7bit
Message-Id: <4FC3AFC3-0B89-4EC3-8F85-45F6FC51B621@gmail.com>
References: <C921BE33-4B35-4981-9069-0814837AF89E@tzi.org> <606367FA-C04B-41D2-A70D-4202668BA951@tzi.org> <8F27BE83-0A0E-4DBA-9156-9E8A8F85E35D@gmail.com> <c18c0872-fcab-f9be-adc3-718052b6acff@sonic.net> <A4851CF6-7656-4E49-A918-3711C2BBF152@ericsson.com> <487F409B-C7F6-4EF1-A4E0-C18213618FD3@ericsson.com> <9413AFB5-F562-4F72-8C04-1F8792AADC40@ericsson.com>
To: t2trg@irtf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/Ik19WhYCpGLMqdcNl1F5Wx-h_g0>
Subject: Re: [T2TRG] T2TRG discovery session notes
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 13:28:47 -0000

Report from t2trg breakout session, 2017-03-27.

Thanks to Dominique Barthel for taking notes.

Topic: What problems need to be solved before I can transfer ownership
of IoT devices when I sell my house?

Summary/Conclusions:

1. IoT devices exist in a web of relationships and interconnections.
Some devices will be part of systems that stay with the house and,
therefore, must be transferred to the new owner, while other devices
will go with the old owner to a new residence.  Any configuration
state that links devices that will stay with the home with devices
that will leave must be cleared.  Similarly, any configuration state
that represents confidential information about the old owner must be
cleared.  There may be some parallels between the process for IoT
devices and familiar processes for transfer of utilities accounts, but
the scale of the interconnections will complicate the transfer process
for IoT devices.

2. The relationships among IoT devices may be mitigated by
controllers, where ownership and control of a set of IoT devices may
be managed through a single controller.  Similarly, cloud services may
allow transfer of ownership of an entire system of IoT devices through
a single interface.  The relationships may change dynamically; for
example, the IoT devices in an automobile may have a relationship with
devices in a home while parked at home, but then have a different
relationship while away from home.

3. The transfer can take place in one of two ways: as a direct
transfer from the old owner to the new owner or through a trusted
third party.  The transfer process must ensure that the new owner has
complete and exclusive authority over the devices.  Authority to
access the devices from external sources like a personal smart phone
must be revoked.  There may be parallels between transferring
ownership between owners and an initial transfer from manufacturer to
the first owner.

4. Other events, such as home rental, providing access to service
personnel or allowing one-time access for a delivery, will have
similar considerations.