1、 International Telecommunication Union ITU-T H.350.4TELECOMMUNICATION 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、 SIP Recommendation ITU-T H.350.4 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 aspects H.230H.239 Com
3、munication 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 architecture for audiovisual a
4、nd 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 multimedia collabo
5、ration 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 procedures H.560H.569
6、 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 middleware H.730H.7
7、39 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.4 (05/2011) i Recommendation ITU-T H.3
8、50.4 Directory services architecture for SIP Summary Recommendation ITU-T H.350.4 describes a lightweight directory access protocol (LDAP) directory services architecture for multimedia conferencing using a session initiation protocol (SIP). In particular, it defines an LDAP schema to represent SIP
9、user agents (UAs) on the network and associate those endpoints with users. This Recommendation is intended to supplement the CommObject directory architecture as discussed in Recommendation ITU-T H.350, and not intended to be used as a stand-alone architecture. The implementation of this LDAP schema
10、, together with the use of the ITU-T H.350 CommObject architecture, facilitates the integration of SIP user agents and conferencing devices into the existing enterprise directories; thus allowing the user to perform white page lookups and access clickable dialling supported by SIP devices. The prima
11、ry reasons for implementing this schema are identical to those listed in Recommendation ITU-T H.350 (the CommObject class definition) as they apply specifically to the use of SIP UAs. This revised version of Recommendation ITU-T H.350.4 introduces several enhancements and clarifications to the previ
12、ous version, primarily the addition of ITU-T X.500 directories support. This Recommendation includes an electronic attachment containing a schema configuration file for SIPIdentity. History Edition Recommendation Approval Study Group 1.0 ITU-T H.350.4 2003-08-06 16 1.0 ITU-T H.350.4 attachment 2003-
13、08-06 16 2.0 ITU-T H.350.4 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-T H.350.4 (05/2011) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications,
14、 information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on
15、 a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by 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 do
16、wn in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication
17、 administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandator
18、y provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws atte
19、ntion to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or other
20、s outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent
21、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 reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T H.350.4 (05/2011)
22、iii Table of Contents Page 1 Scope 1 1.1 Extending the schema . 1 2 References. 1 3 Definitions 2 4 Abbreviations 3 5 Conventions 3 6 Object class definitions . 4 6.1 SIPIdentity 4 6.2 SIPIdentitySIPURI . 4 6.3 SIPIdentityRegistrarAddress 4 6.4 SIPIdentityProxyAddress . 5 6.5 SIPIdentityAddress . 6
23、6.6 SIPIdentityPassword . 6 6.7 SIPIdentityUserName . 7 6.8 SIPIdentityServiceLevel . 7 7 SIPIdentity LDIF files 8 8 Using ITU-T H.350 With ITU-T X.500 directories . 10 8.1 IMPORTS of ITU-T X.500 ASN.1 10 8.2 sipIdentityASN1.asn . 10 Annex A Indexing profile . 13 Appendix I Electronic attachment . 1
24、4 Bibliography. 15 Electronic attachment: Schema configuration file for SIPIdentity Rec. ITU-T H.350.4 (05/2011) 1 Recommendation ITU-T H.350.4 Directory services architecture for SIP 1 Scope This Recommendation1describes a lightweight directory access protocol (LDAP) directory services architecture
25、 for multimedia conferencing using a session initiation protocol (SIP). In particular, it defines an LDAP schema to represent SIP user agents (UAs) on the network and associate those endpoints with users. This Recommendation is intended to supplement the CommObject directory architecture as discusse
26、d in ITU-T H.350, and is not intended to be used as a stand-alone architecture. The implementation of this LDAP schema, together with the use of the ITU-T H.350 CommObject architecture, facilitates the integration of SIP user agents and conferencing devices into the existing enterprise directories;
27、thus allowing the user to perform white page lookups and access clickable dialling supported by SIP devices. The primary reasons for implementing this schema include those listed in ITU-T H.350 (the CommObject class definition) as they apply specifically to the use of SIP UAs, and to facilitate vend
28、ors making SIP services more readily available to their users. The scope of this Recommendation includes recommendations for the architecture to integrate endpoint information for endpoints using SIP into the existing enterprise directories and white pages. The scope of this Recommendation does not
29、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 SIP protocol, but rather to represent the minimal set required to accomplish the design goals enumerated in ITU-T H.350. Note th
30、at SIP provides well-defined methods for discovering registrar addresses and locating users on the network. Some of the attributes defined here are intended for more trivial or manual implementations and may not be needed for all applications. For example, SIPIdentityRegistrarAddress and SIPIdentity
31、Address may not be needed for many applications, but are included here for completeness. Thus, SIPIdentitySIPURI is the primary attribute of interest that will be served out, especially for white page directory applications. 1.1 Extending the schema The SIPIdentity classes may be extended as necessa
32、ry for specific implementations. See the base ITU-T H.350 for a discussion on schema extension. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, th
33、e editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currentl
34、y 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 of a Recommendation. _ 1This Recommendation includes an electronic attachment containing a text file with a schema configuration for SI
35、PIdentity. 2 Rec. ITU-T H.350.4 (05/2011) 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 co
36、ncepts, models and services. 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 Di
37、rectory: Public-key and attribute certificate frameworks. ITU-T X.511 Recommendation ITU-T X.511 (2008) | ISO/IEC 9594-3:2008, Information technology Open Systems Interconnection The Directory: Abstract service definition. ITU-T X.518 Recommendation ITU-T X.518 (2008) | ISO/IEC 9594-4:2008, Informat
38、ion technology Open Systems Interconnection The Directory: Procedures for distributed operation. ITU-T X.519 Recommendation ITU-T X.519 (2008) | ISO/IEC 9594-5:2008, Information technology Open Systems Interconnection The Directory: Protocol specifications. ITU-T X.520 Recommendation ITU-T X.520 (20
39、08) | ISO/IEC 9594-6:2008, Information technology Open Systems Interconnection The Directory: Selected attribute types. ITU-T X.525 Recommendation ITU-T X.525 (2008) | ISO/IEC 9594-9:2008, Information technology Open Systems Interconnection The Directory: Replication. IETF RFC 2069 IETF RFC 2069 (19
40、97), An Extension to HTTP: Digest Access Authentication. IETF RFC 2617 IETF RFC 2617 (1999), HTTP Authentication: Basic and Digest Access Authentication. IETF RFC 3261 IETF RFC 3261 (2002), SIP: Session Initiation Protocol. IETF RFC 4510 IETF RFC 4510 (2006), Lightweight Directory Access Protocol (L
41、DAP): Technical Specification Road Map. IETF RFC 4511 IETF RFC 4511 (2006), Lightweight Directory Access Protocol (LDAP): The Protocol. 3 Definitions This Recommendation defines the following terms: 3.1 client: A SIP client is a network device that initiates SIP requests and receives SIP responses o
42、n a network. 3.2 commObject: An LDAP object class defined in ITU-T H.350 that represents generic multimedia conferencing endpoints. 3.3 endpoint: A logical device that provides video and/or voice media encoding/decoding, and signalling functions. Examples include: 1) a group teleconferencing applian
43、ce that is located in a conference room; 2) an IP telephone; Rec. ITU-T H.350.4 (05/2011) 3 3) a software program that takes video and voice from a camera and microphone and encodes it and applies signalling using a host computer. Note that from the perspective of most signalling protocols, gateways
44、 and MCUs are special cases of endpoints. 3.4 enterprise directory: A canonical collection of information about users in an organization. Typically this information is collected from a variety of organizational units to create a whole. For example, Human Resources may provide name and address, Telec
45、ommunications may provide the telephone number, Information Technology may provide the e-mail address, etc. For the purposes of this architecture, it is assumed that an enterprise directory is accessible via LDAP. 3.5 gateway: A device that translates from one protocol to another. Often gateways tra
46、nslate between the IP network and the public switched voice network to allow integration of the two. 3.6 multipoint control unit (MCU): A device capable of mixing audio/video from multiple endpoints to create a virtual meeting space. 3.7 proxy server, SIP proxy: A server that acts as both a client a
47、nd a server to make requests on behalf of another user agent (UA). The primary role of a proxy server is to ensure that a request generated by a UA is passed to another entity that is closer to the destination user. 3.8 registrar: A registrar is a server that accepts REGISTER requests and places the
48、 information it receives in those requests into the location service for the domain it handles. 3.9 SIP URI: A type of uniform resource identifier (URI) that identifies a communication resource in the session initiation protocol (SIP). A SIP URI usually contains a user name and a host name and is si
49、milar in format to an e-mail address. 3.10 user agent (UA): A device that can function as both a user agent client and server. 3.11 white pages: An application that allows end users to look up the address of another user. 4 Abbreviations This Recommendation uses the following abbreviations: LDAP Lightweight Directory Access Protocol (as defined in IETF RFC 4510) LDIF LDAP Data Interchange Format MCU Multipoint Control Unit SIP Session Initiation Protocol UA Us
