Re: Object identifiers and ASN.1 syntax

2000-10-26 Thread Kevin Blanchard
[EMAIL PROTECTED] Subject: Re: Object identifiers and ASN.1 syntax Date: Tue, 03 Oct 2000 21:31:40 +0100 Message-ID: [EMAIL PROTECTED] drh Richard Levitte - VMS Whacker wrote: drh drh drh I'm trying to make a simple perl script that is capable of parsing drh through an ASN.1 module

Re: Object identifiers and ASN.1 syntax

2000-10-03 Thread Rich Salz
One can see definitions like this: { iso standard 8571 abstract-syntax (2) } The names aren't flat. To find out the number for "standard", you ask iso. To find out the number of abstract-syntax, you ask the entity that maintains "8571" (you might have to ask "standard" who that is).

Re: Object identifiers and ASN.1 syntax

2000-10-03 Thread Dr S N Henson
Richard Levitte - VMS Whacker wrote: I'm trying to make a simple perl script that is capable of parsing through an ASN.1 module embedded in any document an extracting the OIDs from it. When I'm done with that, I'll extend it to be able to parse LDAP schemas entries as in RFC2256. Then

Re: Object identifiers and ASN.1 syntax

2000-10-03 Thread Ben Laurie
Richard Levitte - VMS Whacker wrote: From: Rich Salz [EMAIL PROTECTED] Subject: Re: Object identifiers and ASN.1 syntax Date: Tue, 03 Oct 2000 14:43:05 -0400 Message-ID: [EMAIL PROTECTED] rsalz One can see definitions like this: rsalz rsalz { iso standard 8571 abstract

Re: Object identifiers and ASN.1 syntax

2000-10-03 Thread Ben Laurie
Ben Laurie wrote: What I'm trying to figure out is how I will best get together all the information from reading a number of ASN.1 modules. I'm wondering for example how "standard" is defined. Is it something like this? standard OBJECT IDENTIFIER ::= { iso 0 } Or is it:

Re: Object identifiers and ASN.1 syntax

2000-10-03 Thread Ben Laurie
Rich Salz wrote: One can see definitions like this: { iso standard 8571 abstract-syntax (2) } The names aren't flat. To find out the number for "standard", you ask iso. To find out the number of abstract-syntax, you ask the entity that maintains "8571" (you might have to ask

Re: Object identifiers and ASN.1 syntax

2000-10-03 Thread Richard Levitte - VMS Whacker
From: Ben Laurie [EMAIL PROTECTED] ben BTW, if I'm understanding correctly, what you write is: ben ben iso.standard OBJECT IDENTIFIER ::= { 0 } ben ben or something to that effect... OK, that starts to make sense. Now to figure out the most efficient way to parse a OID value... --

Re: Object identifiers and ASN.1 syntax

2000-10-03 Thread Richard Levitte - VMS Whacker
From: Ben Laurie [EMAIL PROTECTED] ben BTW, are the ways of asking "standard", "iso" and "8571" about ben each other known? Or is that all part of the game? If I understand correctly, it's "all part of the game"... ben Can we write a daemon that does this (I have this vision of one ben of its

Re: Object identifiers and ASN.1 syntax

2000-10-03 Thread Richard Levitte - VMS Whacker
From: Dr S N Henson [EMAIL PROTECTED] Subject: Re: Object identifiers and ASN.1 syntax Date: Tue, 03 Oct 2000 21:31:40 +0100 Message-ID: [EMAIL PROTECTED] drh Richard Levitte - VMS Whacker wrote: drh drh drh I'm trying to make a simple perl script that is capable of parsing drh through

Re: Object identifiers and ASN.1 syntax

2000-10-03 Thread rsalz
BTW, are the ways of asking "standard", "iso" and "8571" about each other known? Or is that all part of the game? you have to go to each registrar (arc owner) in turn. the means of getting name/numbers can be very formal, or wildly informal. /r$