Re: [Roll] Stephen Farrell's Discuss on draft-ietf-roll-applicability-home-building-09: (with DISCUSS and COMMENT)

peter van der Stok <> Tue, 19 May 2015 10:27 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id B560B1A7D80; Tue, 19 May 2015 03:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rkXWbJGLUWYe; Tue, 19 May 2015 03:27:26 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 192C71A702E; Tue, 19 May 2015 03:27:24 -0700 (PDT)
Received: from ([]) by with ESMTP id VmTD1q0094VN29601mTDmr; Tue, 19 May 2015 12:27:21 +0200
Received: from ([]) by with HTTP (HTTP/1.1 POST); Tue, 19 May 2015 12:27:13 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 19 May 2015 12:27:13 +0200
From: peter van der Stok <>
To: Stephen Farrell <>
Organization: vanderstok consultancy
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <>
Message-ID: <>
X-Sender: (gH/7nV35qDxTJarJ9k5P2kBhl7VSuZFb)
User-Agent: XS4ALL Webmail
Archived-At: <>
X-Mailman-Approved-At: Tue, 19 May 2015 04:17:24 -0700
Cc:,, Michael Richardson <>, Routing Over Low power and Lossy networks <>,, The IESG <>,,,
Subject: Re: [Roll] Stephen Farrell's Discuss on draft-ietf-roll-applicability-home-building-09: (with DISCUSS and COMMENT)
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To:, Routing Over Low power and Lossy networks <>
List-Id: Routing Over Low power and Lossy networks <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 19 May 2015 10:27:28 -0000

Hi Stephen,

thanks for continuing the discussion.
I respond between the lines below.
It is possible that my co-authors want to improve on my comments.

Stephen Farrell schreef op 2015-05-17 12:39:
> Hi all, and apologies for the slow response...
> On 27/04/15 08:05, peter van der Stok wrote:
>> Dear all,
>> This new draft includes the return to the RFC2119 text.
>> It includes all comments answered during the security evaluation.
>> It includes suggestions by Michael to answer the DISCUSS raised by
>> Stephen Farrell.
> I'm sorry to say I don't think we're there yet. I just read the
> current draft and I think we still have significant issues for
> this DISCUSS.
> - If the way in which we are achieving interoperable security is
> via layer2-only then I would argue that that has to be more clearly
> stated up front (for truth-in-advertising reasons) as otherwise
> people may implement/deploy assuming the opposite.
> - I really seriously question the proposition that layer2-only
> security is sufficient for more complex building requirements.
> If that is true, then this document needs to say when it is safe
> and when it is unsafe to use RPL in such networks. (I can accept
> that layer2-only is ok for simple buildings and homes, at least
> for the next few years.)

The interpretation that layer-2 security is sufficient for building 
control is not meant.
Point to point security is certainly recommended and is a MUST when 
client and server are separated by a border router
(They reside on different network segments)

I suggest the following phrase at the end of 4.1.8:
The use of security measures at layer 3 or higher is RECOMMENDED. When 
two communicating nodes are separated by a border router, the nodes MUST 
use use security measures at layer 3 or higher.
For example, a client and server that use CoAP MUST use DTLS as 
specified in RFC7252.

Actually, I am not sure if this text addresses your point.

> - The "MUST be present" at the start of 4.1.8 is not quite right.
> If the plan here is layer2-only then you need to say something
> more like that all RPL packets MUST be sent using the layer2
> mechanisms and MUST be verified as having been received using
> the layer2 mechanisms. That (I guess) could require some code
> if a node can ever emit/receive an insecure message.
I will rephrase as you suggest and refer to IEEE 802.15.4 security 
Your suggestion is clearer, but should not imply layer-2 security only 
as clarified above.

> - 7.1 remains a collection of references that will not IMO give
> us interop when multiple vendors are involved. Can you explain
> to me why I'm wrong? (And I don't mean the multicast bit, but
> the stuff about unicast.)
I think from interop point of view, the use of a layer-2 security 
initialization protocol is different from using DTLS or CoAP protocols.
The initialization happens on a given installation that is subject to 
installation specific constraints.
Manufacturers organize themselves in alliances which select the IETF 
protocols which best fit the boundary conditions of their installations.
In analogy section 7.1 refers to ZigBee/IP which recommends PANA with 
EAP/TLS and japanese ECHONET which recommends PANA with EAP/PSK.
Further, L2 key management is not defined in the basic
spec of L2 and other standards have created different key management
methodologies, including IEEE which is creating a framework(IEEE
We see that other key management protocols are specified in the IETF 
currently, with progressing insight in the installation needs.

Therefore, I think that specifying a layer-2 initial deployment beyond 
what is done in 7.1 does not bring much more interop, given the ongoing 
progress in different organizations including IETF,
and given its limited scope to a given installation.
> Again, apologies for being a barrier to progress here, but I
> guess we're paying the price now for us collectively not having
> addressed this issue back at the start of the ROLL WG's work. I
> do think though that we need to ensure that we don't send out a
> set of specifications that might put quite a number of networks
> at risk because of our omissions, even if that means we need to
> address some technically and politically tricky issues.
I hope the issues become tractable with the ongoing discussion.
> Cheers,
> S.
> PS: Sorry to say I'll be travelling for the next few days so
> responses will continue to be slow. Maybe we should try setup a
> concall on this in a week or so? If that helps, I'm very happy
> to do that.

If my responses above add to the confusion, I think that a telconf will 
However, I should very much like that Robert Cragie and/or Michael 
Richardson assist as well.
Their experience will clearly contribute to arrive at a satisfying 


>> It maintains some of the text on the aspects of security in buildings
>> that need additional work.
>> Greetings,
>> Peter
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>  This draft is a work item of the Routing Over Low power and Lossy
>> networks Working Group of the IETF.
>>         Title           : Applicability Statement: The use of the RPL
>> protocol suite in Home Automation and Building Control
>>         Authors         : Anders Brandt
>>                           Emmanuel Baccelli
>>                           Robert Cragie
>>                           Peter van der Stok
>>     Filename        : 
>> draft-ietf-roll-applicability-home-building-10.txt
>>     Pages           : 32
>>     Date            : 2015-04-26
>> 2
>> Abstract:
>>    The purpose of this document is to provide guidance in the 
>> selection
>>    and use of protocols from the RPL protocol suite to implement the
>>    features required for control in building and home environments.
>> The IETF datatracker status page for this draft is:
>> There's also a htmlized version available at:
>> A diff from the previous version is available at:
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at
>> Internet-Drafts are also available by anonymous FTP at:
>> _______________________________________________
>> Roll mailing list
>> _______________________________________________
>> Roll mailing list