[Roll] how to document provisioning model properly

Michael Richardson <mcr@sandelman.ca> Fri, 25 May 2012 14:33 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 29FC721F8617 for <roll@ietfa.amsl.com>; Fri, 25 May 2012 07:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.954
X-Spam-Level:
X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 KgwEWJyrs+vy for <roll@ietfa.amsl.com>; Fri, 25 May 2012 07:33:47 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 9504421F8674 for <roll@ietf.org>; Fri, 25 May 2012 07:33:46 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 23C1586C4; Fri, 25 May 2012 10:32:06 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 42E839823C; Fri, 25 May 2012 10:33:45 -0400 (EDT)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3EC8198239; Fri, 25 May 2012 10:33:45 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: roll@ietf.org
In-Reply-To: <4FBE8CCB.2050504@innovationslab.net>
References: <25665.1337180676@marajade.sandelman.ca> <4FB3C7CB.70709@innovationslab.net> <CAErDfUSjWgcgTt2oLDAFO-b4YUdqqfyUnrOC7AukggSCQNLNqQ@mail.gmail.com> <4FBA58CC.9040109@innovationslab.net> <19650.1337713406@marajade.sandelman.ca> <593C2D52-E780-4D75-B535-7F2B147642A0@gmail.com> <23542.1337782756@marajade.sandelman.ca> <B007D59E-A49D-48C0-B8FD-8EA9C10E4D8D@gmail.com> <32356.1337806435@marajade.sandelman.ca> <4FBE8CCB.2050504@innovationslab.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Fri, 25 May 2012 10:33:45 -0400
Message-ID: <8700.1337956425@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Brian Haberman <brian@innovationslab.net>, draft-ietf-roll-minrank-hysteresis-of@tools.ietf.org, roll-chairs@tools.ietf.org
Subject: [Roll] how to document provisioning model properly
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, 25 May 2012 14:33:48 -0000

(Guys, I pull ietf@ietf.org out, and added the WG)

http://trac.tools.ietf.org/wg/roll/trac/ticket/99

I want to note that Ralph and Brian's request is not really specific to 
MRHOF.

JP, how/where can we deal with this?

I know that Carstan was writing a 6lowpan/LLN/RPL/ND roadmap document
that explained how and where to use all these things together.  

However, while I hate to sound like a broken record, I think that these
things are in fact target application specific, and therefore need to be
addressed in the applicability statments.

My proposal is that we have to build a table of contents for the
applicability statements, and that we need to hold a WG LC on the
result.
See my other email to the list:
    http://www.ietf.org/mail-archive/web/roll/current/msg06982.html

I really do need some feedback here.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition.