H.350 Directory Services
RFC 3944, “H.350 Directory Services”, is an Informational document published in December 2004 by T. Johnson, S. Okubo, S. Campos. The canonical text is published by the RFC Editor.
Abstract
The International Telecommunications Union Standardization Sector (ITU-T) has 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 'directory enable' multimedia conferencing so that these services can leverage existing identity 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 systems, so that multiple call servers from multiple vendors, supporting multiple protocols, can all access the same data store. Because SIP is an IETF standard, the contents of H.350 and H.350.4 are made available via this document to the IETF community. This document contains the entire normative text of ITU-T Recommendations H.350 and H.350.4 in sections 4 and 5, respectively. The remaining sections are included only in this document, not in the ITU-T version. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3944 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3943 Transport Layer Security Protocol Compression Using Lempel- Ziv-Stac
- RFC 3945 Generalized Multi-Protocol Label Switching Architecture
- RFC 3942 Reclassifying Dynamic Host Configuration Protocol version 4 Options
- RFC 3946 Generalized Multi-Protocol Label Switching Extensions for Synchronous Optical Network and Synchronous Digital Hierarchy Control
- RFC 3941 Negative-Acknowledgment -Oriented Reliable Multicast Building Blocks
- RFC 3940 Negative-acknowledgment -Oriented Reliable Multicast Protocol
- RFC 3939 Calling Line Identification for Voice Mail Messages
- RFC 3938 Video-Message Message-Context