[Dtls-iot] Interoperable Software Update Mechanism

Hannes Tschofenig <hannes.tschofenig@gmx.net> Tue, 21 July 2015 12:32 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: dtls-iot@ietfa.amsl.com
Delivered-To: dtls-iot@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2DA1A1AF0 for <dtls-iot@ietfa.amsl.com>; Tue, 21 Jul 2015 05:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Qj1hOf5-QHQM for <dtls-iot@ietfa.amsl.com>; Tue, 21 Jul 2015 05:32:13 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73F8A1A1AB3 for <dtls-iot@ietf.org>; Tue, 21 Jul 2015 05:32:13 -0700 (PDT)
Received: from [192.168.10.134] ([62.168.35.67]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0Ltqmn-1YqTgk3PZV-011ABd for <dtls-iot@ietf.org>; Tue, 21 Jul 2015 14:32:11 +0200
Message-ID: <55AE3BCA.8040202@gmx.net>
Date: Tue, 21 Jul 2015 14:32:10 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: "dtls-iot@ietf.org" <dtls-iot@ietf.org>
References: <55AE3BA1.7080804@gmx.net>
In-Reply-To: <55AE3BA1.7080804@gmx.net>
OpenPGP: id=4D776BC9
X-Forwarded-Message-Id: <55AE3BA1.7080804@gmx.net>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="UcWMX9UjhfnX53TtwnHLqEceQOJHK09uq"
X-Provags-ID: V03:K0:oCSXesNv0vXmVF/FlMlTmayKMCOo7AlTflUHdR1Ehnl0cOuXA1/ pMfERz9AiFYc0nMwYHLmu3SmQMdr0NOLCvbp7qcVxYKSluIQttMTGdOma+KQdFFhslad3Vr FsUoOY5EedHWkV4L8BrdyHdduUHJGwW8E56EJhD/9NSQycGLf/VdMjfpipKFkO4ksRpKhuN 7HSf8YoSCfIHYx5UVwJbg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:flxyD/SILd4=:Bz8LwhWqKI5+aKPHn2wSXJ ZiFDPgz4zuevYkLLzSF2Adeq82dwuw0DFGtuTVhtdOO0l5N48jWKhbJWSOVDzM5NjI4KYWe3/ Q29ZMStJ++w19ARxruv/o/TnDSAhVpbL5wD4K5maoQ/QhfZP5U4S+AgIHYBoKpJQBx+u+BmpE qn0XhbAxld8xcvwQMoF1rhNq8sAu+kg6HACqhmiMA7MRqt45wX16lC/kb5hXddxdb5Lqqwevi a7N+6YoSwFQhUqTAdK2PO7doC3fJWs7hmlwsPNHgkaj87Y0XP+fUXmuySXhHeFD92/mt11uYc IG2y/Rgh3WpesOf1UsqlwqwaErm2BlxPuKIz8Rzu6DDUWo3363TPgG8QxATrI50Yf8gsraJWf G0seCDecaIa8VjEdo+P72gZETDyEB+g/QEri5YSRE47hCf3yOCBwcarXmCdN6f+IF0nEiZlwn ItT0GfgiTd7i93rSAjWchC+ltfU91Ry+urKuH06Mpv//igfCnjl6E8iqCTKur3GI8sXwr9nCI e02r2kxfWvLy0ltpHsvSzBCOVKF1AB/h8RauOsFLxVcHpqiSebIq6CtrrPsKu9Oi67/SLjKRU Pj/V06qFd4ZpC9yWQ67Jt2jsBEnJLWCZH0jicB7hHn1Mom78CV90dZnyJnXeHDn8ivJtOy6PI VelH3frOc//7wKRi1aJq+E8+RBLayRofk0Kkc8CwTzLgnx6WmDMq4UICtBs7pYi1nSVM=
Archived-At: <http://mailarchive.ietf.org/arch/msg/dtls-iot/lZng6IiWb8ABzG3w4b_1i6328kg>
Subject: [Dtls-iot] Interoperable Software Update Mechanism
X-BeenThere: dtls-iot@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DTLS for IoT discussion list <dtls-iot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dtls-iot/>
List-Post: <mailto:dtls-iot@ietf.org>
List-Help: <mailto:dtls-iot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dtls-iot>, <mailto:dtls-iot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jul 2015 12:32:15 -0000

Stephen wrote:

(3) 6.3: How can you have a MUST for s/w update when
there is no well-defined interoperable way to do that. I
think s/MUST/need to/ would be right here. (I'd love to
see us define the IETF bits of a s/w update mechanism
that could be referenced via such a MUST but we don't
have that today so it's a bogus MUST as written.)

You are right. The use of RFC 2119 language was incorrect.
I changed the sentence and removed the must. Since I changed the text in
Section 6 already based of one of your other comments.

Ciao
Hannes