idnits 2.17.00 (12 Aug 2021) /tmp/idnits911/draft-martocci-roll-building-routing-reqs-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 1064. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1041. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1048. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1054. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == Line 1147 has weird spacing: '...ination and r...' == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: It MUST be possible to fully commission devices without requiring any additional commissioning device (e.g. laptop). The device MAY be completely configured for network operation by setting a bank of switches. The number of switches MUST not exceed 16 switches. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: The total installed infrastructure cost including but not limited to the media, required infrastructure devices (amortized across the number of devices); labor to install and commission the network MUST not exceed $1.00/foot for wired implementations. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (September 3, 2008) is 5007 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Networking Working Group J. Martocci, Ed. 2 Internet-Draft Johnson Controls Inc. 3 Intended status: Informational Pieter De Mil 4 Expires: March 3, 2009 Ghent University - IBCN 5 W. Vermeylen 6 Arts Centre Vooruit 7 September 3, 2008 9 Commercial Routing Requirements in Low Power and Lossy Networks 10 draft-martocci-roll-building-routing-reqs-00 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that 15 any applicable patent or other IPR claims of which he or she is 16 aware have been or will be disclosed, and any of which he or she 17 becomes aware will be disclosed, in accordance with Section 6 of 18 BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that other 22 groups may also distribute working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html 35 This Internet-Draft will expire on March 3, 2009. 37 Copyright Notice 39 Copyright (C) The IETF Trust (2008). 41 Abstract 43 The ROLL Working Group was recently chartered by the IETF to define 44 routing characteristics for low power embedded devices. ROLL would 45 like to serve the Industrial, Commercial (Building), Home and Urban 46 markets. Pursuant to this effort, this document defines the 47 functional requirements for installing integrated facility management 48 systems in commercial facilities. The body of this document defines 49 the routing requirements for commercial building application. Other 50 commercial building requirements such as cost and installation 51 requirements have been included in Appendix A for reference. 53 Requirements Language 55 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 56 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 57 document are to be interpreted as described in RFC-2119 Error! 58 Reference source not found.. 60 Table of Contents 62 1. Terminology....................................................4 63 2. Introduction...................................................7 64 2.1. FMS Topology..............................................8 65 2.1.1. Introduction.........................................8 66 2.1.2. Sensors/Actuators....................................9 67 2.1.3. Area Controllers.....................................9 68 2.1.4. Zone Controllers.....................................9 69 2.2. Installation Methods.....................................10 70 2.2.1. Wired Communication Media...........................10 71 2.2.2. Device Density......................................10 72 3. Building Automation Applications..............................12 73 3.1. Locking and Unlocking the Building.......................12 74 3.2. Building Energy Conservation.............................13 75 3.3. Inventory and Remote Diagnosis of Safety Equipment.......13 76 3.4. Life Cycle of Smoke Detectors............................13 77 3.5. Surveillance.............................................14 78 3.6. Emergency................................................14 79 3.7. Public Address...........................................14 80 3.8. Positioning..............................................14 81 4. Building Automation Routing Requirements......................15 82 4.1. Installation.............................................15 83 4.1.1. Computer-free installation..........................15 84 4.1.2. Fixed addressing....................................15 85 4.1.3. Network Setup Time..................................16 86 4.1.4. Battery Powered devices.............................16 87 4.1.5. Local Testing.......................................16 88 4.2. Scalability..............................................16 89 4.2.1. Network Domain......................................16 90 4.2.2. Communication Distance..............................16 91 4.2.3. Automatic Gain Control..............................17 92 4.2.4. Peer-to-peer Communication..........................17 93 4.3. Mobility.................................................17 94 4.3.1. Mobile Device Association...........................17 95 4.4. Resource Constrained Devices.............................17 96 4.4.1. Cost................................................17 97 4.4.2. Limited Processing Power Sensors/Actuators..........18 98 4.4.3. Limited Processing Power Controllers................18 99 4.4.4. Parenting for Constrained Devices...................18 100 4.4.5. Adjustable System Table Sizes.......................18 101 4.5. Prioritized Routing......................................18 102 4.5.1. QoS.................................................18 103 4.6. Addressing...............................................19 104 4.6.1. Unicast/Multicast/Anycast...........................19 105 4.6.2. Unique Addresses....................................19 106 4.7. Manageability............................................19 107 4.7.1. Device Replacement..................................19 108 4.7.2. Firmware Upgrades...................................19 109 4.7.3. Diagnostics.........................................20 110 4.7.4. Trace Route.........................................20 111 4.8. Compatibility............................................20 112 4.8.1. IPv4 Compatibility..................................20 113 4.8.2. Maximum Packet Size.................................20 114 4.9. Route Selection..........................................20 115 4.9.1. Path Cost...........................................21 116 4.9.2. Path Adaptation.....................................21 117 4.9.3. Route Redundancy....................................21 118 4.9.4. Route Preference....................................21 119 4.9.5. Path Symmetry.......................................21 120 4.9.6. Path Persistence....................................21 121 4.10. Reliability.............................................22 122 4.10.1. Device Integrity...................................22 123 5. Traffic Pattern...............................................22 124 6. Open issues...................................................22 125 7. Security Considerations.......................................23 126 8. IANA Considerations...........................................23 127 9. Acknowledgments...............................................23 128 10. References...................................................23 129 10.1. Normative References....................................23 130 10.2. Informative References..................................24 131 Disclaimer of Validity...........................................25 132 11. APPENDIX A - Additional Building Requirements (Informative)..26 133 11.1. Additional Commercial Product Requirements..............26 134 11.1.1. Wired and Wireless Imlementations..................26 135 11.1.2. World-wide Applicability...........................26 136 11.1.3. Support of Building Protocol - BACnet..............27 137 11.1.4. Support of Building Protocol - LON.................27 138 11.1.5. Energy Harvested Sensors...........................27 139 11.2. Additional Installation and Commissioning Requirements..27 140 11.2.1. Device Setup Time..................................27 141 11.2.2. Unavailability of an IT network....................27 142 11.3. Additional Network Requirements.........................27 143 11.3.1. TCP/UDP............................................27 144 11.3.2. Data Rate Performance..............................27 145 11.3.3. Interference Mitigation............................28 146 11.3.4. Real-time Performance Measures.....................28 147 11.3.5. Packet Reliability.................................28 149 1. Terminology 151 Access Point: The access point is an infrastructure device that 152 connects the low power and lossy network system to the 153 Internet, possibly via a customer premises local area 154 network (LAN). 156 Actuator: A field device that controls and/or modulates a flow 157 of a gas or liquid; or controls electricity 158 distribution. 160 ASHRAE: American Society of Heating, Refrigerating and Air- 161 Conditioning Engineers 163 BAS: Building Automation System. This term is synonymous 164 with Facility Management System (FMS). 166 BMS: Building Automation System. This term is synonymous 167 with Facility Management System (FMS). 169 Channel: Radio frequency sub-band used to transmit a modulated 170 signal carrying packets. 172 Channel Hopping An algorithm by which field devices synchronously 173 change channels during operation 175 Commissioning Tool: Any physical or logical device temporarily added 176 to the network for the expressed purpose of setting up 177 the network and device operational parameters. 179 Controller: A field device that can receive sensor input and 180 automatically change the environment in the facility 181 by manipulating digital or analog actuators. 183 Downstream: Data direction traveling from a Local Area Network 184 (LAN) to a Personal Area Network (PAN) device. 186 Field Device: Physical devices placed in the plant's operating 187 environment (both RF and environmental). Field 188 devices include sensors and actuators as well as 189 network routing devices and access points 191 Fire: The term used to describe building equipment used to 192 monitor, control and evacuate an internal space in 193 case of a fire situation. Equipment includes smoke 194 detectors, pull boxes, sprinkler systems and 195 evacuation control. 197 FFD: Full Function Device. An 802.15.4 device that can 198 route messages across the mesh in addition to 199 providing an end application. Most FFD are line 200 powered since they must always be ready to forward 201 messages. 203 FMS: Facility Management System. A global term applied 204 across all the vertical designations within a building 205 including, HVAC, Fire, Security, Lighting and Elevator 206 control. 208 HVAC: Heating, Ventilation and Air Conditioning. A term 209 applied to the comfort level of an internal space. 211 IETF: Internet Engineering Task Force 213 Intrusion Protection: A term used to protect resources from 214 external infiltration. Intrusion protection systems 215 utilize door locks, window tampers and card readers. 217 LAN: Local Area Network. 219 PAN: Personal Area Network. 220 A geographically limited wireless network based on 221 e.g. 802.15.4 or Z-Wave radio. 223 ROLL: Routing Over Low-power and Lossy networks 224 ROLL device: A ROLL network node with constrained CPU and memory 225 resources; potentially constrained power resources. 227 Sensor: A PAN device that measures data and/or detects an 228 event. 230 Upstream: Data direction traveling from a PAN to a LAN device. 232 LLN: Low power and Lossy networks (LLNs) are typically 233 composed of many embedded devices with limited power, 234 memory, and processing resources interconnected by a 235 variety of links, such as IEEE 802.15.4, Bluetooth, 236 Low Power WiFi 238 Lighting: The term used to describe building equipment used to 239 monitor and control an internal or external lighted 240 space. Equipment includes occupancy sensors, light 241 switches and ballasts. 243 LLN: Low power and Lossy Network. 245 PAN: Personnel Area Network 247 RF: Radio Frequency 249 RFD: Reduced Function Device. An 802.15.4 device that can 250 send messages on the network; receive messages from 251 the network; but cannot route messages across the 252 network. In most cases these devices are edge devices 253 of the network.. RFDs may be line powered, but also 254 can be battery powered since they play no role on the 255 mesh. 257 ROLL: Routing over Low power and Lossy networks. This IETF 258 working group will develop routing characteristics and 259 rules for supporting LLNs utilizing 6LoWPAN. 261 Security: The term used to describe building equipment used to 262 monitor and control occupant and equipment safety 263 inside a building. Equipment includes window tamper 264 switches, door access systems, infrared detection 265 systems, and video cameras. 267 Sensors: A field device that monitors an environmental 268 condition in a building and reports its findings to 269 higher order devices for control and alarming 270 operations. 272 Superframe: A collection of timeslots repeating at a constant 273 rate. 275 TC: Trust Center. A logical device on the network that is 276 trusted by the network members. The TC administers 277 security policy. 279 Timeslot: A fixed time interval that may be used for the 280 transmission or reception of a packet between two 281 field devices. A timeslot used for communications is 282 associated with a slotted-link 284 Upstream: Data direction travelling from the field device to the 285 host application. 287 2. Introduction 289 Commercial buildings have been fitted with pneumatic and subsequently 290 electronic communication pathways connecting sensors to their 291 controllers for over one hundred years. Recent economic and 292 technical advances in wireless communication allow facilities to 293 increasingly utilize a wireless solution in lieu of a wired solution; 294 thereby reducing installation costs while maintaining highly reliant 295 communication. Wireless solutions will be adapted from their 296 existing wired counterparts in many of the building applications 297 including, but not limited to HVAC, Lighting, Physical Security, 298 Fire, and Elevator systems. These devices will be developed to 299 reduce installation costs; while increasing installation and retrofit 300 flexibility. Sensing devices may be battery or mains powered. 301 Actuators and area controllers will be mains powered. 303 Facility Management Systems (FMS) are deployed in a large set of 304 vertical markets including universities; hospitals; government 305 facilities; K-12; pharmaceutical manufacturing facilities; and 306 single-tenant or multi-tenant office buildings. These buildings range 307 in size from 100K sqft structures (5 story office buildings), to 1M 308 sqft skyscrapers (100 story skyscrapers) to complex government 309 facilities such as the Pentagon. The described topology is meant to 310 be the model to be used in all these types of environments, but 311 clearly must be tailored to the building class, building tenant and 312 vertical market being served. 314 The following sections describe the sensor, actuator, area controller 315 and zone controller layers of the topology. (NOTE: The Building 316 Controller and Enterprise layers of the FMS are excluded from this 317 discussion since they typically deal in communication rates requiring 318 WLAN communication technologies. Each section describes the basic 319 functionality of the layer, its networking model, power requirements 320 and a brief description of the communication requirements. 322 2.1. FMS Topology 324 2.1.1. Introduction 326 To understand the network systems requirements of a facility 327 management system in a commercial building, this document uses a 328 framework to describe the basic functions and composition of the 329 system. An FMS is a horizontally layered system of sensors, 330 actuators, controllers and user interface devices. Additionally, an 331 FMS may also be divided vertically across alike, but different 332 building subsystems such as HVAC, Fire, Security, Lighting, Shutters 333 and Elevator control systems as denoted in Figure 1. 335 Much of the makeup of an FMS is optional and installed at the behest 336 of the customer. Sensors and actuators have no standalone 337 functionality. All other devices support partial or complete 338 standalone functionality. These devices can optionally be tethered 339 to form a more cohesive system. The customer requirements dictate 340 the level of integration within the facility. This architecture 341 provides excellent fault tolerance since each node is designed to 342 operate in an independent mode if the higher layers are unavailable. 344 +------+ +-----+ +------+ +------+ +------+ +------+ 346 Bldg App'ns | | | | | | | | | | | | 348 | | | | | | | | | | | | 350 Building Cntl | | | | | S | | L | | S | | E | 352 | | | | | E | | I | | H | | L | 354 Area Control | H | | F | | C | | G | | U | | E | 356 | V | | I | | U | | H | | T | | V | 358 Zone Control | A | | R | | R | | T | | T | | A | 359 | C | | E | | I | | I | | E | | T | 361 Actuators | | | | | T | | N | | R | | O | 363 | | | | | Y | | G | | S | | R | 365 Sensors | | | | | | | | | | | | 367 +------+ +-----+ +------+ +------+ +------+ +------+ 369 Figure 1 - Building Systems and Devices 371 2.1.2. Sensors/Actuators 373 As Figure 1 indicates an FMS may be composed of many functional 374 stacks or silos that are interoperably woven together via Building 375 Applications. Each silo has an array of sensors that monitor the 376 environment and actuators that effect the environment as determined 377 by the upper layers of the FMS topology. The sensors typically are 378 the leaves of the network tree structure providing environmental data 379 into the system. The actuators are the sensors counterparts 380 modifying the characteristics of the system based on the input sensor 381 data and the applications deployed. 383 2.1.3. Area Controllers 385 An area describes a small physical locale within a building, 386 typically a room. As noted in Figure 1 the HVAC, Security and 387 Lighting functions within a building address area or room level 388 applications. Area controls are fed by sensor inputs that monitor 389 the environmental conditions within the room. Common sensors found 390 in many rooms that feed the area controllers include temperature, 391 occupancy, lighting load, solar load and relative humidity. Sensors 392 found in specialized rooms (such as chemistry labs) might include air 393 flow, pressure, CO2 and CO particle sensors. Room actuation includes 394 temperature setpoint, lights and blinds/curtains. 396 2.1.4. Zone Controllers 398 Zone Control supports a similar set of characteristics as the Area 399 Control albeit to an extended space. A zone is normally a logical 400 grouping or functional division of a commercial building. A zone may 401 also coincidentally map to a physical locale such as a floor. 403 Zone Control may have direct sensor inputs (smoke detectors for 404 fire), controller inputs (room controllers for air-handlers in HVAC) 405 or both (door controllers and tamper sensors for security). Like 406 area/room controllers, zone controllers are standalone devices that 407 operate independently or may be attached to the larger network for 408 more synergistic control. 410 2.2. Installation Methods 412 2.2.1. Wired Communication Media 414 Commercial controllers are traditionally deployed in a facility using 415 twisted pair serial media following the EIA 485 electrical standard 416 operating nominally at 38400 to 76800 baud. This allows runs to 5000 417 ft without a repeater. With the maximum of three repeaters, a single 418 communication trunk can serpentine 15000 ft. 420 Most sensors and virtually all actuators currently used in commercial 421 buildings are "dumb", non-communicating hardwired devices. However, 422 sensor buses are beginning to be deployed by vendors which are used 423 for smart sensors and point multiplexing. The Fire industry deploys 424 addressable fire devices, which usually use some form of proprietary 425 communication wiring driven by fire codes. 427 2.2.2. Device Density 429 Device density differs depending on the application and code 430 requirements. The following sections detail typical installation 431 densities for different applications. 433 2.2.2.1. HVAC Device Density 435 HVAC room applications typically have sensors and controllers spaced 436 about 50ft apart. In most cases there is a 3:1 ratio of sensors to 437 controllers. That is, for each room there is an installed 438 temperature sensor, flow sensor and damper controller for the 439 associated room controller. 441 HVAC equipment room applications are quite different. An air handler 442 system may have a single controller with upwards to 25 sensors and 443 actuators within 50 ft of the air handler. A chiller or boiler is 444 also controlled with a single equipment controller instrumented with 445 25 sensors and actuators. Each of these devices would be 446 individually addressed. Air handlers typically serve one or two 447 floors of the building. Chillers and boilers may be installed per 448 floor, but many times service a wing, building or the entire complex 449 via a central plant. 451 These numbers are typical. In special cases, such as clean rooms, 452 operating rooms, pharmaceuticals and labs, the ratio of sensors to 453 controllers can increase by a factor of three. Tenant installations 454 such as malls would opt for packaged units where much of the sensing 455 and actuation is integrated into the unit. Here a single device 456 address would serve the entire unit. 458 2.2.2.2. Fire Device Density 460 Fire systems are much more uniformly installed with smoke detectors 461 installed about every 50 feet. This is dictated by local building 462 codes. Fire pull boxes are installed uniformly about every 150 feet. 463 A fire controller will service a floor or wing. The fireman's fire 464 panel will service the entire building and typically is installed in 465 the atrium. 467 2.2.2.3. Lighting Device Density 469 Lighting is also very uniformly installed with ballasts installed 470 approximately every 10 feet. A lighting panel typically serves 48 to 471 64 zones. Wired systems typically tether many lights together into a 472 single zone. Wireless systems configure each fixture independently 473 to increase flexibility and reduce installation costs. 475 2.2.2.4. Physical Security Device Density 477 Security systems are non-uniformly oriented with heavy density near 478 doors and windows and lighter density in the building interior space. 479 The recent influx of interior and perimeter camera systems is 480 increasing the security footprint. These cameras are atypical 481 endpoints requiring upwards to 1mbps data rates per camera as 482 contrasted by the few kbps needed by most other FMS sensing 483 equipment. To date, camera systems have been deployed on a 484 proprietary wired high speed network or on enterprise VLAN. Camera 485 compression technology now supports full-frame video over wireless 486 media. 488 2.2.2.5. Installation Procedure 490 Wired FMS installation is a multifaceted procedure depending on the 491 extent of the system and the software interoperability requirement. 492 However, at the sensor/actuator and controller level, the procedure 493 is typically a two or three step process. 495 Most FMS equipment is 24 VAC equipment that can be installed by a 496 low-voltage electrician. He/she arrives on-site during the 497 construction of the building prior to the sheet wall and ceiling 498 installation. This allows him/her to allocate wall space, easily 499 land the equipment and run the wired controller and sensor networks. 500 The Building Controllers and Enterprise network are not normally 501 installed until months later. The electrician completes his task by 502 running a wire verification procedure that shows proper continuity 503 between the devices and proper local operation of the devices. 505 Later in the installation cycle, the higher order controllers are 506 installed, programmed and commissioned together with the previously 507 installed sensors, actuators and controllers. In most cases the IP 508 network is still not operable. The Building Controllers are 509 completely commissioned using a crossover cable or a temporary IP 510 switch together with static IP addresses. 512 Once the IP network is operational, the FMS may optionally be added 513 to the enterprise network. Wireless installation will necessarily 514 need to keep the same work flow. The electrician will install the 515 products as before and run continuity tests between the wireless 516 devices to assure operation before leaving the job. The electrician 517 does not carry a laptop so the commissioning must be built into the 518 device operation. 520 3. Building Automation Applications 522 Vooruit is an arts centre in a restored monument which dates from 523 1913. This complex monument consists of 366 different rooms 524 including a concert hall, theater hall, several bars, etc. About 525 2000 activities take place at Vooruit on a yearly basis, some 526 activities simultaneously with a total maximum of 3500 visitors. A 527 number of use cases regarding Vooruit are described in the following 528 text. The situations and needs described in these use cases can also 529 be found in all automated large buildings, such as airports and 530 hospitals. 532 3.1. Locking and Unlocking the Building 534 The member of the cleaning staff arrives first in the morning 535 unlocking the building (or a part of it) from the control room. This 536 means that several doors are unlocked; the alarms are switched off; 537 the heating turns on; some lights switch on, etc. Similarly, the 538 last person leaving the building has to lock the building. This will 539 lock all the outer doors, turn the alarms on, switch off heating and 540 lights, etc. 542 This use case is also useful in the home automation scenario, 543 although the requirement about preventing the "popcorn effect" [REF 544 HOME AUTOMATION] can be relaxed a little bit in building automation. 545 It would be nice if lights, roll-down shutters and other actuators in 546 the same room or areas with transparent walls execute the command 547 around the same time (a tolerance of 200 ms is allowed). 549 3.2. Building Energy Conservation 551 A room that is not in use should not be heated, air conditioned or 552 ventilated and the lighting should be turned off. In a building with 553 366 rooms it can happen quite frequently that someone forgets to 554 switch off the HVAC and lighting. This is a real waste of valuable 555 energy. To prevent this from happening, the janitor can program the 556 building according to the day's schedule. This way lighting and HVAC 557 is turned on prior to the use of a room, and turned off afterwards. 558 Using such a system Vooruit has realized a saving of 35% on the gas 559 and electricity bills. Making the control of the building management 560 system wireless (e.g. over a PDA) would be an advantage as you do not 561 have to cross the complete building to the control room to change the 562 temperature of a single room. 564 3.3. Inventory and Remote Diagnosis of Safety Equipment 566 Each month Vooruit is obliged to make an inventory of its safety 567 equipment. This task takes two working days. Each fire extinguisher 568 (100), fire blanket (10), fire-resisted door (120) and evacuation 569 plan (80) must be checked for presence and proper operation. Also 570 the battery and lamp of every safety lamp must be checked before each 571 public event (safety laws). Automating this process would heavily 572 cut into working hours. 574 3.4. Life Cycle of Smoke Detectors 576 A smoke detector must be replaced periodically. A secure mechanism 577 is needed to remove the old device and install the new device. 578 During construction work, the safety can be augmented by temporarily 579 adding extra sensing and/or actuating devices. 581 This life cycle management use case is valid for each type of device 582 we wish to add or to replace. What is the maximum of the time we 583 allow for each task (adding a new device, removal of a device, 584 replacement of a device)? The negative impact on the functionality 585 of the network should be minimal. 587 3.5. Surveillance 589 To protect the building against burglary a guard must be able to 590 monitor and control all entrances (open/close, latch moved) and 591 lights (activated outside the opening hours). It should also be 592 possible to view video streams from several security cameras either 593 from the control room or on a PDA of an in-the-field security person. 594 The arriving and exiting visitors also must be monitored from the 595 control room to guarantee their security. 597 3.6. Emergency 599 In case of an emergency it is very important that all the visitors be 600 evacuated as quickly as possible. The fire and smoke detectors have 601 to set off an alarm, and alert the mobile personnel on their internal 602 mobile telephone system and/or PDAs. All emergency exits have to be 603 instantly unlocked and the emergency lighting has to guide the 604 visitors to these exits. The necessary sprinklers have to be 605 activated and the electricity grid has to be monitored and if it 606 becomes necessary to shut down some parts of the building. Emergency 607 services have to be notified instantly. A wireless system could 608 bring in some extra safety features. Locating fire fighters and 609 guiding them through the building could be a life-saving application. 610 This is also the case for wireless camera surveillance which is 611 monitored via PDA. 613 3.7. Public Address 615 It should be possible to send video, audio and text messages to the 616 visitors in the building. These messages can be very diverse, e.g. 617 commercials on televisions in the bar, ASCII text boards displaying 618 the name of the event in a room, video screens with an outline of the 619 upcoming events at Vooruit, audio announcements such as delays in the 620 program, lost and found children, evacuation orders, etc. 622 3.8. Positioning 624 Person localization / equipment theft: 2s - room accuracy required - 625 high responsiveness required to cope with movement Interaction 626 positioning: detect vicinity of two nodes (people or equipment): 1s - 627 sub-room accuracy - high responsiveness required to cope with 628 movement Equipment localization: 2-4s Or Asset Management - room 629 accuracy required - medium responsiveness. 631 4. Building Automation Routing Requirements 633 Following are the building automation routing requirements for a 634 network used to integrate building sensor actuator and control 635 products. These requirements have been limited to 'routing' 636 requirements only. These requirements are written not presuming any 637 preordained network topology, physical media (wired) or radio 638 technology (wireless). See Appendix A for additional requirements 639 that have been deemed outside the scope of this document yet will 640 pertain to the successful deployment of building automation systems. 642 4.1. Installation 644 Building control systems typically are installed and tested by 645 electricians having little computer knowledge and no network 646 knowledge whatsoever. These systems are often installed during the 647 building construction phase before the drywall and ceilings are in 648 place. There is never an IP network in place during this 649 installation. 651 In retrofit applications, pulling wires from sensors to controllers 652 can be costly and in some applications (e.g. museums) not feasible. 654 Local testing of sensors and room controllers must be completed 655 before the tradesperson can complete his/her work. System level 656 commissioning will later be deployed using a more computer savvy 657 person with access to a laptop computer. The completely installed 658 and commissioned IP network may or may not be in place at this time. 659 Following are the installation routing requirements. 661 4.1.1. Computer-free installation 663 It MUST be possible to fully commission devices without requiring any 664 additional commissioning device (e.g. laptop). The device MAY be 665 completely configured for network operation by setting a bank of 666 switches. The number of switches MUST not exceed 16 switches. 668 4.1.2. Fixed addressing 670 The device network address MUST be settable and henceforth fixed for 671 the device without the need for other system devices such as DHCP 672 servers. 674 4.1.3. Network Setup Time 676 Network setup MUST support device commissioning times of no more than 677 15 minutes per sensor/controller pair. 679 4.1.4. Battery Powered devices 681 Sensing devices must be able to utilize battery power yet still be 682 viable devices on a ROLL network. Batteries must be operational for 683 at least 5 years when the sensing device is transmitting its data (64 684 bytes) once per minute. 686 4.1.5. Local Testing 688 The local sensors and requisite actuators and controllers must be 689 testable within the locale (e.g. room) to assure communication 690 connectivity and local operation. 692 4.2. Scalability 694 Building control systems are designed for facilities from 50000 sq. 695 ft. to 1M+ sq. ft. The networks that support these systems must 696 cost-effectively scale accordingly. In larger facilities 697 installation may occur simultaneously on various wings or floors, yet 698 the end system must seamlessly merge. Following are the scalability 699 requirements. 701 4.2.1. Network Domain 703 A network MUST operationally support at least 1000 routing and 1000 704 non-routing devices. 706 Subnetworks (e.g. rooms, primary equipment) within the network must 707 support upwards to 255 sensors and/or actuators. 709 Subnetworks MUST seamlessly merge into networks. Networks MUST 710 seamlessly merge into internetworks. 712 4.2.2. Communication Distance 714 A source device may be upwards to 1000 feet from its destination. 715 Communication MUST be established between these devices without 716 needing to install other intermediate 'communication only' devices 717 such as repeaters. 719 4.2.3. Automatic Gain Control 721 For wireless implementations, the routing algorithms SHOULD 722 incorporate automatic transmit power regulation to maximize packet 723 transfer and minimize network interference regardless of network size 724 or density. 726 4.2.4. Peer-to-peer Communication 728 Network devices MUST be able to communicate in a peer-to-peer manner 729 with all other devices on the network without being subject to 730 intermediate bridge or gating devices. 732 4.3. Mobility 734 Most devices are affixed to walls or installed on ceilings within 735 buildings. Hence the mobility requirements for commercial buildings 736 are few. However, in wireless environments location tracking of 737 occupants and assets is gaining favor. 739 4.3.1. Mobile Device Association 741 Mobile devices SHOULD be capable of unjoining from an old network 742 joining onto a new network within 15 seconds. 744 4.4. Resource Constrained Devices 746 Sensing and actuator device processing power and memory may be 4 747 orders of magnitude less (i.e. 10,000x) than many more traditional 748 client devices on an IP network. The routing algorithms must 749 therefore be tailored to fit these resource constrained devices. 751 4.4.1. Cost 753 The total installed infrastructure cost including but not limited to 754 the media, required infrastructure devices (amortized across the 755 number of devices); labor to install and commission the network MUST 756 not exceed $1.00/foot for wired implementations. 758 Wireless implementations (total installed cost) must cost no more 759 than 80% of wired implementations. 761 4.4.2. Limited Processing Power Sensors/Actuators 763 The software stack requirements for sensors and actuators MUST be 764 implementable in 8-bit devices with no more than 128kb of flash 765 memory (including at least 32Kb for the application code) and no more 766 than 8Kb of RAM (including at least 1Kb RAM available for 767 application). 769 4.4.3. Limited Processing Power Controllers 771 The software stack requirements for room controllers SHOULD be 772 implementable in 8-bit devices with no more than 256kb of flash 773 memory (including at least 32Kb for the application code) and no more 774 than 8Kb of RAM (including at least 1Kb RAM available for 775 application) 777 4.4.4. Parenting for Constrained Devices 779 The routing algorithms must support in-bound packet caches for sensor 780 and actuator devices when these devices are not accessible on the 781 network. The cached packets need to be delivered to its destination 782 when the device is accessible on the network. 784 4.4.5. Adjustable System Table Sizes 786 ROLL routing MUST support adjustable router table entry sizes on a 787 per node basis to maximize limited RAM in the devices. 789 4.5. Prioritized Routing 791 Network and application routing prioritization is required to assure 792 that mission critical applications (e.g. Fire Detection) cannot be 793 deferred while less critical application access the network. 795 4.5.1. QoS 797 Routers MUST support quality of service prioritization to assure 798 timely response for critical FMS packets (e.g. Fire and Security 799 events). 801 4.6. Addressing 803 Facility Management systems require different communication schema to 804 solicit or post network information. Broadcasts or anycasts need be 805 used to resolve unresolved references within a device when the device 806 first joins the network. Devices operating within a specified locale 807 such as a room will need to multicast to all devices within the room. 809 4.6.1. Unicast/Multicast/Anycast 811 Routing MUST support anycast, unicast, multicast and broadcast 812 services (or IPv6 equivalent). 814 4.6.2. Unique Addresses 816 Sensor/Actuator/Controller addressability MUST be unique site-wide. 817 All addressable nodes MUST be accessible to all other nodes in the 818 internetwork. 820 4.7. Manageability 822 In addition to the initial installation of the system (see Section 823 4.1), the ongoing maintenance of the system is equally important to 824 be simple and inexpensive. 826 4.7.1. Device Replacement 828 Replacement devices must be plug-n-play with no additional setup than 829 what is normally required for a new device. No bound information 830 from other nodes MUST need be reconfigured. 832 4.7.2. Firmware Upgrades 834 To support high speed code downloads, a mechanism MUST be defined to 835 download firmware to devices in parallel yet support guaranteed 836 delivery. Devices receiving a high speed download MAY cease normal 837 operation, but upon completion of the download MUST automatically 838 resume normal operation. 840 4.7.3. Diagnostics 842 To improve diagnostics, the network layer SHOULD be able to be placed 843 in and out of 'verbose' mode. Verbose mode is a temporary debugging 844 mode that provides additional communication information including at 845 least total number of packets sent, packets received, number of 846 failed communication attempts, neighbor table and routing table 847 entries. 849 4.7.4. Trace Route 851 Network diagnostics such as PING and Trace Route SHOULD be supported 852 with extensions in Trace Route describing wireless parameter 853 information when applicable. 855 4.8. Compatibility 857 The building automation industry adheres to application layer 858 protocol standards to achieve vendor interoperability. These 859 standards are BACnet and LON. It is estimated that fully 80% of the 860 customer bid requests received world-wide will require compliance to 861 one or both of these standards. The ROLL routing algorithms will 862 therefore need to dovetail to these application protocols to assure 863 acceptance in the building automation industry. These protocols have 864 been in place for over 10 years. Many sites will require backwards 865 compatibility with the existing legacy devices. 867 4.8.1. IPv4 Compatibility 869 The routing protocol MUST define a communication scheme to assure 870 compatibility of IPv4 and IPv6 devices. 872 4.8.2. Maximum Packet Size 874 Routing algorithms must support packet sizes to 1526 octets. 876 4.9. Route Selection 878 Route selection determines reliability and quality of the 879 communication paths among the devices. Optimizing the routes over 880 time resolve any nuances developed at system startup when nodes are 881 asynchronously adding themselves to the network. Route adaptation 882 also reduces latency if the new route costs consider hop count as a 883 cost attribute. 885 4.9.1. Path Cost 887 Path selection MUST be based on path quality, rather than signal 888 strength only. Path quality includes signal strength, available 889 bandwidth, hop count and communication error rates. 891 4.9.2. Path Adaptation 893 Communication paths MUST adapt toward signal quality optimality in 894 time. 896 4.9.3. Route Redundancy 898 To reduce real-time latency, the network layer SHOULD be configurable 899 to allow secondary and tertiary paths to be established and used upon 900 failure of the primary path 902 4.9.4. Route Preference 904 The route discovery mechanism SHOULD allow a source node (sensor) to 905 dictate a configured destination node (controller) as a preferred 906 routing path. 908 4.9.5. Path Symmetry 910 The network layer SHOULD support both asymmetric and symmetric routes 911 as requested by the application layer. When the application layer 912 selects asymmetry the network layer MAY elect to find either 913 asymmetric or symmetric routes. When the application layer requests 914 symmetric routes, then only symmetric routes MUST be utilized. The 915 default MUST be asymmetric routes. 917 4.9.6. Path Persistence 919 Devices SHOULD optionally persist communication paths across boots 921 4.10. Reliability 923 4.10.1. Device Integrity 925 Commercial Building devices MUST all be periodically scanned to 926 assure that the device is viable and can communicate data and alarm 927 information as needed. 929 5. Traffic Pattern 931 The independent nature of the automation systems within a building 932 plays heavy onto the network traffic patterns. Much of the real-time 933 sensor data stays within the local environment. Alarming and other 934 event data will percolate to higher layers. 936 Systemic data may be either polled or event based. Polled data 937 systems will generate a uniform packet load on the network. This 938 architecture has proven not scalable. Most vendors have developed 939 event based systems which passes data on event. These systems are 940 highly scalable and generate low data on the network at quiescence. 941 Unfortunately, the systems will generate a heavy load on startup 942 since all the initial data must migrate to the controller level. 943 They also will generate a temporary but heavy load during firmware 944 upgrades. This latter load can normally be mitigated by performing 945 these downloads during off-peak hours. 947 Devices will need to reference peers occasionally for sensor data or 948 to coordinate across systems. Normally, though, data will migrate 949 from the sensor level upwards through the local, area then 950 supervisory level. Bottlenecks will typically form at the funnel 951 point from the area controllers to the supervisory controllers. 953 6. Open issues 955 Other items to be addressed in further revisions of this document 956 include: 958 Need to complete the Acknowledgement section below and develop 959 Reference and Normative Reference sections. 961 7. Security Considerations 963 Security policies, especially wireless encryption and overall device 964 authentication need to be considered. These issues are out of scope 965 for the routing requirements, but could have an impact on the 966 processing capabilities of the sensors and controllers. 968 As noted above, the FMS systems are typically highly configurable in 969 the field and hence the security policy is most often dictated by the 970 type of building to which the FMS is being installed. 972 8. IANA Considerations 974 This document includes no request to IANA. 976 9. Acknowledgments 978 J. P. Vasseur, Ted Humpal and Zach Shelby are gratefully acknowledged 979 for their contributions to this document. 981 This document was prepared using 2-Word-v2.0.template.dot. 983 10. References 985 TBD 987 10.1. Normative References 989 TBD 991 10.2. Informative References 993 Authors' Addresses 995 Jerry Martocci 996 Johnson Control 997 507 E. Michigan Street 998 Milwaukee, Wisconsin, 53202 999 USA 1001 Phone: 414.524.4010 1002 Email: jerald.p.martocci@jci.com 1004 Nicolas Riou 1005 ? 1006 ? 1007 ? 1009 Phone: ? 1010 Email: nicolas.riou@fr.schneider-electric.com 1012 Pieter De Mil 1013 Ghent University - IBCN 1014 G. Crommenlaan 8 bus 201 1015 Ghent 9050 1016 Belgium 1018 Phone: +32-9331-4981 1019 Fax: +32--9331--4899 1020 Email: pieter.demil@intec.ugent.be 1022 Wouter Vermeylen 1023 Arts Centre Vooruit 1024 ??? 1025 Ghent 9000 1026 Belgium 1028 Phone: ??? 1029 Fax: ??? 1030 Email: wouter@vooruit.be 1032 Intellectual Property Statement 1034 The IETF takes no position regarding the validity or scope of any 1035 Intellectual Property Rights or other rights that might be claimed to 1036 pertain to the implementation or use of the technology described in 1037 this document or the extent to which any license under such rights 1038 might or might not be available; nor does it represent that it has 1039 made any independent effort to identify any such rights. Information 1040 on the procedures with respect to rights in RFC documents can be 1041 found in BCP 78 and BCP 79. 1043 Copies of IPR disclosures made to the IETF Secretariat and any 1044 assurances of licenses to be made available, or the result of an 1045 attempt made to obtain a general license or permission for the use of 1046 such proprietary rights by implementers or users of this 1047 specification can be obtained from the IETF on-line IPR repository at 1048 http://www.ietf.org/ipr. 1050 The IETF invites any interested party to bring to its attention any 1051 copyrights, patents or patent applications, or other proprietary 1052 rights that may cover technology that may be required to implement 1053 this standard. Please address the information to the IETF at 1054 ietf-ipr@ietf.org. 1056 Disclaimer of Validity 1058 This document and the information contained herein are provided on an 1059 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1060 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 1061 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 1062 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1063 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1064 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1066 Copyright Statement 1068 Copyright (C) The IETF Trust (2008). 1070 This document is subject to the rights, licenses and restrictions 1071 contained in BCP 78, and except as set forth therein, the authors 1072 retain all their rights. 1074 Acknowledgment 1076 Funding for the RFC Editor function is currently provided by the 1077 Internet Society. 1079 11. APPENDIX A - Additional Building Requirements (Informative) 1081 Appendix A contains additional building requirements that were deemed 1082 out of scope for the routing document yet provided ancillary 1083 informational substance to the reader. The requirements will need to 1084 be addressed by ROLL or other WGs before adoption by the building 1085 automation industrial will be considered. 1087 11.1. Additional Commercial Product Requirements 1089 11.1.1. Wired and Wireless Imlementations 1091 Solutions MUST support both wired and wireless implementations. 1093 11.1.2. World-wide Applicability 1095 Wireless devices MUST be supportable at the 2.4Ghz ISM band Wireless 1096 devices SHOULD be supportable at the 900 and 868 ISM bands as well. 1098 11.1.3. Support of Building Protocol - BACnet 1100 Devices implementing the ROLL features MUST be able to support the 1101 BACnet protocol. 1103 11.1.4. Support of Building Protocol - LON 1105 Devices implementing the ROLL features MUST be able to support the 1106 LON protocol. 1108 11.1.5. Energy Harvested Sensors 1110 RFDs SHOULD target for operation using viable energy harvesting 1111 techniques such as ambient light, mechanical action, solar load, air 1112 pressure and differential temperature. 1114 11.2. Additional Installation and Commissioning Requirements 1116 11.2.1. Device Setup Time 1118 Network setup by the installer MUST take no longer than 20 seconds 1119 per device installed. 1121 11.2.2. Unavailability of an IT network 1123 Product commissioning MUST be performed by an application engineer 1124 prior to the installation of the IT network. 1126 11.3. Additional Network Requirements 1128 11.3.1. TCP/UDP 1130 Connection based and connectionless services MUST be supported 1132 11.3.2. Data Rate Performance 1134 An effective data rate of 20kbps is the lowest acceptable operational 1135 data rate acceptable on the network. 1137 11.3.3. Interference Mitigation 1139 The network MUST automatically detect interference and migrate the 1140 network to a better 802.15.4 channel to improve communication. 1141 Channel changes and nodes response to the channel change MUST occur 1142 within 60 seconds. 1144 11.3.4. Real-time Performance Measures 1146 A node transmitting a 'request with expected reply' to another node 1147 MUST send the message to the destination and receive the response 1148 in not more than 120 msec. This response time SHOULD be achievable 1149 with 5 or less hops in each direction.This requirement assumes 1150 network quiescence and a negligible turnaround time at the 1151 destination node. 1153 11.3.5. Packet Reliability 1155 Reliability MUST meet the following minimum criteria : 1157 < 1% MAC layer errors on all messages; After no more than three 1158 retries 1160 < .1% Network layer errors on all messages; 1162 After no more than three additional retries; 1164 < 0.01% App?n layer errors on all messages. 1166 Therefore application layer messages will fail no more than once 1167 every 100,000 messages.