AKBKHOME Consulting Services Available : Linux, Embedded Linux, C, PHP and PHP-GTK, just Contact me at alan@akbkhome.com 
LDAP Schema | AKBK Home >>>
ldap objectclass
AKBK Home :: LDAP :: Attributes :: mobile

Attribute:  mobile 

Description:
Note: RFC 1274 uses the longer name 'mobileTelephoneNumber'.

BNC Syntax: 0.9.2342.19200300.100.1.41 NAME 'mobile' EQUALITY telephoneNumberMatch Used By: inetOrgPerson

Syntax: Telephone Number

ID : 1.3.6.1.4.1.1466.115.121.1.50
Values in this syntax are encoded as if they were Printable String types. Telephone numbers are recommended in X.520 to be in international form, as described in E.123 [15].

Example:

+1 512 305 0280

 
BNC Syntax:

Equality Matching: telephoneNumberMatch

Description:

Servers SHOULD be capable of performing the following matching rules.

For all these rules, the assertion syntax is the same as the value syntax.

When performing the caseIgnoreMatch, caseIgnoreListMatch, telephoneNumberMatch, caseExactIA5Match and caseIgnoreIA5Match, multiple adjoining whitespace characters are treated the same as an individual space, and leading and trailing whitespace is ignored.

Clients MUST NOT assume that servers are capable of transliteration of Unicode values.

BNC Syntax: 

Substring Matching: telephoneNumberSubstringsMatch

Description:

The Substring Assertion is encoded according to the following BNF:

      substring = [initial] any [final]
      initial = value
      any = "*" *(value "*")
      final = value

The production is UTF-8 encoded string. Should the backslash or asterix characters be present in a production of , they are quoted as described in section 4.3.

Servers SHOULD be capable of performing the following matching rules, which are used in substring filters.

BNC Syntax:


 





Contact me at alan@akbkhome.com - especially if you have some work for me :)