draft-ietf-roll-building-routing-reqs-04.txt   draft-ietf-roll-building-routing-reqs-05.txt 
skipping to change at page 1, line 14 skipping to change at page 1, line 14
Intended status: Informational Pieter De Mil Intended status: Informational Pieter De Mil
Expires: August 3, 2009 Ghent University IBCN Expires: August 3, 2009 Ghent University IBCN
W. Vermeylen W. Vermeylen
Arts Centre Vooruit Arts Centre Vooruit
Nicolas Riou Nicolas Riou
Schneider Electric Schneider Electric
February 3, 2009 February 3, 2009
Building Automation Routing Requirements in Low Power and Lossy Building Automation Routing Requirements in Low Power and Lossy
Networks Networks
draft-ietf-roll-building-routing-reqs-04 draft-ietf-roll-building-routing-reqs-05
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 17 skipping to change at page 2, line 17
The Routing Over Low power and Lossy network (ROLL) Working Group has The Routing Over Low power and Lossy network (ROLL) Working Group has
been chartered to work on routing solutions for Low Power and Lossy been chartered to work on routing solutions for Low Power and Lossy
networks (LLN) in various markets: Industrial, Commercial (Building), networks (LLN) in various markets: Industrial, Commercial (Building),
Home and Urban. Pursuant to this effort, this document defines the Home and Urban. Pursuant to this effort, this document defines the
routing requirements for building automation. routing requirements for building automation.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119. document are to be interpreted as described in [RFC2119].
Table of Contents Table of Contents
1. Terminology....................................................4 1. Terminology....................................................4
2. Introduction...................................................4 2. Introduction...................................................4
3. Facility Management System (FMS) Topology......................5 3. Facility Management System (FMS) Topology......................5
3.1. Introduction..............................................5 3.1. Introduction..............................................5
3.2. Sensors/Actuators.........................................7 3.2. Sensors/Actuators.........................................7
3.3. Area Controllers..........................................7 3.3. Area Controllers..........................................7
3.4. Zone Controllers..........................................7 3.4. Zone Controllers..........................................7
skipping to change at page 18, line 4 skipping to change at page 18, line 4
level network wide during the commissioning phase of the system. level network wide during the commissioning phase of the system.
7.1. Security Requirements 7.1. Security Requirements
7.1.1. Authentication 7.1.1. Authentication
Authentication SHOULD be optional on the LLN. Authentication SHOULD Authentication SHOULD be optional on the LLN. Authentication SHOULD
be fully configurable on-site. Authentication policy and updates MUST be fully configurable on-site. Authentication policy and updates MUST
be routable over-the-air. Authentication SHOULD occur upon joining be routable over-the-air. Authentication SHOULD occur upon joining
or rejoining a network. However, once authenticated devices SHOULD or rejoining a network. However, once authenticated devices SHOULD
not need to reauthenticate with any other devices in the LLN. NOT need to reauthenticate with any other devices in the LLN.
Packets may need authentication at the source and destination nodes, Packets may need authentication at the source and destination nodes,
however, packets routed through intermediate hops should not need however, packets routed through intermediate hops should not need
reauthentication at each hop. reauthentication at each hop.
7.1.2. Encryption 7.1.2. Encryption
7.1.2.1. Encryption Types 7.1.2.1. Encryption Types
Data encryption of packets MUST optionally be supported by use of Data encryption of packets MUST optionally be supported by use of
either a network wide key and/or application key. The network key either a network wide key and/or application key. The network key
skipping to change at page 19, line 26 skipping to change at page 19, line 26
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
10.2. Informative References 10.2. Informative References
[1] [I-D.ietf-roll-home-routing-reqs] Brandt, A., Buron, J., and [I-D.ietf-roll-terminology] Vasseur, J., "Terminology in Low
G. Porcu, "Home Automation Routing Requirements in Low Power
and Lossy Networks", draft-ietf-roll-home-routing-reqs-06 (work
in progress), November 2008.
[2] [I-D.ietf-roll-indus-routing-reqs] Networks, D., Thubert,
P., Dwars, S., and T. Phinney, "Industrial Routing Requirements
in Low Power and Lossy Networks", draft-ietf-roll-indus-
routing-reqs-03 (work in progress), December 2008.
[3] [I-D.ietf-roll-terminology]Vasseur, J., "Terminology in Low
power And Lossy Networks", draft-ietf-roll-terminology-00 (work power And Lossy Networks", draft-ietf-roll-terminology-00 (work
in progress), October 2008. in progress), October 2008.
[4] "RS-485 EIA Standard: Standard for Electrical
Characteristics of Generators and Receivers for use in Balanced
[5] "BACnet: A Data Communication Protocol for Building and
Automation Control Networks" ANSI/ASHRAE Standard 135-2004",
2004
11. Appendix A: Additional Building Requirements 11. Appendix A: Additional Building Requirements
Appendix A contains additional building requirements that were deemed Appendix A contains additional building requirements that were deemed
out of scope for ROLL, yet provided ancillary substance for the out of scope for ROLL, yet provided ancillary substance for the
reader. reader.
11.1. Additional Commercial Product Requirements 11.1. Additional Commercial Product Requirements
11.1.1. Cost 11.1.1. Cost
 End of changes. 5 change blocks. 
20 lines changed or deleted 4 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/