Re: [Roll] RPL Next Steps
Tim Winter <wintert@acm.org> Wed, 12 August 2009 19:55 UTC
Return-Path: <wintert@acm.org>
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 1F1EA3A6807 for <roll@core3.amsl.com>; Wed, 12 Aug 2009 12:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.381
X-Spam-Level:
X-Spam-Status: No, score=-102.381 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
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 gawTPVvfuWq6 for <roll@core3.amsl.com>; Wed, 12 Aug 2009 12:55:06 -0700 (PDT)
Received: from smtp108.prem.mail.ac4.yahoo.com (smtp108.prem.mail.ac4.yahoo.com [76.13.13.47]) by core3.amsl.com (Postfix) with SMTP id 31E193A67B7 for <roll@ietf.org>; Wed, 12 Aug 2009 12:55:06 -0700 (PDT)
Received: (qmail 12038 invoked from network); 12 Aug 2009 19:53:43 -0000
Received: from 206-83-249-194.edurostream.com (wintert@206.83.249.194 with plain) by smtp108.prem.mail.ac4.yahoo.com with SMTP; 12 Aug 2009 12:53:43 -0700 PDT
X-Yahoo-SMTP: 30iEHGKswBCbca_Y5pX7d6RVQMoT5Mk-
X-YMail-OSG: ICKBBGQVM1krtzOSSJo2EZqPg_B5tzUEKnhAbxpghPZFKhzNbuuZy8wpBMFPXPHio1V1OIAn21WK9oIwQUMk3rbDeUxIo4JtRuaX.EnBOPjkzf6UXC_mQ7x5uum0mLTILM6moUxPjaQgHM1ZV7bixHP5HL3883Ii5ukuUaQ._D6fNiMViiTXSmHSnOoiDh_OvF.REaF_Yowg5sJu0L6tFE2kiFINZWqtosyx3fau6EsCmoh58b9bc6byIOFibRkywN5mq6sGiwHzWUNNegwZBA5PywK8NjEHIFb4oAduCnMwh9svI.HM410My34fMZifscQSLrkJbmgpxPv4A.AiFrhjKj6LHKlEtK2X
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4A831DC8.6000806@acm.org>
Date: Wed, 12 Aug 2009 15:53:44 -0400
From: Tim Winter <wintert@acm.org>
User-Agent: Thunderbird 2.0.0.21 (X11/20090330)
MIME-Version: 1.0
To: ROLL WG <roll@ietf.org>
References: <OF92EF1176.5D438D93-ON86257610.0051C496-86257610.00628656@jci.com>
In-Reply-To: <OF92EF1176.5D438D93-ON86257610.0051C496-86257610.00628656@jci.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [Roll] RPL Next Steps
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: Wed, 12 Aug 2009 19:55:07 -0000
Hi Jerry, Sorry for the confusion- The individual submission, draft-dt-roll-rpl, had made it to revision -01 with the OCP additions. The WG draft, draft-ietf-roll-rpl, is still at -00. (The contents are equivalent). So the next revision of the WG document will be be draft-ietf-roll-rpl-01 Thanks, -Tim Jerald.P.Martocci@jci.com wrote: > > > */This sounds like a plan. However, aren't you talking about the -02 > version? I thought we already have a -01 version that introduced 'OCP'?/* > > > > > *Tim Winter <wintert@acm.org>* > Sent by: roll-bounces@ietf.org > > 08/11/2009 06:00 PM > > > To > ROLL WG <roll@ietf.org> > cc > > Subject > [Roll] RPL Next Steps > > > > > > > > > WG, > > Please find below some additional feedback from the design team on the > questions that have been raised so far for RPL. Not everything has been > covered- but the questions have served to point out some areas of the draft > where we need to continue and focus efforts. > > We (DT) propose, in the -01 version of the draft, to clarify as much > as possible the outstanding questions and concerns in the current > specification of RPL, with emphasis on the existing (-00) mechanisms. The > intent is to provide a solid, unambiguous, implementable, foundation of the > existing core mechanisms in -01. On this foundation we can then continue > to build and expand other necessary mechanisms in later revisions, such as > are being discussed for P2P routing. There is no doubt that the P2P issues > need to be further discussed and addressed, but the thought is that by > clearing up the existing mechanisms we may be able to make better progress > in moving forward beyond the existing mechansisms in later revisions. > > WG, how does this sound as a strategy to make progress on RPL? > > <SNIP>
- Re: [Roll] RPL Next Steps Jerald.P.Martocci
- Re: [Roll] RPL Next Steps Tim Winter
- [Roll] RPL Next Steps Tim Winter
- Re: [Roll] RPL Next Steps Alexandru Petrescu
- Re: [Roll] RPL Next Steps Alexandru Petrescu