Re: [Roll] Node Ability to Participate (NAP)

Abdussalam Baryun <abdussalambaryun@gmail.com> Fri, 08 June 2012 03:48 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 7AA9B11E816C; Thu, 7 Jun 2012 20:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level:
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086, 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 xO-HXi45QNtB; Thu, 7 Jun 2012 20:48:28 -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 6257911E80B3; Thu, 7 Jun 2012 20:48:24 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so873087vbb.31 for <multiple recipients>; Thu, 07 Jun 2012 20:48:24 -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=7SzKFibBbDZXylEigmUHPxIhKr195tGLZJSDazSih1o=; b=JaJ5MV2t09vzqkpKMkJXRRpBDipTc9gMIrfNsiVhiffG+fFKEI3Moc0Fl0fYku6vYq RQ6EaAFVOymjPfV/ek2Vey48e+Zd+3XqDK+/R13GBWBv+Qhe5IbXJFGYkN/TpdSNQTT+ kz2Yn1PiDmz+Haibuz6q98BDR8thbkr7FBpCRwQO5e6w93GK7nLZEstYxAqPqN2TDEZt QS8ymJ2Cs88DRfIF67N1yJjJN4sr3qlUb6D9lknTVtewsIiRY7Q2zLSYbTRbRyh8otSY P8m7tcv2uhtNwAriHj+yvdG8bRhukrNu7AZEmjloHtVZkfFkjOFCjDOMYxF3ocn28XJt FeOg==
MIME-Version: 1.0
Received: by 10.52.90.196 with SMTP id by4mr3988010vdb.103.1339127303929; Thu, 07 Jun 2012 20:48:23 -0700 (PDT)
Received: by 10.220.98.77 with HTTP; Thu, 7 Jun 2012 20:48:23 -0700 (PDT)
In-Reply-To: <E045AECD98228444A58C61C200AE1BD806E78C95@xmb-rcd-x01.cisco.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> <13731.1338814785@marajade.sandelman.ca> <CADnDZ88prkVhco73YrHgnQ=8R9JH2GWnFTUj_GMouiQPWbkPyg@mail.gmail.com> <4787.1338995178@marajade.sandelman.ca> <CADnDZ8_3T-07UQ3h7MTLRU52qq6fhAv216vPdV4Wke-bFNyZYA@mail.gmail.com> <17448.1339014690@marajade.sandelman.ca> <CADnDZ89OYhXM=9BuAxfjo9xF8_oe+F_Cpfr1mN+f4_GXeFzVHA@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD806E78C95@xmb-rcd-x01.cisco.com>
Date: Fri, 8 Jun 2012 05:48:23 +0200
Message-ID: <CADnDZ8_sjXLvkrX6kjP1pgmXUX8y6AzQGZJ55pk_BcZrGSAMMg@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: roll <roll@ietf.org>, roll-owner <roll-owner@ietf.org>
Subject: Re: [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: Fri, 08 Jun 2012 03:48:29 -0000

Hi Pascal,

I was thinking of route-control enhancement, not network management,
however, I agree it is an iteresting issue as well, you gave me a new
point, thanks,

Abdussalam Baryun
=======================
On 6/7/12, Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
> Hello Abdussalam:
>
> I'd say it is a great discussion that might end up impacting routing. But
> also basic network operations (DNS, DHCP ...) and services.
> So where is the right place to start with?
> Tthe COMA mailing list is starting about network management, and I'd have
> thought that your discussion could begin there.
>
> What do you think?
>
>
> "
> List address: coma@ietf.org
> Archive:  http://www.ietf.org/mail-archive/web/coma/
> To subscribe:  https://www.ietf.org/mailman/listinfo/coma
>
> Purpose: This list is for the discussion related to the management of
> constrained networks and devices. The IETF so far has not developed specific
> technologies for the management of constrained networks. There is a need to
> understand the requirements for the management of such a constrained network
> and its devices.
> "
>
> Cheers,
>
> Pascal
>
>
> -----Original Message-----
> From: roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] On Behalf Of
> Abdussalam Baryun
> Sent: jeudi 7 juin 2012 11:00
> To: roll
> Cc: roll-owner
> Subject: [Roll] Node Ability to Participate (NAP)
>
> +++++++++++++++++  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. IETF 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 purpose other than IETF procedures' purposes.
> *****************************************************************************************
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>