[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: I-D ACTION:draft-klasen-ldap-facs-tel-number-matching-00.txt



Hallavard,

--On Donnerstag, 8. Mai 2003 18:07 +0200 Hallvard B Furuseth <h.b.furuseth@usit.uio.no> wrote:

I wrote:
Steven Legg writes:

The assertion syntax for facsimileNumberMatch is TelephoneNumber, i.e. SYNTAX 1.3.6.1.4.1.1466.115.121.1.50 . The assertion syntax for facsimileNumberSubstringsMatch is SubstringAssertion, i.e. SYNTAX 1.3.6.1.4.1.1466.115.121.1.58 .

The '$' separators in fax-numbers are just treated as plain characters when matching?

The point is that these matching rules only act on the telephone number part of a Facsimile Telephone Number. So only characters before the first '$' are taken into account when matching. That is why the ASSERTION syntax is TelephoneNumber.


Hold on.  According to the Syntaxes draft, TelephoneNumber is a
PrintableString, and PrintableString doesn't allow '$'.  Me not
understand...

Take as example the following entry: dn: o=avinci objectclass: organization o: avinci facsimileTelephoneNumber: +49 2102 124 555 $fineResolution$a3Width

Now, searching for "facsimileTelephoneNumber=+49-2102-124-555" would match this entry, as
- only the telephone-number part, ie. "+49 2102 124 555 " of the attribute value is taken into account
- and the assertion value "+49-2102-124-555" matches the attribute value
"+49 2102 124 555 " by the telephone number matching rule, ie. ignoring
the case of letters, and ignoring space and `-' characters.


I think adding this example and a copy of the ABNF from the definition of the Facsimile Telephone Number syntax to the draft should make things a lot clearer.

Norbert