Issue 4268: How to Partition the ServiceConfiguration syntax space to support vendor sp (csiv2-ftf)
Source: Oracle (Mr. Ron Monzillo, ronald.monzillo(at)east.sun.com)
Nature: Uncategorized Issue
Severity: 
Summary: We need to define how the namespace of ServiceConfiguration syntax
identifiers (used in privilege_authorities) is to be partitioned 
so that individual vendors have some identifiers reserved for
their use (i.e. the definition of vendor specific syntaxes).

Resolution: Recommend closure with revised text
Revised Text: Base document:

http://cgi.omg.org/pub/csiv2-ftf/csiv2-031401.pdf

[1] Add two new paragraphs following the second half of para 148
(which was split as one result of the resolution to issue 4118).

The high order 20-bits of each ServiceConfigurationSyntax constant
shall contain the Vendor Minor Codeset ID (VMCID) of the
organization that defined the syntax. The low order 12 bits shall
contain the organization-scoped syntax identifier. The high-order 20
bits of all syntaxes defined by the OMG shall contain the VMCID
allocated to the OMG (that is, 0x4F4D0).

Organizations must register their VMCIDs with the OMG before
using them to define a ServiceConfigurationSyntax.

[2] change the defintion of the ServiceConfigurationSyntax type, and
the syntax contants in

a. the IDL following para 147
b. in section 16.9.4 Module CSIIOP

to:


// The high order 20-bits of each ServiceConfigurationSyntax constant
// shall contain the Vendor Minor Codeset ID (VMCID) of the
// organization that defined the syntax. The low order 12 bits shall
// contain the organization-scoped syntax identifier. The high-order 20
// bits of all syntaxes defined by the OMG shall contain the VMCID
// allocated to the OMG (that is, 0x4F4D0).

typedef unsigned long ServiceConfigurationSyntax;

// The OMG VMCID; same value as CORBA::OMGVMCID. Do not change ever.

const unsigned long OMGVMCID = 0x4F4D0;

const ServiceConfigurationSyntax SCS_GeneralNames = OMGVMCID | 0;



const ServiceConfigurationSyntax SCS_GSSExportedName = OMGVMCID | 1;

Actions taken:
April 11, 2001: received issue
October 3, 2001: closed issue
Discussion: 
How to Partition the ServiceConfiguration syntax space to support vendor specific extensions
End of Annotations:=====
Date: Wed, 11 Apr 2001 17:13:11 -0400
From: Ron Monzillo <Ronald.Monzillo@Sun.COM>
X-Mailer: Mozilla 4.76 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: issues@omg.org, csiv2-ftf@omg.org
Subject: ISSUE: CSIv2 How to Partition the ServiceConfiguration syntax
space to 
 support vendor specific extensions
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: @!dd90%2e9FkAe97M1!!

How to Partition the ServiceConfiguration syntax space to support
vendor
specific extensions

base document:

http://cgi.omg.org/pub/csiv2-ftf/csiv2-031401.pdf

Description:

We need to define how the namespace of ServiceConfiguration syntax
identifiers (used in privilege_authorities) is to be partitioned 
so that individual vendors have some identifiers reserved for
their use (i.e. the definition of vendor specific syntaxes).


 6. I think Issue 4268: How to Partition the ServiceConfiguration
    syntax
> space to
> support vendor specific extensions can be easily resolved given that
> somewhere
> in the OMG there is already a registry of member specific numeric
> identifiers
> (that can be encoded) in a part of the ServiceConfigurationSyntax
    type.
> It may be necessary to increase the size of this type (as it is
> currently a short).



Date: Tue, 29 May 2001 17:46:52 -0400
From: Ron Monzillo <Ronald.Monzillo@Sun.COM>
X-Mailer: Mozilla 4.76 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: csiv2-ftf@omg.org
Subject: Issue 4268: Proposed Resolution - How to Partition the
Service 
 Configuration syntax space
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: E';!!%`d!!X~%!!^M4e9

base document: http://cgi.omg.org/pub/csiv2-ftf/csiv2-031401.pdf

Proposed Resolution:

[1] Add two new paragraphs following the second half of para 148
    (which was split as one result of the resolution to issue 4118).

    The high order 20-bits of each ServiceConfigurationSyntax constant
    shall contain the Vendor Minor Codeset ID (VMCID) of the
    organization that defined the syntax. The low order 12 bits shall
    contain the organization-scoped syntax identifier. The high-order
    20
    bits of all syntaxes defined by the OMG shall contain the VMCID
    allocated to the OMG (that is, 0x4F4D0). 

    Organizations must register their VMCIDs with the OMG before 
    using them to define a ServiceConfigurationSyntax.

[2] change the defintion of the ServiceConfigurationSyntax type, and
    the syntax contants in

    a. the IDL following para 147
    b. in section 16.9.4 Module CSIIOP

    to:

// The high order 20-bits of each ServiceConfigurationSyntax constant
// shall contain the Vendor Minor Codeset ID (VMCID) of the
// organization that defined the syntax. The low order 12 bits shall
// contain the organization-scoped syntax identifier. The high-order
20
// bits of all syntaxes defined by the OMG shall contain the VMCID
// allocated to the OMG (that is, 0x4F4D0).

typedef unsigned long ServiceConfigurationSyntax;

// The OMG VMCID; same value as CORBA::OMGVMCID. Do not change ever.

const unsigned long OMGVMCID = 0x4F4D0;

const ServiceConfigurationSyntax SCS_GeneralNames = OMGVMCID | 0;
const ServiceConfigurationSyntax SCS_GSSExportedName = OMGVMCID | 1;


Date: Wed, 30 May 2001 08:55:04 -0400
From: Ron Monzillo <Ronald.Monzillo@Sun.COM>
X-Mailer: Mozilla 4.76 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ron Monzillo <Ronald.Monzillo@Sun.COM>
CC: csiv2-ftf@omg.org
Subject: Re: Issue 4268: Proposed Resolution - How to Partition the
Service 
 Configuration syntax space
References: <3B1418CC.6D16B922@east.sun.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: m/`!!BRZ!!M;dd9b:@!!

Ron Monzillo wrote:
> 
> base document: http://cgi.omg.org/pub/csiv2-ftf/csiv2-031401.pdf

discussion:

The VMCID technique should also be applied to
AuthorizationElementType constants. The appropriate changes 
have been made to the proposed resolution.

> 
> Proposed Resolution:
> 
[1] Add two new paragraphs following the second half of para 148
    (which was split as one result of the resolution to issue 4118).

The high order 20-bits of each ServiceConfigurationSyntax constant
shall contain the Vendor Minor Codeset ID (VMCID) of the
organization that defined the syntax. The low order 12 bits shall
contain the organization-scoped syntax identifier. The high-order 20
bits of all syntaxes defined by the OMG shall contain the VMCID
allocated to the OMG (that is, 0x4F4D0).
 
Organizations must register their VMCIDs with the OMG before
using them to define a ServiceConfigurationSyntax.

[2] add the following comment in front of the definition of the
ServiceConfigurationSyntax type in section 16.9.4 Module CSIIOP

// The high order 20-bits of each ServiceConfigurationSyntax constant
// shall contain the Vendor Minor Codeset ID (VMCID) of the
// organization that defined the syntax. The low order 12 bits shall
// contain the organization-scoped syntax identifier. The high-order
20
// bits of all syntaxes defined by the OMG shall contain the VMCID
// allocated to the OMG (that is, 0x4F4D0).

[3] change the defintion of the ServiceConfigurationSyntax type, and
    the syntax contants in
 
    a. the IDL following para 147
    b. in section 16.9.4 Module CSIIOP
 
    to:

typedef unsigned long ServiceConfigurationSyntax;
 
const ServiceConfigurationSyntax SCS_GeneralNames = CSI::OMGVMCID | 0;
const ServiceConfigurationSyntax SCS_GSSExportedName = CSI::OMGVMCID |
1;

[4] add the definition of the OMG VMCID constant to section 16.9.3 
    Module CSI

// The OMG VMCID; same value as CORBA::OMGVMCID. Do not change ever.

const unsigned long OMGVMCID = 0x4F4D0;

[5] Add two new paragraphs following para 32.

The high order 20-bits of each AuthorizationElementType constant
shall contain the Vendor Minor Codeset ID (VMCID) of the
organization that defined the element type. The low order 12 bits 
shall contain the organization-scoped element type identifier. The 
high-order 20 bits of all element types defined by the OMG shall 
contain the VMCID allocated to the OMG (that is, 0x4F4D0).

Organizations must register their VMCIDs with the OMG before
using them to define an AuthorizationElementType.

[6] add the following comment in front of the definition of the
AuthorizationElementType in section 16.9.3 Module CSI

// The high order 20-bits of each AuthorizationElementType constant
// shall contain the Vendor Minor Codeset ID (VMCID) of the
// organization that defined the element type. The low order 12 bits 
// shall contain the organization-scoped element type identifier. The 
// high-order 20 bits of all element types defined by the OMG shall 
// contain the VMCID allocated to the OMG (that is, 0x4F4D0).

[7] change the defintion of the X509AttributeCertChain contant in
 
     a. the IDL following para 32
     b. in section 16.9.3 Module CSI

     to:

const AuthorizationElementType X509AttributeCertChain = OMGVMCID | 1;