|
|
| Author |
Message |
|
| Guest |
 Posted: Fri Dec 04, 2009 12:55 pm |
 |
|
|
Guest
|
Hi,
This isa new LDAP ASN.1 spec that I have not seen before.
The previous ones has passed the Erlang ASN.1 compiler without problems.
The Erlang ASN.1 compiler does not support everything in the 2002
standard of ASN.1 and there might also be limitations vs the 1997
standard.
We have implemented the constructs that we have seen need for because
they have occured in specifications used by our customers.
This is the firs time I see use of:
EXSTENSIBILITY IMPLIED, % I will implement that soon, quite easy
SEQUENCE OF NamedType which is equivalent to
SEQUENCE OF identifier Type % I will implement that too,the
identifier is of no real use as I understand it except maybe if the
XML encoding rules and value notation is to be used. And
we don't support them now.
SET OF identifier Type % will implement that too, same as SEQUENCE OF
SEQUENCE SIZE (1..MAX) OF uri URI % I can't see that this is allowed
syntax in any version of ASN.1?
/Kenneth , Erlang/OTP Ericsson
On Sun, Nov 8, 2009 at 4:38 PM, Steve Davis
<steven.charles.davis@gmail.com> wrote:
> While working towards implementing an LDAP server I found that asn1ct does
> not appear to support the current LDAP asn.1 specification format.
>
> http://tools.ietf.org/html/rfc4511#appendix-B
>
> Attached is the modified ASN.1 for LDAP3 with the statements that cause the
> compile time errors commented out as: --##
>
> Of course, the modified asn file defines a protocol that is no longer
> "according to spec"
>
> /s
>
> --## Lightweight-Directory-Access-Protocol-V3 {1 3 6 1 1 18}
> -- Copyright (C) The Internet Society (2006). |
|
|
| Back to top |
|
| Guest |
| Posted: Tue Dec 08, 2009 9:40 pm |
|
|
|
Guest
|
Hi again,
I was a bit quick in the last answer regarding the SEQUENCE SIZE() OF construct.
This construct is already supported, but not the NamedType following
the OF keyword.
This is the same limitation as the plain SEQUENCE OF which also did
not support NamedType.
By the way thanks for the bug-report.
I will correct and add this functionality in the next release.
I also think that your changes in the ASN.1 spec in order to let it
through the compiler is
perfectly ok because they will have no impact on the BER encoding
(which is used in LDAP).
/Kenneth
On Fri, Dec 4, 2009 at 1:52 PM, Kenneth Lundin <kenneth.lundin@gmail.com> wrote:
> Hi,
>
> This isa new LDAP ASN.1 spec that I have not seen before.
> The previous ones has passed the Erlang ASN.1 compiler without problems.
>
> The Erlang ASN.1 compiler does not support everything in the 2002
> standard of ASN.1 and there might also be limitations vs the 1997
> standard.
>
> We have implemented the constructs that we have seen need for because
> they have occured in specifications used by our customers.
>
> This is the firs time I see use of:
>
> EXSTENSIBILITY IMPLIED, % I will implement that |
|
|
| Back to top |
|
| steved |
| Posted: Wed Dec 09, 2009 12:16 am |
|
|
|
User
Joined: 29 Apr 2008
Posts: 78
|
Hi Kenneth,
Thanks for your complete and excellent response to this issue. I'm most
impressed by you and also by your team.
(btw the github move, the beta website, and doc searching is all truly
spectacular and highly appreciated)
Best regards,
Steve
Kenneth Lundin wrote:
> Hi again,
>
> I was a bit quick in the last answer regarding the SEQUENCE SIZE() OF construct.
> This construct is already supported, but not the NamedType following
> the OF keyword.
> This is the same limitation as the plain SEQUENCE OF which also did
> not support NamedType.
>
> By the way thanks for the bug-report.
> I will correct and add this functionality in the next release.
>
> I also think that your changes in the ASN.1 spec in order to let it
> through the compiler is
> perfectly ok because they will have no impact on the BER encoding
> (which is used in LDAP).
>
> /Kenneth
>
> On Fri, Dec 4, 2009 at 1:52 PM, Kenneth Lundin <kenneth.lundin@gmail.com> wrote:
>> Hi,
>>
>> This isa new LDAP ASN.1 spec that I have not seen before.
>> The previous ones has passed the Erlang ASN.1 compiler without problems.
>>
>> The Erlang ASN.1 compiler does not support everything in the 2002
>> standard of ASN.1 and there might also be limitations vs the 1997
>> standard.
>>
>> We have implemented the constructs that we have seen need for because
>> they have occured in specifications used by our customers.
>>
>> This is the firs time I see use of:
>>
>> EXSTENSIBILITY IMPLIED, % I will implement that soon, quite easy
>> SEQUENCE OF NamedType which is equivalent to
>> SEQUENCE OF identifier Type % I will implement that too,the
>> identifier is of no real use as I understand it except maybe if the
>> XML encoding rules and value notation is to be used. And
>> we don't support them now.
>>
>> SET OF identifier Type % will implement that too, same as SEQUENCE OF
>>
>> SEQUENCE SIZE (1..MAX) OF uri URI % I can't see that this is allowed
>> syntax in any version of ASN.1?
>>
>> /Kenneth , Erlang/OTP Ericsson
>>
>> On Sun, Nov 8, 2009 at 4:38 PM, Steve Davis
>> <steven.charles.davis@gmail.com> wrote:
>>> While working towards implementing an LDAP server I found that asn1ct does
>>> not appear to support the current LDAP asn.1 specification format.
>>>
>>> http://tools.ietf.org/html/rfc4511#appendix-B
>>>
>>> Attached is the modified ASN.1 for LDAP3 with the statements that cause the
>>> compile time errors commented out as: --##
>>>
>>> Of course, the modified asn file defines a protocol that is no longer
>>> "according to spec"
>>>
>
________________________________________________________________
erlang-bugs mailing list. See http://www.erlang.org/faq.html
erlang-bugs (at) erlang.org
Post received from mailinglist |
|
|
| Back to top |
 
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
