Re: Security Considerations, IoT and Everything

Michael StJohns <mstjohns@comcast.net> Tue, 22 November 2016 22:36 UTC

Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC9F1297AB for <ietf@ietfa.amsl.com>; Tue, 22 Nov 2016 14:36:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
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 ZtzGJTEpo1gW for <ietf@ietfa.amsl.com>; Tue, 22 Nov 2016 14:36:09 -0800 (PST)
Received: from resqmta-po-11v.sys.comcast.net (resqmta-po-11v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:170]) (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 EC2F1129412 for <ietf@ietf.org>; Tue, 22 Nov 2016 14:36:08 -0800 (PST)
Received: from resomta-po-13v.sys.comcast.net ([96.114.154.237]) by resqmta-po-11v.sys.comcast.net with SMTP id 9JfZcgkn9Ep5X9JfbcI00f; Tue, 22 Nov 2016 22:36:07 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1479854167; bh=iCtsGd+MLjhsZaAHQUzd5mpcJDYaP/saVdicJFLct4k=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=BD2zO6f26NBVvncTC+hZdkh1oWxq9aChSH4oTyf736Dk7eZU2veKB1K8B2yI1+qMF eHI5+HchjPR2vAZod96Z6xl9z02pdJJ6H7BUCoZnWFrYEiC6EowIve/+l5tNOvQDC9 3wV46ov5MzXc+30/PPZLZnHIeBPKUKs3J7vOLZ/TrWQ3I5c2LPVHz/ylRBN/5ddF0s Gyptvtc3C40e1gWiDVSHhcoIRqLyT8koGSvFpXPaZItOERohRaY3z+4zjkFNPdiXgI TkMZ0EtcFbcBmAP5ZS2hJxE5TGoWkgmVybgPjM7o3Gon0i7siOGtnGCIfqULW3riFc KfWKMJWfYIUug==
Received: from [192.168.1.115] ([68.83.216.245]) by resomta-po-13v.sys.comcast.net with SMTP id 9JfaczaNe7blB9JfacIAzo; Tue, 22 Nov 2016 22:36:07 +0000
Subject: Re: Security Considerations, IoT and Everything
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, ietf@ietf.org
References: <734ef353-487f-4f64-6cfe-f7909e705a41@comcast.net> <ad06fa17-e810-62e9-a890-c7a66ce850c2@cs.tcd.ie>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <662c9bc7-29ae-9b8e-fdf3-56f2f17adc34@comcast.net>
Date: Tue, 22 Nov 2016 17:35:25 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <ad06fa17-e810-62e9-a890-c7a66ce850c2@cs.tcd.ie>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfMcE8pqp02Ct7JCnIsYBOJmLfJRwLvB4iIVvwCGyggihYD2v9jfhfWCh/5RixZzEBDQXJYV8VJ3/2L4wZteSCfNqVlGC1yJty7J5LBS5aP/MB9v8Knat nxlKEQxJ+Tai4D9FALKgTqVym7R4CeKmrb5PpQY0+1VgMPxZdP+kB7y2DZ2oVP+wUbcmHQo1v48Yt0uCto34+wiaPskLAinVw1Q=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GW-N952EAwmT3ptkyJNJ5hm1hd8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Nov 2016 22:36:10 -0000

On 11/22/2016 4:56 PM, Stephen Farrell wrote:
>
> On 22/11/16 20:25, Michael StJohns wrote:
>> Is it time to revise BCP72/RFC3522 to require we also address threats
>> *from* the protocols to the Internet as a whole?
> Yes. As Kathleen said please do contribute to the relevant
> thread [1] on the saag list.
>
> S.
>
> [1] https://www.ietf.org/mail-archive/web/saag/current/msg07514.html
>
Thanks - missed this on the SAAG list when it first came out.

To be honest, this thread/discussion appears a bit moribund: it wasn't 
brought up during the SAAG meeting this time AFAICT, it doesn't appear 
to actually be a WG item as of yet, there doesn't appear to be much if 
any discussion on the SAAG list (a quick look doesn't find anything 
since July excepts Stephen's note - and that was all related to 
privacy), and the ID and GIT don't appear to have been updated since 
August.  The version on GIT seems to be only a references update from 
3522.  It looks like there was maybe a 10 minute - if that - chat about 
this in Berlin.

Perhaps it's time to have a broader (than SAAG) discussion on this as it 
really reaches further?

Mike

ps - on another note, why doesn't the SAAG have a datatracker page like 
rtgwg?