IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 10 June 2012 23:49 UTC

Return-Path: <mcr@sandelman.ca>
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 9AE2221F84FE for <roll@ietfa.amsl.com>; Sun, 10 Jun 2012 16:49:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.646
X-Spam-Level:
X-Spam-Status: No, score=0.646 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
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 H2ikROS8TSDu for <roll@ietfa.amsl.com>; Sun, 10 Jun 2012 16:49:18 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 114F321F84FD for <roll@ietf.org>; Sun, 10 Jun 2012 16:49:17 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id E1FAF836F for <roll@ietf.org>; Sun, 10 Jun 2012 19:46:58 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 66D109823C; Sun, 10 Jun 2012 19:49:16 -0400 (EDT)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 55BD898239 for <roll@ietf.org>; Sun, 10 Jun 2012 19:49:16 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "roll@ietf.org" <roll@ietf.org>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD807CFB5B8@xmb-rcd-x01.cisco.com>
References: <831338825.521366.1338009982543.JavaMail.root@mail17.pantherlink.uwm.edu> <8EFE80AF-3E7C-494E-8237-C63E6ECDAE7E@gmail.com> <53E28E3B-4C73-4BD3-BCFE-2C669FC3FA1D@cs.stanford.edu> <CAC8E858-8215-4BC8-98C6-962109324BED@gmail.com> <E045AECD98228444A58C61C200AE1BD806E78F8F@xmb-rcd-x01.cisco.com> <4FFC4E5C-03CA-43D3-9220-DABDD52102FB@cs.stanford.edu> <5395.1339164690@marajade.sandelman.ca> <E045AECD98228444A58C61C200AE1BD807CFB5B8@xmb-rcd-x01.cisco.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Sun, 10 Jun 2012 19:49:16 -0400
Message-ID: <14770.1339372156@marajade.sandelman.ca>
Sender: 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: Sun, 10 Jun 2012 23:49:18 -0000

>>>>> "Pascal" == Pascal Thubert <(pthubert)" <pthubert@cisco.com>> writes:
    Pascal> My understanding is that it is simpler to just check the OCP
    Pascal> than first match the OCP in the config option and then go
    Pascal> figure the metric in the metric option. 

I don't understand.

    Pascal> Not that it is a huge overhead but I fail to understand why
    Pascal> you claim that the single OCP is simpler. 

I don't claim it, I'm trying to understand what you are saying.

    Pascal> And no, I do not see that splitting in a future when
    Pascal> implementations are already shipping will be easy;  

okay.

    Pascal> a mixed deployment would have to fall back to legacy from
    Pascal> the root down, meaning that it will hardly ever evolve.  
    Pascal> LLN Devices that we install now some of the deployments (eg
    Pascal> industrial) are expected last for 20+ years with minimum
    Pascal> (no) intervention on them but maybe battery changes. 

I don't expect any deployed device to change.
They won't change for a new OF or OCP, etc. 
What would happen is that new deployments might use it.

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works 
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/

v2.23.0 | Report a Bug | By Email