[Roll] Comments For ROLL terminology-06

Abdussalam Baryun <abdussalambaryun@gmail.com> Thu, 05 July 2012 15:36 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D34BE21F873A for <roll@ietfa.amsl.com>; Thu, 5 Jul 2012 08:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.458
X-Spam-Status: No, score=-3.458 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ixTn8ShfPUPR for <roll@ietfa.amsl.com>; Thu, 5 Jul 2012 08:36:44 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id 132C321F86C9 for <roll@ietf.org>; Thu, 5 Jul 2012 08:36:43 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so6080208vbb.31 for <roll@ietf.org>; Thu, 05 Jul 2012 08:36:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=M4yLmjpzCSj5h99YPdkrsih392Ae7wCOSwLfiqh698I=; b=F+1R2kRRANtb4gzc2sOrMpgHhqAm/dfK4kL/Ibo/nCQtWfxDFeNa0VCRnaGvD3dZYl VdIm++OdagvuIUH8IdLgzjQxlhlbcpctb2LBUpeuQd0e2DaICNM9DAwYgxdS4pEXgylk LVd1NWhCAAp3mwJvZErr/K/vce4RmkfrkpLBhFLfOE5EjFqVOMhZZLznSEG/CxAFx3vO w2UmVafKpLJQdFoZLtdCPjVA2NA8MCNxWmUOl3PKZgvC/Zzsnahfg0+Gj5faufZye9wR 3ckpOQAXCsJzzXLSQHp4Rs7ktKZ6E1SWI070IDOE65E3JzyuP7sI3cIdJFaOCcfHtYeD JJ5Q==
MIME-Version: 1.0
Received: by with SMTP id r15mr12834083vcv.1.1341502617528; Thu, 05 Jul 2012 08:36:57 -0700 (PDT)
Received: by with HTTP; Thu, 5 Jul 2012 08:36:57 -0700 (PDT)
Date: Thu, 05 Jul 2012 17:36:57 +0200
Message-ID: <CADnDZ8_kjUidiPu-ZwGDoFdVdACPRYUGwrFg-euxnBb5WP7tuQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: JP Vasseur <jpv@cisco.com>, roll <roll@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Abdussalam Baryun <abdussalambaryun@googlemail.com>
Subject: [Roll] Comments For ROLL terminology-06
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: Thu, 05 Jul 2012 15:36:45 -0000

Hi Vasseur, and All,


AB>general comment> ROLL is about routers/nodes/hosts Why not defined
:  Host, Node, Link, Interface

In the body of draft-06:-

Closed Loop Control: A process whereby a device controller controls
an actuator based on information sensed by one or more field devices.

AB>suggest> replace [process] with [procedure]
AB>suggest> replace [information] with [input information]

Downstream: Data direction traveling from outside of the LLN (e.g.
traffic coming from a LAN, WAN or the Internet) via a LBR.

AB> suggest> remove the example, because first, ROLL is inside LLN not
outside, and second, most of the data-traffic MAY go from the LLN to
the Internet/LBR. IMHO downstream is in the direction of the havier

AB> please note that if we use word [data] is different than
[message]. While using [message] we may mean all traffic includes data
and control messages, so the use of downstream and upstream as in
draft-06 will be ok, but if we mention data-direction IMHO the use
downstream-upstream will be the other way around.

AB> suggest> replace [data] with [message]

Field Device:

AB> delete word> field

MP2P: Multipoint-to-Point is used to describe a particular traffic
pattern (e.g. MP2P flows collecting information from many nodes
flowing inwards towards a collecting sink or an LBR).

AB>opinion> MP2P is not a traffic pattern it is a transmission method

I am not sure if the draft covers all terms used in ROLL protocols, I
will check and post on the same thread after. Thanking you,

Best Regards

Abdussalam Baryun
University of glamorgan, UK
I may be wrong, or may be right, but it does not matter if we work together
 as a group to discuss and resolve all issues. WGs are always right.
This email and any attachments are confidential to the intended recipient
and may also be privileged. If you are not the intended recipient please
delete it from your system and notify the sender. The contents are comply
to the IETF regulations, and WG procedures. You should not copy the
email nor use it for any other purpose, nor disclose, nor distribute its
contents to any other person.