IETF Logo Mail Archive

Re: [Roll] definition of sleepy node

"JP Vasseur (jvasseur)" <jvasseur@cisco.com> Thu, 31 January 2013 10:42 UTC

Return-Path: <jvasseur@cisco.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 6DCA321F86BC for <roll@ietfa.amsl.com>; Thu, 31 Jan 2013 02:42:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0u1X5FNJFGl for <roll@ietfa.amsl.com>; Thu, 31 Jan 2013 02:42:01 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 8549321F86BB for <roll@ietf.org>; Thu, 31 Jan 2013 02:42:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4981; q=dns/txt; s=iport; t=1359628921; x=1360838521; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=+3uNkLj5XmmBDWlcLAxQyAQsxGUP21kZaftT2Vd3iFk=; b=MPzrskKtaeBhhKsHUBLM0ovxSvs/7973vrNatvE4QVJYlo8fDK5fX3I/ p5T8ZyephH271I4/UAZ/CQkfqdie4bxhTtfRavMa7bZL6mt1qE409U3ea ftlgv693AGgS1C5LuRlZGlWxw+fjocMSvP8HrpkmIIEvil8CfxCcQ0eeG c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqwFAAdJClGtJV2a/2dsb2JhbABFrHaJEwGJFhZzgh8BAQQBAQFrCxACAQgEHh0HJwsUEQIEDgUIiAkMwgWNIoMJYQOXLo8wgneBZiMBGg
X-IronPort-AV: E=Sophos; i="4.84,575,1355097600"; d="scan'208,217"; a="170982844"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP; 31 Jan 2013 10:42:01 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r0VAg19d028792 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 31 Jan 2013 10:42:01 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.64]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Thu, 31 Jan 2013 04:42:00 -0600
From: "JP Vasseur (jvasseur)" <jvasseur@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Thread-Topic: [Roll] definition of sleepy node
Thread-Index: AQHN/5+ZgMkErc4YM06OsbUF+Z2e7g==
Date: Thu, 31 Jan 2013 10:42:00 +0000
Message-ID: <03B78081B371D44390ED6E7BADBB4A772324DDB5@xmb-rcd-x02.cisco.com>
References: <50FEE333.5080706@saloits.com> <6366.1358887999@sandelman.ca> <CADnDZ8_-PViLncCUgRo8Rw8N7VxVLbwJrmk_5NGMMtjQz9-epg@mail.gmail.com>
In-Reply-To: <CADnDZ8_-PViLncCUgRo8Rw8N7VxVLbwJrmk_5NGMMtjQz9-epg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.98.78]
Content-Type: multipart/alternative; boundary="_000_03B78081B371D44390ED6E7BADBB4A772324DDB5xmbrcdx02ciscoc_"
MIME-Version: 1.0
Cc: "<roll@ietf.org>" <roll@ietf.org>
Subject: Re: [Roll] definition of sleepy node
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: Thu, 31 Jan 2013 10:42:02 -0000

Seems like we have a consensus for:


Sleepy Node
A sleepy node is a node that may sometimes go into a sleep mode (i.e. go into a low power state to conserve power) and temporarily suspend protocol communication.  A sleepy node may also sometimes remain in a fully powered on state where it has the capability to perform RPL protocol communication.


Non-Sleepy Node
A non-sleepy node is a node that always remains in a fully powered on state (i.e. always awake) where it has the capability to perform RPL protocol communication.


Added to draft-ietf-roll-terminology-10.

Thanks.

JP.

On Jan 22, 2013, at 4:36 PM, Abdussalam Baryun wrote:

+1

AB

On 1/22/13, Michael Richardson <mcr+ietf@sandelman.ca<mailto:mcr+ietf@sandelman.ca>> wrote:

Please be aware that the definition of sleepy node need not be
pendantically precise.  The purpose of the glossary of terms is
mostly so that when discussing LLNs with non-LLN network specialists
that we give them an idea what this could mean, not that we find do
LLN taxonomy.





--
Michael Richardson <mcr+IETF@sandelman.ca<mailto:mcr+IETF@sandelman.ca>>, Sandelman Software Works
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/


_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll

v2.23.0 | Report a Bug | By Email