Re: [Ace] Stephen Farrell's Yes on draft-ietf-ace-usecases-09: (with COMMENT)

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Fri, 23 October 2015 15:21 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 920A81A1C02 for <ace@ietfa.amsl.com>; Fri, 23 Oct 2015 08:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 z3OZudJQnFWC for <ace@ietfa.amsl.com>; Fri, 23 Oct 2015 08:21:48 -0700 (PDT)
Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (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 A4DE51A1EF6 for <ace@ietf.org>; Fri, 23 Oct 2015 08:21:47 -0700 (PDT)
Received: by qgad10 with SMTP id d10so73389488qga.3 for <ace@ietf.org>; Fri, 23 Oct 2015 08:21:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=T+0+PWOCLLfEmW2GXbx9D24Am2XBuvtJpHUc1tpAr/U=; b=JlqucZGLJEOiT3jpCrN/7NMPYcG71AfaLvWd3eb/7e6UeaLf+jQWCG610XUVxBf3kn v/Jk3v6a00RN3RFxR2Q9FfBFRVb7EkpfiIgI1tqFRExvjE7Y7iEOqapo3/z1nibsw6fh oAFLTW5oWOy4TU8QYYbEXE047ZGA8VdNGzlK/6PZmLJ/8oSblpz9JqoKb1lZ1j0lHM2X Br4ZYxmNmS23Kn7b7z4PI5L9dIWka9hd5NCQIANr9P/jwLi/5Z9lwvu8qGqT4d1vyER0 poimyrSRqS4dhzzWRWAv8mMvLyYGyjycEe9sLF0pABwmlLu4e8WfqpDJUTZ2FNpyADUW uXEw==
X-Received: by 10.140.39.199 with SMTP id v65mr2350487qgv.34.1445613706854; Fri, 23 Oct 2015 08:21:46 -0700 (PDT)
Received: from [192.168.1.3] (209-6-114-252.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com. [209.6.114.252]) by smtp.gmail.com with ESMTPSA id k201sm7011638qhc.34.2015.10.23.08.21.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Oct 2015 08:21:45 -0700 (PDT)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Google-Original-From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (12H143)
In-Reply-To: <562A4B07.9080305@tzi.de>
Date: Fri, 23 Oct 2015 11:21:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E79B71B-FBE1-4FB6-B9B9-16E6C44C67BA@gmail.com>
References: <20151022132903.23826.2689.idtracker@ietfa.amsl.com> <5629EA01.6020506@sics.se> <5629EED2.5080005@cs.tcd.ie> <CAHbuEH6LNA6XaY8kUkZZ20A+Jc2V4SWriDajuZOkxq2JFuZX0Q@mail.gmail.com> <562A3647.3030101@sics.se> <562A4B07.9080305@tzi.de>
To: Stefanie Gerdes <gerdes@tzi.de>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ace/s2TCdCd0BmffYCkBsZF67Er0XXI>
Cc: "ace@ietf.org" <ace@ietf.org>, Ludwig Seitz <ludwig@sics.se>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [Ace] Stephen Farrell's Yes on draft-ietf-ace-usecases-09: (with COMMENT)
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2015 15:21:54 -0000


Sent from my iPhone

> On Oct 23, 2015, at 10:58 AM, Stefanie Gerdes <gerdes@tzi.de> wrote:
> 
> Hi all,
> 
>>>> 1. Software update is really needed and often missing and
>>>> usually hard. There's at least a need to authenticate and
>>>> authorize new firmware, when there is any update. That may not
>>>> be the same as authorizing a new config.
>> 
>> 
>> Isn't this covered in section 2.4.1.3. ?
>> 
>> "At some point the facility management company wants to update the
>> firmware of lighting devices in order to eliminate software bugs.
>> Before accepting the new firmware, each device checks the
>> authorization of the facility management company to perform this
>> update."
>> 
>> There is simply not a specific authorization problem listed for this, I
>> could argue that it is subsumed under U4.4 but if you think it deserves
>> specific mention under the problems section I can live with adding a point.
> 
> I think adding a point in 2.4.3 is a good idea. We could also add an
> item to 3.3 that emphasizes the problem.
> 

Great, I think adding a point would be helpful.  You'd be authenticating the device to receive the update preventing fraud, which is different from the existing point referenced.

Thanks,
Kathleen 

> Thanks,
> Steffi