Re: [Roll] Ralph's DISCUSS on MRHOF spec

Ralph Droms <rdroms.ietf@gmail.com> Fri, 08 June 2012 12:05 UTC

Return-Path: <rdroms.ietf@gmail.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 3BDDA21F8786 for <roll@ietfa.amsl.com>; Fri, 8 Jun 2012 05:05:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 fuB1Ib0ikmSu for <roll@ietfa.amsl.com>; Fri, 8 Jun 2012 05:05:40 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id A973121F8448 for <roll@ietf.org>; Fri, 8 Jun 2012 05:05:14 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so1020306vcq.31 for <roll@ietf.org>; Fri, 08 Jun 2012 05:05:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=/P7pUlS1TGUwZbeQ/0hPDODJBNQ8Bbq9D8MY2aECgRk=; b=0ZQxepA0FFPgknLCnpep9LwsVBouMDlPhYXjWEIw+zIos6onpngVmrq8I8yhPHYEgD cO7PAU4fuwNcrTQPc9xhFr7bqFuHjl2y55vqlPrRt3f2f+RJZruXyw7PXoiGGpOBysNi Oq1SMzACi+QA1oDUAuSQvcyHJTpW0quBr0gWqY2sFkvmPA2fP+IeRtF/xxiJqpGJ7Ocv HUCMYJbDMOK9OyTzMVD7wqX9dw1yYqVZ978ZMVASDwIuMKLo5rIVsK5q5xsrvoOWpgKd JbG3cMzuucHaV9SMg5hsdSQn9G6T8+htUF75/gNXOnknQ2t107E403wF5pVPVFfGQE+Q 23fg==
Received: by 10.52.30.110 with SMTP id r14mr5190310vdh.0.1339157114168; Fri, 08 Jun 2012 05:05:14 -0700 (PDT)
Received: from rtp-rdroms-8912.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPS id by3sm9378193vdc.17.2012.06.08.05.05.11 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 08 Jun 2012 05:05:12 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="us-ascii"
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <1016954968.629428.1339154827389.JavaMail.root@mail17.pantherlink.uwm.edu>
Date: Fri, 08 Jun 2012 08:05:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8FBA7931-52C0-4E4A-9637-AE471FF8F157@gmail.com>
References: <1016954968.629428.1339154827389.JavaMail.root@mail17.pantherlink.uwm.edu>
To: Mukul Goyal <mukul@uwm.edu>
X-Mailer: Apple Mail (2.1278)
Cc: Haberman Brian <brian@innovationslab.net>, Stiemerling Martin <mstiemerling@googlemail.com>, roll <roll@ietf.org>, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [Roll] Ralph's DISCUSS on MRHOF spec
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: Fri, 08 Jun 2012 12:05:41 -0000

On Jun 8, 2012, at 7:27 AM 6/8/12, Mukul Goyal wrote:

>>>> Is the receiving node supposed to infer that the selected metric for a RPL Instance using MRHOF is the one metric container included in the DIO (or, in the case of ETX, there is no metric container)?
>>> 
>>> In my opinion, yes.
> 
>> Where is that behavior explicitly described in the relevant specifications?
> 
> It is not. It should be.

OK, having *some* way for a node to determine the selected metric for MRHOF in an advertised RPL Instance tells me how MRHOF can provide the necessary information for the policy decision in section 18.6 of RFC 6550.

I would encourage some more discussion about metric-encoded OCPs.  Seems to me the metric is of at least as much importance (more important, in my opinion) in choosing a RPL Instance as the way in which the DODAG is constructed based on that metric (i.e., the computation part of the OF).  If I were trying to get a packet from a node to the LBR, I'd be much more interested in the ETX or the latency than whether the path is computed with hysteresis.

- Ralph

> 
> Mukul
>