IETF Logo Mail Archive

Re: [Suit] SUIT Architecture -- Operating modes

Matthias Waehlisch <m.waehlisch@fu-berlin.de> Wed, 06 June 2018 10:27 UTC

Return-Path: <m.waehlisch@fu-berlin.de>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7D4C130EE5 for <suit@ietfa.amsl.com>; Wed, 6 Jun 2018 03:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 wKbvvbCpsjZD for <suit@ietfa.amsl.com>; Wed, 6 Jun 2018 03:26:58 -0700 (PDT)
Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 A4EC6130E5F for <suit@ietf.org>; Wed, 6 Jun 2018 03:26:58 -0700 (PDT)
Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from <m.waehlisch@fu-berlin.de>) id <1fQVeZ-001sVM-Dg>; Wed, 06 Jun 2018 12:26:55 +0200
Received: from ze304.pia.fu-berlin.de ([87.77.227.4] helo=mw-x1.zedat.fu-berlin.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from <m.waehlisch@fu-berlin.de>) id <1fQVeZ-000xqc-7V>; Wed, 06 Jun 2018 12:26:55 +0200
Date: Wed, 06 Jun 2018 12:26:53 +0200
From: Matthias Waehlisch <m.waehlisch@fu-berlin.de>
To: Dave Thaler <dthaler=40microsoft.com@dmarc.ietf.org>
cc: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "suit@ietf.org" <suit@ietf.org>
In-Reply-To: <CY4PR21MB07746C16253D71D61702C90DA3650@CY4PR21MB0774.namprd21.prod.outlook.com>
Message-ID: <alpine.WNT.2.00.1806061206490.13556@mw-x1>
References: <VI1PR0801MB211259B72731F37766C0227CFA650@VI1PR0801MB2112.eurprd08.prod.outlook.com> <CY4PR21MB07746C16253D71D61702C90DA3650@CY4PR21MB0774.namprd21.prod.outlook.com>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
X-X-Sender: waehl@mail.zedat.fu-berlin.de
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Originating-IP: 87.77.227.4
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/cOaGRd6GV7BZaHYo_9R2f_P60CY>
Subject: Re: [Suit] SUIT Architecture -- Operating modes
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2018 10:27:02 -0000

On Wed, 6 Jun 2018, Dave Thaler wrote:

> The notification of an update can be device initiated (pull) or remotely initiated (push).
> The transfer of the actual image can also be device initiated (pull) or remotely initiated (push).
>
  in general I agree with this classification but just wondering about 
"initiated". How would you map a remotely initiated pull, e.g., someone 
logs in to the IoT device to trigger the update?


Cheers
  matthias


-- 
Matthias Waehlisch
.  Freie Universitaet Berlin, Computer Science
.. http://www.cs.fu-berlin.de/~waehl

v2.46.0 | Report a Bug | By Email | System Status