Re: [Roll] Comments For ROLL terminology-06

Abdussalam Baryun <abdussalambaryun@gmail.com> Sat, 07 July 2012 10:15 UTC

Return-Path: <abdussalambaryun@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 DFF5521F85A5 for <roll@ietfa.amsl.com>; Sat, 7 Jul 2012 03:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.161
X-Spam-Level:
X-Spam-Status: No, score=-3.161 tagged_above=-999 required=5 tests=[AWL=-0.162, BAYES_00=-2.599, J_CHICKENPOX_27=0.6, RCVD_IN_DNSWL_LOW=-1]
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 248VkGoApayV for <roll@ietfa.amsl.com>; Sat, 7 Jul 2012 03:15:48 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id EF11921F858F for <roll@ietf.org>; Sat, 7 Jul 2012 03:15:47 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so7157438vbb.31 for <roll@ietf.org>; Sat, 07 Jul 2012 03:16:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=6c82+vaa//C9P61RDH9CP5w2KLlw/dqxXL4hGAhVzqA=; b=sO2CsAS7B0qPIYJ/BJ0S5+4WlplZ+JfhEjfzpXOjGIQhWhccElp064D3q2H/iWwJE2 6CfGx9+WZSX+qow/+nTSTEeDxNbB8wsSQXdh5gyYaRCJrURAHwiUdLBqL/sTPSXh8ANH hbmDFlotOSAJZu7JpA0i8n5uwg9VBSC1TwwO1xu6bxsS3p6fY1IM/U2xoLI/SPsLROgF nACahLUttlsxFWdF1cBjXHwBJC/EdvG+BL0WGni8OUC8/7LEkI3bKenuAC4dWF1BgjT2 aPiL2dXK58YFl/js9AedYbT3AkBrAraKa8ZGoKYbK/GyTBympKckzZr97vt/Kc1MBFMS /vpQ==
MIME-Version: 1.0
Received: by 10.52.94.36 with SMTP id cz4mr13576565vdb.10.1341656166527; Sat, 07 Jul 2012 03:16:06 -0700 (PDT)
Received: by 10.220.110.130 with HTTP; Sat, 7 Jul 2012 03:16:06 -0700 (PDT)
In-Reply-To: <CADnDZ8_kjUidiPu-ZwGDoFdVdACPRYUGwrFg-euxnBb5WP7tuQ@mail.gmail.com>
References: <CADnDZ8_kjUidiPu-ZwGDoFdVdACPRYUGwrFg-euxnBb5WP7tuQ@mail.gmail.com>
Date: Sat, 07 Jul 2012 12:16:06 +0200
Message-ID: <CADnDZ8_2qXNrwvb9JOFSMw=KqJitAnEE0o+Ojdt=YPNx04PJdA@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: roll <roll@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: Re: [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: Sat, 07 Jul 2012 10:15:49 -0000

I suggest also to add in section-4 [1], security terms that are
related to ROLL (or Terminology in ROLL security). IMO in any document
of defining terms, we can consider their implications or when do we
use these terms and terms related to the technology under study (e.g.
ROLL, MANET,  etc) . I use this approach in I-D [2].

[1] http://tools.ietf.org/id/draft-ietf-roll-terminology-06.txt
[2] http://tools.ietf.org/id/draft-baryun-manet-terminology-00.txt

AB
+++++++++++++++++++++++++++++++++++++++++++++++++++++
On 7/5/12, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> Hi Vasseur, and All,
>
> Comments:
> +++++++++
>
> 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
> unit-flow.
>
> 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.
> *****************************************************************************
>