Re: [Roll] [roll] #91: Is it possible for an origin to get an error message in case the P2P-RPL route discovery fails.
C Chauvenet <c.chauvenet@watteco.com> Thu, 05 April 2012 13:31 UTC
Return-Path: <c.chauvenet@watteco.com>
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 AD7FB21F85EF for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 06:31:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Uf5yJhNO-6Ed for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 06:31:40 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by ietfa.amsl.com (Postfix) with ESMTP id BFD6721F85D4 for <roll@ietf.org>; Thu, 5 Apr 2012 06:31:39 -0700 (PDT)
Received: from mail76-va3-R.bigfish.com (10.7.14.237) by VA3EHSOBE009.bigfish.com (10.7.40.29) with Microsoft SMTP Server id 14.1.225.23; Thu, 5 Apr 2012 13:31:39 +0000
Received: from mail76-va3 (localhost [127.0.0.1]) by mail76-va3-R.bigfish.com (Postfix) with ESMTP id 29E92360637; Thu, 5 Apr 2012 13:31:39 +0000 (UTC)
X-SpamScore: -70
X-BigFish: VPS-70(zzc89bh15caKJzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839h93fhd25h)
X-Forefront-Antispam-Report: CIP:157.56.248.181; KIP:(null); UIP:(null); IPV:NLI; H:AMXPRD0510HT001.eurprd05.prod.outlook.com; RD:none; EFVD:NLI
Received: from mail76-va3 (localhost.localdomain [127.0.0.1]) by mail76-va3 (MessageSwitch) id 1333632697312351_875; Thu, 5 Apr 2012 13:31:37 +0000 (UTC)
Received: from VA3EHSMHS002.bigfish.com (unknown [10.7.14.243]) by mail76-va3.bigfish.com (Postfix) with ESMTP id 4465A2000EC; Thu, 5 Apr 2012 13:31:37 +0000 (UTC)
Received: from AMXPRD0510HT001.eurprd05.prod.outlook.com (157.56.248.181) by VA3EHSMHS002.bigfish.com (10.7.99.12) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 5 Apr 2012 13:31:36 +0000
Received: from AMXPRD0510MB390.eurprd05.prod.outlook.com ([169.254.3.137]) by AMXPRD0510HT001.eurprd05.prod.outlook.com ([10.255.57.36]) with mapi id 14.16.0135.002; Thu, 5 Apr 2012 13:31:35 +0000
From: C Chauvenet <c.chauvenet@watteco.com>
To: "mukul@UWM.EDU" <mukul@UWM.EDU>, "jpv@cisco.com" <jpv@cisco.com>
Thread-Topic: [Roll] [roll] #91: Is it possible for an origin to get an error message in case the P2P-RPL route discovery fails.
Thread-Index: AQHNExs8Cb9i217zFE+hTC4RxCYWnpaMOSrw
Date: Thu, 05 Apr 2012 13:31:35 +0000
Message-ID: <97B69B30E0EF244B940B65EA541E3F2D02216366@AMXPRD0510MB390.eurprd05.prod.outlook.com>
References: <055.920233a6500cd12143f61f93f9b312dd@trac.tools.ietf.org>
In-Reply-To: <055.920233a6500cd12143f61f93f9b312dd@trac.tools.ietf.org>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.3.4.7]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: watteco.com
Cc: "roll@ietf.org" <roll@ietf.org>
Subject: Re: [Roll] [roll] #91: Is it possible for an origin to get an error message in case the P2P-RPL route discovery fails.
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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 13:31:40 -0000
-----Message d'origine----- De : roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] De la part de roll issue tracker Envoyé : jeudi 5 avril 2012 13:00 À : mukul@UWM.EDU; jpv@cisco.com Cc : roll@ietf.org Objet : [Roll] [roll] #91: Is it possible for an origin to get an error message in case the P2P-RPL route discovery fails. #91: Is it possible for an origin to get an error message in case the P2P-RPL route discovery fails. Discussion: [Cedric] On big question that rise my mind is, what happened if the route discovery fail ? Some protocols sends out an error message when the route discovery fails or get stuck. Do authors think that it could be relevant to add a "discovery-error" message as defined in other route discovery protocols ? [Mukul] I dont think it is possible to detect the failure of a P2P-RPL route discovery. No node knows if a P2P-RPL route discovery has failed. P2P-RPL forms a temporary DAG and the route discovery (well, at least the first half) succeeds when a target joins the DAG. Only the target knows whether it joined the DAG or not. So, no node knows if the (first half of the) route discovery failed. Second half involves the target sending DRO to the origin. If the DRO does not reach the origin, (the second half of) the route discovery fails. The target can ensure (or at least increase the probability of) success by asking for DRO-ACK and retransmitting the DRO if the DRO-ACK is not received within certain time duration. DRO message travels by multicast, so an intermediate router, that forwards a DRO further, has no idea whether the next hop on the route received the DRO or not. Again, no node knows if the (second half of the) there is no one to generate the discovery-error message. I think an origin might infer the route discovery to have failed, if the DAG's life time has expired but no DRO is received. But I am not sure we should mandate this to be the way failure is inferred. We have just 4 values for the DAG life time. So, I think we should leave it to origin how much to wait for a DRO before admitting failure. [Cedric2] I was thinking about an error message if the delivery of a message fails when using a route established by the P2P-RPL mechanism. When a node included in the discovered route cannot be reached, then an error message could initiate a new route discovery using the P2P-RPL mechanism. -- -----------------------------------+--------------------- Reporter: jpv@… | Owner: mukul@… Type: defect | Status: new Priority: major | Milestone: Component: p2p-rpl | Version: Severity: Submitted WG Document | Keywords: -----------------------------------+--------------------- Ticket URL: <http://trac.tools.ietf.org/wg/roll/trac/ticket/91> roll <http://tools.ietf.org/wg/roll/> _______________________________________________ Roll mailing list Roll@ietf.org https://www.ietf.org/mailman/listinfo/roll
- [Roll] [roll] #91: Is it possible for an origin t… roll issue tracker
- Re: [Roll] [roll] #91: Is it possible for an orig… C Chauvenet
- Re: [Roll] [roll] #91: Is it possible for an orig… Mukul Goyal
- Re: [Roll] [roll] #91: Is it possible for an orig… C Chauvenet
- Re: [Roll] [roll] #91: Is it possible for an orig… Mukul Goyal
- [Roll] Closure text for ticket #91 Mukul Goyal
- Re: [Roll] [roll] #91: Is it possible for an orig… roll issue tracker