[Roll] [roll] #87: Can't we split the target from the RDO ?
"roll issue tracker" <trac+roll@trac.tools.ietf.org> Wed, 04 April 2012 13:09 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 2508B21F8734 for <roll@ietfa.amsl.com>; Wed, 4 Apr 2012 06:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level:
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=0.310, 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 hOsi8pkAzLMD for <roll@ietfa.amsl.com>; Wed, 4 Apr 2012 06:09:57 -0700 (PDT)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id 90DC221F86BD for <roll@ietf.org>; Wed, 4 Apr 2012 06:09:57 -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 1SFPyG-0006C3-TW; Wed, 04 Apr 2012 09:09:56 -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: Wed, 04 Apr 2012 13:09:56 -0000
X-URL: http://tools.ietf.org/wg/roll/
X-Trac-Ticket-URL: https://svn.tools.ietf.org/wg/roll/trac/ticket/87
Message-ID: <055.f551806bbfcbaa57b44d89571c962af8@trac.tools.ietf.org>
X-Trac-Ticket-ID: 87
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] #87: Can't we split the target from the RDO ?
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: Wed, 04 Apr 2012 13:09:58 -0000
#87: Can't we split the target from the RDO ? Problem (proposed resolution) ------------------------------ The RDO is a garbage option will all sorts of data in it. The advocated reason for that is conciseness since separate options mean overhead. OTOH, it makes more sense to have all the targets expresses as target options as opposed to having one target in the DRO and then all other targets listed after. Having the target separate would allow for a DIO with no RDO but only a target, which would be useful to poll a device on an existing DAG. Currently the draft MUST a RDO and MAY and target option. The suggestion is to allow for a target in DIO without a RDO. Proposed resolution ------------------------- Keep it at that since 1) there are implementations and 2) it's experimental . This resolution implies that the issue will be reopened should the work go for standard track Discussion ------------- [Pascal]" MAY carry one or more RPL Target Options to specify additional unicast/multicast addresses for the target." Now here I would have a MUST carry at least one target. That is indeed what makes is a lookup DIO... [Mukul] As I stated in the previous message, we need to include the target in the P2P-RDO to save bytes for the common case (discover route to one unicast/multicast target). So, we cannot make using the target option a MUST. [Pascal2] Certainly. I prefer the split, in which case the MUST IMHO goes to the target as opposed to the RDO. In a case where the RDO is not needed, the target only message is actually shorter... [Mukul2] As I said before, I think a P2P mode DIO always needs to have one P2P-RDO. I guess, in this case, we agree to disagree! [Pascal3] Certainly. And there's nothing blocking with that disagreement, mostly if the draft targets experimental. I think it's OK to keep your response as the proposed resolution for the issue. Still I'd like advice from others so exposing the issue as LC will help. Let's see on which side the coin falls. [Mukul3] OK. I will be happy to hear additional opinions. [Pascal4] Fine, let's keep that as the proposed resolution [Mukul4] OK. Pascal -- -----------------------------------+--------------------- Reporter: jpv@… | Owner: mukul@… Type: defect | Status: new Priority: major | Milestone: Component: p2p-rpl | Version: Severity: Submitted WG Document | Keywords: -----------------------------------+--------------------- Ticket URL: <https://svn.tools.ietf.org/wg/roll/trac/ticket/87> roll <http://tools.ietf.org/wg/roll/>
- [Roll] [roll] #87: Can't we split the target from… roll issue tracker
- Re: [Roll] [roll] #87: Can't we split the target … Mukul Goyal
- Re: [Roll] [roll] #87: Can't we split the target … Pascal Thubert (pthubert)
- [Roll] Closure text for ticket #87 Mukul Goyal
- Re: [Roll] [roll] #87: Can't we split the target … roll issue tracker