[Roll] Node Ability to Participate (NAP)

Abdussalam Baryun <abdussalambaryun@gmail.com> Mon, 04 June 2012 06:09 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 451BB21F87F5 for <roll@ietfa.amsl.com>; Sun, 3 Jun 2012 23:09:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.475
X-Spam-Status: No, score=-3.475 tagged_above=-999 required=5 tests=[AWL=0.124, 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 CPFKqc6Rlo9H for <roll@ietfa.amsl.com>; Sun, 3 Jun 2012 23:09:54 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id 651D021F87E3 for <roll@ietf.org>; Sun, 3 Jun 2012 23:09:54 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so2568628vcq.31 for <roll@ietf.org>; Sun, 03 Jun 2012 23:09:53 -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=5ATxOjAtCenIlZ5esZbpmSq2dNr9K+LOqghn0WvlCeo=; b=TdiQTiOe1aANhe3q5BblwBg9lJ4mOIuNuO9XuWVtu5JJYvfGSSS7VzJLo1pVuA/R9E 85FALOcxBb6rRDzvQ6zml0ti3iZdRMUpd84BgFZpGqT50DqIrCSv0Yq8HkU0Zj+ScU9T nzU1JixKhE3I5V5DhfUBIQogS/htpF1xYbIB/pV8trwn9NvXcaGSM2znvZijHUvg/4OS kgUOqownDcDtW40wbLoyGrRXH88+S7vJnMYWEsAIrovA3qf9euamN3eF3nCOxoknAFXN UQ18yaDKWzee7SUZUsRAMOSjS4qhNtoMUjF/QjGH/hPE2SuUtYq213GC20AVDASSkcO+ NJZA==
MIME-Version: 1.0
Received: by with SMTP id p20mr9582763vdj.129.1338790193777; Sun, 03 Jun 2012 23:09:53 -0700 (PDT)
Received: by with HTTP; Sun, 3 Jun 2012 23:09:53 -0700 (PDT)
In-Reply-To: <CADnDZ8-6XubLe1uTZ_-7H-bQYRy71H6KPJskNBKfkv9bpVbMHA@mail.gmail.com>
References: <CADnDZ893+npCLZxStpOQtm=gNfyShh6o6q-pNxSQC5b7EsM0+A@mail.gmail.com> <CADnDZ8-EirrhjXvx1-iZBtKrVEZUbvP6MUhGBs=Jhbw0cYC=uA@mail.gmail.com> <1FFD6787-3529-462B-B59A-115ADC99B842@cisco.com> <CADnDZ8-6XubLe1uTZ_-7H-bQYRy71H6KPJskNBKfkv9bpVbMHA@mail.gmail.com>
Date: Mon, 04 Jun 2012 08:09:53 +0200
Message-ID: <CADnDZ88H=3-0gVA6Br=wONtSdomNc9pCV9t_4ZGLPf-R-GNatg@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"
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: Mon, 04 Jun 2012 06:09:55 -0000

================== Possible Duplication ===================
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.