[Roll] Fwd: RFC 5548 on Routing Requirements for Urban Low-Power and Lossy Networks
JP Vasseur <jvasseur@cisco.com> Fri, 22 May 2009 05:58 UTC
Return-Path: <jvasseur@cisco.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 4038B3A7023 for <roll@core3.amsl.com>; Thu, 21 May 2009 22:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.168
X-Spam-Level:
X-Spam-Status: No, score=-10.168 tagged_above=-999 required=5 tests=[AWL=0.430, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 1622JOHBad3U for <roll@core3.amsl.com>; Thu, 21 May 2009 22:58:50 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 272AE3A7021 for <roll@ietf.org>; Thu, 21 May 2009 22:58:50 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.41,231,1241395200"; d="scan'208,217"; a="41102112"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 22 May 2009 05:59:54 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n4M5xs5F031422 for <roll@ietf.org>; Fri, 22 May 2009 07:59:54 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n4M5xsRU004534 for <roll@ietf.org>; Fri, 22 May 2009 05:59:54 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 22 May 2009 07:59:54 +0200
Received: from ams-jvasseur-8712.cisco.com ([10.55.201.131]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 22 May 2009 07:59:53 +0200
Message-Id: <ECD85AC1-E2DC-4872-BD67-A634E9EAE301@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: ROLL WG <roll@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail-123-524304883"
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 22 May 2009 07:59:53 +0200
References: <20090519215358.9EC7B2B1BF9@bosco.isi.edu>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 22 May 2009 05:59:54.0337 (UTC) FILETIME=[87205510:01C9DAA2]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=12221; t=1242971994; x=1243835994; c=relaxed/simple; s=amsdkim1002; 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:=20Fwd=3A=20RFC=205548=20on=20Routing=20Requiremen ts=20for=20Urban=20Low-Power=20and=20Lossy=20Networks |Sender:=20; bh=5MtmJbp3PIu2daqnviLt4//kolOoMyhd03Q0A9qEnMU=; b=t0HDRU7CHg5HKVDGzTdcnq9VcCo1p88pFxigitH/2mgj/AQ+H3f9I7BlyS ccgfT9xyKQBDZ5qllkyniv88Wqc11NKz8gGSY+cuxdH1aBbNYCC27CWpc4Rs lW7EUzbyGM;
Authentication-Results: ams-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
Subject: [Roll] Fwd: RFC 5548 on Routing Requirements for Urban Low-Power and Lossy Networks
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: Fri, 22 May 2009 05:58:57 -0000
Our first RFC :-) JP. Begin forwarded message: > From: rfc-editor@rfc-editor.org > Date: May 19, 2009 11:53:58 PM CEDT > To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org > Cc: roll@ietf.org, rfc-editor@rfc-editor.org > Subject: RFC 5548 on Routing Requirements for Urban Low-Power and > Lossy Networks > > > A new Request for Comments is now available in online RFC libraries. > > > RFC 5548 > > Title: Routing Requirements for Urban Low-Power > and Lossy Networks > Author: M. Dohler, Ed., > T. Watteyne, Ed., > T. Winter, Ed., > D. Barthel, Ed. > Status: Informational > Date: May 2009 > Mailbox: mischa.dohler@cttc.es, > watteyne@eecs.berkeley.edu, > wintert@acm.org, > Dominique.Barthel@orange-ftgroup.com > Pages: 21 > Characters: 47759 > Updates/Obsoletes/SeeAlso: None > > I-D Tag: draft-ietf-roll-urban-routing-reqs-05.txt > > URL: http://www.rfc-editor.org/rfc/rfc5548.txt > > The application-specific routing requirements for Urban Low-Power and > Lossy Networks (U-LLNs) are presented in this document. In the near > future, sensing and actuating nodes will be placed outdoors in urban > environments so as to improve people's living conditions as well as > to monitor compliance with increasingly strict environmental laws. > These field nodes are expected to measure and report a wide gamut of > data (for example, the data required by applications that perform > smart-metering or that monitor meteorological, pollution, and allergy > conditions). The majority of these nodes are expected to communicate > wirelessly over a variety of links such as IEEE 802.15.4, low-power > IEEE 802.11, or IEEE 802.15.1 (Bluetooth), which given the limited > radio range and the large number of nodes requires the use of > suitable routing protocols. The design of such protocols will be > mainly impacted by the limited resources of the nodes (memory, > processing power, battery, etc.) and the particularities of the > outdoor urban application scenarios. As such, for a wireless > solution for Routing Over Low-Power and Lossy (ROLL) networks to be > useful, the protocol(s) ought to be energy-efficient, scalable, and > autonomous. This documents aims to specify a set of IPv6 routing > requirements reflecting these and further U-LLNs' tailored > characteristics. This memo provides information for the Internet > community. > > This document is a product of the Routing Over Low power and Lossy > networks Working Group of the IETF. > > > INFORMATIONAL: This memo provides information for the Internet > community. > It does not specify an Internet standard of any kind. Distribution of > this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html > . > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. > Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > USC/Information Sciences Institute > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce