Re: [Roll] RPL Status

Alexandru Petrescu <alexandru.petrescu@gmail.com> Sat, 22 May 2010 10:07 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: roll@core3.amsl.com
Delivered-To: roll@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56BE33A6C52 for <roll@core3.amsl.com>; Sat, 22 May 2010 03:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.069
X-Spam-Level:
X-Spam-Status: No, score=0.069 tagged_above=-999 required=5 tests=[AWL=-0.282, BAYES_50=0.001, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8uuoMjmCkUnd for <roll@core3.amsl.com>; Sat, 22 May 2010 03:06:59 -0700 (PDT)
Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [212.27.42.2]) by core3.amsl.com (Postfix) with ESMTP id 1B55C3A6C39 for <roll@ietf.org>; Sat, 22 May 2010 03:06:57 -0700 (PDT)
Received: from smtp2-g21.free.fr (localhost [127.0.0.1]) by smtp2-g21.free.fr (Postfix) with ESMTP id 6A8904B0024; Sat, 22 May 2010 12:06:48 +0200 (CEST)
Received: from [127.0.0.1] (bur91-3-82-239-213-32.fbx.proxad.net [82.239.213.32]) by smtp2-g21.free.fr (Postfix) with ESMTP; Sat, 22 May 2010 12:06:46 +0200 (CEST)
Message-ID: <4BF7ACB2.6030406@gmail.com>
Date: Sat, 22 May 2010 12:06:42 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: JP Vasseur <jpv@cisco.com>
References: <D77B6BCD-BB54-4CA9-B532-C0C89E900215@cisco.com> <6D9687E95918C04A8B30A7D6DA805A3E0142A175@zensys17.zensys.local> <4BF52DB6.8050905@gmail.com> <6F6D0CF1-A454-4591-B5D2-302529D5A861@cisco.com>
In-Reply-To: <6F6D0CF1-A454-4591-B5D2-302529D5A861@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 100522-0, 22/05/2010), Outbound message
X-Antivirus-Status: Clean
Cc: roll@ietf.org
Subject: Re: [Roll] RPL Status
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 22 May 2010 10:07:00 -0000

Le 21/05/2010 14:37, JP Vasseur a écrit :
> Hi Alex,
>
> Few comments. Last calling the base specification does not imply by all
> means that the work is complete,

I would have expected to Last Call a document which we believe is almost 
done.

Alex

> we have other items in our charter, could be re-chartered according to
> the WG's feed-back, etc ...
> We were referring to the */base/* RPL specification and for that we have
> a ticket opened that helps
> us track that the base specification meets the requirements spelled out
> in the four requirements
> document. For the record, I'll resend the document, that will be updated
> after each revision of RPL.
> As pointed out by Phil, if we can move forward with P2P I-D that'd be great.
>
> Thanks.
>
> JP and David.
>
> On May 20, 2010, at 2:40 PM, Alexandru Petrescu wrote:
>
>> Le 19/05/2010 09:39, Anders Brandt a écrit :
>>> All,
>>> >the plan is still to Last Call RPL before the next IETF
>>> I would like to poll the WG on this statement.
>>> The home and building requirements are not met by the current RPL draft
>>> and we have not even started discussing the P2P ID mechanisms in detail -
>>> or frame format modifications for that matter.
>>> Does the WG agree that a RPL spec without support for home and building
>>> applications is acceptable?
>>
>> Only in part because of the failure to meet requirements - I disagree
>> to pursue RPL towards LC before the next IETF: it is way too early.
>>
>> We have wide technical misunderstandings about the scope of this
>> protocol and its applicability.
>>
>> Alex
>>
>>> Thanks,
>>> Anders
>>>
>>> ------------------------------------------------------------------------
>>> *From:* roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] *On
>>> Behalf Of *JP Vasseur
>>> *Sent:* Tuesday, May 18, 2010 11:48
>>> *To:* roll WG
>>> *Subject:* [Roll] RPL Status
>>>
>>> Dear WG,
>>>
>>> Here is a quick status. First, we would like to thank the WG again
>>> for the continuous effort and lots of fruitful and productive work !
>>> As discussed in Anaheim, the plan is still to Last Call RPL before
>>> the next IETF. The plan is to release the next revision of the RPL
>>> I-D by end of next week. Rev-08 will address the following:
>>>
>>> 1) Security section (integrating the work on the security DT)
>>> 2) New DAO mechanism (cleaner and more simple), as agreed on the
>>> Mailing List
>>> 3) Basic source routing => See also companion drafts to be published
>>> very soon for (RH-0 like)
>>> 4) Updated manageability section
>>> 5) DAO ACK
>>> 6) Trickle algorithm removed from the core specification (in a
>>> separate doc), Examples removed
>>> 7) Several Edits, clarifications, ...
>>>
>>> I had a discussion with David, and the plan is to have the P2P a
>>> separate ID (the current RPL specification provides basic P2P, with
>>> "advanced" P2P defined in that I-D), with the objective to progress
>>> both documents in parallel.
>>>
>>> */What else ?/*
>>> We need to progress a few other documents:
>>> 1) Use of the RPL TLV: see draft-hui-6man-rpl-option (6man WG)
>>> 2) Source routing header (RH-0 like): to be published soon
>>> (Jonathan/David)
>>> 3) RPL Variables (ticket #22)
>>> 4) ID related to measurement from P2P (if consensus on Mailing list)
>>>
>>> Looking forward to your comments as soon as rev-08 will be published.
>>>
>>> Thanks.
>>>
>>> JP and David.
>>>
>>>
>>>
>>> _______________________________________________
>>> Roll mailing list
>>> Roll@ietf.org <mailto:Roll@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/roll
>>
>>
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org <mailto:Roll@ietf.org>
>> https://www.ietf.org/mailman/listinfo/roll
>