C.1.6 sipIdentity (H.350.4)

OID: 0.0.8.350.1.1.6.2.1

objectclasses: (0.0.8.350.1.1.6.2.1

NAME 'SIPIdentity'

DESC 'SIPIdentity object'

SUP top AUXILIARY

MAY ( SIPIdentitySIPURI $ SIPIdentityRegistrarAddress $

SIPIdentityProxyAddress $ SIPIdentityUserName $

SIPIdentityPassword $ SIPIdentityServiceLevel $

userSMIMECertificate )

)

DEFINITION & USE:

 
The SIPIdentity object class represents SIP User Agents (UAs). It is an auxiliary class and is derived from the commObject class and is used to represent SIP User Agents (UAs) on the network and associate those endpoints with users.

C.1.6.1 SIPIdentitySIPURI

OID: 0.0.8.350.1.1.6.1.1

attributetypes: (0.0.8.350.1.1.6.1.1

NAME 'SIPIdentitySIPURI'

DESC 'Universal Resource Indicator of the SIP UA'

EQUALITY caseExactMatch

SUBSTR caseExactSubstringsMatch

SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

DEFINITION & USE:

 
Uniform Resource Identifier that identifies a communication resource in SIP- usually contains a user name and a host name and is often similar in format to an email address. This URI may institute SIP or SIPS (secure). In the event that SIPS is instituted, the URI must reflect that it is using SIPS as opposed to SIP. See Examples below.

NUMBER OF VALUES:

 
multi

INDEXING PROFILE:

 
equality

EXAMPLE APPLICATION USING ATTRIBUTE:

 
Online representation of most current listing of a user's SIP(S) UA.

EXAMPLE (LDIF FRAGMENT):

 
SIPIdentitySIPURI: sip:alice@foo.com // SIP example 
SIPIdentitySIPURI: sip:alice@152.2.158.212 // SIP example 
SIPIdentitySIPURI: sips:bob@birmingham.edu // SIPS example

C.1.6.2 SIPIdentityRegistrarAddress

OID: 0.0.8.350.1.1.6.1.2

attributetypes: (0.0.8.350.1.1.6.1.2

NAME 'SIPIdentityRegistrarAddress'

DESC 'specifies the location of the registrar'

EQUALITY caseIgnoreIA5Match

SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )

DEFINITION & USE:

 
Address for the domain to which the server that handles REGISTER requests and forwarding to the location server for a particular domain belongs. Note that RFC 3261 states that user agents can discover their registrar address by configuration, using the address-of-record, or by multicast. The first scenario, by configuration, is noted as out of scope for RC 3261. This attribute may be used for the first scenario. It can be accomplished manually, (e.g. a web page that displays a user's correct registrar address) or automatically with an H.350.4 aware user agent.

NUMBER OF VALUES:

 
multi

EXAMPLE APPLICATION USING ATTRIBUTE:

 
white pages, a web page that displays a user's correct configuration information.

EXAMPLE (LDIF FRAGMENT):

 
SIPIdentityRegistrarAddress: 152.2.15.22 //IP address example 
SIPIdentityRegistrarAddress: sipregistrar.unc.edu //FQDN example 
SIPIdentityRegistrarAddress: 152.2.15.22:1785 //Specify PORT example

INDEXING PROFILE:

 
no recommendation

C.1.6.3 SIPIdentityProxyAddress

OID: 0.0.8.350.1.1.6.1.3

attributetypes: (0.0.8.350.1.1.6.1.3

NAME 'SIPIdentityProxyAddress'

DESC 'Specifies the location of the SIP Proxy'

EQUALITY caseIgnoreIA5Match

SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )

DEFINITION & USE:

 
Address that specifies the domain location of SIP proxy within a domain. RFC 3261 defines the role of the SIP proxy. SIP User Agents are not required to use a proxy, but will in many cases.

NUMBER OF VALUES:

 
multi

EXAMPLE APPLICATION USING ATTRIBUTE:

 
white pages, a web page that displays a user's correct configuration information.

EXAMPLE (LDIF FRAGMENT):

 
SIPIdentityProxyAddress: 172.2.13.234 //IP address example 
SIPIdentityProxyAddress: sipproxy.unc.edu //FQDN example

INDEXING PROFILE:

 
no recommendation

C.1.6.4 SIPIdentityAddress

OID: 0.0.8.350.1.1.6.1.4

attributetypes: (0.0.8.350.1.1.6.1.4

NAME 'SIPIdentityAddress'

DESC 'IP address or FQDN of the UA'

EQUALITY caseIgnoreIA5Match

SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )

DEFINITION & USE:

 
Specifies the IP address or fully qualified domain name of the UA. This attribute may be useful for applications in which UA to UA communication is direct, not involving a proxy or registrar.

NUMBER OF VALUES:

 
multi

EXAMPLE APPLICATION USING ATTRIBUTE:

 
A web page that displays a user's proper user agent configuration information.

EXAMPLE (LDIF FRAGMENT):

 
SIPIdentityAddress: 152.2.121.36 // IP address example 
SIPIdentityAddress: ipPhone.foo.org // FQDN example

INDEXING PROFILE:

 
equality

C.1.6.5 SIPIdentityPassword

OID: 0.0.8.350.1.1.6.1.5

attributetypes: (0.0.8.350.1.1.6.1.5

NAME 'SIPIdentityPassword'

DESC 'The user agent SIP password '

EQUALITY octetStringMatch

SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 )

DEFINITION & USE:

 
The SIP user agent's password, used for the HTTP digest authentication scheme as defined in RFC 2617. Because RFC 2069, which was made obsolete by RFC 2617, was used as the basis for HTTP Digest in RFC 2543, any SIP servers supporting RFC 2617 must ensure backward compatibility with RFC 2069. SIPIdentityUserName, together with SIPIdentityPassword, are reserved for the purpose of use with Digest Access Authentication, and not intended for use with Basic Authentication methods. LDAP provides one method to store user passwords for reference. If passwords are stored in LDAP it makes the LDAP server a particularly valuable target for attack. Implementers are encouraged to exercise caution and implement appropriate security procedures such as encryption, access control, and transport layer security for access to this attribute. (See further discussion in chapter on Authentication)

NUMBER OF VALUES:

 
multi

INDEXING PROFILE:

 
no recommendation

EXAMPLE (LDIF FRAGMENT):

 
SIPIdentityPassword: 36zxJmCIB18dM0FVAj

C.1.6.6 SIPIdentityUserName

OID: 0.0.8.350.1.1.6.1.6

attributetypes: (0.0.8.350.1.1.6.1.6

NAME 'SIPIdentityUserName'

DESC 'The user agent user name.'

EQUALITY caseIgnoreMatch

SUBSTR caseIgnoreSubstringsMatch

SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

DEFINITION & USE:

 
The SIP user agent's user name, used for the HTTP digest authentication scheme as defined in RFC 2617. Note that in many cases the user name will be parsed from the user@proxy.domain portion of the SIP URI. In that case it may not be necessary to populate this attribute. Because RFC 2069, which was made obsolete by RFC 2617, was used as the basis for HTTP Digest Authentication in RFC 2543, any SIP servers supporting HTTP Digest Authentication as defined in RFC 2617 must ensure backward compatibility with RFC 2069. This SIPIdentityUserName, together with SIPIdentityPassword, are reserved for the purpose of use with Digest Access Authentication, and not intended for use with Basic Authentication methods.

NUMBER OF VALUES:

 
multi

INDEXING PROFILE:

 
equality

EXAMPLE (LDIF FRAGMENT):

 
SIPIdentityUserName: nelkhour

C.1.6.7 SIPIdentityServiceLevel

OID: 0.0.8.350.1.1.6.1.7

attributetypes: (0.0.8.350.1.1.6.1.7

NAME 'SIPIdentityServiceLevel'

DESC 'To define services that a user can belong to.'

EQUALITY caseIgnoreIA5Match

SUBSTR caseIgnoreIA5SubstringsMatch

SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )

DEFINITION & USE:

 
This describes the level of services a user can belong to. This attribute does not represent a data element found in SIP; SIP itself does not support distinctions in service levels. Instead, this attribute provides a mechanism for the storage of locally meaningful service level information directly in LDAP. This mapping allows service providers to adapt to an existing LDAP directory without changing the values of the SIPIdentityServiceLevel instances in the directory.

NUMBER OF VALUES:

 
multi

INDEXING PROFILE:

 
equality

EXAMPLE (LDIF FRAGMENT):

 
SIPIdentityServiceLevel: premium