Issue 3973: inconsistent definition of target_name field (csiv2-ftf) Source: Oracle (Mr. Ron Monzillo, ronald.monzillo(at)east.sun.com) Nature: Uncategorized Issue Severity: Summary: Document: orbos/2000-08-04 CSIv2 Final Submission Issue: target_name(s) field of struct AS_ContextSec is defined and described inconsistently in various places in the submission. Description: In section 6.1.4.1 this field is defined as sequence <Security::GSS_NT_exportedName> target_names; and defined as a list of target names. In the IDL in section B.7 this field is defined as sequence <Security::GSS_NT_exportedName> target_name; There are other places in the document where the singular form of this field name is used, including in the examples of the scenarios chapter. Proposed Solution: The change of this field to a list was not necessary, as it is difficult to make a case for requiring multiple target names within a single mechanism (as there is a multiple mechanism workaround). We should at least fix the inconsitencies in the document. If we keep the ability to express multiple targets, then we should also say something about the semantics of position in the list. The prefered solution would be to revert back to the singular form. Security::GSS_NT_exportedName target_name; and fix all references to this field accordingly. Resolution: Make it singular. Close issue with revised text. Revised Text: The following modifications are presented against document http://cgi.omg.org/pub/csiv2-ftf/csiv2-0117011.pdf. with the assumption that the resolution of Issue 4141 has been applied. (Moving OID and GSS_NT_ExportedName from Security to CSI). [1] Change the IDL between para 138 and 139 to the following: struct AS_ContextSec{ AssociationOptions target_supports; AssociationOptions target_requires; CSI::OID client_authentication_mech; CSI::GSS_NT_ExportedName target_name; }; [2] Change para 141 to read: The target uses the target_name field to make its security name and or authentication domain available to clients. This information may be required by the client to obtain or construct (depending on the mechanism) a suitable initial context token. [3] Change the IDL definition of AS_ContextSec in Section 16.9.7, Module CSIIOP to the following: struct AS_ContextSec{ AssociationOptions target_supports; AssociationOptions target_requires; CSI::OID client_authentication_mech; CSI::GSS_NT_ExportedName target_name; }; Actions taken: October 19, 2000: received issue October 3, 2001: closed issue Discussion: End of Annotations:===== Date: Thu, 19 Oct 2000 11:50:43 -0400 From: Ron Monzillo X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: juergen@omg.org Subject: [Fwd: ISSUE: inconsistent definition of target_name field] Content-Type: multipart/mixed; boundary="------------74F8317141A19129116137F1" X-UIDL: /;e!!]~m!![8O!!k9-!! Message-ID: <39EC9D61.459F660A@east.sun.com> Date: Tue, 17 Oct 2000 14:41:37 -0400 From: Ron Monzillo X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: csiv2-ftf@omg.org Subject: ISSUE: inconsistent definition of target_name field Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Document: orbos/2000-08-04 CSIv2 Final Submission Issue: target_name(s) field of struct AS_ContextSec is defined and described inconsistently in various places in the submission. Description: In section 6.1.4.1 this field is defined as sequence target_names; and defined as a list of target names. In the IDL in section B.7 this field is defined as sequence target_name; There are other places in the document where the singular form of this field name is used, including in the examples of the scenarios chapter. Proposed Solution: The change of this field to a list was not necessary, as it is difficult to make a case for requiring multiple target names within a single mechanism (as there is a multiple mechanism workaround). We should at least fix the inconsitencies in the document. If we keep the ability to express multiple targets, then we should also say something about the semantics of position in the list. The prefered solution would be to revert back to the singular form. Security::GSS_NT_exportedName target_name; and fix all references to this field accordingly. X-Authentication-Warning: marcy.adiron.com: polar owned process doing -bs Date: Thu, 18 Jan 2001 02:46:33 -0500 (EST) From: Polar Humenn To: csiv2-ftf@omg.org Subject: Proposed Vote Resolution Issue 3973 Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-427817617-1073594979-979803993=:5895" X-UIDL: 20gd9hmD!!Z3j!!O'a!! Attached is Proposed Vote resolution for: Issue 3973: inconsistent definition of target_name field Makes "target_name" of the AS_ContextSec singular, and also fixes an incosistency between the definition of the AS_ContextSec in the text, and in the IDL at the end. Cheers, -Polar ------------------------------------------------------------------- Polar Humenn Adiron, LLC mailto:polar@adiron.com 2-212 CST Phone: 315-443-3171 Syracuse, NY 13244-4100 Fax: 315-443-4745 http://www.adiron.com [] FTF-Issue3973.html