Re: [Roll] ** Resending ** Re: Adoption draft-martocci-roll-building-routing-reqs-01.txt as a new ROLL WG document

"Mischa Dohler" <mischa.dohler@cttc.es> Tue, 21 October 2008 09:07 UTC

Return-Path: <roll-bounces@ietf.org>
X-Original-To: roll-archive@ietf.org
Delivered-To: ietfarch-roll-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72DF63A692B; Tue, 21 Oct 2008 02:07:13 -0700 (PDT)
X-Original-To: roll@core3.amsl.com
Delivered-To: roll@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A1433A692B for <roll@core3.amsl.com>; Tue, 21 Oct 2008 02:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level:
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W+kqABdmIt0y for <roll@core3.amsl.com>; Tue, 21 Oct 2008 02:07:12 -0700 (PDT)
Received: from scorpius.cttc.es (scorpius.cttc.es [84.88.62.197]) by core3.amsl.com (Postfix) with ESMTP id A16673A67E7 for <roll@ietf.org>; Tue, 21 Oct 2008 02:07:11 -0700 (PDT)
Received: from leo (postfix@leo.cttc.es [84.88.62.208]) by scorpius.cttc.es (8.13.8/8.13.5) with ESMTP id m9L96wDG005221 for <roll@ietf.org>; Tue, 21 Oct 2008 11:06:58 +0200
Received: from CTTCPCMDOHLER (pcmdohler.cttc.es [84.88.61.89]) by leo (Postfix) with ESMTP id B935310C21F for <roll@ietf.org>; Tue, 21 Oct 2008 11:06:58 +0200 (CEST)
From: Mischa Dohler <mischa.dohler@cttc.es>
To: roll@ietf.org
Date: Tue, 21 Oct 2008 11:03:23 +0200
Organization: CTTC
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AckuCwnC7N1yTf4ouUO/C8KPBKVFaQDtQgZKAGZHBVA=
In-Reply-To: <C520B498.5798F%jvasseur@cisco.com>
Message-Id: <20081021090658.B935310C21F@leo>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (leo); Tue, 21 Oct 2008 11:06:58 +0200 (CEST)
X-Scanned-By: MIMEDefang 2.57 on 84.88.62.197
Subject: Re: [Roll] ** Resending ** Re: Adoption draft-martocci-roll-building-routing-reqs-01.txt as a new ROLL WG document
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mischa.dohler@cttc.es
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: roll-bounces@ietf.org
Errors-To: roll-bounces@ietf.org

Dear Jerry,

The building draft was an interesting read and certainly warrants being a
stand-alone ROLL WG document. I felt however that the building and home
drafts have some similarities. To this end, would you please be so kind and
summarize in a few words the key differences between both approaches, mainly
from a routing perspective? Thanks. (For example, focus of the urban draft
is on scalability; focus of the industrial draft is on reliable and quick
reporting; focus of the home draft is, so I believe, on heterogeneity and
also quick response.)

A small side note on your assumption of 1000+ nodes in the network,
something we also struggle(d) with in the urban draft. Watteyne et al have
done some studies with real-world hardware figures assuming a 1000 node
network and figured out that - no matter how hard you try - you can not make
nodes report more frequently than every 8 seconds. This is mainly because
the nodes close to the sink run out of buffer pretty quickly. I think this
will have an impact on your mentioned applications because you either have
to perform some heavy aggregation (which has not been mentioned, I think) or
heavy prioritization (which is central to your draft but only in the context
of time critical alarms).

Kind regards,
Mischa.

_____________________________________

Dr Mischa Dohler
Senior Researcher
CTTC, Barcelona

Tel: +34 93 645 2900
Fax: +34 93 645 2901
Mob: +34 6 7909 4007

www.cttc.es/home/mdohler
_____________________________________

... www.ict09.org ...................
... www.iwcld2009.org ...............
... www.ieee-secon.com/2009 .........
... www.ieeevtc.org/vtc2009spring ...
_____________________________________






-----Original Message-----
From: roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] On Behalf Of JP
Vasseur
Sent: Sunday, October 19, 2008 9:56 AM
To: JP Vasseur; roll@ietf.org
Subject: [Roll] ** Resending ** Re: Adoption
draft-martocci-roll-building-routing-reqs-01.txt as a new ROLL WG document

As you know building automation is part of our charter. Could you please let
us know what you think about this ID (in favor or opposed)?

Thanks.

JP.


On 10/14/08 4:42 PM, "JP Vasseur" <jvasseur@cisco.com> wrote:

> Dear WG,
> 
> A new revision of draft-martocci-roll-building-routing-reqs-01.txt has
just
> been posted that addresses many of comments that we all provided so far.
> 
>
http://www.ietf.org/internet-drafts/draft-martocci-roll-building-routing-req
> s-01.txt
> 
> Are you in favor/opposed to the adoption
> draft-martocci-roll-building-routing-reqs-01.txt as a ROLL WG document ?
> 
> Thanks.
> 
> JP.
> 
> _______________________________________________
> 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 mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll