Re: Security Considerations, IoT and Everything

Yoav Nir <ynir.ietf@gmail.com> Wed, 23 November 2016 09:05 UTC

Return-Path: <ynir.ietf@gmail.com>
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 7EBBA12963E for <ietf@ietfa.amsl.com>; Wed, 23 Nov 2016 01:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 w6lMfSrPaI0X for <ietf@ietfa.amsl.com>; Wed, 23 Nov 2016 01:05:10 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 BF71A1295B5 for <ietf@ietf.org>; Wed, 23 Nov 2016 01:05:09 -0800 (PST)
Received: by mail-wm0-x230.google.com with SMTP id f82so13455237wmf.1 for <ietf@ietf.org>; Wed, 23 Nov 2016 01:05:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=dk9SengBVNn8SFBRzwmJgbkzhkDsW6T7XroyI2QZ9Tw=; b=zBrnzgiqsI+Lu4muKYvbpWd42cw7qT16/ZDjUDCOnIH8YjJvd9Gdw8WFCNOEnaVTJy wDnQbBtav9g9o0nquRfBbP+9AH7LCqhvsKf+JRB2c1+AfiBeMcN/dY4wFqi/Ol4pjE3H 7Fw+QQ9MhpHxslDMxB/vzV5f1o2Wm0K4Zg8FFVfWOAhfgw/CfkAUHoF/aA9T3qFaij0M XJyEurvPYVQaH3COiz1whR5Uqg0QCUM9M/piRoehNJbgAzPN5C9AQBu0aYvswRHAeSVW DFU03g1DuIcJRN9uKougR6VdFlC3U7nbPYoMEYr/S4cHfoK/2aLdfSqjHo/y75XPgQSk 322Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=dk9SengBVNn8SFBRzwmJgbkzhkDsW6T7XroyI2QZ9Tw=; b=a1IWF5gnC2Ksa8uOjv+7JRJmgOhw/qTmy1jWuIJAIAp0BWenw+Nh+ne2OPsJgT0ynw BUTJ4QxIfGiQ6FCIzKDXIqthDL1pAY/AmETOBw+3Ey+Us7eQf5UQmHVQzUiJ7RkwqHTG HaTQKFutCoqm4uUPLrlEy+oc9ryUCsZL+cUHtlNOltlzujXvhDoVORMXiJKEKXqJ1qq9 ySfmisTiW3JVgTW6e6Fgf/guloGJhHv5nHYBt46eu/ZIDejUveX9oY8BzbGeffZMZv5y uiYGs1lRxKnTmYMAD2FEIGE30n03bvrbS61tVHOPPOPo/+JL200qGOuSVrlYWf2IO2nz 5WUg==
X-Gm-Message-State: AKaTC00VTz7GFwdmLcaTmbuifnyEibhaGmT2BluYzeyx9qdF8Sg/1yRE6SSPpZNYNf37Zw==
X-Received: by 10.28.173.4 with SMTP id w4mr2145792wme.70.1479891908327; Wed, 23 Nov 2016 01:05:08 -0800 (PST)
Received: from [172.24.250.223] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id d184sm1621513wmd.8.2016.11.23.01.05.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 23 Nov 2016 01:05:07 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <966D9B78-5731-4FD3-90E0-D7924ED9430F@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_544A4429-4AA4-45FC-878B-E3BD12CF771B"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Subject: Re: Security Considerations, IoT and Everything
Date: Wed, 23 Nov 2016 11:05:05 +0200
In-Reply-To: <ee79c249-151a-5d73-f9e3-d4df7ad11be6@comcast.net>
To: Michael StJohns <mstjohns@comcast.net>
References: <734ef353-487f-4f64-6cfe-f7909e705a41@comcast.net> <ad06fa17-e810-62e9-a890-c7a66ce850c2@cs.tcd.ie> <662c9bc7-29ae-9b8e-fdf3-56f2f17adc34@comcast.net> <c98df9c6-55cb-8bc5-dd2b-d6189a41a7c0@cs.tcd.ie> <ee79c249-151a-5d73-f9e3-d4df7ad11be6@comcast.net>
X-Mailer: Apple Mail (2.3251)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HYYy4GVzdmPeesN-f-cjFawwyng>
Cc: ietf@ietf.org
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: Wed, 23 Nov 2016 09:05:11 -0000

> On 23 Nov 2016, at 3:01, Michael StJohns <mstjohns@comcast.net> wrote:
> 
> On 11/22/2016 5:48 PM, Stephen Farrell wrote:
>>> ps - on another note, why doesn't the SAAG have a datatracker page like
>>> rtgwg?
>> Saag's not a WG. People suggest it now and then (and others
>> dislike the idea). Feel free to raise that too (though I'd
>> far prefer we discuss 3552bis myself.)
> I didn't ask why SAAG is not a WG, I asked why it didn't have a datatracker page.  Not having a datatracker page makes it difficult to track things that are associated only with the SAAG (e.g. the draft 3552 replacement).  In the IETF meeting APP, I can't lookup "saag" in the wg list to see what's what for the meeting for example and that appears to be a directly related to SAAGs lack of datatracker presence.
> 
Hi, Mike. 

While there isn’t a SAAG datatracker page, there is a SAAG github group where you can find (among no other things) the text of rfc3552bis.

Having a datatracker page implies that there are drafts in there. AFAICT this is the first draft that people associate with SAAG so a page didn’t make sense before.

https://github.com/IETF-SAAG

Yoav