logo资料库

ZB_SEC-PICS(ZigBee2007协议规范资料).pdf

发布时间：2022-04-14 发布人：admin 分类：互联网 资料大小：0.05M 资料格式：pdf 举报 版权申诉
第1页 / 共20页
第2页 / 共20页
第3页 / 共20页
第4页 / 共20页
第5页 / 共20页
第6页 / 共20页
第7页 / 共20页
第8页 / 共20页
资料共20页，剩余部分请下载后查看
    May, 2007 Project ZigBee Alliance ZigBee-043171ZBr04 Title ZigBee Security Services protocol implementation conformance (PICS) proforma Date Submitted Source Re: Abstract Purpose Notice [June 05, 2007] [Robert Cragie] [Jennic] [Furnival Street, Sheffield, S1 4QT, UK] The ZigBee Specification (053474r16ZB). Voice: Fax: E-mail: [+44 114 281 2655] [+44 114 281 2951] [rcc@jennic.com] As a part of formal conformance testing, developers will be asked to submit a statement of protocol conformance with respect to the ZigBee stack profile required by the Application Profile under test. This document is intended to provide the form of that statement of conformance. This document, after review by the relevant working groups, should provide a form whereby developers can proffer a statement of protocol conformance to be tested under platform and profile testing. This document has been prepared to assist the ZigBee Alliance. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release The contributor acknowledges and accepts that this contribution will be posted in the member area of the ZigBee web site. Submission Page 1 Robert Cragie, Jennic
    May, 2007 Legal Notice ZigBee-043171ZBr04 Copyright © ZigBee Alliance, Inc. (2004, 2005, 2007). All rights Reserved. This information within this document is the property of the ZigBee Alliance and its use and disclosure are restricted. Elements of ZigBee Alliance specifications may be subject to third party intellectual property rights, including without limitation, patent, copyright or trademark rights (such a third party may or may not be a member of ZigBee). ZigBee is not responsible and shall not be held responsible in any manner for identifying or failing to identify any or all such third party intellectual property rights. This document and the information contained herein are provided on an “AS IS” basis and ZigBee DISCLAIMS ALL WARRANTIES EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO (A) ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OF THIRD PARTIES (INCLUDING WITHOUT LIMITATION ANY INCLUDING PATENT, COPYRIGHT OR TRADEMARK RIGHTS) OR (B) ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON- INFRINGEMENT. IN NO EVENT WILL ZIGBEE BE LIABLE FOR ANY LOSS OF PROFITS, LOSS OF BUSINESS, LOSS OF USE OF DATA, INTERRUPTION OF BUSINESS, OR FOR ANY OTHER DIRECT, INDIRECT, SPECIAL OR EXEMPLARY, INCIDENTIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES OF ANY KIND, IN CONTRACT OR IN TORT, IN CONNECTION WITH THIS DOCUMENT OR THE INFORMATION CONTAINED HEREIN, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. All Company, brand and product names may be trademarks that are the sole property of their respective owners. The above notice and this paragraph must be included on all copies of this document that are made. ZigBee Alliance, Inc. 2694 Bishop Drive, Suite 275 San Ramon, CA 94583 INTELLECTUAL PROPERTY RIGHTS Submission Page 2 Robert Cragie, Jennic
    May, 2007 ZigBee-043171ZBr04 References The following standards contain provisions, which, through reference in this document, constitute provisions of this standard. All the standards listed are normative references. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. 1.1 ZigBee Alliance documents [R1] Document 02039r0: Security Working Group Requirements Definition, August 2003. Document 053474r16: ZigBee Specification, May 2007. Document 053275r03: ZigBee Protocol Stack Settable Values (knobs), February 2005. Document 064321r04: ZigBee Stack Profile, December 2006. Document 074855r01: ZigBee PRO Stack Profile, May 2007. IEEE documents IEEE Standard for Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer (PHY) specifications for Low Rate Wireless Personal Area Networks (LR-WPANs), 2003. ISO documents ISO/IEC 9646-1:1991, Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts. ISO/IEC 9646-7:1995, Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7. Implementation conformance statements. [R2] [R3] [R4] [R5] 1.2 [R6] 1.3 [R7] [R8] Submission Page 3 Robert Cragie, Jennic
    May, 2007 ZigBee-043171ZBr04 Change history The following table shows the change history for this specification. Revision 4 (June 05, 2007) Table 1 – Revision change history for revision 3 Revision Version Description 0 1 2 3 4 - 1 1 1 1 Initial draft incorporating content from v0.92 specification. Editorial changes. Split app. And TC master keys. Completed stack profile table As a result of ZigBee V1.0 Platform Conformance testing (CCB item 302), the following changes were made: SL7 is Optional. MLS1 and MLS2 were made optional. Bought up to date for 053474r13 Bought up to date for 053474r16 Submission Page 4 Robert Cragie, Jennic
    May, 2007 ZigBee-043171ZBr04 Introduction 2 To evaluate conformance of a particular implementation, it is necessary to have a statement of which capabilities and options have been implemented for a given standard. Such a statement is called a protocol implementation conformance statement (PICS). 2.1 Scope This document provides the protocol implementation conformance statement (PICS) proforma for the ZigBee security services section (053474r16, Clause 4) in compliance with the relevant requirements, and in accordance with the relevant guidance, given in ISO/IEC 9646-7. 2.2 Purpose The supplier of a protocol implementation claiming to conform to the ZigBee standard shall complete the following PICS proforma and accompany it with the information necessary to identify fully both the supplier and the implementation. The protocol implementation conformance statement (PICS) of a protocol implementation is a statement of which capabilities and options of the protocol have been implemented. The statement is in the form of answers to a set of questions in the PICS proforma. The questions in a proforma consist of a systematic list of protocol capabilities and options as well as their implementation requirements. The implementation requirement indicates whether implementation of a capability is mandatory, optional, or conditional depending on options selected. When a protocol implementer answers questions in a PICS proforma, they would indicate whether an item is implemented or not, and provide explanations if an item is not implemented. Submission Page 5 Robert Cragie, Jennic
    May, 2007 ZigBee-043171ZBr04 Mandatory Optional Optional, but support of at least one of the group of options labeled O.n is required. Not applicable Prohibited 3 Abbreviations and special symbols Notations for requirement status: M O O.n N/A X “item”: Conditional, status dependent upon the support marked for the “item”. For example, FD1: O.1 indicates that the status is optional but at least one of the features described in FD1 and FD2 is required to be implemented, if this implementation is to follow the standard of which this PICS Proforma is a part. Submission Page 6 Robert Cragie, Jennic
    May, 2007 ZigBee-043171ZBr04 Instructions for completing the PICS proforma 4 If a given implementation is claimed to conform to this standard, the actual PICS proforma to be filled in by a supplier shall be technically equivalent to the text of the PICS proforma in this annex, and shall preserve the numbering and naming and the ordering of the PICS proforma. A PICS which conforms to this document shall be a conforming PICS proforma completed in accordance with the instructions for completion given in this annex. The main part of the PICS is a fixed-format questionnaire, divided into five tables. Answers to the questionnaire are to be provided in the rightmost column, either by simply marking an answer to indicate a restricted choice (such as Yes or No), or by entering a value or a set or range of values. The ZigBee Specification [R2] contains the notion of a “stack profile” (see also [R4]and [R5]). A stack profile is a collection of settings for the operational parameters of the network layer (see [R3]). Stack profiles exist primarily to address concerns about interoperability of devices implementing a specification with many optional features and tunable parameters in a multi- vendor, multi-application environment. The operative restriction is that devices implementing the same stack profile are required to interoperate. It is expected that a large number of application profiles will each select a single stack profile and that the universe of stack profiles advanced and supported by the ZigBee Alliance will be kept as small as possible. In light of this and of the fact that embedded stack implementers can ill afford to implement more than the minimum set of features required to support their application, protocol conformance will generally be tested with respect to a specific stack profile or at most a small set of stack profiles. This document is organized such that the general PICS outlined in clause 8 may be further constrained using the tables in clause 9 to reflect a particular stack profile. Items not included in the constrained set need not be answered. Items that have optional status in the general PICS may be made mandatory or disallowed under a given stack profile. Submission Page 7 Robert Cragie, Jennic
    May, 2007 ZigBee-043171ZBr04 Identification of the implementation 5 Implementation under test (IUT) identification IUT name: _____________________________________________________________________ IUT version: ____________________________________________________________________ ______________________________________________________________________________ System under test (SUT) identification SUT name: _____________________________________________________________________ Hardware configuration: ___________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ Operating system: ________________________________________________________________ Product supplier Name: ________________________________________________________________________ Address: ______________________________________________________________________ _____________________________________________________________________________ Telephone number: _____________________________________________________________ Facsimile number: ______________________________________________________________ Email address: _________________________________________________________________ Submission Page 8 Robert Cragie, Jennic
    分享到：
    赞 收藏

    相关推荐

    最新资料