--- 1/draft-ietf-roll-home-routing-reqs-10.txt 2010-01-13 17:10:36.000000000 +0100 +++ 2/draft-ietf-roll-home-routing-reqs-11.txt 2010-01-13 17:10:36.000000000 +0100 @@ -1,21 +1,21 @@ Networking Working Group A. Brandt Internet Draft Sigma Designs, Inc. Intended status: Informational J. Buron Expires: July 2010 Sigma Designs, Inc. G. Porcu Telecom Italia - January 6, 2010 + January 13, 2010 Home Automation Routing Requirements in Low Power and Lossy Networks - draft-ietf-roll-home-routing-reqs-10 + draft-ietf-roll-home-routing-reqs-11 Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -25,21 +25,21 @@ documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on July 6, 2010. + This Internet-Draft will expire on July 13, 2010. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license- info). @@ -90,33 +90,32 @@ 2.4. Adding A New Module To The System......................7 2.5. Controlling Battery Operated Window Shades.............8 2.6. Remote Video Surveillance..............................8 2.7. Healthcare.............................................8 2.7.1. At-home Health Reporting..........................9 2.7.2. At-home Health Monitoring........................10 2.8. Alarm Systems.........................................10 3. Unique Routing Requirements of Home Automation Applications11 3.1. Constraint-based Routing..............................11 3.2. Support of Mobility...................................12 - 3.3. Healthcare Routing....................................13 - 3.4. Scalability...........................................13 - 3.5. Convergence Time......................................13 - 3.6. Manageability.........................................14 - 3.7. Stability.............................................14 - 4. Traffic Pattern............................................14 - 5. Security Considerations....................................15 + 3.3. Scalability...........................................12 + 3.4. Convergence Time......................................13 + 3.5. Manageability.........................................13 + 3.6. Stability.............................................13 + 4. Traffic Pattern............................................13 + 5. Security Considerations....................................14 6. IANA Considerations........................................16 7. Acknowledgments............................................16 - 8. Disclaimer for pre-RFC5378 work............................17 - 9. References.................................................17 - 9.1. Normative References..................................17 - 9.2. Informative References................................17 + 8. Disclaimer for pre-RFC5378 work............................16 + 9. References.................................................16 + 9.1. Normative References..................................16 + 9.2. Informative References................................16 1. Introduction This document presents home control and automation application specific requirements for Routing Over Low power and Lossy networks (ROLL). In the near future many homes will contain high numbers of wireless devices for a wide set of purposes. Examples include actuators (relay, light dimmer, heating valve), sensors (wall switch, water leak, blood pressure) and advanced controllers. Basic home control modules such as wall switches and @@ -464,44 +463,44 @@ 3. Unique Routing Requirements of Home Automation Applications Home automation applications have a number of specific routing requirements related to the set of home networking applications and the perceived operation of the system. The relations of use cases to requirements are outlined in the table below: - +-------------------------------+-----------------------------+ + +------------------------------+-----------------------------+ | Use case | Requirement | - +-------------------------------+-----------------------------+ + +------------------------------+-----------------------------+ |2.1. Lighting Application In |3.2. Support of Mobility | - |Action |3.4. Scalability | + |Action |3.3. Scalability | | | | - +-------------------------------+-----------------------------+ + +------------------------------+-----------------------------+ |2.2. Energy Conservation and |3.1. Constraint-based Routing| |Optimizing Energy Consumption | | - +-------------------------------+-----------------------------+ + +------------------------------+-----------------------------+ |2.3. Moving a Remote Control |3.2. Support of Mobility | - |Around |3.5. Convergence Time | - +-------------------------------+-----------------------------+ - |2.4. Adding A New Module To The|3.5. Convergence Time | - |System |3.6. Manageability | - +-------------------------------+-----------------------------+ + |Around |3.4. Convergence Time | + +------------------------------+-----------------------------+ + |2.4. Adding A New Module To |3.4. Convergence Time | + |The System |3.5. Manageability | + +------------------------------+-----------------------------+ |2.7. Healthcare |3.1. Constraint-based Routing| | |3.2. Support of Mobility | - | |3.3. Healthcare Routing | - | |3.5. Convergence Time | - +-------------------------------+-----------------------------+ - |2.8. Alarm Systems |3.4. Scalability | - | |3.5. Convergence Time | - +-------------------------------+-----------------------------+ + | |3.4. Convergence Time | + | | | + +------------------------------+-----------------------------+ + |2.8. Alarm Systems |3.3. Scalability | + | |3.4. Convergence Time | + +------------------------------+-----------------------------+ 3.1. Constraint-based Routing For convenience and low operational costs, power consumption of consumer products must be kept at a very low level to achieve a long battery lifetime. One implication of this fact is that Random Access Memory (RAM) is limited and it may even be powered down; leaving only a few 100 bytes of RAM alive during the sleep phase. The use of battery powered devices reduces installation costs and @@ -537,94 +536,72 @@ While healthcare devices delivering measurement results can tolerate route discovery times measured in seconds, a remote control appears unresponsive if using more than 0.5 seconds to e.g. pause the music. In more rare occasions, receiving nodes may also have moved. Examples include safety-off switch in a clothes iron, a vacuum cleaner robot or the wireless chime of doorbell set. - Refer to section 3.5. for routing protocol convergence times. + Refer to section 3.4. for routing protocol convergence times. A non-responsive node can either be caused by 1) a failure in the node, 2) a failed link on the path to the node or 3) a moved node. In the first two cases, the node can be expected to reappear at roughly the same location in the network, whereas it can return anywhere in the network in the latter case. -3.3. Healthcare Routing - - Because most health care applications may run on battery, this - leads to specific requirements for the routing protocol. Most - health care applications may also be portable and therefore need - to locate a new neighbor router on a frequent basis. - Not being powered most of the time, the nodes should not be used - as routing nodes. However, battery-powered nodes may be involved - in routing. Examples include cases where a person falls during a - power blackout. In that case it may be that no mains-powered - routers are available for forwarding the alarm message to a - (battery-backed) internet gateway located out of direct range. - - Delivery of measurement data has a more relaxed requirement for - route discovery time compared to a remote control. On the other - hand, it is critical that a "person fell" alarm is actually - delivered. - - If possible at all, the routing protocol MUST deliver a health- - care related message. It is NOT a requirement that such message is - delivered in less than a second. - -3.4. Scalability +3.3. Scalability Looking at the number of wall switches, power outlets, sensors of various nature, video equipment and so on in a modern house, it seems quite realistic that hundreds of low power devices may form a home automation network in a fully populated "smart" home. Moving towards professional building automation, the number of such devices may be in the order of several thousands. The routing protocol MUST support 250 devices in the network. -3.5. Convergence Time +3.4. Convergence Time A wireless home automation network is subject to various instabilities due to signal strength variation, moving persons and the like. Measured from the transmission of a packet, the following convergence time requirements apply. The routing protocol MUST converge within 0.5 second if no nodes have moved. The routing protocol MUST converge within 4 seconds if nodes have moved. In both cases, "converge" means "the originator node has received a response from the destination node". The above-mentioned convergence time requirements apply to a home control network environment of up to 250 nodes with up to 4 repeating nodes between source and destination. -3.6. Manageability +3.5. Manageability The ability of the home network to support auto-configuration is of the utmost importance. Indeed, most end users will not have the expertise and the skills to perform advanced configuration and troubleshooting. Thus the routing protocol designed for home automation networks MUST provide a set of features including zero- configuration of the routing protocol for a new node to be added to the network. From a routing perspective, zero-configuration means that a node can obtain an address and join the network on its own, almost without human intervention. -3.7. Stability +3.6. Stability If a node is found to fail often compared to the rest of the network, this node SHOULD NOT be the first choice for routing of traffic. 4. Traffic Pattern Depending on the design philosophy of the home network, wall switches may be configured to directly control individual lamps or alternatively, all wall switches send control commands to a