Re: [Suit] Firmware Update Paper

Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr> Tue, 03 December 2019 14:03 UTC

Return-Path: <emmanuel.baccelli@gmail.com>
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 26C1E12006B for <suit@ietfa.amsl.com>; Tue, 3 Dec 2019 06:03:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.471
X-Spam-Level:
X-Spam-Status: No, score=-1.471 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.073, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 u0FpL7k9Eu93 for <suit@ietfa.amsl.com>; Tue, 3 Dec 2019 06:03:04 -0800 (PST)
Received: from mail-oi1-f177.google.com (mail-oi1-f177.google.com [209.85.167.177]) (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 6469C120043 for <suit@ietf.org>; Tue, 3 Dec 2019 06:03:01 -0800 (PST)
Received: by mail-oi1-f177.google.com with SMTP id l136so3382048oig.1 for <suit@ietf.org>; Tue, 03 Dec 2019 06:03:01 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EAHkR+21+q6cY/nmMBwLUD99dFxHRwaiuy186dYY2xo=; b=hGti/FfpZI/hVbzWD8lhEaF6cl5rz3vrnvdbQdQG4ejZSH0RLRdoG718tcxIDVEdRN R9CfoAUWJCjexu4Dq38sXieEkCh30aubtyJ4+CLQsoiNkV8GXjna04MFdHHkaZwj0uFO RaExQHYQRIpQfE+xYVwaSVi3xdgXeW8lXMdO2TMeIENpqV7ETuj1A/Aw9rp8ERD7Ual/ JYNfLJg/w3JUI1K6vavVOOrqtFLeYaq22xKWCoQo/hQgRdxQ6alXetlAPqIOppFnWtuP QBgIbzaT6i/RecTsIZPybDgt+yB3ex7+PKq0UXPnL+0dTEWie4EO2ndLiGSFszkOnfOB gEjQ==
X-Gm-Message-State: APjAAAV5QVUCh3XaeWaD5tpwQMinLR8Ev9qmgJYHcA1JHygnpKl0Evyj tk49kTUuncMsrbGafm+buFYju772jsX3p4cXcDgxjw==
X-Google-Smtp-Source: APXvYqzcmPnLZrQvsj0AquBSWl9wyt6FYkFJ+mn49EraizUn9LTOq9H5S5wPaE/AQ0diU3SJyb0BeLE4DxE4doBLar8=
X-Received: by 2002:aca:b38b:: with SMTP id c133mr3476370oif.2.1575381780244; Tue, 03 Dec 2019 06:03:00 -0800 (PST)
MIME-Version: 1.0
References: <VI1PR08MB53600B1D1A194F49B67B90DFFAC60@VI1PR08MB5360.eurprd08.prod.outlook.com> <20191127203651.GA117656@davidb.org> <CANK0pbaWkn7w2swRgkOqsTubE1os=rDo2BLjrTZ5eW6ePv3WnA@mail.gmail.com> <20191129183627.GA16289@davidb.org> <DB6PR0801MB1879D9742622EA0AE08A8B72EA430@DB6PR0801MB1879.eurprd08.prod.outlook.com> <CABNHR1yEFvgEzHjBhpqTW-FX+LQTVYuSJE_9SP9OMwzjWsdORQ@mail.gmail.com> <CANK0pbaf8TTtMOSKHD0D-73+MCzSdjk7p+6hVO0WzpSxhF2fVg@mail.gmail.com> <23912.1575379400@localhost>
In-Reply-To: <23912.1575379400@localhost>
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
Date: Tue, 3 Dec 2019 15:02:48 +0100
Message-ID: <CANK0pbaNrAiAcYd=nVpo0kDfAj7nVzu=L8_GN-Yz1HB2tFq_DQ@mail.gmail.com>
To: "suit@ietf.org" <suit@ietf.org>
Cc: Koen Zandberg <koen@bergzand.net>, Kaspar Schleiser <kaspar@schleiser.de>
Content-Type: multipart/alternative; boundary="00000000000065b1ec0598cd27b2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/J9fJYaw1DySy0SuU9POplwWoQsI>
Subject: Re: [Suit] Firmware Update Paper
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 03 Dec 2019 14:03:06 -0000

Hi Michael,

in the paper, we implemented and comparatively evaluated various
configurations.
Some configurations use CoAP Block1, others use Block2 (see section IV.C.
in [1]).
For Table 3, CoAP Block1 is used, IIRC.
(Ccing Koen and Kaspar in case they know better).

cheers,

Emmanuel

[1] https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8725488


On Tue, Dec 3, 2019 at 2:23 PM Michael Richardson <mcr@sandelman.ca> wrote:

> Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr> wrote:
>     > in the paper [1] for our experiements we used CoAP as transport,
> over UDP,
>     > 6LoWPAN and IEEE 802.15.4 low power radio.
>
> CoAP Block Mode?
>
> _______________________________________________
> Suit mailing list
> Suit@ietf.org
> https://www.ietf.org/mailman/listinfo/suit
>