[Roll] Presenting about a draft

Abdussalam Baryun <abdussalambaryun@gmail.com> Tue, 10 July 2012 15:08 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 13F3321F851C for <roll@ietfa.amsl.com>; Tue, 10 Jul 2012 08:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.455
X-Spam-Level:
X-Spam-Status: No, score=-3.455 tagged_above=-999 required=5 tests=[AWL=0.144, 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 3HpORUiuKoc7 for <roll@ietfa.amsl.com>; Tue, 10 Jul 2012 08:08:36 -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 7DCD121F851A for <roll@ietf.org>; Tue, 10 Jul 2012 08:08:36 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so63776vbb.31 for <roll@ietf.org>; Tue, 10 Jul 2012 08:09:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=KmH3z58ViJwwTur3MVCdrEJPCo2KpHoj7w2gBrEzYHU=; b=Nc6J1T2ThVM2sO3BkxNl2t+4hvd59XmFWO5wuA0o5bzA2LZGzwtj7BHB4+MGAvvXHU y5YndP8KQh/qg8/rXMiTdStRWfDImvOvPP60F9dhW5nXCKUCkwFuJuWcnJESTHWmGrUL FKkzO1k1c3L4TmQVRKX6ygb09TLDREzBZuhf5gdQNe1I385iiqAncaM+Y4pmRJRnXJi0 ERtKq2aXpOdZ9PPh3UndYJZjySIddYQ0VTpHs5bWpC3uG5iIll5usSOjbsd5uUOBafqe XqucIY1TzpkbWRHsHUn2hpHEs2YKWZAjg58euU4M+KFL/VFemTjOCSgaNIjVRXlc7nax KQAA==
MIME-Version: 1.0
Received: by 10.52.97.227 with SMTP id ed3mr6600594vdb.103.1341932943902; Tue, 10 Jul 2012 08:09:03 -0700 (PDT)
Received: by 10.220.110.130 with HTTP; Tue, 10 Jul 2012 08:09:03 -0700 (PDT)
Date: Tue, 10 Jul 2012 17:09:03 +0200
Message-ID: <CADnDZ8_QeuVDNtiqqWEddqvmg1kb2sSMqEQiz5+GG29wxz39GQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: roll <roll@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [Roll] Presenting about a draft
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, 10 Jul 2012 15:08:37 -0000

I am preparing the draft to submit (within some days) about the node
ability to participate (NAP) to the ROLL WG. I got a request for the
meeting purposes, to post this message about the draft objective and
introduction,

The Draft initial Objectives:

1) NAP Applicability (use cases).
2) NAP Protocol Considerations.
3) NAP Operation.

Introduction:

NAP protocol is intended to be used for LLN and wireless ad hoc networks.
The NAP protocol considers; 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 (TBD)). The node-ability can be useful if we have
different devices capabilities or/and conditions. This
knowledge-factor can be useful and may be included in some technique,
or forwarding table in the protocol specification. The general idea is
that each node may get to a situation to advertise its *ability*
limits for the network benefit, on the other hand, some nodes in some
situation may request information about such *ability* for their
benefit.

Thanking you,

Abdussalam Baryun
University of Glamorgan, UK