1、 IEEE Standard for Discovery, Authentication, and Authorization in Host Attachments of Storage Devices Sponsored by the Information Assurance Committee IEEE 3 Park Avenue New York, NY 10016-5997 USA IEEE Computer Society IEEE Std 1667-2015(Revision ofIEEE Std 1667-2009) IEEE Std 1667-2015(Revision o
2、fIEEE Std 1667-2009)IEEE Standard for Discovery, Authentication, and Authorization in Host Attachments of Storage DevicesSponsorInformation Assurance Committeeof theIEEE Computer SocietyApproved 3 September 2015IEEE-SA Standards BoardThe Institute of Electrical and Electronics Engineers, Inc.3 Park
3、Avenue, New York, NY 10016-5997, USACopyright 2016 by The Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 22 January 2016. Printed in the United States of America.IEEE is a registered trademark in the U.S. Patent fitnessfor a particular purpose; non-infringement
4、; and quality, accuracy, effectiveness, currency, or completeness ofmaterial. In addition, IEEE disclaims any and all conditions relating to: results; and workmanlike effort.IEEE standards documents are supplied “AS IS” and “WITH ALL FAULTS.”Use of an IEEE standard is wholly voluntary. The existence
5、 of an IEEE standard does not imply that thereare no other ways to produce, test, measure, purchase, market, or provide other goods and services related tothe scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved andissued is subject to change brought ab
6、out through developments in the state of the art and commentsreceived from users of the standard. In publishing and making its standards available, IEEE is not suggesting or rendering professional or otherservices for, or on behalf of, any person or entity nor is IEEE undertaking to perform any duty
7、 owed by anyother person or entity to another. Any person utilizing any IEEE Standards document, should rely upon hisor her own independent judgment in the exercise of reasonable care in any given circumstances or, asappropriate, seek the advice of a competent professional in determining the appropr
8、iateness of a given IEEEstandard.IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO:PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND O
9、N ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE UPONANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE ANDREGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.iiiCopyr
10、ight 2016 IEEE. All rights reserved.TranslationsThe IEEE consensus development process involves the review of documents in English only. In the eventthat an IEEE standard is translated, only the English version published by IEEE should be considered theapproved IEEE standard.Official statements A st
11、atement, written or oral, that is not processed in accordance with the IEEE-SA Standards BoardOperations Manual shall not be considered or inferred to be the official position of IEEE or any of itscommittees and shall not be considered to be, or be relied upon as, a formal position of IEEE. At lectu
12、res,symposia, seminars, or educational courses, an individual presenting information on IEEE standards shallmake it clear that his or her views should be considered the personal views of that individual rather than theformal position of IEEE. Comments on standardsComments for revision of IEEE Standa
13、rds documents are welcome from any interested party, regardless ofmembership affiliation with IEEE. However, IEEE does not provide consulting information or advicepertaining to IEEE Standards documents. Suggestions for changes in documents should be in the form of aproposed change of text, together
14、with appropriate supporting comments. Since IEEE standards represent aconsensus of concerned interests, it is important that any responses to comments and questions also receivethe concurrence of a balance of interests. For this reason, IEEE and the members of its societies andStandards Coordinating
15、 Committees are not able to provide an instant response to comments or questionsexcept in those cases where the matter has previously been addressed. For the same reason, IEEE does notrespond to interpretation requests. Any person who would like to participate in revisions to an IEEEstandard is welc
16、ome to join the relevant IEEE working group.Comments on standards should be submitted to the following address:Secretary, IEEE-SA Standards Board 445 Hoes Lane Piscataway, NJ 08854 USALaws and regulations Users of IEEE Standards documents should consult all applicable laws and regulations. Complianc
17、e with theprovisions of any IEEE Standards document does not imply compliance to any applicable regulatoryrequirements. Implementers of the standard are responsible for observing or referring to the applicableregulatory requirements. IEEE does not, by the publication of its standards, intend to urge
18、 action that is notin compliance with applicable laws, and these documents may not be construed as doing so.CopyrightsIEEE draft and approved standards are copyrighted by IEEE under U.S. and international copyright laws.They are made available by IEEE and are adopted for a wide variety of both publi
19、c and private uses. Theseinclude both use, by reference, in laws and regulations, and use in private self-regulation, standardization,and the promotion of engineering practices and methods. By making these documents available for use andadoption by public authorities and private users, IEEE does not
20、 waive any rights in copyright to thedocuments.ivCopyright 2016 IEEE. All rights reserved.Photocopies Subject to payment of the appropriate fee, IEEE will grant users a limited, non-exclusive license tophotocopy portions of any individual standard for company or organizational internal use or indivi
21、dual, non-commercial use only. To arrange for payment of licensing fees, please contact Copyright Clearance Center,Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission tophotocopy portions of any individual standard for educational classroom use can also be obtain
22、ed throughthe Copyright Clearance Center.Updating of IEEE Standards documents Users of IEEE Standards documents should be aware that these documents may be superseded at any timeby the issuance of new editions or may be amended from time to time through the issuance of amendments,corrigenda, or erra
23、ta. An official IEEE document at any point in time consists of the current edition of thedocument together with any amendments, corrigenda, or errata then in effect. Every IEEE standard is subjected to review at least every ten years. When a document is more than ten yearsold and has not undergone a
24、 revision process, it is reasonable to conclude that its contents, although still ofsome value, do not wholly reflect the present state of the art. Users are cautioned to check to determine thatthey have the latest edition of any IEEE standard.In order to determine whether a given document is the cu
25、rrent edition and whether it has been amendedthrough the issuance of amendments, corrigenda, or errata, visit the IEEE-SA Website at http:/ieeexplore.ieee.org/expel/standards.jsp or contact IEEE at the address listed previously. For moreinformation about the IEEE SA or IOWAs standards development pr
26、ocess, visit the IEEE-SA Website athttp:/standards.ieee.org.Errata Errata, if any, for all IEEE standards can be accessed on the IEEE-SA Website at the following URL: http:/standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errataperiodically.PatentsAttention i
27、s called to the possibility that implementation of this standard may require use of subject mattercovered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to theexistence or validity of any patent rights in connection therewith. If a patent holder or p
28、atent applicant hasfiled a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA Website at http:/standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicatewhether the Submitter is willing or unwilling to grant licenses unde
29、r patent rights without compensation orunder reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfairdiscrimination to applicants desiring to obtain such licenses.Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE
30、is notresponsible for identifying Essential Patent Claims for which a license may be required, for conductinginquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms orconditions provided in connection with submission of a Letter of Assurance, if any,
31、or in any licensingagreements are reasonable or non-discriminatory. Users of this standard are expressly advised thatdetermination of the validity of any patent rights, and the risk of infringement of such rights, is entirely theirown responsibility. Further information may be obtained from the IEEE
32、 Standards Association.vCopyright 2016 IEEE. All rights reserved.ParticipantsThe following is a list of participants in the IEEE 1667 Working Group. Curtis Stevens, ChairJim Hatfield, Vice Chair and EditorJohn Geldman, SecretaryPatrick Hery, TreasurerThe following members of the entity balloting com
33、mittee voted on this standard. Balloters may have votedfor approval, disapproval, or abstention. David AbzarianDaniele BalluchiKiran BangaloreLeonid BaryudinBart BombayJames BordenGary CalderJason CambriaJorge CampelloLaurent CastilloJoseph ChenDan ColegroveJason Cox Mike DanielsonBoris DolgunovTom
34、FriendMichael GeorgeDaniel GoodmanBill GraceCyril GuyotAidan HerbertMichael JamesGreg KazmierczakDave LandsmanKelin LeeDuoying LiuLeo LiuJean LusettiGrigory LyakhovitskiyDale McNamaraTim MarkeyGary MooreheadJack NagleDmitry ObukhovSteve OlssonHiromichi OribeTeruki OrihashiLei PooLee PrewittDonald Ri
35、chMarco SanvidoAvraham ShimorYoni ShternhellHeng TangJon TanguyBob ThibadeauVictor TsaiMike TsangRam ValliyappanLen VeilYun WangJim WarinoRalph WeberMichael WillettDanny YbarraJing ZhuCadence Design Systems, Inc.DellEDFMarvell Semiconductor, Inc.Micron Technology, Inc.Microsoft CorporationNokiaPhiso
36、n Electronics Corp.PMC-Sierra, Inc.SanDisk CorporationSeagate Technology LLCSynopsys, Inc.TOSHIBA CorporationULINK Technology, Inc.Western Digital CorporationCopyright 201vi6 IEEE. All rights reserved.When the IEEE-SA Standards Board approved this standard on 3 September 2015, it had the followingme
37、mbership:John D. Kulick, ChairJon Walter Rosdahl, Vice ChairRichard H. Hulett, Past ChairKonstantinos Karachalios, Secretary*Member EmeritusMasayuki AriyoshiTed BurseStephen DukesJean-Philippe FaureJ. Travis GriffithGary HoffmanMichael Janezic Joseph L. Koepfinger*David J. LawHung LingAndrew MylesT.
38、 W. OlsenGlenn ParsonsRonald C. PetersenAnnette D. ReillyStephen J. ShellhammerAdrian P. StephensYatin TrivediPhillip WinstonDon WrightYu YuanDaidi ZhongCopyriviight 2016 IEEE. All rights reserved.IntroductionThe following are included in this document:Front mater 12 clauses 11 annexesThis is the th
39、ird published version of IEEE Std 1667, as follows: IEEE Std 1667-2006 (superseded by IEEE Std 1667-2009) IEEE Std 1667-2009 (superseded by IEEE Std 1667-2015) IEEE Std 1667-2015This standard provides the following: Device-type independent protocol for discovering and using multiple interfaces Suppo
40、rt for multiple applications (silos) A mechanism and ground rules for externally defined functional modulesPrincipal changes from IEEE Std 1667-2009 are as follows: Support for the Password, Smart Card Transport, and TCG Storage Transport silos Obsoleted support for the Certificate Authentication Si
41、lo Additional Probe Silo functionality General clarifications Support for interface transports: Serial ATA, USB BOT, UAS, CompactFlash, eMMC, and UFS.This introduction is not part of IEEE Std 1667-2015, IEEE Standard for Discovery, Authentication, andAuthorization in Host Attachments of Storage Devi
42、ces.viiiCopyright 2016 IEEE. All rights reserved.Contents1. Overview 11.1 Scope 11.2 Purpose. 11.3 Conventions . 12. Normative references. 83. Definitions . 104. Special terms, acronyms, and abbreviations 114.1 Special terms 114.2 Acronyms and abbreviations . 155. Model . 165.1 How to use this stand
43、ard 165.2 Stack. 175.3 Silo Type Identifier (STID) . 185.4 Silo interactions . 195.5 Provisioning . 205.6 Authentication 205.7 Authorization . 206. Host requirements 226.1 Overview 226.2 Host requirements for the Probe Silo.226.3 Host requirements for the Password Silo. 226.4 Host requirements for t
44、he Smart Card Transport Silo . 226.5 Host requirements for the TCG Storage Transport Silo 227. Addressable Command Target requirements. 237.1 General ACT requirements 237.2 IEEE 1667 Reset types 238. Status Codes. 258.1 Common Status Codes. 258.2 Success. 268.3 Failure 268.4 Invalid Parameter Combin
45、ation . 268.5 Invalid Parameter Length. 268.6 Inconsistent Payload Content Length 268.7 Invalid Silo. 268.8 Incomplete Command Received 268.9 Invalid Parameter. 268.10 No Probe 268.11 Silo Interactions Error 278.12 P_OUT/P_IN Sequence Rejection. 278.13 Invalid Command ID . 27ixCopyright 2016 IEEE. A
46、ll rights reserved.9. Password Silo. 289.1 Overview 289.2 Model . 289.3 Status Codes. 529.4 IEEE 1667 Reset responses . 579.5 Commands . 5710. Probe Silo. 7510.1 Overview 7510.2 Model . 7510.3 Status Codes. 7610.4 IEEE 1667 Reset responses . 7610.5 Commands . 7611. Smart Card Transport Silo . 7811.1
47、 Overview 7811.2 Model . 7811.3 Status Codes. 8111.4 IEEE 1667 Reset responses . 8111.5 Commands . 8612. TCG Storage Transport Silo 8812.1 Overview 8812.2 Model . 8812.3 Status Codes. 9012.4 IEEE 1667 Reset responses . 9112.5 Commands . 91Annex A (informative) Bibliography 94Annex B (normative) IEEE
48、 1667 over SCSI and ATA devices 95Annex C (normative) SAS transport 173Annex D (normative) ATA transport. 177Annex E (normative) USB BOT transport 181Annex F (normative) USB UASP transport 185Annex G (normative) CompactFlash transport 190Annex H (normative) eMMC transport 191Annex I (normative) UFS
49、transport . 195Annex J (informative) SCTS usage notes and examples of exchanges. 199Annex K (informative) TCG Storage Transport Silo examples 208xCopyright 2016 IEEE. All rights reserved.List of tablesTable 1HEX ASCII conversion . 3Table 2Acronyms and abbreviations . 15Table 3Distribution of requirements in this standard 16Table 4STID values defined in this standard. 18Table 5PROBE command interaction pool numbers. 19Table 6High-level IEEE 1667 reset types 24Table 7Common Status Codes. 25Table 8Password Silo commands 28Table 9SHA-256 digest ca
