ANSI INCITS 400-2004 for Information Technology SCSI Object-Based Storage Device Commands (OSD).pdf
《ANSI INCITS 400-2004 for Information Technology SCSI Object-Based Storage Device Commands (OSD).pdf》由会员分享,可在线阅读,更多相关《ANSI INCITS 400-2004 for Information Technology SCSI Object-Based Storage Device Commands (OSD).pdf(190页珍藏版)》请在麦多课文档分享上搜索。
1、American National StandardDeveloped byfor Information Technology SCSI Object-Based Storage Device Commands (OSD)ANSI INCITS 400-2004ANSIINCITS400-2004ANSIINCITS 400-2004American National Standardfor Information Technology SCSI Object-Based StorageDevice Commands (OSD)SecretariatInformation Technolog
2、y Industry CouncilApproved December 15, 2004 American National Standards Institute, Inc.AbstractThis SCSI command set is designed to provide efficient operation of input/output logical units thatmanage the allocation, placement, and accessing of variable-size data-storage containers, calledobjects.
3、Objects are intended to contain operating system and application constructs.Approval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the
4、 judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially affected interests. Substantial agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a
5、concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary; theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures
6、not conforming to the standards.The American National Standards Institute does not develop standards andwill in no circumstances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard i
7、n the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the secretariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the Ame
8、rican National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National Standa
9、rdPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2005 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior wr
10、itten permission of ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may be re-quired for the implementation of the standard disclose such patents to the publisher. However, nei-
11、ther the developers nor the publisher have undertaken a patent search in order to identify which, ifany, patents may apply to this standard. As of the date of publication of this standard, followingcalls for the identification of patents that may be required for the implementation of the standard,no
12、tice of one or more such claims has been received. By publication of this standard, no positionis taken with respect to the validity of this claim or of any rights in connection therewith. The knownpatent holder(s) has (have), however, filed a statement of willingness to grant a license underthese r
13、ights on reasonable and nondiscriminatory terms and conditions to applicants desiring to ob-tain such a license. Details may be obtained from the publisher. No further patent search is con-ducted by the developer or publisher in respect to any standard it processes. No representation ismade or impli
14、ed that this is the only license that may be required to avoid infringement in the use ofthis standard.iContentsPageForeword xIntroduction xv1 Scope . 12 Normative references. 52.1 Normative references 52.2 Approved ISO references 52.3 Approved FIPS references 52.4 Approved IETF References. 52.5 Ref
15、erences under development 63 Definitions, symbols, abbreviations, and conventions 73.1 Definitions . 73.2 Acronyms 103.3 Keywords 103.4 Conventions 113.5 Bit and byte ordering . 123.6 Notation conventions. 123.6.1 Notation for byte encoded character strings 123.6.2 Notation for procedure calls . 133
16、.7 Data field requirements . 143.7.1 ASCII data field requirements 143.7.2 Data field termination and padding requirements 144 SCSI OSD Model . 154.1 The request-response model 154.2 OSD type devices . 154.3 OSD object abstraction . 164.4 Elements of the example configuration . 174.5 Description of
17、the OSD Architecture . 184.6 Stored data objects . 184.6.1 Stored data object types 184.6.2 Identifying OSD objects 194.6.3 Root object . 194.6.4 Partitions 194.6.5 User objects . 204.6.6 Collections 204.7 OSD object attributes 214.7.1 Overview 214.7.2 Command function ordering for commands that get
18、 and/or set attributes. 21iiPage4.7.3 Attributes pages . 224.7.4 Attributes 234.7.5 Attributes directories 244.8 Quotas. 244.8.1 Introduction 244.8.2 Quota errors. 254.8.3 Quota testing 254.8.4 Changing quotas 254.9 Policy/storage management 264.9.1 Overview 264.9.2 Capabilities. 264.9.2.1 Introduct
19、ion . 264.9.2.2 Capability format . 274.9.2.2.1 Introduction 274.9.2.2.2 U/C capability object descriptor 314.9.2.2.3 PAR capability object descriptor 324.9.2.3 Capabilities and commands allowed. 334.9.3 Policy access tags 374.10 Security . 384.10.1 Basic security model 384.10.2 Trust assumptions 40
20、4.10.3 Preparing credentials . 414.10.4 Security methods . 424.10.4.1 Introduction . 424.10.4.2 The NOSEC security method 434.10.4.3 The CAPKEY security method 444.10.4.4 The CMDRSP security method. 444.10.4.5 The ALLDATA security method. 454.10.5 Credentials. 484.10.5.1 Credential format. 484.10.5.
21、2 Capability key 484.10.6 OSD device server security algorithms 494.10.6.1 Credential validation 494.10.6.2 Reconstructing the credential 494.10.6.3 Computing the credential integrity check value. 504.10.6.4 Invalidating credentials 504.10.7 Request nonces . 514.10.7.1 Request nonce format. 514.10.7
22、.2 Device server validation of request nonces 514.10.7.3 Lists of previously used request nonces . 524.10.7.3.1 Introduction 524.10.7.3.2 Freezing capability audit fields. 524.10.7.3.3 Freezing working keys . 534.10.8 Integrity check values. 534.10.9 Secret keys 544.10.9.1 Introduction . 544.10.9.2
23、Computing updated generation keysand new authentication keys 554.10.10 OSD security interactions with SPC-3 commands and SAM-3 task management functions . 56iiiPage4.11 Data persistence model. 564.12 Data-In and Data-Out Buffer model. 574.12.1 Bidirectional data transfers. 574.12.2 OSD meta data. 57
24、4.12.3 OSD Data-In Buffer format . 584.12.4 OSD Data-Out Buffer format 594.12.5 Data-In and Data-Out buffer offsets . 604.13 Interactions between concurrently processed commands. 604.14 Error reporting . 614.14.1 Introduction. 614.14.2 OSD-specific sense data descriptors . 624.14.2.1 OSD error ident
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
10000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- ANSIINCITS4002004FORINFORMATIONTECHNOLOGYSCSIOBJECTBASEDSTORAGEDEVICECOMMANDSOSDPDF

链接地址:http://www.mydoc123.com/p-435708.html