Re: [Roll] Last Call: draft-ietf-roll-building-routing-reqs (Building Automation Routing Requirements in Low Power and Lossy Networks) to Informational RFC

Alexandru Petrescu <alexandru.petrescu@gmail.com> Sat, 07 March 2009 00:20 UTC

Return-Path: <alexandru.petrescu@gmail.com>
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 8587F3A6969; Fri, 6 Mar 2009 16:20:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.967
X-Spam-Level:
X-Spam-Status: No, score=-1.967 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 39WQ9UnOxjgl; Fri, 6 Mar 2009 16:20:29 -0800 (PST)
Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5]) by core3.amsl.com (Postfix) with ESMTP id B7B1E3A6A99; Fri, 6 Mar 2009 16:20:27 -0800 (PST)
Received: from smtp5-g21.free.fr (localhost [127.0.0.1]) by smtp5-g21.free.fr (Postfix) with ESMTP id 12F69D48044; Sat, 7 Mar 2009 01:20:54 +0100 (CET)
Received: from [127.0.0.1] (bur91-3-82-239-213-32.fbx.proxad.net [82.239.213.32]) by smtp5-g21.free.fr (Postfix) with ESMTP id F10AED48031; Sat, 7 Mar 2009 01:20:51 +0100 (CET)
Message-ID: <49B1BDDB.4020509@gmail.com>
Date: Sat, 07 Mar 2009 01:20:43 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: ietf@ietf.org
References: <20090220013719.C2CCD3A6952@core3.amsl.com>
In-Reply-To: <20090220013719.C2CCD3A6952@core3.amsl.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 090306-0, 06/03/2009), Outbound message
X-Antivirus-Status: Clean
Cc: roll@ietf.org
Subject: Re: [Roll] Last Call: draft-ietf-roll-building-routing-reqs (Building Automation Routing Requirements in Low Power and Lossy Networks) to Informational RFC
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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/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: Sat, 07 Mar 2009 00:20:30 -0000

Dear IETF,

This may be late, after 2009-03-05, but here it goes anyways.

There was some discussion in the WG about the Mobility requirement,
section 5.3.  It seems the requirement is indeed in the draft but
discussions don't make it appear as important as it may imply.  This
leads to potentially unclear decisions about what kind of protocol work
should be done in ROLL WG.

A simple example:
> To minimize network dynamics, mobile devices SHOULD not be allowed to
>  act as forwarding devices (routers) for other devices in the LLN.

This effectively prohibits the use of a NEMOv6 Mobile Router (RFC3963),
which I find otherwise very appropriate for this task.  Because I'm not
sure I know of any other mobility protocol which would achieve the same.

So, is this a requirement?  A so-and-so requirement?

A suggestion would be to completely remove the Mobility requirement
section from the draft.  But I'm not sure I could suggest that because
it appears also that the requirements are very strongly supported by
industry needs.

That's my comment,

Alex

The IESG a écrit :
> The IESG has received a request from the Routing Over Low power and 
> Lossy networks WG (roll) to consider the following document:
> 
> - 'Building Automation Routing Requirements in Low Power and Lossy 
> Networks ' <draft-ietf-roll-building-routing-reqs-05.txt> as an 
> Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
>  final comments on this action.  Please send substantive comments to 
> the ietf@ietf.org mailing lists by 2009-03-05. Exceptionally, 
> comments may be sent to iesg@ietf.org instead. In either case, please
>  retain the beginning of the Subject line to allow automated sorting.
> 
> 
> 
> The file can be obtained via 
> http://www.ietf.org/internet-drafts/draft-ietf-roll-building-routing-reqs-05.txt
> 
> 
> 
> 
> IESG discussion can be tracked via 
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=17943&rfc_flag=0The
>  following IPR Declarations may be related to this I-D:
> 
> 
> 
> _______________________________________________ Roll mailing list 
> Roll@ietf.org https://www.ietf.org/mailman/listinfo/roll
>