Re: [Roll] draft-ietf-roll-security-framework returned to working group.

Abdussalam Baryun <abdussalambaryun@gmail.com> Sun, 12 August 2012 14:09 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D292721F852E for <roll@ietfa.amsl.com>; Sun, 12 Aug 2012 07:09:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.484
X-Spam-Level:
X-Spam-Status: No, score=-3.484 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cktXiDPRemnz for <roll@ietfa.amsl.com>; Sun, 12 Aug 2012 07:09:12 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A836821F8513 for <roll@ietf.org>; Sun, 12 Aug 2012 07:09:11 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so3037971vbb.31 for <roll@ietf.org>; Sun, 12 Aug 2012 07:09:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=CHMwdTI04eckvPwuBhs2GuK1p93qgh/xoZKouio03zo=; b=mNfYHRuDCJaoCJvF/oS6A0ge2waPnY1bWFCWLUw0vlwTgDdfCYYyREOQekUHWv2ohu k7YJDKI+RSItk3tkcuIAp++A1WypWc7TpIWvp7igdpNe9cieNUNtsmaarsO9reF099Gv iAsOUuCgvYhzML0SVHrvkrQ2Lzb2yvaYDNetQ3CGQ8nXElmOpZzzIOYNgs1Lk8+gSczB 52DzUvmryEj56kCmHP9H+6f3RRB44dg9f3Xkf87YQNYGbNCFeu1kcG9ZSOMmZ0ZfgbXw FJVFeRaekRsuoDPd0TE7OjMWihksu1U7msZjsa5XV9qwi4/prpNvWvlRzluj+Z20gQzR mDWA==
MIME-Version: 1.0
Received: by 10.52.95.225 with SMTP id dn1mr5709416vdb.99.1344780551190; Sun, 12 Aug 2012 07:09:11 -0700 (PDT)
Received: by 10.220.62.77 with HTTP; Sun, 12 Aug 2012 07:09:11 -0700 (PDT)
Date: Sun, 12 Aug 2012 16:09:11 +0200
Message-ID: <CADnDZ8_iguRy6wixyNRTXbn+P=OXQyU2zS07onx2A+DpJmU=3g@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: roll@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Cc: tzeta.tsao@cooperindustries.com
Subject: Re: [Roll] draft-ietf-roll-security-framework returned to working group.
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Sun, 12 Aug 2012 14:09:13 -0000

 I thought that this informational draft had in 2011 enough position
to pass (subject to resolve discuss position), also not sure why the
draft left to expire while it had a new version in 2012 without any
discussion from January until July [1].

 There was no abstain or objection positions, but discuss positions,
meaning things can be fixed [2-3]. Am I missing some thing?

[1] http://www.ietf.org/mail-archive/web/roll/current/msg06615.html
[2] http://www.ietf.org/mail-archive/web/ietf/current/msg68450.html
[3] http://www.ietf.org/iesg/statement/discuss-criteria.html

Regards
Abdussalam

>
> This document has sat in IESG Evaluation::AD Followup for 467 days.
>
> The blocking issue has been that the document does not actually provide any
> security guidelines or mechanisms, and RPL itself (RFC 6550) is also sadly
> lacking.
>
> Michael Richardson and I sat down with Stephen Farrell (Security AD) and
> cooked
> up a plan to generate some useful security documents for RPL. Inevitably
> this
> will introduce more delay, but at least there is a plan that we might manage
> to
> execute. Michael has introduced the plan to the WG and there seems to be
> support.
>
> Part of this plan involves pulling draft-ietf-roll-security-framework back
> from
> the IESG, returning it to the WG, and re-casting it as a threat analysis
> (something it does quite well at the moment).
>
> Thus, this document is returned to the working group for further work.
>
> Thanks,
> Adrian
>
>