[Roll] Node Ability to Participate (NAP)
Abdussalam Baryun <abdussalambaryun@gmail.com> Tue, 05 June 2012 15:37 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 01ABC21F86B0 for <roll@ietfa.amsl.com>; Tue, 5 Jun 2012 08:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.489
X-Spam-Level:
X-Spam-Status: No, score=-3.489 tagged_above=-999 required=5 tests=[AWL=0.110, 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 2vExE8SUdjAz for <roll@ietfa.amsl.com>; Tue, 5 Jun 2012 08:36:59 -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 625D721F85A5 for <roll@ietf.org>; Tue, 5 Jun 2012 08:36:59 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so3633622vbb.31 for <roll@ietf.org>; Tue, 05 Jun 2012 08:36:59 -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 :cc:content-type; bh=slzpmvugEDyTt/B16kOWHR2Rk0f0NNXgA8HnKttWZP0=; b=AJy93LRen7HRf9JBzl3kd/aA7mRrxI5Eu+fXPH5PaSdDSPFAuoekRVKwBFAklSVs4a XBrvfT4jX3PORN9ef0dGQ8X+4f3qd/jPoL+K1+zkyz+8RgsqqSWpQSvfzVJ/yjJ1jlIS lg1RkFzuqvEhAKfXnKodvWp7ysmArdWnpPTzC5cYnhsT8sNpmKoO00WZDHiSncU7ZLBu 9SfUxgj9SYleXDYybZzioARbzGbAeGH7c7oTJZyRphNs1T+5h4Exz108arfwR2GV/Ozr InK86ksdkkTGveiWY6dswuHwezAhQqBOowqirqYPCCsgfNq7M27cH/88ekkwo/NtgbFj xcAw==
MIME-Version: 1.0
Received: by 10.220.140.193 with SMTP id j1mr4737921vcu.4.1338910618935; Tue, 05 Jun 2012 08:36:58 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Tue, 5 Jun 2012 08:36:58 -0700 (PDT)
In-Reply-To: <CADnDZ893+npCLZxStpOQtm=gNfyShh6o6q-pNxSQC5b7EsM0+A@mail.gmail.com>
References: <CADnDZ893+npCLZxStpOQtm=gNfyShh6o6q-pNxSQC5b7EsM0+A@mail.gmail.com>
Date: Tue, 05 Jun 2012 17:36:58 +0200
Message-ID: <CADnDZ89_Btc2m+JWD9pAnrXs4KBW0nxRFcdLJr=efyXm1uRrtw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: 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: Tue, 05 Jun 2012 15:37:00 -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. *****************************************************************************************
- [Roll] Node Ability to Participate (NAP) Abdussalam Baryun
- [Roll] Node Ability to Participate (NAP) Abdussalam Baryun
- [Roll] Node Ability to Participate (NAP) Abdussalam Baryun
- [Roll] Node Ability to Participate (NAP) Abdussalam Baryun
- [Roll] Node Ability to Participate (NAP) Abdussalam Baryun
- [Roll] Node Ability to Participate (NAP) Abdussalam Baryun
- Re: [Roll] Node Ability to Participate (NAP) Pascal Thubert (pthubert)
- Re: [Roll] Node Ability to Participate (NAP) Abdussalam Baryun
- Re: [Roll] Node Ability to Participate (NAP) C Chauvenet
- Re: [Roll] Node Ability to Participate (NAP) Abdussalam Baryun