RFC 3944:H.350 Directory Services
RFC-Ref

enterprise director


Click on the red underlined text to get to the source

... leverage existing identity management and enterprise directories. A particular goal is to enable an enterprise or service provider to ...


... computer. * enterprise directory: A canonical collection of information about users in an organization. Typically this information is collected ...
... email address, etc. For the purposes of this architecture, it is assumed that an enterprise directory is accessible via LDAP. ...


... implementation considerations for the inter-relation of video and voice-specific directories, enterprise directories, call servers and endpoints. ...
... resources can be associated with endpoints. The only change required in the enterprise directory is the addition of the simple object class commURI. CommObject data may be instantiated in the same or in entirely separate directories, thus allowing flexibility in ...
... administrators need call servers that are aware of enterprise directories to avoid duplication of account management processes. Users need 'white pages ...
... that endpoints can be managed through manipulations of an enterprise directory, rather than by direct entry into the call server; ...
... portals" that allow searching for users across multiple institutional directories. In this application, each enterprise directory registers itself with (or is unknowingly discovered by) a directory of ...
... attributes to be included; 9) be non-invasive to the enterprise directory, so that support for multimedia conferencing can be added in a modular fashion ...
... multimedia conferencing can be added in a modular fashion without significant changes to the enterprise directory. The scope of this Recommendation does not include extensions of ...
... endpoint in the commObject directory. It must be unique within that directory, but need not be unique globally. This attribute has no relationship to the enterprise directory. Semantics ...
... applications where it is desired to bind authentication information across both the commObject and enterprise directories, it may be desirable that commOwner points to a dn rather than a cn, thus uniquely identifying the owner of the commObject. ...


... H.350 CommObject architecture, facilitates the integration of SIP User Agents and conferencing devices into existing Enterprise Directories, thus allowing the user to perform white page lookups and ...
... endpoints using SIP into existing enterprise directories and white pages. ...



Google
Web
RFC-Ref