[Roll] Node Ability to Participate (NAP)

Abdussalam Baryun <abdussalambaryun@gmail.com> Sat, 02 June 2012 09:36 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 6F90D21F8962; Sat, 2 Jun 2012 02:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.424
X-Spam-Level:
X-Spam-Status: No, score=-3.424 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, 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 5gNZYwdxZL4H; Sat, 2 Jun 2012 02:36:44 -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 BF93721F8961; Sat, 2 Jun 2012 02:36:43 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1941945vbb.31 for <multiple recipients>; Sat, 02 Jun 2012 02:36:43 -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:content-type; bh=ME/3HnYjTtezDYvIE6rLCnc8fzoXdRVrSygd86zVh1E=; b=d3PvknqL6eeTQqfCK5YSCz+lwHFcOuMSCoEhBDt4am8gNd5zeb688omXbQQYn7zDTJ VVWBRFnf5+iFVa5YqdtyqmN4Qit3HUosqB8u/X3w461whfH/Ds5qGnZAOPunU38c9+OV UpSKo2NZzql4kpFzZ8Xefbp8i3o0tKWuLHj2OKI/Kne9ZVoII//yzOAJf5iTg6nvOBU3 EL0TTsmEcBB0maq449IwLqtuIJUqxk82W6LGpAeyIjsgbVUKyC26/8klg4VmD0sK7z5E YAHt+1ueiwvUBLay3+1yzM0yUwVRHyXz3O8AOdLvOmQtI7OUS04WTDKse6tIQWa0XulP 9ZQA==
MIME-Version: 1.0
Received: by 10.52.33.37 with SMTP id o5mr5120786vdi.86.1338629803033; Sat, 02 Jun 2012 02:36:43 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Sat, 2 Jun 2012 02:36:42 -0700 (PDT)
Date: Sat, 2 Jun 2012 11:36:42 +0200
Message-ID: <CADnDZ893+npCLZxStpOQtm=gNfyShh6o6q-pNxSQC5b7EsM0+A@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: roll@ietf.org, 6lowpan@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Mon, 04 Jun 2012 05:48:14 -0700
Subject: [Roll] Node Ability to Participate (NAP)
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, 02 Jun 2012 09:36:44 -0000

Hi All,

I want to discuss is there a need to consider the node ability to
participate (NAP) in LLN functions?

I think that the node ability (considering; energy consumption issue,
routing issue, and environment-event issue), it is good for some
node-originators to know neighbor nodes/sinks ability ( NAP to-route,
or NAP continue-to-route, or NAP to-survive, NAP to-store, NAP
to-manage, or other abilities), but not sure if it is available in
some of the ROLL or 6lowpan protocols, nor sure if it can make side
effects to LLN performance. The node-ability can be useful if we have
different devices capabilities and conditions. This knowledge-factor
can be useful and may be included in some technique, or forwarding
table in the protocol specification.

I want to know your advises and opinion, thanking you,

Best regards

Abdussalam Baryun,
University of Glamorgan, UK.
=======================================================
( One 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.
*****************************************************************************************