Issue 3045: Section:  15.8.14 CORBA Interface (sec-rev)
Source: Syracuse University (Dr. Polar Humenn, polar(at)adiron.com)
Nature: Uncategorized Issue
Severity: 
Summary: Subject:  Need MechanismType identifier for TAG_GENERIC_SEC_MECH
          components.
Discussion:

Mechanism Type identifier is said to be constructed by the IOR's tagged
component identifier. However, under the current specification, all
mechanisms represented by the TAG_GENERIC_SEC_MECH still need to be
further distinguished by their security_mechanism_type identifier.
Resolution: 
Revised Text: Close issue 3045 on not being able to distinguish generic
security mechanisms in the current mechanism identifier
framework.
Move paragraph on page 15-219 "Mechanism tags in the IOR
and mechanism type Object Identifiers...." To page 15-218 before
paragraph "MechanismType is used for...." and add paragraph, such
that the following exists:
Cryptographic profiles are identified by a "stringified" form of the
CryptographicProfile value as used in the IOR.
Mechanism tags in the IOR and mechanism type Object Identifiers (as in
GSS-API) in SECIOP messages are also used as appropriate.
A MechanismType identfier for a generic security mechanism is the
stringified value of SECIOP::TAG_GENERIC_SEC_MECH concatenated
with a colon ":" concatenated with the stringified hexadecimal encoding
of the octet sequence in the security_mechanism_type field of the
components associated SECIOP:GenericMechanismInfo structure.
Actions taken:
November 22, 1999: received issue
March 10, 2000: closed issue
Discussion: 

End of Annotations:=====
Issue:
Document: Security 1.5
Section:  15.8.14 CORBA Interface
Subject:  Need MechanismType identifier for TAG_GENERIC_SEC_MECH
          components.
Discussion:

Mechanism Type identifier is said to be constructed by the IOR's
tagged
component identifier. However, under the current specification, all
mechanisms represented by the TAG_GENERIC_SEC_MECH still need to be
further distinguished by their security_mechanism_type identifier.