[Roll] [roll] #94: Why does DRO travel by multicast.
"roll issue tracker" <trac+roll@trac.tools.ietf.org> Thu, 05 April 2012 11:01 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 0C2CD21F85F8 for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 04:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level:
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, 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 V3GdZ9ccJ66J for <roll@ietfa.amsl.com>; Thu, 5 Apr 2012 04:01:54 -0700 (PDT)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 79D5721F86A0 for <roll@ietf.org>; Thu, 5 Apr 2012 04:01:54 -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 1SFkRt-0001f8-M9; Thu, 05 Apr 2012 07:01:53 -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:01:53 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/roll/trac/ticket/94
Message-ID: <055.5e7958cf85282c164ccf1feb557bf9dc@trac.tools.ietf.org>
X-Trac-Ticket-ID: 94
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] #94: Why does DRO travel by multicast.
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:01:55 -0000
#94: Why does DRO travel by multicast. Resolution: Because we want the stop flag in DRO to reach as many nodes as possible. Discussion: p14 : A DRO message travels from the target to the origin via link-local multicast along the route specified inside the Address vector in the P2P-RDO. [Cedric] Why using multicast if you know every destinators ? Could we unicast packets to each destinators in the address vector ? [Mukul] DRO travels by link local multicast so that the nodes, that are on the temporary DAG but not necessarily on a discovered route, may know that the route discovery is over (via the stop flag) and there is no need to generate any more DIOs. This may lead to a significant reduction in the (unnecessary) DIOs generated. Only the routers on the discovered route do the multicast-based forwarding though. -- -----------------------------------+--------------------- 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/94> roll <http://tools.ietf.org/wg/roll/>
- [Roll] [roll] #94: Why does DRO travel by multica… roll issue tracker
- Re: [Roll] [roll] #94: Why does DRO travel by mul… C Chauvenet
- [Roll] Closure text for ticket #94 Mukul Goyal
- Re: [Roll] [roll] #94: Why does DRO travel by mul… roll issue tracker