[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: String Encodings - was RE: Applicability Stmt (AS) rescinding "IESG Note" and defining "LDAPv3"
> It's a shame the LDAP string encodings for attribute values weren't
> defined by some algorithmic relationship to the ASN.1 type of the
> syntax, much like the way ASN.1 value notation is related to the type.
> It wouldn't then be necessary to define a string encoding for each new
> attribute value syntax or assertion value syntax imported from X.500,
> X.509, etc. The required string encoding would fall out naturally from
> the relevant ASN.1 type.
How right you are. I have noticed this when writing the latest
schema ID for PKIX.
>
> It's never too late to start though.
>
I could really do with a BNF wiz kid to help me do this on the PKIX
schema. Are you such a person?
David
> Regards,
> Steven
>
>
***************************************************
David Chadwick
IS Institute, University of Salford, Salford M5 4WT
Tel +44 161 295 5351 Fax +44 161 745 8169
Mobile +44 790 167 0359
Email D.W.Chadwick@salford.ac.uk
Home Page http://www.salford.ac.uk/its024/chadwick.htm
Understanding X.500 http://www.salford.ac.uk/its024/X500.htm
X.500/LDAP Seminars http://www.salford.ac.uk/its024/seminars.htm
Entrust key validation string MLJ9-DU5T-HV8J
***************************************************