1、American National StandardDeveloped byfor Information Technology Systems Management Discoveryfor Managed Computer SystemsINCITS 531-2013INCITS 531-2013INCITS 531-2013American National Standardfor Information Technology Systems Management Discoveryfor Managed Computer SystemsSecretariatInformation Te
2、chnology Industry CouncilApproved December 30, 2013American National Standards Institute, Inc.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 establ
3、ished when, in the 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 consi
4、dered, and that a 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, process
5、es, or procedures 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 N
6、ational Standard in 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 pro
7、cedures of the American 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.Americ
8、an National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2014 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 otherwis
9、e,without prior written permission of ITI, 1101 K Street NW, Suite 610, Washington, DC 20005. Printed in the United States of AmericaCAUTION: The developers of this standard have requested that holders of patents that may berequired for the implementation of the standard disclose such patents to the
10、 publisher. However,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may apply to this standard. As of the date of publication of this standardand following calls for the identification of patents that may be required for the impleme
11、ntation ofthe standard, no such claims have been made. No further patent search is conducted by the de-veloper or publisher in respect to any standard it processes. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.CONTENTS Introduct
12、ion . 1 Document conventions 1 Typographical conventions . 1 ABNF usage conventions . 1 Experimental material . 2 1 Scope 3 1.1 WBEM Discovery using the Service Location Protocol (SLP) 3 2 Normative references 3 3 Terms and definitions 4 4 Symbols and abbreviated terms 4 5 WBEM Discovery using the S
13、ervice Location Protocol (DSP0205) 5 5.1 WBEM Discovery using the SLP 5 5.1.1 WBEM Server 5 Annex A (normative) WBEM SLP Template 6 A.1 Abstract . 6 A.2 Security considerations . 6 A.3 General . 6 Annex B (informative) Bibliography 11 i Foreword (This foreword is not part of American National Standa
14、rd INCITS 531-2013.)This standard was prepared by the DMTF WBEM Infrastructure Model WorkingGroup.DMTF is a not-for-profit association of industry members dedicated to promoting en-terprise and systems management and interoperability. For information about theDMTF, see http:/www.dmtf.org.Requests fo
15、r interpretation, suggestions for improvement or addenda, or defect re-ports are welcome. They should be sent to InterNational Committee for InformationTechnology Standards (INCITS), ITI, 1101 K Street, NW, Suite 610, Washington, DC20005.This standard was processed and approved for submittal to ANSI
16、 by INCITS. Com-mittee approval of this standard does not necessarily imply that all committee mem-bers voted for its approval. At the time it approved this standard, INCITS had thefollowing members:Philip Wennblom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe
17、Systems, Inc Scott Foshee Steve Zilles (Alt.)AIM Global, Inc. . Steve HallidayChuck Evanhoe (Alt.)Dan Kimball (Alt.)Apple . Helene WorkmanMarc Braner (Alt.)David Singer (Alt.)Distributed Management Task Force John Crandall Jeff Hilland (Alt.)Lawrence Lamers (Alt.)EMC Corporation . Gary RobinsonSteph
18、en Diamond (Alt.)Farance, Inc Frank FaranceTimothy Schoechle (Alt.)Futurewei Technologies, Inc. Yi ZhaoTimothy Jeffries (Alt.)Wilbert Adams (Alt.)GS1GO. Frank SharkeyCharles Biss (Alt.)Hewlett-Packard Company Karen Higginbottom Paul Jeran (Alt.)IBM Corporation Alexander TarpinianRobert Weir (Alt.)Ar
19、naud Le Hors (Alt.)Steve Holbrook (Alt.)Gerald Lane (Alt.)IEEE . Jodie HaaszTerry deCourcelle (Alt.)Bob Labelle (Alt.)Tina Alston (Alt.)Intel Philip Wennblom Grace Wei (Alt.)Stephen Balogh (Alt.)Microsoft Corporation . Jim Hughes Dick Brackney (Alt.)John Calhoon (Alt.)LLOrganization Represented Name
20、 of RepresentativeNational Institute of Standards The ABNF rule “service: URL“ defined in RFC2609 defines the format of service: URLs ; and its grammar provides the basis for the following refining ABNF rules: service-type = abstract-type “:“ url-scheme ; Restricted to abstract service types only. a
21、bstract-type = “wbem“ url-scheme = resname ; The value shall be a valid URL scheme for the WBEM ; protocols registered for this service location. For ; example, “http“ or “https“ for CIM-XML or WS-Management, ; and “telnet“ or “ssh“ for SM-CLP. sap = site ; Restricted to not allow url-part. site = i
22、psite ; Restricted to IP sites only. ipsite = “/“ hostport ; Restricted to not allow “user“ and to require hostport. hostport = host “:“ port ; Restricted to require port. host = hostnumber ; Restricted to numbered addresses only (no host names). hostnumber = ipv4-number / ipv6-number ; Extended to
23、also allow IPV6 addresses. ipv6-number = “ ipv6-address “ ; Using the common syntax. ; Definition of IPV6 address syntax, for additional restrictions see RFC4291: ipv6-address = ipv6-hexpart “:“ ipv4-number ipv6-hexpart = ipv6-hexseq / ipv6-hexseq “:“ ipv6-hexseq ipv6-hexseq = 1*4HEXDIGIT *( “:“ 1*4
24、HEXDIGIT ) ; Examples of service: URLs using this syntax: ; “service:wbem:http:/192.168.0.1:5988“ ; “service:wbem:https:/fe80:200:f8ff:fe21:67cf:5989“ This attribute is optional to be registered. When registered, the value of this attribute shall be the ABNF grammar string specified above. Version 1
25、.0 of this template used this attribute to register a portion of the service: INCITS 531-2013 8 URL. This enabled SLP User Agents to determine the service location from the value of this attribute, or from the value of the service: URL. With version 2.0 of this template, SLP User Agents need to dete
26、rmine the service location from the value of the service: URL only. service-hi-name=string O The value of this attribute shall be the value of the ElementName property of the CIM_ObjectManager instance representing the WBEM server that is registered. A value of NULL in that property shall be represe
27、nted by omitting this attribute. (This is why it is defined as optional (O).) The value of this attribute can be used in any human interfaces as the name of that WBEM server. service-hi-description=string O The value of this attribute shall be the value of the Description property of the CIM_ObjectM
28、anager instance representing the WBEM server that is registered. A value of NULL in that property shall be represented by omitting this attribute. (This is why it is defined as optional (O).) The value of this attribute can be used in any human interfaces as a description of that WBEM server. servic
29、e-id=string L The value of this attribute shall be the value of the Name property of the CIM_ObjectManager instance representing the WBEM server that is registered. The value of this attribute can be used as a programmatic identification of that WBEM server within the host offering that service. Com
30、municationMechanisms=string L M The set of values of this multi-valued attribute shall be the values of the CommunicationMechanism property of those CIM_ObjectManagerCommunicationMechanism instances that represent the WBEM protocols supported by the service access point identified by the service: UR
31、L. Each value can be used as a programmatic identification of the WBEM protocol that is supported. For a description of these values, see the definition of that property in the CIM Schema. “Unknown“, “Other“, “CIM-XML“, “WS-Management“, “SM-CLP“ OtherCommunicationMechanisms=string L M O This attribu
32、te shall be registered only if any of the CommunicationMechanisms attribute values has a value of “Other“. If registered, the following applies: The values of this multi-valued attribute shall be index-correlated with the values of the CommunicationMechanisms attribute, such that values at the same
33、index represent the same WBEM protocol. Values at indexes for which the corresponding value of the CommunicationMechanisms attribute is “Other“ shall be the value of the OtherCommunicationMechanismDescription property of the CIM_ObjectManagerCommunicationMechanism instance representing the WBEM prot
34、ocol for that index. Property values of NULL shall be represented by an empty string. Values at indexes for which the corresponding value of the CommunicationMechanisms attribute is not “Other“ shall be an empty string. These values can be used as a programmatic identification of the WBEM protocols
35、that are supported, in case the CommunicationMechanism attribute value is “Other“. The CIM Schema defines this property to contain free-form strings; other specifications (such as management initiative wrapper specifications) may define additional constraints on the values. CommunicationMechanismsVe
36、rsion=string L M The values of this multi-valued attribute shall be index-correlated with the values of the CommunicationMechanisms attribute, such that values at the same index represent the same WBEM protocol. The value of this attribute at any index shall be the value of the Version property of t
37、he CIM_ObjectManagerCommunicationMechanism instance representing the WBEM protocol for that index, if that property is non-NULL. A property value of NULL shall be represented by an empty string. AuthenticationMechanisms=string L M INCITS 531-2013 9 The set of values of this multi-valued attribute sh
38、all be the unique set of values of the array entries of the AuthenticationMechanismsSupported array property of the CIM_ObjectManagerCommunicationMechanism instances representing the WBEM protocols supported by the service access point identified by the service: URL. In other words, the set of value
39、s represents the superset of all authentication mechanisms supported by these WBEM protocols, without correlating any authentication mechanism to the WBEM protocol or protocols supporting it. A WBEM client needs to try the desired authentication mechanism with the desired WBEM protocol to see whethe
40、r it is available. For a description of these values, see the definition of that property in the CIM Schema. “Unknown“, “None“, “Other“, “Basic“, “Digest“ OtherAuthenticationMechanisms=string L M O This attribute shall be registered only if any of the AuthenticationMechanisms attribute values has a
41、value of “Other“. If registered, the following applies: The values of this multi-valued attribute shall be index-correlated with the values of the AuthenticationMechanisms attribute, such that values at the same index represent the same authentication mechanism. Values at indexes for which the corre
42、sponding value of the AuthenticationMechanisms attribute is “Other“ shall be the value of the AuthenticationMechanismDescriptions property of the CIM_ObjectManagerCommunicationMechanism instance representing the authentication mechanism for that index. Property values of NULL shall be represented by
43、 an empty string. Values at indexes for which the corresponding value of the AuthenticationMechanisms attribute is not “Other“ shall be an empty string. The CIM Schema defines this property to contain free-form strings; other specifications (such as management initiative wrapper specifications) may
44、define additional constraints on the values. InteropNamespaces=string L M This multi-valued attribute shall have one value for each distinct major version of the CIM Schema supported by the WBEM server that is registered. Each attribute value shall be the name of the Interop namespace for that major
45、 CIM Schema version. For a definition of the concept of an Interop namespace, see DSP1033. The name of a namespace can be found in the Name property of the CIM_Namespace instance representing the namespace. Namespaces=string L M O If this multi-valued attribute is registered, it shall have one value
46、 for each distinct CIM namespace supported by the WBEM server that is registered. Each attribute value shall be the name of the namespace. The name of a namespace can be found in the Name property of the CIM_Namespace instance representing the namespace. The set of distinct namespaces (of a given ma
47、jor CIM Schema version) supported by a WBEM server is represented as instances of CIM_Namespace in the Interop namespace of the WBEM server. InitiativesSupported=string L M O If this multi-valued attribute is registered, it shall have one value for each management initiative that is implemented by t
48、he WBEM server such that it conforms to the implementation requirements specification of the management initiative. Each attribute value shall have the following format (expressed in ABNF): registered-org “:“ registered-name Where: registered-org shall identify the business entity owning the impleme
49、ntation requirements specification of the management initiative. The registered-org value shall include a copyrighted, trademarked, or otherwise unique name that is owned by that business entity or that is a registered ID assigned to that business entity by a recognized global authority. In addition, to ensure uniqueness, the registered-org value shall not contain a colon (:). For implementation requirements specifications owned by DMTF, the value shall be “DMTF“. registere
