Re: Syntax Survey Version 2

[Chris Ridd <chris.ridd@messagingdirect.com>]

Steven Legg <steven.legg@adacel.com.au> wrote:
>             OID: 1.3.6.1.4.1.1466.115.121.1.18
>   RFC 2252 NAME: DL Submit Permission
> STRING ENCODING: Section 2.34, RFC 1778
>      ASN.1 TYPE: DLSubmitPermission, ...
>     CONFORMANCE: unspecified
> 
> I haven't got the relevant X.400 standard (yet) to confirm the reference
> for the ASN.1 type.

X.402(1992) has this:

DLSubmitPermission ::= CHOICE {
    individual      [0] ORName,
    member-of-dl    [1] ORName,
    pattern-match   [2] ORNamePattern,
    member-of-group [3] Name }

Incidentally, X.402 actually defines an OID for this syntax:

id-as-mhs-dl-submit-permission ID ::= { 2 6 5 3 0 }

Incidentally what is the purpose of the 'LDAP OID' for this syntax? Does it
merely define the LDAP string representation of these values? If so, why
define LDAP OIDs for the syntaxes like ACI item that don't have a string
representation? Or is that a bug?

>             OID: 1.3.6.1.4.1.1466.115.121.1.33
>   RFC 2252 NAME: MHS OR Address
> STRING ENCODING: Section 4.1, RFC 2156
>                : RFC 2252 references the obsolete RFC 1327
>      ASN.1 TYPE: ORAddress, ...
>     CONFORMANCE: SHOULD, Section 6, RFC 2252
> 
> I haven't got the relevant X.400 standard (yet) to confirm the reference
> for the ASN.1 type.

The ASN.1 definition for ORAddress (and ORName, see DLSubmitPermission) is
found in X.411(1992). It's a bit too big to include here :-)

It also has a syntax OID specified for it:

id-as-mhs-or-address ID ::= { 2 6 5 3 1 } 

Cheers,

Chris