3:29 a.m.
Hi!
I see that core.schema defines:
---
attributetype ( 2.5.4.22 NAME 'teletexTerminalIdentifier'
DESC 'RFC2256: Teletex Terminal Identifier'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.51 )
---
However I cannot locate the syntax for the OID. It's mentioned in secion 6.5 of RFC
2256, however.
How is an LDAP client expected to resolve this?
I see the following syntaxes defines in the LDAP schema:
DB<17> print sort map { $_->{name} . "\n" } $s->all_syntaxes
1.2.36.79672281.1.5.0
1.3.6.1.1.1.0.0
1.3.6.1.1.1.0.1
1.3.6.1.1.16.1
1.3.6.1.4.1.1466.115.121.1.10
1.3.6.1.4.1.1466.115.121.1.11
1.3.6.1.4.1.1466.115.121.1.12
1.3.6.1.4.1.1466.115.121.1.14
1.3.6.1.4.1.1466.115.121.1.15
1.3.6.1.4.1.1466.115.121.1.22
1.3.6.1.4.1.1466.115.121.1.24
1.3.6.1.4.1.1466.115.121.1.26
1.3.6.1.4.1.1466.115.121.1.27
1.3.6.1.4.1.1466.115.121.1.28
1.3.6.1.4.1.1466.115.121.1.34
1.3.6.1.4.1.1466.115.121.1.36
1.3.6.1.4.1.1466.115.121.1.38
1.3.6.1.4.1.1466.115.121.1.39
1.3.6.1.4.1.1466.115.121.1.4
1.3.6.1.4.1.1466.115.121.1.40
1.3.6.1.4.1.1466.115.121.1.41
1.3.6.1.4.1.1466.115.121.1.44
1.3.6.1.4.1.1466.115.121.1.45
1.3.6.1.4.1.1466.115.121.1.49
1.3.6.1.4.1.1466.115.121.1.5
1.3.6.1.4.1.1466.115.121.1.50
1.3.6.1.4.1.1466.115.121.1.52
1.3.6.1.4.1.1466.115.121.1.6
1.3.6.1.4.1.1466.115.121.1.7
1.3.6.1.4.1.1466.115.121.1.8
1.3.6.1.4.1.1466.115.121.1.9
1.3.6.1.4.1.4203.666.11.10.2.1
Regards,
Ulrich
7:49 a.m.
Ulrich Windl wrote:
I see that core.schema defines:
---
attributetype ( 2.5.4.22 NAME 'teletexTerminalIdentifier'
DESC 'RFC2256: Teletex Terminal Identifier'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.51 )
---
However I cannot locate the syntax for the OID. It's mentioned in secion 6.5 of RFC
2256, however.
Don't expect the subschema subentry to be complete. There are likely dangling
references in the subschema.
How is an LDAP client expected to resolve this?
Do you ask for a fully schema-aware generic LDAP client?
It depends on the client and which schema element is actually missing.
BTW: I will present some aspects regarding missing schema elements in my
LDAPcon talk next week.
Why are you digging into this so deeply?
Ciao, Michael.
1:15 a.m.
New subject: Antw: Re: Q: syntax 1.3.6.1.4.1.1466.115.121.1.51
>> Michael Ströder<michael(a)stroeder.com> schrieb am
11.11.2013 um 16:49 in
Nachricht <5280FC93.4090408(a)stroeder.com>:
Ulrich Windl wrote:
> I see that core.schema defines:
> ---
> attributetype ( 2.5.4.22 NAME 'teletexTerminalIdentifier'
> DESC 'RFC2256: Teletex Terminal Identifier'
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.51 )
> ---
>
> However I cannot locate the syntax for the OID. It's mentioned in secion
6.5
of RFC 2256, however.
Don't expect the subschema subentry to be complete. There are likely
dangling
references in the subschema.
> How is an LDAP client expected to resolve this?
Do you ask for a fully schema-aware generic LDAP client?
I am writing an LDAP client at the moment ;-) I'd like my client to provide a
description of each object class, attribute, attribute type, and possible
allowed lengths.
Talking about lenghts: A few attributes seem to have rather arbitrary lengths
(e.g. cn=32768, description=1024), while others have none.
It depends on the client and which schema element is actually
missing.
BTW: I will present some aspects regarding missing schema elements in my
LDAPcon talk next week.
Why are you digging into this so deeply?
Start well, improve, until perfect ;-)
Ciao, Michael.
Regards,
Ulrich
1:28 a.m.
Ulrich Windl wrote:
>>> Michael Ströder<michael(a)stroeder.com> schrieb am
11.11.2013 um 16:49 in
Nachricht <5280FC93.4090408(a)stroeder.com>:
> Ulrich Windl wrote:
>> I see that core.schema defines:
>> ---
>> attributetype ( 2.5.4.22 NAME 'teletexTerminalIdentifier'
>> DESC 'RFC2256: Teletex Terminal Identifier'
>> SYNTAX 1.3.6.1.4.1.1466.115.121.1.51 )
>> ---
>>
>> However I cannot locate the syntax for the OID. It's mentioned in secion
6.5
> of RFC 2256, however.
>
> Don't expect the subschema subentry to be complete. There are likely
> dangling
> references in the subschema.
>
>> How is an LDAP client expected to resolve this?
>
> Do you ask for a fully schema-aware generic LDAP client?
I am writing an LDAP client at the moment ;-) I'd like my client to provide a
description of each object class, attribute, attribute type, and possible
allowed lengths.
Then you should probably dig into ietf-ldapbis mailing list archives. I
suspect that question you will ask were already asked by myself, most times on
ldapbis.
Talking about lenghts: A few attributes seem to have rather arbitrary
lengths
(e.g. cn=32768, description=1024), while others have none.
It's the so-called "minimum upper bound". It's rather useless for UI.
> It depends on the client and which schema element is actually
missing.
>
> BTW: I will present some aspects regarding missing schema elements in my
> LDAPcon talk next week.
>
> Why are you digging into this so deeply?
Start well, improve, until perfect ;-)
I'm looking forward to your implementation. You should test it with many servers.
But you should really consider whether you want to waste so much spare time on
it. Being the author of web2ldap I really know how much time it takes. It's a
little better today because server implementations are much more LDAPv3
compliant than they used to be.
Ciao, Michael.
3609
days inactive
3610
days old
openldap-technical@openldap.org
3 comments
2 participants
participants (2)
-
Michael Ströder -
Ulrich Windl