1、 International Telecommunication Union ITU-T H.350.5TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (05/2011) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMSInfrastructure of audiovisual services Directory services architecture for audiovisual and multimedia services Directory services architecture for
2、 non-standard protocols Recommendation ITU-T H.350.5 ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS H.100H.199 INFRASTRUCTURE OF AUDIOVISUAL SERVICES General H.200H.219 Transmission multiplexing and synchronization H.220H.229 Systems asp
3、ects H.230H.239 Communication procedures H.240H.259 Coding of moving video H.260H.279 Related systems aspects H.280H.299 Systems and terminal equipment for audiovisual services H.300H.349 Directory services architecture for audiovisual and multimedia services H.350H.359Quality of service architectur
4、e for audiovisual and multimedia services H.360H.369 Supplementary services for multimedia H.450H.499 MOBILITY AND COLLABORATION PROCEDURES Overview of Mobility and Collaboration, definitions, protocols and procedures H.500H.509 Mobility for H-Series multimedia systems and services H.510H.519 Mobile
5、 multimedia collaboration applications and services H.520H.529 Security for mobile multimedia systems and services H.530H.539 Security for mobile multimedia collaboration applications and services H.540H.549 Mobility interworking procedures H.550H.559 Mobile multimedia collaboration inter-working pr
6、ocedures H.560H.569 BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629 IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV General aspects H.700H.719 IPTV terminal devices H.720H.729 IPTV
7、middleware H.730H.739 IPTV application event handling H.740H.749 IPTV metadata H.750H.759 IPTV multimedia application frameworks H.760H.769 IPTV service discovery up to consumption H.770H.779 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T H.350.5 (05/2011) i Recom
8、mendation ITU-T H.350.5 Directory services architecture for non-standard protocols Summary Recommendation ITU-T H.350.5 describes a lightweight directory access protocol (LDAP) schema to represent non-standard multimedia communications endpoints, and is meant to provide a very basic framework for re
9、presenting these elements in a directory. It is an auxiliary class related to Recommendation ITU-T H.350 and derives much of its functionality from that architecture. Implementers should review Recommendation ITU-T H.350 in detail before proceeding with this Recommendation. The scope of this Recomme
10、ndation does not include normative methods for the use of the LDAP directory itself or the data it contains. The purpose of the schema is not to represent all possible data elements in the ITU-T H.323 protocol, but rather to represent the minimal set required to accomplish the design goals enumerate
11、d in Recommendation ITU-T H.350. This revised version of Recommendation ITU-T H.350.5 introduces several enhancements and clarifications to the previous version, primarily the addition of ITU-T X.500 directories support. This Recommendation includes an electronic attachment containing a schema confi
12、guration file for genericIdentity. History Edition Recommendation Approval Study Group 1.0 ITU-T H.350.5 2003-08-06 16 1.0 ITU-T H.350.5 attachment 2003-08-06 16 2.0 ITU-T H.350.5 2011-05-14 16 Keywords Directory services, ITU-T H.235.0, ITU-T H.320, ITU-T H.323, LDAP, SIP, ITU-T X.500. ii Rec. ITU-
13、T H.350.5 (05/2011) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is
14、responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by
15、the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collab
16、orative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certai
17、n mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requireme
18、nts. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. I
19、TU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual
20、 property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2012 All rights res
21、erved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.350.5 (05/2011) iii Table of Contents Page 1 Scope 1 1.1 Extending the schema . 1 2 References. 1 3 Definitions 2 4 Abbreviations 2 5 Conventions 2 6 Object class
22、definitions . 3 6.1 genericIdentity 3 6.2 genericIdentityProtocolIdentifier . 3 6.3 genericIdentityMessage 3 7 genericIdentity LDIF files 4 8 Using ITU-T H.350 with ITU-T X.500 directories 5 8.1 IMPORTS of ITU-T X.500 ASN.1 5 8.2 genericIdentityASN1.asn 6 Annex A Indexing profile . 8 Appendix I Elec
23、tronic attachment . 9 Bibliography. 10 Electronic attachment: Schema configuration file for genericIdentity Rec. ITU-T H.350.5 (05/2011) 1 Recommendation ITU-T H.350.5 Directory services architecture for non-standard protocols 1 Scope This Recommendation1describes a lightweight directory access prot
24、ocol (LDAP) schema to represent non-standard multimedia communications endpoints, and is meant to provide a very basic framework for representing these elements in a directory. It is an auxiliary class related to ITU-T H.350 and derives much of its functionality from that architecture. Implementers
25、should review ITU-T H.350 in detail before proceeding with this Recommendation. The scope of this Recommendation does not include normative methods for the use of the LDAP directory itself or the data it contains. The purpose of the schema is not to represent all possible data elements in the ITU-T
26、H.323 protocol, but rather to represent the minimal set required to accomplish the design goals enumerated in ITU-T H.350. 1.1 Extending the schema The genericIdentity classes may be extended as necessary for specific implementations. See the base ITU-T H.350 for a discussion on schema extension. In
27、 general, non-standard protocols will have a variety of attributes that only have meaning to the specific protocol. Implementers should be careful to use consistent and meaningful naming schemes to avoid confusion with other protocols that may be represented by the same object class. It should be no
28、ted that standardized protocols should not extend and use genericIdentity, but should instead create and standardize their own protocol-specific auxiliary classes as new contributions to the ITU-T H.350.x-series of Recommendations. 2 References The following ITU-T Recommendations and other reference
29、s contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investig
30、ate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status
31、 of a Recommendation. ITU-T H.350 Recommendation ITU-T H.350 (2011), Directory services architecture for multimedia conferencing. ITU-T X.500 Recommendation ITU-T X.500 (2008) | ISO/IEC 9594-1:2008, Information technology Open Systems Interconnection The Directory: Overview of concepts, models and s
32、ervices. ITU-T X.501 Recommendation ITU-T X.501 (2008) | ISO/IEC 9594-2:2008, Information technology Open Systems Interconnection The Directory: Models. ITU-T X.509 Recommendation ITU-T X.509 (2008) | ISO/IEC 9594-8:2008, Information technology Open Systems Interconnection The Directory: Public-key
33、and attribute certificate frameworks. _ 1This Recommendation includes an electronic attachment containing a text file with a schema configuration for genericIdentity. 2 Rec. ITU-T H.350.5 (05/2011) ITU-T X.511 Recommendation ITU-T X.511 (2008) | ISO/IEC 9594-3:2008, Information technology Open Syste
34、ms Interconnection The Directory: Abstract service definition. ITU-T X.518 Recommendation ITU-T X.518 (2008) | ISO/IEC 9594-4:2008, Information technology Open Systems Interconnection The Directory: Procedures for distributed operation. ITU-T X.519 Recommendation ITU-T X.519 (2008) | ISO/IEC 9594-5:
35、2008, Information technology Open Systems Interconnection The Directory: Protocol specifications. ITU-T X.520 Recommendation ITU-T X.520 (2008) | ISO/IEC 9594-6:2008, Information technology Open Systems Interconnection The Directory: Selected attribute types. ITU-T X.525 Recommendation ITU-T X.525 (
36、2008) | ISO/IEC 9594-9:2008, Information technology Open Systems Interconnection The Directory: Replication. IETF RFC 4510 IETF RFC 4510 (2006), Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map. IETF RFC 4511 IETF RFC 4511 (2006), Lightweight Directory Access Protocol (
37、LDAP): The Protocol. 3 Definitions This Recommendation defines the following terms: 3.1 commObject: An LDAP object class defined in ITU-T H.350 that represents generic multimedia conferencing endpoints. 3.2 white pages: An application that allows end users to look up the address of another user. 4 A
38、bbreviations This Recommendation uses the following abbreviations: LDAP Lightweight Directory Access Protocol (as defined in IETF RFC 4510) LDIF LDAP Data Interchange Format 5 Conventions In this Recommendation, the following conventions are used: “Shall“ indicates a mandatory requirement. “Should“
39、indicates a suggested but optional course of action. “May“ indicates an optional course of action rather than a recommendation that something takes place. References to clauses, subclauses, annexes and appendices refer to those items within this Recommendation, unless another specification is explic
40、itly listed. 6 Object class definitions The genericIdentity object class represents generic multimedia conferencing information associated with a person or resource. It is an auxiliary class and is related to the commObject class, which is defined in ITU-T H.350. It should be noted that the particul
41、ar user or resource with which an Rec. ITU-T H.350.5 (05/2011) 3 endpoint is associated via commOwner takes on special importance, as that may represent contact information required for further information in the use of the particular endpoint. If specific attributes, such as IP address or URIs, are
42、 necessary to support this endpoint type, then the standard attributes defining IP address and URI should be used. Keep in mind that in a directory of directories scenario, external searches will only be aware of the genericIdentity attributes and will not display IP address or URI. 6.1 genericIdent
43、ity OID: 0.0.8.350.1.1.7.2.1 objectclasses: (0.0.8.350.1.1.7.2.1 NAME genericIdentity DESC genericIdentity object SUP top AUXILIARY MAY (genericIdentityProtocolIdentifier $ genericIdentityMessage ) ) 6.2 genericIdentityProtocolIdentifier OID: 0.0.8.350.1.1.7.1.1 attributetypes: (0.0.8.350.1.1.7.1.1
44、NAME genericIdentityProtocolIdentifier DESC name of the non-standard protocol EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15) Application utility class Standard Number of values multi Definition Text string indicating the name of the non-standard proto
45、col represented by this endpoint. Notes Semantics Example applications for which this attribute would be useful Search for endpoints that support a specific non-standard protocol. Example (LDIF fragment) genericIdentityProtocolIdentifier: MPEG2 /MPEG2 endpoint 6.3 genericIdentityMessage OID: 0.0.8.3
46、50.1.1.7.1.2 attributetypes: (0.0.8.350.1.1.7.1.2 NAME genericIdentityMessage DESC informative text string EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15) Application utility class Standard Number of values 4 Rec. ITU-T H.350.5 (05/2011) multi Definiti
47、on Informative text string containing information about multimedia conferencing capabilities of the associated user and/or location of the service. This information may include instructions, other connection information, or pointers to specific documentation. Notes Semantics Example applications for
48、 which this attribute would be useful Multimedia conferencing services that are not ITU-T H.323, ITU-T H.320, or SIP; for example: MPEG2, access grid or other IP multicast service; instant messaging service. Example (LDIF fragment) genericIdentityMessage: see for connection instructions 7 genericId
49、entity LDIF files This clause contains a schema configuration file for genericIdentity that can be used to configure an LDAP server to support this class # genericIdentity Object Schema # # Schema for representing a genericIdentity Protocol Object in an LDAP Directory # # Abstract # # This Recommendation defines the schema for representing genericIdentity # object in an LDAP directory LDAPv3. It defines schema elements # to
