CSIv2 1.0 NO IDEA Avatar
  1. OMG Issue

CSIV2 — OIDs

Open Closed All
  • Key: CSIV2-12
  • Legacy Issue Number: 4143
  • Status: closed  
  • Source: Syracuse University ( Polar Humenn)
  • Summary:

    There is a need to define OIDs, at least one for GSSUP. However, an OID is
    represented by a sequence of positive integers, encoded as a octet
    sequence. The encoding has the property that two encodings are equivalent
    if and only if their definitions are equivalent (which is something ASN.1
    DER is not particulary good at).

    We cannot define a costant in IDL for a sequence of octets. However, I've
    seen an number of ASN.1 compilers and it seems that the internal form of
    the definition of an OID is a string of natural numbers in base 10
    separated by dots. This is a parseable representation, and widely used.

    I suggest that we introduce a definition, possibly a type, for and OID
    string representation.

    module CSI

    { // // An OID String Representation. // The OID is represented in dot format. // For example, "2.23.130.1.1.1". // typedef string OIDStringRep; }

    ;

    module GSSUP

    { const OIDStringRep GSSUP_OID_DEF = "2.23.130.1.1.1"; }

    ;

    This will allow ASN.1 compilers to at least map from this internal string
    representation if they don't already do so.

    What do you think? If there is consensus, I'll raise an issue, and we can
    resolve it.
  • Reported: CSIv2 1.0b1 — Wed, 10 Jan 2001 05:00 GMT
  • Disposition: Resolved — CSIv2 1.0
  • Disposition Summary:

    Close issue with revised text.
  • Updated: Fri, 6 Mar 2015 20:58 GMT