IETF Logo Mail Archive

Re: [T2TRG] [saag] New Version Notification for draft-irtf-t2trg-iot-seccons-02.txt

Barry Raveendran Greene <bgreene@senki.org> Wed, 05 April 2017 13:56 UTC

Return-Path: <bgreene@senki.org>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E74C912946A for <t2trg@ietfa.amsl.com>; Wed, 5 Apr 2017 06:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.696
X-Spam-Level:
X-Spam-Status: No, score=-4.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796] 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 5QL9TDvWZZqk for <t2trg@ietfa.amsl.com>; Wed, 5 Apr 2017 06:56:29 -0700 (PDT)
Received: from smtp101.iad3a.emailsrvr.com (smtp101.iad3a.emailsrvr.com [173.203.187.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DEB1129437 for <T2TRG@irtf.org>; Wed, 5 Apr 2017 06:56:28 -0700 (PDT)
Received: from smtp5.relay.iad3a.emailsrvr.com (localhost [127.0.0.1]) by smtp5.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 119D225BA1; Wed, 5 Apr 2017 09:56:25 -0400 (EDT)
X-Auth-ID: bgreene@senki.org
Received: by smtp5.relay.iad3a.emailsrvr.com (Authenticated sender: bgreene-AT-senki.org) with ESMTPSA id 5F2F725B84; Wed, 5 Apr 2017 09:56:24 -0400 (EDT)
X-Sender-Id: bgreene@senki.org
Received: from [172.16.1.5] (c-73-92-124-43.hsd1.ca.comcast.net [73.92.124.43]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Wed, 05 Apr 2017 09:56:25 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Barry Raveendran Greene <bgreene@senki.org>
In-Reply-To: <1491374652157.84909@cs.auckland.ac.nz>
Date: Wed, 05 Apr 2017 06:56:22 -0700
Cc: Eliot Lear <lear@cisco.com>, Mohit Sethi <mohit.m.sethi@ericsson.com>, "T2TRG@irtf.org" <T2TRG@irtf.org>, "saag@ietf.org" <saag@ietf.org>, "Kumar, Sandeep" <sandeep.kumar@philips.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D69EDD72-28EC-4AD9-B91A-7A9344ECE8E4@senki.org>
References: <149096223256.21673.7096150636636687245.idtracker@ietfa.amsl.com> <1546ba0e65e946b681ccec46f2abcd8c@DB5PR9001MB0165.MGDPHG.emi.philips.com> <483ad18f-5ded-96e0-3008-1d0eb38f5566@cisco.com> <0DC0BAC2-C6BA-4D15-9343-60642BBD93C7@senki.org> <1491374652157.84909@cs.auckland.ac.nz>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/IOCDg4CWMQxM2PYl4hwuUkF8iEo>
Subject: Re: [T2TRG] [saag] New Version Notification for draft-irtf-t2trg-iot-seccons-02.txt
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IRTF Thing-to-Thing \(T2T\) Research-Group-in-creation" <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 13:56:32 -0000

> On Apr 4, 2017, at 11:44 PM, Peter Gutmann <pgut001@cs.auckland.ac.nz> wrote:
> 
> I don't want to start nitpicking individual bits of the draft

I’m OK with the draft. It is a good solid document for anyone who is taking an interest in secure IoT or looking to build a “RFP security requirements” checklist. We need this. Good work. 

But, from an IETF POV …. where we have to think forward to the next set of engineering problems, we need to be mindful of your illustration …

> So the diagram in Figure 1 is replaced after "application
> running" with a dotted line leading up to the present day, there's no updates,
> no reconfiguration, no maintenance and re-bootstrapping, it just keeps running
> once put into service.

What does a network do? Lets start digging into that problem.

v2.23.0 | Report a Bug | By Email