Re: [Roll] [roll] #136: - draft-ietf-roll-applicability-ami - Add a section of the Security Considerations for each instance where the RPL security mechanism are not to be used

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 25 January 2014 15:06 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 212591A0254 for <roll@ietfa.amsl.com>; Sat, 25 Jan 2014 07:06:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.009
X-Spam-Level: *
X-Spam-Status: No, score=1.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=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 fdbZGulKGHzZ for <roll@ietfa.amsl.com>; Sat, 25 Jan 2014 07:06:27 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 9B51D1A00E3 for <roll@ietf.org>; Sat, 25 Jan 2014 07:06:27 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DE3402002F; Sat, 25 Jan 2014 11:22:45 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 6D6F964647; Sat, 25 Jan 2014 10:06:25 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 592BB63AB2; Sat, 25 Jan 2014 10:06:25 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Chris Lonvick <clonvick@cisco.com>
In-Reply-To: <alpine.LRH.2.00.1401240912530.20137@sjc-xdm-112.cisco.com>
References: <067.78cf5d635bca77cded1fb433c133c835@trac.tools.ietf.org> <9546f1bf3d68401a8cdf837ca5528de4@BY2PR04MB807.namprd04.prod.outlook.com> <alpine.LRH.2.00.1401240912530.20137@sjc-xdm-112.cisco.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Sat, 25 Jan 2014 10:06:25 -0500
Message-ID: <12988.1390662385@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "draft-ietf-roll-applicability-ami.all@tools.ietf.org" <draft-ietf-roll-applicability-ami.all@tools.ietf.org>, "roll@ietf.org" <roll@ietf.org>
Subject: Re: [Roll] [roll] #136: - draft-ietf-roll-applicability-ami - Add a section of the Security Considerations for each instance where the RPL security mechanism are not to be used
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jan 2014 15:06:29 -0000

Chris Lonvick <clonvick@cisco.com> wrote:
    > Has a threat model been defined for RPL?  And do you know that the link-layer
    > security provided by the two IEEE mechanisms will thwart the threats?  This
    > isn't meant to be an onerous exercise.  :-)  What has been done in several
    > WGs has been to define a simple threat model (usually taken from RFC 3552)
    > and then describe how the security mechanisms will thwart the threats.  For
    > example, see sections 2 and 3 in RFC 5426 (TLS for syslog).

    > If you can point to the threat model for RPL then you can probably state
    > (just once in the Security Considerations section) how the IEEE link-layer
    > security mechanisms will address the threats so therefore the security
    > mechanisms already contained within RPL will not be needed.

draft-ietf-roll-security-threats.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works