RFC 3944:H.350 Directory Services
RFC-Ref

service


Click on the red underlined text to get to the source

... created the H.350 series of Recommendations that specify directory services architectures in support of multimedia conferencing protocols. The goal of the architecture is to ...
... architecture is to 'directory enable' multimedia conferencing so that these services can leverage existing identity management ...
... management and enterprise directories. A particular goal is to enable an enterprise or service provider to maintain a canonical source of users and their multimedia conferencing ...
... H.350 - Directory Services Architecture for Multimedia Conferencing H.350 ...
... Multimedia Conferencing H.350.1 - Directory Services Architecture for H.323 H.350 ...
... H.323 H.350.2 - Directory Services Architecture for H.235 H.350.3 - Directory Services Architecture ...
... Directory Services Architecture for H.235 H.350.3 - Directory Services Architecture for H.320 H.350.4 - Directory Services Architecture ...
... Directory Services Architecture for H.320 H.350.4 - Directory Services Architecture for SIP H.350 ...
... SIP H.350.5 - Directory Services Architecture for Non-Standard Protocols Because SIP ...


... This Recommendation describes a directory services architecture for multimedia conferencing using LDAP ...
... multimedia conferencing using LDAP. Standardized directory services can support association of persons with endpoints ...
... endpoints, searchable white pages, and clickable dialling. Directory services can also assist in the configuration of endpoints ...
... important aspect of large scale multimedia conferencing environments. Without a common data source, service providers must create separate processes to manage each of these functions. By standardizing the ...
... Management of endpoint configurations can be improved if the correct settings are stored by the service provider in a location that is accessible to both service provider and endpoint ...
... settings are stored by the service provider in a location that is accessible to both service provider and endpoint. LDAP provides a ...
... deployments of IP video and voice services have demonstrated the need for complementary directory services ...
... voice services have demonstrated the need for complementary directory services middleware. Service administrators ...
... demonstrated the need for complementary directory services middleware. Service administrators need call servers that are aware ...
... In fact, each commURI instance could point to an endpoint managed by a different service provider. ...


... This Recommendation describes an LDAP directory services architecture for multimedia conferencing ...
... vendors making SIP services more readily available to their users. The scope of this Recommendation includes recommendations for the ...
... attributetypes: (0.0.8.350.1.1.6.1.7 NAME 'SIPIdentityServiceLevel' DESC 'To define services that a user can belong to.' EQUALITY caseIgnoreIA5Match ...
... multi Definition This describes the level of services a user can belong to. Permissible values (if controlled) Notes ...
... SIP. SIP itself does not support distinctions in service levels. Instead, this attribute provides a mechanism for the storage of service level ...
... SIP itself does not support distinctions in service levels. Instead, this attribute provides a mechanism for the storage of service level information directly in LDAP. This mapping allows service providers ...
... service level information directly in LDAP. This mapping allows service providers to adapt to an existing LDAP directory without changing the values ...
... attributetypes: (0.0.8.350.1.1.6.1.7 NAME 'SIPIdentityServiceLevel' DESC 'To define services that a user can belong to.' EQUALITY caseIgnoreIA5Match ...


... ITU-T Recommendation H.350, "Directory services architecture for multimedia conferencing", 2003. ...
... ITU-T Recommendation H.350.4, "Directory services architecture for SIP", 2003. ...
... ITU-T Recommendation H.350.1, "Directory services architecture for H.323", 2003. ...
... ITU-T Recommendation H.350.2, "Directory services architecture for H.235", 2003. ...
... ITU-T Recommendation H.350.3, "Directory services architecture for H.320", 2003. ...
... ITU-T Recommendation H.350.5, "Directory services architecture for Non-Standard Protocols", 2003. ...
... ITU-T Recommendation H.350.6, "Directory services architecture for Call Forwarding and Preferences", 2004. ...
... Howes T. and M. Smith, "Understanding And Deploying LDAP Directory Services", New Riders Publishing, ISBN: 1578700701, 1999. ...


... For some background information on the ITU and IETF directory service protocols, reading [8], [9 ...



Google
Web
RFC-Ref