Re: [Roll] Node Ability to Participate (NAP)
C Chauvenet <c.chauvenet@watteco.com> Fri, 22 June 2012 10:13 UTC
Return-Path: <c.chauvenet@watteco.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 708A721F861D for <roll@ietfa.amsl.com>; Fri, 22 Jun 2012 03:13:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Li49Xkrlj7l4 for <roll@ietfa.amsl.com>; Fri, 22 Jun 2012 03:13:12 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id AA68621F861A for <roll@ietf.org>; Fri, 22 Jun 2012 03:13:12 -0700 (PDT)
Received: from mail81-tx2-R.bigfish.com (10.9.14.238) by TX2EHSOBE002.bigfish.com (10.9.40.22) with Microsoft SMTP Server id 14.1.225.23; Fri, 22 Jun 2012 10:11:43 +0000
Received: from mail81-tx2 (localhost [127.0.0.1]) by mail81-tx2-R.bigfish.com (Postfix) with ESMTP id 0ADD4360483; Fri, 22 Jun 2012 10:11:43 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.252.165; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0510HT004.eurprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -81
X-BigFish: VPS-81(zzbb2dI98dIc89bh542M1dbaI1432I1418I15caKJ14ffIzz1202hzz1033IL8275bh8275dhz2dh2a8h668h839hd25hf0ah)
Received: from mail81-tx2 (localhost.localdomain [127.0.0.1]) by mail81-tx2 (MessageSwitch) id 1340359900516713_14829; Fri, 22 Jun 2012 10:11:40 +0000 (UTC)
Received: from TX2EHSMHS028.bigfish.com (unknown [10.9.14.245]) by mail81-tx2.bigfish.com (Postfix) with ESMTP id 7B30F1400EF; Fri, 22 Jun 2012 10:11:40 +0000 (UTC)
Received: from DBXPRD0510HT004.eurprd05.prod.outlook.com (157.56.252.165) by TX2EHSMHS028.bigfish.com (10.9.99.128) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 22 Jun 2012 10:11:40 +0000
Received: from DBXPRD0510MB395.eurprd05.prod.outlook.com ([169.254.7.215]) by DBXPRD0510HT004.eurprd05.prod.outlook.com ([10.255.67.167]) with mapi id 14.16.0164.004; Fri, 22 Jun 2012 10:13:03 +0000
From: C Chauvenet <c.chauvenet@watteco.com>
To: 'Abdussalam Baryun' <abdussalambaryun@gmail.com>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Thread-Topic: [Roll] Node Ability to Participate (NAP)
Thread-Index: AQHNRIv/1FnSK8b/vEGEuTOnYY1xMpbvWQ0AgABw9YCAFmsNwA==
Date: Fri, 22 Jun 2012 10:13:03 +0000
Message-ID: <97B69B30E0EF244B940B65EA541E3F2D02296E1C@DBXPRD0510MB395.eurprd05.prod.outlook.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> <CADnDZ8_sjXLvkrX6kjP1pgmXUX8y6AzQGZJ55pk_BcZrGSAMMg@mail.gmail.com>
In-Reply-To: <CADnDZ8_sjXLvkrX6kjP1pgmXUX8y6AzQGZJ55pk_BcZrGSAMMg@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [82.241.54.131]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: watteco.com
Cc: roll <roll@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, 22 Jun 2012 10:13:13 -0000
Hi, Could RFC6551 (the ex-metric draft) help ? I think the metric container option could embed a constraint to adress the NAP functionality you are describing Best, Cédric. -----Message d'origine----- De : roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] De la part de Abdussalam Baryun Envoyé : vendredi 8 juin 2012 05:48 À : Pascal Thubert (pthubert) Cc : roll; roll-owner Objet : Re: [Roll] Node Ability to Participate (NAP) 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 > _______________________________________________ Roll mailing list Roll@ietf.org https://www.ietf.org/mailman/listinfo/roll
- [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