IETF Logo Mail Archive

[Roll] [roll] #97: A fixed value for DRO_ACK_WAIT_TIME not OK for all P2P-RPL deployments.

"roll issue tracker" <trac+roll@trac.tools.ietf.org> Thu, 05 April 2012 11:19 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 869AA21F872A for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 04:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.547
X-Spam-Level:
X-Spam-Status: No, score=-102.547 tagged_above=-999 required=5 tests=[AWL=0.052, 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 vVuPKo-a1FLT for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 04:19:01 -0700 (PDT)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 1A01D21F872E for <roll@ietf.org>; Thu, 5 Apr 2012 04:19:01 -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 1SFkTD-0002JC-F9; Thu, 05 Apr 2012 07:03:15 -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: Thu, 05 Apr 2012 11:03:15 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/roll/trac/ticket/97
Message-ID: <055.7d6225a737a857a571e335c8e6245a84@trac.tools.ietf.org>
X-Trac-Ticket-ID: 97
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: [Roll] [roll] #97: A fixed value for DRO_ACK_WAIT_TIME not OK for all P2P-RPL deployments.
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: Thu, 05 Apr 2012 11:19:01 -0000

#97: A fixed value for DRO_ACK_WAIT_TIME not OK for all P2P-RPL deployments.

 Resolution: Make DRO_ACK_WAIT_TIME as well as MAX_DRO_RETRANSMISSIONS
 configurable parameters.

 Discussion:

 p25 :  o DRO_ACK_WAIT_TIME: The time duration a target waits for the DRO-
 ACK before retransmitting a DRO message. DRO_ACK_WAIT_TIME has a
      value of 1 second.

 [Cedric]
 I'm not sure it is compliant with all RPL deployments.
 Could we adapt it to the characteristics of the network used ?

 [Mukul]
 I am OK with making DRO_ACK_WAIT_TIME as well as MAX_DRO_RETRANSMISSIONS
 configurable parameters.

-- 
-----------------------------------+---------------------
 Reporter:  jpv@…                  |      Owner:  mukul@…
     Type:  defect                 |     Status:  new
 Priority:  major                  |  Milestone:
Component:  applicability-ami      |    Version:
 Severity:  Submitted WG Document  |   Keywords:
-----------------------------------+---------------------

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

v2.23.0 | Report a Bug | By Email