Minutes - Security Industry Association

SIA Standards
Kickoff Meeting – Intrusion Subcommittee
Wednesday, October 5, 2011 – 3PM ET
Draft Minutes
1. Call to Order and Opening Remarks
The meeting was called to order at 3:02 PM. Mr. Nesse thanked participants for joining
the call and requested we do a roll call before proceeding to Mr. Van Till’s opening
remarks.
Mr. Van Till addressed the group and gave a description of the landscape that we are
working in. He talked about SIA’s harmonization efforts and how SIA plans to
collaborate with other standards/specification bodies and the new Roadmap. He
stressed participation from business leaders in getting their engineers involved, and
using the working group as a forum to drive work products along.
2. Roll Call
A complete list of attendees is included as Attachment A.
3. Approval of Draft Agenda
Mr. Nesse asked for a motion to approve the draft agenda as structured
L. Dischert/K. Harris
Motion Passes with Unanimous consent.
4. Committee Overview
a. Recent Standards Restructuring – Mr. Nesse explained that this subcommittee
was the Field Devices Interface Standards and oversaw activities related to
direct communication standards, control panel standards including CP-01 and
also activities such as the security industry glossary. The new subcommittee
focuses on much of the same work, however the Glossary has been moved to
the Framework subcommittee.
b. DC-09 Review Project – this standard is coming up on review and there have
been a few proposals and contributions presented.
c. Other Standards Reviews – There are a number of standards coming up for
revision that the group must decide on how we are to proceed.

d. DSC Fibro Protocol Publication – There has been talk about SIA Standards
publishing and distributing the DSC Fibro protocol, this will be discussed
e. CP-01 Status – A review of the CP-01 happenings since it’s release in 2010
f. Glossary Project Status – Glossary update
5. DC-09 Project Review
a. Review Project Proposal (Attachment B)
Mr. Nesse went over the highlights of the project proposal. The group had no
questions about the proposal. The proposal will be forwarded to the SIA
Standards Committee on November 2 nd for approval. Mr Nesse asked for a
motion to forward the project proposal to the SIA Standards Committee for
approval.
R. Hinkson/L. Dischert
Motion Passes with Unanimous Consent
b. Review Contribution from Amstein & Walthert (Attachment C)
Mr. Nesse summarized the contribution to the standard from Amstein &
Walthert: as follows, and gave his own thoughts on whether the contribution
would be beneficial to be included.
2.1b Additional Parameters
• MAC - matches existing, OK
• alarm text: OK
• site name: OK
• building name: OK
• location: OK
• room: OK
• trigger: OK, may conflict with or duplicate the data message, but seems a
useful extension
• X, Y, Z: OK
• an extension of ASCII to allow accented characters should be considered
(how is this extension defined?)

Is the intent to send multiple messages to send more information to describe an
event, or to define a delimiter? It seems multiple messages are more likely to
be acceptable due to limitations on the overall message length.
1.2 Sequential Retransmission
The proposed sequence appears reasonable and effective. Perhaps this can be
added as annex material.
2.2 Examples
The UML sequence diagrams appear effective and would be a good addition to
the document.
1.3 Monitoring of the Connection
This information seems to go beyond the scope of the protocol standard. If
included at all, it would be annex material.
1.3a Transmission Parameter
This too is beyond the protocol spec, but seems to be useful annex material
once the details are defined.
1.3b Redundancy
This information seems to go beyond the scope of the protocol standard. If
included at all, it would be annex material.
1.4, 2.4 Messages for Reverse Commands
It may not be feasible to document these requirements, and polling intervals are
generally too long to allow reasonable response times for commands. Also, it
generally doesn't make sense to administer this through the receivers- in most
systems where it started in the receivers it has been moved to a separate PC
application.
1 NAK
The transmitter should process the NAK message to set its internal time
reference to that of the receiver so that the next message can be accepted. This
seems clear in the document: "in order to allow the transmitter to adjust its
internal clock". Generally, the transmitter would maintain a time base
independently of the user-viewable time base, as even with mandated GMT
time usage, it is common that the time used by the central station and the time
used by the user are not the same.

2 Error Handling
Handling for a wrong CRC (checksum) or time stamp are specifically covered in
the existing document. Incorrect decryption would cause a checksum failure.
The DUH message is intended as a catchall for messages that are
"unprocessable" for other reasons, so it would be difficult to further define this.
1 Check Criterion
The existing extended data definition to carry the MAC address seems sufficient.
Should this field become mandatory for some implementations?
2 Encrypted Size
Less effort is being expended in newer designs to reduce data size, so that the
data encoding is more robust and more easily debugged.
3 Checklist of Main Requirements
This would be an excellent annex.
4 Token Table
It's generally avoided to duplicate information from one standard in another
document to keep the two documents from coming into later conflict. But
repeating the reference table as an annex would be reasonable.
1 Data Encryption
The document references FIPS 197 for AES encryption. Use of encryption is
certainly desirable, but this standard does not need to mandate its use.
2 Hash
The encryption provides enough of a signature to satisfy most message
authentication requirements, but a scheme to include a specific signature could
be designed and included in the standard.
3 2009 Errata
This information needs to be incorporated in the published document.
4 Formatting
The document could be reformatted to improve clarity.
5 prEN 50136-1-7 Interoperability
Considerable analysis would be required to comment on the feasibility of
defining a translation from one protocol to the next.

c. Next steps
Schedule a meeting of this committee with the primary focus of tackling DC-09.
This meeting will be discussed at the end of the call.
6. Other Standards Reviews (Brief Discussion & Prioritize)
a. DC-03 -- Digital Communications Standard
i. There were no thoughts on this standard, Mr. Nesse suggested a
superficial update.
b. DC-04 – SIA 2000 Protocol
i. Mr. Hinkson said that he has seen some receiver implementations, but
isn’t sure that it got any traction, one route would be to move that this
standard be withdrawn.
c. DC-05 – Ademco ® Contact ID Protocol
i. SIA Distribution of new definitions
ii. Publish updated event table
iii. Rich Hinkson from Ademco said that he can send the documents to SIA
and have them distributed with the standard.
d. DC-07 – Receiver to Computer Interface Protocol (Type 2)
i. Normal, superficial update may be in order
e. AV-01 -- Audio Verification Standard Protocol for Audio Verification and Two-
Way Voice - Monitoring Service Command Set
i. Reaffirm possible without an update
f. MSD-01 – Monitoring Practices Standard
i. ANSI Standard that hasn’t been updated since 2000
ii. Has been a candidate for administratively withdrawn
iii. PINS in place, we can reaffirm or review within the next few
g. PIR-01 -- Passive Infrared Motion Detector Standard Revisions
i. Mr. Hinkson mentioned that PIR-01 for QC testing as a reference
ii. Mr. Reimer from Bosch volunteered to look into the usage within his
company.

7. DSC Fibro Protocol
a. Status Update
This standard was supposed to be released similar to the DC-05 standard, at this
point we are waiting for DSC to send an email back to begin the process. Kevin
Harris from DSC volunteered to contact the correct people internally for
approval.
b. Application Guide
This could cover some specialized use cases and informal applications that can
be published after the specification is green-lit.
8. CP-01
a. Current Status
The last meeting clarified that manufacturers can label their product as
compliant to older versions of CP-01 as long as they make clear to what version
the product is compliant to.
b. Call for Volunteers to Lead CP-01 Working Group
SIA would like to have someone close to the effort take over leadership of the
working group. A call for volunteers will be released in the upcoming weeks.
9. Glossary project
a. Current Status
160+ definitions are available and are housed on www.securityglossary.wikispaces.net
b. Call for Volunteers to Lead Working Group
A call for volunteers will also be distributed to lead this group
10. Adjournment & Next Steps
Mr. Nesse proposed a meeting of the committee after ISC Solutions that will consider 2
topics. Disposition of renewed/withdrawn standards and also an in-depth DC-09
conversation. In order to make it more accessible for participants from Europe the
proposed time would be 8AM PT.

Mr. Nesse entertained a motion to adjourn at 4:05PM
Dischert/Hinkson

Attachment A – List of Participants
Organization
ADT
AES
AES
Amstein & Walthert
Bosch
Bosch
Bosch
Brivo
Honeywell
Honeywell
North Lattitude
Tyco
UL
UTC
Participant
Larry Dischert
Bill Goretkin
Jim Lynch
Stephane Jacquet
Micheal Reimer
Bryan Matthewson
Denis Caler
Steve Van Till
Rich Hinkson
Linda Ortezi
Ted Nesse
Kevin Harris
Bryon Monte
Kevin Flanders