Re: [Roll] [roll] #102: Why have a Data Option in P2P-RPL. Why have a sequence number in the data option?

"roll issue tracker" <trac+roll@trac.tools.ietf.org> Mon, 04 June 2012 14:16 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3453A21F88A1 for <roll@ietfa.amsl.com>; Mon, 4 Jun 2012 07:16:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 cjcBQOhKk1lP for <roll@ietfa.amsl.com>; Mon, 4 Jun 2012 07:16:13 -0700 (PDT)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id AF6C021F889D for <roll@ietf.org>; Mon, 4 Jun 2012 07:16:13 -0700 (PDT)
Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+roll@trac.tools.ietf.org>) id 1SbY4q-0001Y1-Ug; Mon, 04 Jun 2012 10:16:12 -0400
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.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: mukul@UWM.EDU, jpv@cisco.com
X-Trac-Project: roll
Date: Mon, 04 Jun 2012 14:16:12 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/roll/trac/ticket/102#comment:1
Message-ID: <070.760e3f2cf470c2b2b4c45f05e6975edc@trac.tools.ietf.org>
References: <055.0400b84aef3418e790354e422e9667aa@trac.tools.ietf.org>
X-Trac-Ticket-ID: 102
In-Reply-To: <055.0400b84aef3418e790354e422e9667aa@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: mukul@UWM.EDU, jpv@cisco.com, roll@ietf.org
X-SA-Exim-Mail-From: trac+roll@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false
Cc: roll@ietf.org
Subject: Re: [Roll] [roll] #102: Why have a Data Option in P2P-RPL. Why have a sequence number in the data option?
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
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, 04 Jun 2012 14:16:14 -0000

#102: Why have a Data Option in P2P-RPL. Why have a sequence number in the data
option?

Changes (by jpv@…):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Resolution:
 1) Data Option is a sensible and necessary design choice for home
 automation networks. Home automation frequently requires low-latency
 messages to be delivered to targets for which the originator has no route.
 The fastest way to do that in a reactive routing scheme is to piggyback
 the data on the routing packets. The other option would be to use simple
 flooding, with no trickle control, which would involve generating a huge
 number of packets. Piggybacking data on routing packets helps avoid
 generating extra packets.

 2) There is no need for the origin to change the data option during a
 route discovery. So there is no need for a sequence number. Further, P2P-
 RPL would explictly forbid an origin to change the data option during a
 route discovery.

-- 
-----------------------------------+----------------------
 Reporter:  jpv@…                  |       Owner:  mukul@…
     Type:  defect                 |      Status:  closed
 Priority:  major                  |   Milestone:
Component:  p2p-rpl                |     Version:
 Severity:  Submitted WG Document  |  Resolution:  fixed
 Keywords:                         |
-----------------------------------+----------------------

Ticket URL: <http://trac.tools.ietf.org/wg/roll/trac/ticket/102#comment:1>
roll <http://tools.ietf.org/wg/roll/>