Issue 4293: CSIv2 Issue: SECIOP does not have multiple addresses. (csiv2-ftf) Source: Adiron, LLC (Mr. Polar Humenn, polar(at)adiron.com) Nature: Uncategorized Issue Severity: Summary: This issue is the exactly the same issue as issue 4200, which is for TLS (SSL) transport addresses. It notes that the component for a SECIOP transport needs to support multiple addresses. The recommended solutioin to this issue is to adopt the analogous resolution to the 4200 issue. Resolution: Close issue with revised text. Revised Text: Base document: http://cgi.omg.org/pub/csiv2-ftf/csiv2-031401.pdf [1] Add Minor Heading Section before TAG_TLS_SEC_TRANS Transport Address The TransportAddress structure indicates an INTERNET address where the TSS is listening for connection requests. struct TransportAddress { string host_name; unsigned short port; }; typedef sequence <TransportAddress> TransportAddressList; The host_name field identifies the Internet host to which connection requests will be made. The host_name field shall not contain an empty string. The port field contains the TCP/IP port number (at the specified host) where the TSS is listening for connection requests. The port number shall not be zero. [2] Replace paragraph 133 with the following: The SECIOP_SEC_TRANS structure defines the transport addresses for SECIOP messages, the association options pertaining to the particular GSS mechanism being supported, the GSS mechanism identifier, and the target's GSS exported name. [3] Change the IDL for SECIOP_SEC_TRANS after paragraph 133 to the following: struct SECIOP_SEC_TRANS { AssociationOptions target_supports; AssociationOptions target_requires; CSI::OID mech_oid; CSI::GSS_NT_ExportedName target_name; TransportAddressList addresses; }; [4] Add the following paragraph following the IDL after paragraph 133: The addresses field provides a shorthand for defining multiple security mechanisms that differ only in their transport addresses. The addresses field shall contain at least one address. [5] Add the following IDL for TransportAddress 16.9.4 on page 16-65 after the definition of CompoundSecMechList: struct TransportAddress { string host_name; unsigned short port; }; typedef sequence <TransportAddress> TransportAddressList; [6] Change the IDL for SECIOP_SEC_TRANS in section 16.9.4 on page 16-65 to the following: struct SECIOP_SEC_TRANS { AssociationOptions target_supports; AssociationOptions target_requires; CSI::OID mech_oid; CSI::GSS_NT_ExportedName target_name; TransportAddressList addresses; }; Actions taken: May 3, 2001: received issue October 3, 2001: closed issue Discussion: We add a minor section describing a TransportAddress structure with wording close to that of the IIOP profile on page 15-50 of CORBA 2.3. formal/99-10-07. We also add a typedef for a sequence of these structures. We change the SECIOP_SEC_TRANS structure to use a list of these addresses. End of Annotations:===== X-Authentication-Warning: marcy.adiron.com: polar owned process doing -bs Date: Thu, 3 May 2001 12:43:57 -0400 (EDT) From: Polar Humenn To: Subject: CSIv2 Issue: SECIOP does not have multiple addresses. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: NAK!!MIC!!C]Ne9I6 4200, test should > be proposed to close this resolution. Issue 4293: CSIv2 Issue: SECIOP does not have multiple addresses. (csiv2-ftf) Click here for this issue's archive. Source: Adiron, LLC (Mr. Polar Humenn, polar@adiron.com) Nature: Uncategorized Issue Severity: Summary: This issue is the exactly the same issue as issue 4200, which is for TLS (SSL) transport addresses. It notes that the component for a SECIOP transport needs to support multiple addresses. The recommended solutioin to this issue is to adopt the analogous resolution to the 4200 issue. Discussion: We add a minor section describing a TransportAddress structure with wording close to that of the IIOP profile on page 15-50 of CORBA 2.3. formal/99-10-07. We also add a typedef for a sequence of these structures. We change the SECIOP_SEC_TRANS structure to use a list of these addresses. Resolution: Close issue with revised text. Revised Text: Base document: http://cgi.omg.org/pub/csiv2-ftf/csiv2-031401.pdf [1] Add Minor Heading Section before TAG_TLS_SEC_TRANS Transport Address The TransportAddress structure indicates an INTERNET address where the TSS is listening for connection requests. struct TransportAddress { string host_name; unsigned short port; }; typedef sequence TransportAddressList; The host_name field identifiers the Internet host to which connection requests will be made. The host_name field shall not be empty string. The port field contains the TCP/IP port number (at the specified host) where the TSS is listening for connection requests. The port number shall not be zero. [2] Replace paragraph 133 with the following: The SECIOP_SEC_TRANS structure defines the transport addresses for SECIOP messages, the association options pertaining to the particular GSS mechanism being supported, the GSS mechanism identifier, and the target's GSS exported name. [3] Change the IDL for SECIOP_SEC_TRANS after paragraph 133 to the following: struct SECIOP_SEC_TRANS { AssociationOptions target_supports; AssociationOptions target_requires; CSI::OID mech_oid; CSI::GSS_NT_ExportedName target_name; TransportAddressList addresses; }; [4] Add the following paragraph following the IDL after paragraph 133: The addresses field provides a shorthand for defining multiple security mechanisms that differ only in their transport addresses. The addresses field shall contain at least one address. [5] Add the following IDL for TransportAddress 16.9.4 on page 16-65 after the definition of CompoundSecMechList: struct TransportAddress { string host_name; unsigned short port; }; typedef sequence TransportAddressList; [6] Change the IDL for SECIOP_SEC_TRANS in section 16.9.4 on page 16-65 to the following: struct SECIOP_SEC_TRANS { AssociationOptions target_supports; AssociationOptions target_requires; CSI::OID mech_oid; CSI::GSS_NT_ExportedName target_name; TransportAddressList addresses; }; Actions Taken: May 3, 2001: received issue June XX, 2001: closed issue Date: Fri, 01 Jun 2001 13:40:37 -0400 From: Ron Monzillo X-Mailer: Mozilla 4.76 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Polar Humenn , csiv2-ftf@omg.org Subject: Re: Issue 4200 and 4293 References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-UIDL: ~?@!!OY!e9L~Ud9],A!! You ahve the following in both resolutions. "The host_name field identifiers the Internet host to which connection requests will be made. The host_name field shall not be empty string." Polar Humenn wrote: > > Greetings, > > To help Don out with his constraints on his time, I have composed > the resolutions to 4200 (SSL Addresses) and 4293 (SECIOP addresses). > > They are attached and also viewable from the following URLs: > > ftp://greene.case.syr.edu/pub/omg/csiv2-ftf/FTF-Issue4200-1.html > ftp://greene.case.syr.edu/pub/omg/csiv2-ftf/FTF-Issue4293-1.html > > Since both resolutions make use of a common data structure (i.e. > TransportAddress) it is placed in a different section. > > Furthermore, these issues are written in such a manner that they are > compatible with each other, so each can be voted on separately, and there > should be no editorial conflicts. > > 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 > > ------------------------------------------------------------------------ > Name: FTF-Issue4200-1.html > FTF-Issue4200-1.html Type: Hypertext Markup Language (TEXT/html) > Encoding: BASE64 > > Name: FTF-Issue4293-1.html > FTF-Issue4293-1.html Type: Hypertext Markup Language (TEXT/html) > Encoding: BASE64 X-Authentication-Warning: marcy.adiron.com: polar owned process doing -bs Date: Fri, 1 Jun 2001 14:12:09 -0400 (EDT) From: Polar Humenn To: Ron Monzillo , Don Flinn cc: Subject: Re: Issue 4200 and 4293 In-Reply-To: <3B17D395.35985E5E@east.sun.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-427817617-1048416130-991419129=:2948" X-UIDL: cmdd9~K6!!=-4!!UIhd9 On Fri, 1 Jun 2001, Ron Monzillo wrote: > You ahve the following in both resolutions. > > "The host_name field identifiers the Internet host to which > connection requests will be made. The host_name field shall > not be empty string." Yep, I "ahve"! :) Sorry about that. Here's an update with this paragraph: The host_name field identifies the Internet host to which connection requests will be made. The host_name field shall not contain an empty string. They are attached and available at: ftp://greene.case.syr.edu/pub/omg/csiv2-ftf/FTF-Issue4200-2.html ftp://greene.case.syr.edu/pub/omg/csiv2-ftf/FTF-Issue4293-2.html Cheers, -Polar > > Polar Humenn wrote: > > > > Greetings, > > > > To help Don out with his constraints on his time, I have composed > > the resolutions to 4200 (SSL Addresses) and 4293 (SECIOP >addresses). > > > > They are attached and also viewable from the following URLs: > > > > ftp://greene.case.syr.edu/pub/omg/csiv2-ftf/FTF-Issue4200-1.html > > ftp://greene.case.syr.edu/pub/omg/csiv2-ftf/FTF-Issue4293-1.html > > > > Since both resolutions make use of a common data structure (i.e. > > TransportAddress) it is placed in a different section. > > > > Furthermore, these issues are written in such a manner that they >are > > compatible with each other, so each can be voted on separately, >and there > > should be no editorial conflicts. > > > > 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 > > > > >------------------------------------------------------------------------ > > Name: FTF-Issue4200-1.html > > FTF-Issue4200-1.html Type: Hypertext Markup Language >(TEXT/html) > > Encoding: BASE64 > > > > Name: FTF-Issue4293-1.html > > FTF-Issue4293-1.html Type: Hypertext Markup Language >(TEXT/html) > > Encoding: BASE64 > ------------------------------------------------------------------- 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-Issue4200-2.htm [] FTF-Issue4293-2.htm