C.1.2 commObject (H.350)

OID: 0.0.8.350.1.1.2.2.1

objectclasses: (0.0.8.350.1.1.2.2.1

NAME 'commObject'

DESC 'object that contains the Communication attributes'

SUP top STRUCTURAL

MUST commUniqueId

MAY ( commOwner $ commPrivate )

)

DEFINITION & USE:

 
Abstraction of video or voice over IP device. The commObject class permits an endpoint (H.323 endpoint or SIP user agent or other protocol endpoint) and all their aliases to be represented by a single entry in a directory. Each directory entry should contain commObject as the entry's structural object class; that entry may also contain H.350.X auxiliary classes.

C.1.2.1 commUniqueId

OID: 0.0.8.350.1.1.2.1.1

attributetypes: (0.0.8.350.1.1.2.1.1

NAME 'commUniqueId'

DESC 'To hold the endpoints unique Id'

EQUALITY caseIgnoreIA5Match

SUBSTR caseIgnoreIA5SubstringsMatch

SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )

DEFINITION & USE:

 
The endpoint's unique ID. This is the real distinguished name (RDN)of this object. In practice, there will always be one and only one commUniqueId for every endpoint. This attribute uniquely identifies an 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; it may however be handy to use the enterprise distinguished name as part of commUniqueId..

NUMBER OF VALUES:

 
multi

INDEXING PROFILE:

 
equality

EXAMPLES (LDIF FRAGMENTS):

 
commUniqueId: Device4321 
commUniqueId: jilltaylor003

C.1.2.2 commOwner

OID: 0.0.8.350.1.1.2.1.2

attributetypes: 0.0.8.350.1.1.2.1.2

NAME 'commOwner'

DESC 'Labeled URI to point back to the original owner'

EQUALITY caseExactMatch

SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

DEFINITION & USE:

 
Labelled URI format to point back to the person or resource object associated with this entry. Used as a reverse entry finder of the owner(s). This attribute may point to groups. Note that this URI can point to a cn, but applications that want to bind authentication information across both the commObject and enterprise directories should points to a dn rather than a cn, thus uniquely identifying the owner of the commObject.

NUMBER OF VALUES:

 
multi

INDEXING PROFILE:

 
presence

EXAMPLE (LDIF FRAGMENT):

 
commOwner: ldap://dir.acme.com/dc=acme,dc=com??sub?(dn=rsmith42) 
commOwner: uid=rsmith42,ou=people,dc=acme,dc=com

C.1.2.3 commPrivate

OID: 0.0.8.350.1.1.2.1.3

attributetypes: (0.0.8.350.1.1.2.1.3

NAME 'commPrivate'

DESC 'To decide whether the entry is visible to world or not'

SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )

DEFINITION & USE:

 
To be used by the user and indicate privacy options for an endpoint, i.e. unlisted number. This attribute is defined as Boolean. Future version of this Recommendation may develop a controlled vocabulary for this attribute to accommodate multiple types of privacy.

The iPlanet ACI rules can be set to check the value of the commPrivate attribute to determine whether it should be hidden. This feature is not available in OpenLDAP's ACI syntax.

NUMBER OF VALUES:

 
multi

INDEXING PROFILE:

 
presence

EXAMPLE (LDIF FRAGMENT):

 
commPrivate: true