[Roll] [roll] #169 (draft-richardson-roll-applicability-template): Work Item Proposals

"roll issue tracker" <trac+roll@trac.tools.ietf.org> Mon, 06 April 2015 10:14 UTC

Return-Path: <trac+roll@trac.tools.ietf.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB2481A702F for <roll@ietfa.amsl.com>; Mon, 6 Apr 2015 03:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9p7E7LrH3ykR for <roll@ietfa.amsl.com>; Mon, 6 Apr 2015 03:14:41 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C18EE1A7023 for <roll@ietf.org>; Mon, 6 Apr 2015 03:14:41 -0700 (PDT)
Received: from localhost ([::1]:39391 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+roll@trac.tools.ietf.org>) id 1Yf43F-0003fZ-23; Mon, 06 Apr 2015 03:14:41 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "roll issue tracker" <trac+roll@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-richardson-roll-applicability-template@tools.ietf.org, mariainesrobles@gmail.com
X-Trac-Project: roll
Date: Mon, 06 Apr 2015 10:14:41 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/roll/trac/ticket/169
Message-ID: <067.820b527e86b1f7925fabfdf4ce3ebe71@trac.tools.ietf.org>
X-Trac-Ticket-ID: 169
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-richardson-roll-applicability-template@tools.ietf.org, mariainesrobles@gmail.com, roll@ietf.org
X-SA-Exim-Mail-From: trac+roll@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: draft-richardson-roll-applicability-template@ietf.org
Resent-Message-Id: <20150406101441.C18EE1A7023@ietfa.amsl.com>
Resent-Date: Mon, 6 Apr 2015 03:14:41 -0700 (PDT)
Resent-From: trac+roll@trac.tools.ietf.org
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/4J0mf25iZnTXAMicGDq01lfEQkQ>
Cc: roll@ietf.org
Subject: [Roll] [roll] #169 (draft-richardson-roll-applicability-template): Work Item Proposals
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: roll@ietf.org
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: Mon, 06 Apr 2015 10:14:46 -0000

#169: Work Item Proposals

 Source: http://www.ietf.org/mail-archive/web/roll/current/msg09217.html

 From: "Pascal Thubert (pthubert)" <pthubert at cisco.com> - Thu, 2 Apr
 2015

 - One is a MOP based on BIER and/or Bloom filters, which is a way to
 compress BIER with a chance of false positive. Carsten has a draft that
 details the use of Bloom filters for source routing, but really both BIER
 and Bloom can apply to either storing and non-storing.

 - Work on mixed storing and non-storing, and all sort of optimization for
 the storing mode. I’m aware of feasible solutions in that space that
 really should be shared and made available to all.

 - Work on additional capabilities that we did not initially include in the
 spec:

 - The capability to kill a route from the root, e.g. if a DAO state is
 installed and should be cleaned up, e.g. if the root realizes that the
 node is no more there or there is a duplication or what-else.

 - The capability to trigger a DAO from the root if a target is expected to
 be present in the network but there is no DAO state (maybe to save
 resources)

 - The capability to request the triggering of a new iteration of a DODAG
 from a RPL node or a controlling element.

 ------ 2015-03-31 - Pascal Thubert:

 - How RPL works outside LLNs and in mixed environments?

 - I'd like to see work on RPL over foo where foo is Ethernet or Wi-Fi.
 Applicability of RPL in various environments outside LLN would be of
 interest, e.g. to build a Wi-Fi mesh or an unmanaged network. It seems
 that a DT will form at HOMENET to select a routing protocol, and an
 applicability statement of RPL for that case would be a good read if we
 can produce it in time.

 - From our experience of actually doing RPL over Ethernet, it is mostly a
 matter of *not* using the packet artifacts, probably not using the stretch
 in local repair, and reacting immediately to changes in link state. This
 is a very small spec indeed, mostly guidance on what to use and what not
 to use from RFC 6550, how to tune some parameters, which OF to use and
 how.

 - The work should also detail the mode where there is a backbone and a
 virtual root. I think that the current charter does not cover work outside
 LLN but considering that we are the group that knows RPL best, that work
 should happen here.

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |      Owner:  draft-richardson-roll-
  mariainesrobles@gmail.com          |  applicability-
     Type:  task                     |  template@tools.ietf.org
 Priority:  minor                    |     Status:  new
Component:  draft-richardson-roll-   |  Milestone:
  applicability-template             |    Version:
 Severity:  Candidate WG Document    |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/roll/trac/ticket/169>
roll <http://tools.ietf.org/wg/roll/>