Re: [secdir] Fwd: FW: draft-ietf-roll-applicability-template

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 30 January 2013 10:35 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD7F321F87B9 for <secdir@ietfa.amsl.com>; Wed, 30 Jan 2013 02:35:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level:
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJuuzokT4m-f for <secdir@ietfa.amsl.com>; Wed, 30 Jan 2013 02:35:55 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id B5DD221F878F for <secdir@ietf.org>; Wed, 30 Jan 2013 02:35:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id DB6E8BE3E; Wed, 30 Jan 2013 10:35:32 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cY2CQwV2FyYZ; Wed, 30 Jan 2013 10:35:31 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:75b2:48e:2a5f:bc82] (unknown [IPv6:2001:770:10:203:75b2:48e:2a5f:bc82]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id F1558BE39; Wed, 30 Jan 2013 10:35:30 +0000 (GMT)
Message-ID: <5108F774.20804@cs.tcd.ie>
Date: Wed, 30 Jan 2013 10:35:32 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Ben Laurie <benl@google.com>
References: <003e01cdfe4a$6af134c0$40d39e40$@olddog.co.uk> <510869C4.9060706@cs.tcd.ie> <CABrd9SSB9TFtKZVTjD3RXCYi5teno0rCT8R1T9fdywKA-w1FxQ@mail.gmail.com> <5108F629.2090306@cs.tcd.ie>
In-Reply-To: <5108F629.2090306@cs.tcd.ie>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "secdir@ietf.org" <secdir@ietf.org>
Subject: Re: [secdir] Fwd: FW: draft-ietf-roll-applicability-template
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2013 10:35:56 -0000

On 01/30/2013 10:30 AM, Stephen Farrell wrote:
> 
> Ah, apologies for even asking if its that non-draft.
> (I didn't look;-)
> 
> I'll go back and beat 'em up if so.

Sorry again. Now I remember.

So this is really a template. Their plan is that they'll
have a bunch of other RPL applicability statement
drafts that say how to use the protocol in building
control, etc. Each will use this template.

Their question to us is what other things should those
drafts be required (by this template) to say about
security. So I guess we might say e.g. automated key
management (BCP 107) needs to be well-defined and
mandatory to implement.

S.

> 
> S.
> 
> On 01/30/2013 10:00 AM, Ben Laurie wrote:
>> On 30 January 2013 00:31, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>>>
>>> Hi all,
>>>
>>> The roll folks are looking for a review of this I-D.
>>> If someone feels the love, can you let Tero know and
>>> he'll capture that. If nobody does, then Tero, can
>>> you pick whoever's next in the rotation.
>>
>> Do you mean https://datatracker.ietf.org/doc/draft-richardson-roll-applicability-template/?include_text=1?
>> There doesn't appear to be a draft-ietf-
>>
>> If so, there's no info in it to base a security review on.
>>
>>>
>>> Thanks,
>>> S.
>>>
>>>
>>> -------- Original Message --------
>>> Subject: FW: draft-ietf-roll-applicability-template
>>> Date: Tue, 29 Jan 2013 17:59:36 -0000
>>> From: Adrian Farrel <adrian@olddog.co.uk>
>>> Reply-To: <adrian@olddog.co.uk>
>>> To: <turners@ieca.com>
>>> CC: <stephen.farrell@cs.tcd.ie>, <roll-chairs@tools.ietf.org>
>>>
>>> Copying Sean in just in case he is inclined to say something.
>>>
>>> A
>>>
>>>> -----Original Message-----
>>>> From: mcr@sandelman.ca [mailto:mcr@sandelman.ca] On Behalf Of Michael
>>>> Richardson
>>>> Sent: 27 January 2013 20:46
>>>> To: stephen.farrell@cs.tcd.ie
>>>> Cc: Adrian Farrel; jpv@cisco.com
>>>> Subject: draft-ietf-roll-applicability-template
>>>>
>>>>
>>>> I'm still looking for SEC Directorate review of the ROLL applicability
>>>> template.
>>>>
>>>> The idea is to make sure that security question will get addressed
>>>> earlier in the process, rather than at SEC Directorate review time.
>>>>
>>>> --
>>>> ]               Never tell me the odds!                 | ipv6 mesh networks [
>>>> ]   Michael Richardson, Sandelman Software Works        | network architect  [
>>>> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> secdir mailing list
>>> secdir@ietf.org
>>> https://www.ietf.org/mailman/listinfo/secdir
>>> wiki: http://tools.ietf.org/area/sec/trac/wiki/SecDirReview
>>
>>
> _______________________________________________
> secdir mailing list
> secdir@ietf.org
> https://www.ietf.org/mailman/listinfo/secdir
> wiki: http://tools.ietf.org/area/sec/trac/wiki/SecDirReview
> 
>