IETF Logo Mail Archive

Re: Security Considerations, IoT and Everything

Dave Taht <dave.taht@gmail.com> Thu, 24 November 2016 15:43 UTC

Return-Path: <dave.taht@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 7EBF112964C for <ietf@ietfa.amsl.com>; Thu, 24 Nov 2016 07:43:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, 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 Yk4dQ2JBSwJo for <ietf@ietfa.amsl.com>; Thu, 24 Nov 2016 07:43:15 -0800 (PST)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (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 A7877129442 for <ietf@ietf.org>; Thu, 24 Nov 2016 07:43:15 -0800 (PST)
Received: by mail-qt0-x232.google.com with SMTP id c47so43412067qtc.2 for <ietf@ietf.org>; Thu, 24 Nov 2016 07:43:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=LLc7I5xEN23+90s7Zp5TpujzsKDUgkwdl/TooSTdjn8=; b=LB+1qGnQCHG0Q4jL4JWRGrgyGJ0ZUOuw7fNXZvECd4rBYDMWtAtDbZfoUF3HVkgukR 2GJQqtMZePWpybd78AqpxDtdrd3znbQn1Ov9dZjK8Dr8CYGP2WZvCymAUyldU2HGQ02s a9wj7fhiZANUEkBif+m7pz4Ozhgz3/rMBm4nMdj/ERn5tfZ0bQ41D3eiWffNZw2X+Ecx Q42/yc/qevsQYULJlI82e9lNP6tT235hcD5SnIrKifX9Q/9iCJU5Xfzz6/iDTtuoRrTU lrU+KMFR4Wu41YY2SAxVOQ6nbUSC2xI6p5i5BDcUrp485JP38KgH82NwpK2j0C3CinxR qnXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=LLc7I5xEN23+90s7Zp5TpujzsKDUgkwdl/TooSTdjn8=; b=A7zXWJ21y62479M+zGIYg6IwmXlsQKOclY+7hMOR88rKpnxsdCagak2pWpbcuHuwZH lEHtDqIR1Btw+u213qDPne4wygevOKNeHHmt1VjP1XAsdZrjMaoQzu58fzoC/qd5yLg/ sYCcS3eKD0uZmf5rrlQTEFvhnjbMYFNz3eW09z4kIKa9MtR65o1wzDCUU8ZusszXEEzW IImTBeM+GfESsbbqShfR2bqD+Uqy9xVT7/O2TsYAmtxsQuql9vRgv4LcAB/X2JcSgo+o bRXpy7mTs4Sul3DBduVx/j+qYPbLp98Q8NybLSM8LUqSzgu9h816xdjscYIHdnvcOIg8 ZcqA==
X-Gm-Message-State: AKaTC0010JXvH1RCmrD4tZM1MYMWXF0U1gpRCsItFFjUmv1eh7iYcoIHh4t068YYlxH0OGXmM3V328inou++ng==
X-Received: by 10.200.57.134 with SMTP id v6mr2524290qte.36.1480002194762; Thu, 24 Nov 2016 07:43:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.137.198 with HTTP; Thu, 24 Nov 2016 07:43:14 -0800 (PST)
In-Reply-To: <966D9B78-5731-4FD3-90E0-D7924ED9430F@gmail.com>
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> <966D9B78-5731-4FD3-90E0-D7924ED9430F@gmail.com>
From: Dave Taht <dave.taht@gmail.com>
Date: Thu, 24 Nov 2016 07:43:14 -0800
Message-ID: <CAA93jw5B5UmsceFTnEFitxdsNVtYvRd3wd0+rQiiKFbuCdiVew@mail.gmail.com>
Subject: Re: Security Considerations, IoT and Everything
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RAt5IaPMkqd52QkBQO8jo1u8ha0>
Cc: IETF Discussion Mailing List <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: Thu, 24 Nov 2016 15:43:17 -0000

NIST published this last month.

http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-160.pdf


On Wed, Nov 23, 2016 at 1:05 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:
>
> 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
>
>



-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

v2.23.0 | Report a Bug | By Email