
From nobody Thu Feb  9 13:59:19 2017
Return-Path: <a@ackl.io>
X-Original-To: fud@ietfa.amsl.com
Delivered-To: fud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 246E6129CAA for <fud@ietfa.amsl.com>; Thu,  9 Feb 2017 13:59:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 63qD5dV-QydW for <fud@ietfa.amsl.com>; Thu,  9 Feb 2017 13:59:15 -0800 (PST)
Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [IPv6:2001:4b98:c:538::197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCCED129CA6 for <fud@ietf.org>; Thu,  9 Feb 2017 13:59:12 -0800 (PST)
Received: from mfilter13-d.gandi.net (mfilter13-d.gandi.net [217.70.178.141]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id DADF441C08A for <fud@ietf.org>; Thu,  9 Feb 2017 22:59:10 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter13-d.gandi.net
Received: from relay5-d.mail.gandi.net ([IPv6:::ffff:217.70.183.197]) by mfilter13-d.gandi.net (mfilter13-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id ggtTV6C96SyD for <fud@ietf.org>; Thu,  9 Feb 2017 22:59:09 +0100 (CET)
X-Originating-IP: 37.164.178.174
Received: from [192.168.43.129] (unknown [37.164.178.174]) (Authenticated sender: alex@ackl.io) by relay5-d.mail.gandi.net (Postfix) with ESMTPSA id 5A92041C08B for <fud@ietf.org>; Thu,  9 Feb 2017 22:59:08 +0100 (CET)
From: Alexander Pelov <a@ackl.io>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Message-Id: <F1D42897-2A38-4A2C-B3B2-04FA85E497D1@ackl.io>
Date: Thu, 9 Feb 2017 22:59:08 +0100
To: fud@ietf.org
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/p_HdTos5XLH0EvSz6c-ptYxjs44>
Subject: [Fud] Firmware updates and CoAP
X-BeenThere: fud@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: FUD - Firmware Updating Description <fud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fud>, <mailto:fud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/fud/>
List-Post: <mailto:fud@ietf.org>
List-Help: <mailto:fud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fud>, <mailto:fud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 21:59:18 -0000

Dear all,

This is indeed a very interesting work and I would be looking forward to =
learn more about the gaps you think should be addressed in the first =
place.

Do you think the focus of the future work should be exclusively on =
updates via CoAP, should it include more generic approach (RESTful or =
not), or do you think there should be separate tracks of work? There are =
already some works on CoAP multicast, but maybe this work would need to =
be adjusted for firmware updates?

Best,
Alexander


From nobody Sat Feb 11 01:33:50 2017
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: fud@ietfa.amsl.com
Delivered-To: fud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A390F129468 for <fud@ietfa.amsl.com>; Sat, 11 Feb 2017 01:33:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.487
X-Spam-Level: 
X-Spam-Status: No, score=-4.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 MwWwYCrR3-Br for <fud@ietfa.amsl.com>; Sat, 11 Feb 2017 01:33:47 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 BE712129502 for <fud@ietf.org>; Sat, 11 Feb 2017 01:33:46 -0800 (PST)
Received: from [192.168.91.173] ([88.128.80.215]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MEsXW-1ce8kA0v1O-00Fzry; Sat, 11 Feb 2017 10:33:40 +0100
To: Alexander Pelov <a@ackl.io>, fud@ietf.org
References: <F1D42897-2A38-4A2C-B3B2-04FA85E497D1@ackl.io>
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Openpgp: id=071A97A9ECBADCA8E31E678554D9CEEF4D776BC9
Message-ID: <106c3852-c330-3dbd-62ac-08edfc3664bf@gmx.net>
Date: Sat, 11 Feb 2017 10:33:38 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <F1D42897-2A38-4A2C-B3B2-04FA85E497D1@ackl.io>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6xRWpeTCLTgIJBetgAU6ihcwo5QbAOkcH"
X-Provags-ID: V03:K0:4t9qXPqaEJpKZhvThgDX6sexjQljH/t0Trs+SbjMnSjOtBFI+8B AFznebkwXw18sCBDGpdFh03dSauVC8MGhpKaMvS/CldgVIcGEBTsOVB4JL27LCXZcMs0QHG KhXd364oDfniTr5wb605P7WNxsWzU+bGMvqnMGh58AoOdyT97qFoDA0YaMp2fHEIM9ypQOZ Pfu5alA9v+Rn2Tc78lnmQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:1jlg3u3UCiA=:QMChCklgEOQEue/h+BTZzN joue1m4g5GdwuNCn7jENgzZVnn6qSJorEjrwVgCqGLGqXyZccD7vTwq7RwwF6Kfvw86xL188L kNidBY3otzh5l/iPCYA1Qrjfa1wWUII0fppC1N0uvRZC+WDKeQzubVpvW3I1bFE7qnT3go6db DCK0pRcLCHhJcyyO5XZPl3ulaR8xSPFb0dU6ZtoRgzkn/X/vsloxgRrBJEXMDt9bqpLaXTCBY EpMTe1FH+5tlfvNL8RHx4i+ztbkaNNaa9m9MDUxPpJ8fvEn6rR53A8ii5JIAu+h/MJKqYd9Pv HaoAS/dt1pLbSAfcc0qgbbiq01SliCv8G7rVWjsSydd6h/71pAn7wYS7I3ZqbV8CbUfCu23o3 w+vwwW7G17UZrKB232Ir/eBlo+r+coMcjCq3uuoo77zhyK+JL/j8pLyfuu18uP+GqDENhW5Mz cxvOBwtJVNKusI7JBPdCcbmtoq66G8deVhgjRKN34OTGaufyIZqOVL76l7/7DwjY3cheUKvhA KBx0e4iDjh36GQMuNlC/TmwApe61ILKimlgz/A8ZBPS+23p97deAGaJVBkUrkMX13SKYP9qQM 4aup/L9HhecX6hfYKVA6U0HpPaQYKHINaZVLj8olWl2EsKCubfqw1SlU402U93V5wPF28pz7P MwedtjktJqrU1oYgWhShjFIoaZfUki9/btBj7Pws5/DyRz+ONy0XvT8SBNzKzGl3xLCx5mC20 5KFmW/yMkscZOOsz64It+AyoYZ6iAEz6/xJpKYTJQ0TJHstbblUNPYWSQaVwtQUIEH9RK3MJN PQuXZKD1WpAD+olOW/Ey0LiL7Aik/cuUGx5GSuhjg12rnv4JodjhoaCwPD9kTYpUHiEsj6hfN rgLLHNtUitaW9aEZ+/nTu0vjFSh08gH3mmJm5hRclCnbtkykJiJ7oHcQTPBfz3uTAnVeTc3Uo MJlyNfqJ+bQg7beDQyw8OBMDhS2GJVOxKqOOySBJOMCGaaYXNw4JcCiHaqWDdzbnYWwyqlC+g M1yqt0JHascI4LRuQMmhWTw=
Archived-At: <https://mailarchive.ietf.org/arch/msg/fud/H9V6Hp295eDgI_rlHoSzElyphzs>
Subject: Re: [Fud] Firmware updates and CoAP
X-BeenThere: fud@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: FUD - Firmware Updating Description <fud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fud>, <mailto:fud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/fud/>
List-Post: <mailto:fud@ietf.org>
List-Help: <mailto:fud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fud>, <mailto:fud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 09:33:48 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6xRWpeTCLTgIJBetgAU6ihcwo5QbAOkcH
Content-Type: multipart/mixed; boundary="i9u1KcJt7ccWuE5ompcc7A7gJ9Vjb3THx";
 protected-headers="v1"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
To: Alexander Pelov <a@ackl.io>, fud@ietf.org
Message-ID: <106c3852-c330-3dbd-62ac-08edfc3664bf@gmx.net>
Subject: Re: [Fud] Firmware updates and CoAP
References: <F1D42897-2A38-4A2C-B3B2-04FA85E497D1@ackl.io>
In-Reply-To: <F1D42897-2A38-4A2C-B3B2-04FA85E497D1@ackl.io>

--i9u1KcJt7ccWuE5ompcc7A7gJ9Vjb3THx
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Alexander,

Good questions and here is how I see the story.

For an interoperable firmware update solution you need the following
building blocks:

 a) A transport mechanism to get the firmware images from a repository
to the clients. While this sounds trivial it is actually quite complex
since you often need to know exactly what device you are dealing with to
provide it with the appropriate image. Hence, this is a bit different to
the way how software is updated on Linux-based systems with their
package manager.

 b) You need a security wrapper that protects the actual firmware image.

 (c) Finally, you need information about the firmware image itself. Call
it meta-data.

We are using LwM2M, i.e., a CoAP-based RESTful API protocol for (a), for
(b) you could use something like RFC 4108 (or similar). For (c) we have
a bit of meta-data defined in the LwM2M spec and there is some info also
defined in RFC 4108.

We are suggesting to revisit RFC 4108 (b) and define additional
meta-data (c).

Does this make sense?

Ciao
Hannes

On 02/09/2017 10:59 PM, Alexander Pelov wrote:
> Dear all,
>=20
> This is indeed a very interesting work and I would be looking forward t=
o learn more about the gaps you think should be addressed in the first pl=
ace.
>=20
> Do you think the focus of the future work should be exclusively on upda=
tes via CoAP, should it include more generic approach (RESTful or not), o=
r do you think there should be separate tracks of work? There are already=
 some works on CoAP multicast, but maybe this work would need to be adjus=
ted for firmware updates?
>=20
> Best,
> Alexander
>=20
> _______________________________________________
> Fud mailing list
> Fud@ietf.org
> https://www.ietf.org/mailman/listinfo/fud
>=20


--i9u1KcJt7ccWuE5ompcc7A7gJ9Vjb3THx--

--6xRWpeTCLTgIJBetgAU6ihcwo5QbAOkcH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJYntpzAAoJEGhJURNOOiAt2GUH/2hJ5xjagr8r3t5h/4etjaRY
HaZ49rdQKEDlqZ2Mm6LHxi2T4/w6gusdRpTgn6/o2s+4YGdUrL5a1U3F0BC5yh6E
jUimqTcsHaiZi8cs7+eDzaPswAfgxh40ddIZ8mo03pDEZp0bNS4LkDfed8TMJK1p
knGg7yOwoIEKiF+XyDyXFqt+MKHXAH5GgAAeZRfN5GLesnY/StVlYti7jasFbcEi
LEHwn6piGjLdtJgnxitGEpjCJTUs/Fcye2W701MgkFsUKOJM2bZO4EAjfxjzDKG/
ByiJ1+GStxJYHjUJlwLn2iI7j1w6y8GP1msfGvajpudiqkFr4MZUwo2KAkRgxWY=
=cX9k
-----END PGP SIGNATURE-----

--6xRWpeTCLTgIJBetgAU6ihcwo5QbAOkcH--

