RE: ASN.1 definitions in draft-ietf-ldapbis-syntaxes-01.txt

["Timothy Hahn" <hahnt@us.ibm.com>]

Steven,

There's an extension capability for additional information in these things.
Where do you see that being placed?

I would suggest:

    LDAPSchemaDefinition ::= SEQUENCE {
        identifier      OBJECT IDENTIFIER,
        name            SET OF DirectoryString { ub-schema } OPTIONAL,
        obsolete        BOOLEAN DEFAULT FALSE,
        information     LDAPSchemaInformation
        extensions      LDAPSchemaExtensions
    }

    LDAPSchemaExtensions ::= SEQUENCE OF SEQUENCE {
        extensionType   DirectoryString,
        extensionValues SEQUENCE OF DirectoryString
    }

I realize that these don't quite apply to RFC2252bis, but in hopes that
ASN.1 for these is defined at some point, I figured you'd like the
feedback.

Regards,
Tim Hahn

Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388     tie-line: 8/852.6388
fax: 607.752.3681



                                                                                                                                          
                      "Steven Legg"                                                                                                       
                      <steven.legg@adacel.        To:       "'Jim Sermersheim'" <JIMSE@novell.com>, <IETF-LDAPbis@OpenLDAP.org>           
                      com.au>                     cc:                                                                                     
                      Sent by:                    Subject:  RE: ASN.1 definitions in draft-ietf-ldapbis-syntaxes-01.txt                   
                      owner-ietf-ldapbis@O                                                                                                
                      penLDAP.org                                                                                                         
                                                                                                                                          
                                                                                                                                          
                      03/04/2002 06:18 PM                                                                                                 
                      Please respond to                                                                                                   
                      steven.legg                                                                                                         
                                                                                                                                          
                                                                                                                                          




Jim,

Jim Sermersheim wrote:
> Also, there are many multipart syntaxes that lack an ASN.1 definition,
> do we plan to define the ASN.1 for these?

In reviewing the LDAP syntaxes some time ago I found ASN.1 type
definitions for all but three syntaxes. These were:

             LDAP Syntax Description - 1.3.6.1.4.1.1466.115.121.1.54
             LDAP Schema Definition  - 1.3.6.1.4.1.1466.115.121.1.56
             LDAP Schema Description - 1.3.6.1.4.1.1466.115.121.1.57

I proposed this ASN.1 type for LDAP Syntax Description:

    LDAPSyntaxDescription ::= SEQUENCE {
        identifier       OBJECT IDENTIFIER,
        description      DirectoryString { ub-schema } OPTIONAL
    }

I proposed this ASN.1 type for LDAP Schema Definition:

    LDAPSchemaDefinition ::= SEQUENCE {
        identifier      OBJECT IDENTIFIER,
        name            SET OF DirectoryString { ub-schema } OPTIONAL,
        obsolete        BOOLEAN DEFAULT FALSE,
        information     LDAPSchemaInformation
    }

    LDAPSchemaInformation ::= SEQUENCE {
        imports         [0] SET SIZE (1..MAX) OF OBJECT IDENTIFIER
OPTIONAL,
        classes         [1] SET SIZE (1..MAX) OF OBJECT-CLASS.&id OPTIONAL,
        attributes      [2] SET SIZE (1..MAX) OF ATTRIBUTE.&id OPTIONAL,
        matching-rules  [3] SET SIZE (1..MAX) OF MATCHING-RULE.&id
OPTIONAL,
        syntaxes        [4] SET SIZE (1..MAX) OF OBJECT IDENTIFIER OPTIONAL
    }

If the group agrees, Kathy and I can put these definitions, plus all the
others I've found, into the syntaxes I-D.

Consensus on LDAP Schema Description was to remove it since it has no
defined native or binary encoding, and no-one implements it.

Regards,
Steven