Re: [RSN] Re: WG Review: Routing Over Low power and Lossy networks (roll)

JP Vasseur <jvasseur@cisco.com> Thu, 24 January 2008 21:26 UTC

Return-path: <rsn-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI9aF-00077W-Tv; Thu, 24 Jan 2008 16:26:03 -0500
Received: from rsn by megatron.ietf.org with local (Exim 4.43) id 1JI9aE-00077G-Go for rsn-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 16:26:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JI9aE-000777-5Q; Thu, 24 Jan 2008 16:26:02 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JI9aD-00019L-RG; Thu, 24 Jan 2008 16:26:02 -0500
X-IronPort-AV: E=Sophos;i="4.25,246,1199682000"; d="scan'208";a="84320492"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 24 Jan 2008 16:26:02 -0500
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m0OLQ1bK018882; Thu, 24 Jan 2008 16:26:01 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m0OLPuIx018010; Thu, 24 Jan 2008 21:26:01 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 24 Jan 2008 16:25:28 -0500
Received: from 10.86.104.178 ([10.86.104.178]) by xmb-rtp-213.amer.cisco.com ([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; Thu, 24 Jan 2008 21:25:27 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Thu, 24 Jan 2008 16:23:34 -0500
Subject: Re: [RSN] Re: WG Review: Routing Over Low power and Lossy networks (roll)
From: JP Vasseur <jvasseur@cisco.com>
To: Bernard Tourancheau <Bernard.Tourancheau@ens-lyon.fr>
Message-ID: <C3BE6C06.22182%jvasseur@cisco.com>
Thread-Topic: [RSN] Re: WG Review: Routing Over Low power and Lossy networks (roll)
Thread-Index: Achez1/inos0/srCEdyD6gANk8WjQA==
In-Reply-To: <694772F2-2A38-49E2-B53F-1E87FD100F61@ens-lyon.fr>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 24 Jan 2008 21:25:28.0493 (UTC) FILETIME=[A4210DD0:01C85ECF]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1604; t=1201209961; x=1202073961; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20<jvasseur@cisco.com> |Subject:=20Re=3A=20[RSN]=20Re=3A=20WG=20Review=3A=20Routin g=20Over=20Low=20power=20and=20Lossy=0A=20networks=20(roll) |Sender:=20 |To:=20Bernard=20Tourancheau=20<Bernard.Tourancheau@ens-lyo n.fr>; bh=5n5i6mMRoJSakUdyTBn1guEW/EJmO+TuxBN7l+8qw4I=; b=Qf7/PMljWsADwrBumZfCY0epOWGbXo5RLOs/9g7fEI5RihrUNRGuYt6i1d ZvAXGjoA33FB97Tp/NAePOz9e4ml8tUKqIIU7RQ3o/BEYFN9YZSWqKihtOCd O5zezGjE/w;
Authentication-Results: rtp-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: rsn@ietf.org, iesg@ietf.org
X-BeenThere: rsn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Sensor Networks <rsn.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rsn>, <mailto:rsn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rsn>
List-Post: <mailto:rsn@ietf.org>
List-Help: <mailto:rsn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rsn>, <mailto:rsn-request@ietf.org?subject=subscribe>
Errors-To: rsn-bounces@ietf.org



> From: Bernard Tourancheau <Bernard.Tourancheau@ens-lyon.fr>
> Date: Tue, 22 Jan 2008 17:01:35 +0100
> To: JP Vasseur <jvasseur@cisco.com>
> Cc: Ian Chakeres <ian.chakeres@gmail.com>, <iesg@ietf.org>, <rsn@ietf.org>
> Subject: Re: [RSN] Re: WG Review: Routing Over Low power and Lossy networks
> (roll)
> 
>>>> 
>>>> Low power and Lossy networks (LLNs) are typically composed of many
>>>> embedded devices with limited power, memory, and processing
>>>> resources
>>>> interconnected by a variety of links, such as IEEE 802.15.4,
>>>> Bluetooth,
>>>> Low Power WiFi. LLNs are transitioning to an end-to-end IP-based
>>>> solution
>>>> to avoid the problem of non-interoperable networks interconnected by
>>>> protocol translation gateways and proxies. In addition, LLNs have
>>>> specific
>>>> routing requirements that may not be met by existing routing
>>>> protocols,
>>>> such as OSPF, IS-IS, AODV and OLSR. For example path selection
>>>> must be
>>>> designed to take into consideration the specific power capabilities,
>>>> attributes and functional characteristics of the links and nodes
>>>> in the
>>>> network.
> I think application, its context and its environment may also be
> decision makers for the path selection and should be added here.
> --

Note that these are examples and of course detailed requirements for the
routing protocols will be specified in the application-specific routing
requirement documents. Note also that application-level capabilities are
functional characteristics of the node.

Thanks.

JP.

> Bernard.
>>>> 
> 




_______________________________________________
RSN mailing list
RSN@ietf.org
https://www1.ietf.org/mailman/listinfo/rsn