H.350
Click on the red underlined text to get to the source
... (ITU-T) has created the H.350 series of Recommendations that specify
directory services architectures in support of multimedia
conferencing ...
... store.
H.350 architectures are not intended to change the operation of
multimedia conferencing ...
... manner.
In the H.350 series, Recommendation H.350 specifies the base
architecture and object classes ...
...
In the H.350 series, Recommendation H.350 specifies the base
architecture and object classes, while subordinate Recommendations
...
... Currently, the Recommendations include:
H.350 - Directory Services Architecture for Multimedia Conferencing
...
... Directory Services Architecture for Multimedia Conferencing
H.350.1 - Directory Services Architecture for H.323
...
... Directory Services Architecture for H.323
H.350.2 - Directory Services Architecture for H.235
H.350 ...
... H.350.2 - Directory Services Architecture for H.235
H.350.3 - Directory Services Architecture for H.320
H.350.4 ...
... H.350.3 - Directory Services Architecture for H.320
H.350.4 - Directory Services Architecture for SIP
...
... Directory Services Architecture for SIP
H.350.5 - Directory Services Architecture for Non-Standard Protocols
...
... 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 ...
... SIP is an IETF standard, the contents of H.350 and H.350.4
are made available via this document to the IETF community.
...
... H.350 ...
...
The normative text of H.350 is reproduced in this section.
...
... SRV records for obtaining registration server
addresses. Therefore, H.350 should be viewed not as an authoritative
endpoint configuration architecture ...
... tool that can
assist with this task. Note that the use of H.350 has as a feature
endpoint specific configuration, where it is desirable that each
...
... specific protocols, such as H.323, H.235, or H.320,
as described in the H.350.x series of Recommendations. Multiple
H.350.x classes ...
... as described in the H.350.x series of Recommendations. Multiple
H.350.x classes can be combined to represent endpoints that support
...
... endpoints that support H.323,
H.235 and H.320 would include H.350, H.350.1, H.350.2, and H.350 ...
... H.350, H.350.1, H.350.2, and H.350.3 in
their LDAP representations. Further, each entry should contain
...
...
H.350 object classes may be extended as necessary for specific
implementations. For example, a class ...
... as part of the Recommendation and do not signify compliance.
In some cases it may be necessary to extend the H.350 schemas in
order to represent more information than is supported by the
Recommendations. This may be important for developers that implement
...
... created attributes. This
example also uses ITU-T Rec. H.350.1 for h323Identity.
dn: commUniqueId=2000,ou=h323identity, dc=company ...
... Note that this example and approach demonstrate extension of the
general commObject object class, and not any individual H.350.x
classes. If it is desired to extend an H.350 ...
... H.350.x
classes. If it is desired to extend an H.350.x auxiliary class, then
that should be accomplished through the definition of additional
...
... endpoint that utilizes the new
auxiliary class and attributes. This example also uses H.350.1 for
h323Identity.
...
... contain commObject as the entry's structural object class. That
entry may also contain H.350.x auxiliary classes.
...
... H.350.4 ...
...
The normative text of H.350 is reproduced in this section.
...
... directory architecture as discussed in ITU-T Rec. H.350, and not
intended to be used as a stand-alone architecture. The
...
... implementation of this LDAP schema, together with the use of the
H.350 CommObject architecture, facilitates the integration of SIP
User Agents and conferencing devices into existing Enterprise
Directories ...
... ITU-T
Rec. H.350 (the CommObject class definition) as they apply
specifically to the use of SIP ...
... SIP protocol, but rather to represent the minimal set required
to accomplish the design goals enumerated in ITU-T Rec. H.350.
Note that SIP ...
... classes may be extended as necessary for specific
implementations. See the base of ITU-T Rec. H.350 for a discussion
on schema extension.
...
... displays a user's correct registrar address) or automatically with
an H.350.4 aware user agent.
Semantics ...
... Group 16.
H.350 does not alter the security architectures of any particular
protocol. However, it does offer a standardized place to store
...
... call server have access to the password. Thus, if the call
server or H.350 directory is compromised, passwords also may become
compromised. These weaknesses may be due to weaknesses in the
...
... passwords also may become
compromised. These weaknesses may be due to weaknesses in the
systems (H.350 directory or call servers) and their operation rather
than in H.350 ...
... H.350 directory or call servers) and their operation rather
than in H.350 per se.
The userSMIMECertificate attribute is defined in RFC 2798 ...
...
It is strongly encouraged that call servers and an H.350 directory
mutually authenticate each other before sharing information.
...
... mutually authenticate each other before sharing information.
Further, it is strongly encouraged that communications between H.350
directories and call servers or endpoints ...
... System administrators are
advised to use common sense when setting access control on H.350
attributes. For example, password attributes should only be
...
... ITU-T Recommendation H.350, "Directory services architecture for multimedia conferencing", 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. ...