Re: [Roll] RPL Status
JP Vasseur <jpv@cisco.com> Fri, 21 May 2010 16:28 UTC
Return-Path: <jpv@cisco.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 86C303A704D for <roll@core3.amsl.com>; Fri, 21 May 2010 09:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.934
X-Spam-Level:
X-Spam-Status: No, score=-7.934 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 bj2NxWeNa04T for <roll@core3.amsl.com>; Fri, 21 May 2010 09:28:24 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 8079728CA3B for <roll@ietf.org>; Fri, 21 May 2010 08:36:45 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMZE9kurR7H+/2dsb2JhbACeIHGkD4tUjhaFEgQ
X-IronPort-AV: E=Sophos; i="4.53,279,1272844800"; d="scan'208,217"; a="328161886"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 21 May 2010 15:36:39 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o4LFacnm029940; Fri, 21 May 2010 15:36:38 GMT
Received: from xfe-ams-102.cisco.com ([144.254.231.94]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 21 May 2010 17:36:37 +0200
Received: from ams-jvasseur-8717.cisco.com ([10.55.201.136]) by xfe-ams-102.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 21 May 2010 17:36:36 +0200
Message-Id: <6F6D0CF1-A454-4591-B5D2-302529D5A861@cisco.com>
From: JP Vasseur <jpv@cisco.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
In-Reply-To: <4BF52DB6.8050905@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-193--214508336"
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 21 May 2010 14:37:14 +0200
References: <D77B6BCD-BB54-4CA9-B532-C0C89E900215@cisco.com> <6D9687E95918C04A8B30A7D6DA805A3E0142A175@zensys17.zensys.local> <4BF52DB6.8050905@gmail.com>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 21 May 2010 15:36:37.0231 (UTC) FILETIME=[666BEFF0:01CAF8FB]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-6.000.1038-17398.000
X-TM-AS-Result: No--18.605100-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
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: Fri, 21 May 2010 16:28:25 -0000
Hi Alex, Few comments. Last calling the base specification does not imply by all means that the work is complete, 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 >> https://www.ietf.org/mailman/listinfo/roll > > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll
- [Roll] RPL Status JP Vasseur
- Re: [Roll] RPL Status Anders Brandt
- Re: [Roll] RPL Status Richard Kelsey
- Re: [Roll] RPL Status Pascal Thubert (pthubert)
- [Roll] RPL multicast (was Re: RPL Status) Richard Kelsey
- Re: [Roll] RPL Status Samita Chakrabarti
- Re: [Roll] RPL Status Anders Brandt
- Re: [Roll] RPL multicast (was Re: RPL Status) Pascal Thubert (pthubert)
- Re: [Roll] RPL Status Richard Kelsey
- Re: [Roll] RPL multicast (was Re: RPL Status) Richard Kelsey
- Re: [Roll] RPL Status Jerald.P.Martocci
- Re: [Roll] RPL multicast (was Re: RPL Status) JP Vasseur
- Re: [Roll] RPL Status Alexandru Petrescu
- Re: [Roll] RPL multicast (was Re: RPL Status) Alexandru Petrescu
- Re: [Roll] RPL Status Philip Levis
- Re: [Roll] RPL multicast (was Re: RPL Status) JP Vasseur
- Re: [Roll] RPL Status Samita Chakrabarti
- [Roll] whither draft-ietf-roll-protocols-survey-07 Geoff Mulligan
- Re: [Roll] whither draft-ietf-roll-protocols-surv… JP Vasseur
- Re: [Roll] RPL Status JP Vasseur
- Re: [Roll] whither draft-ietf-roll-protocols-surv… Alexandru Petrescu
- Re: [Roll] RPL Status JP Vasseur
- Re: [Roll] whither draft-ietf-roll-protocols-surv… Geoff Mulligan
- Re: [Roll] whither draft-ietf-roll-protocols-surv… Robert Cragie
- Re: [Roll] RPL Status Jerald.P.Martocci
- Re: [Roll] whither draft-ietf-roll-protocols-surv… Alexandru Petrescu
- Re: [Roll] whither draft-ietf-roll-protocols-surv… Alexandru Petrescu
- Re: [Roll] RPL Status Alexandru Petrescu
- Re: [Roll] whither draft-ietf-roll-protocols-surv… Dearlove, Christopher (UK)
- Re: [Roll] whither draft-ietf-roll-protocols-surv… Alexandru Petrescu
- Re: [Roll] whither draft-ietf-roll-protocols-surv… JP Vasseur
- Re: [Roll] whither draft-ietf-roll-protocols-surv… Alexandru Petrescu