[Fud] Firmware updates and CoAP
Alexander Pelov <a@ackl.io> Thu, 09 February 2017 21:59 UTC
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, 09 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
- [Fud] Firmware updates and CoAP Alexander Pelov
- Re: [Fud] Firmware updates and CoAP Hannes Tschofenig