Issue 4342: Question about corbaname URL (interop) Source: Raytheon (Mr. Craig Rodrigues, nobody) Nature: Uncategorized Issue Severity: Summary: I have an interoperability question regarding the corbaname URL in the CORBA 2.4.2 specification and would appreciate clarification. In 13.6.7.3, it states that for a corbaloc URL which uses IIOP, if the port number of the endpoint is not specified, then the IIOP profile should default to port 2809 which is specified by IANA as the corbaloc port. eg. corbaloc:iiop:myhost.com/SomeKey In 13.6.7.5, the corbaname URL is described. If a corbaname URL is specified for IIOP, but the port number is omitted, should the ORB assume that the root naming context will be on port 2809 of the host specified? eg. corbaname:iiop:myhost.com:3000#path/obj will look for the root naming context on port 3000 of myhost.com. eg. corbaname:iiop:myhost.com#path/obj Should this look to port 2809 for the root naming context? Resolution: see above Revised Text: Actions taken: June 8, 2001: received issue May 13, 2002: closed issue Discussion: Rationale for Rejection Section 2.5.3.6 of the Naming Service specification unambiguously answers these questions, so no change is necessary. End of Annotations:===== X-Authentication-Warning: emerald.omg.org: hobbit.omg.org [192.67.184.3] didn't use HELO protocol Received: from crodrigues.bbn.com (128.89.13.35) by hobbit.omg.org asmtp(1.0) id 16753; Fri, 08 Jun 2001 13:27:35 -0400 (EDT) Received: (from crodrigu@localhost) by crodrigues.bbn.com (8.9.3/8.9.3) id NAA04333 for interop@omg.org; Fri, 8 Jun 2001 13:22:34 -0400 Date: Fri, 8 Jun 2001 13:22:34 -0400 From: Craig Rodrigues To: interop@omg.org Subject: Question about corbaname URL Message-ID: <20010608132234.A4294@bbn.com> Mime-Version: 1.0 Content-Disposition: inline User-Agent: Mutt/1.2.4i Content-Type: text/plain; charset=us-ascii X-UIDL: 0N$"!Vl9!!79Le94/5!! Hi, I have an interoperability question regarding the corbaname URL in the CORBA 2.4.2 specification and would appreciate clarification. In 13.6.7.3, it states that for a corbaloc URL which uses IIOP, if the port number of the endpoint is not specified, then the IIOP profile should default to port 2809 which is specified by IANA as the corbaloc port. eg. corbaloc:iiop:myhost.com/SomeKey In 13.6.7.5, the corbaname URL is described. If a corbaname URL is specified for IIOP, but the port number is omitted, should the ORB assume that the root naming context will be on port 2809 of the host specified? eg. corbaname:iiop:myhost.com:3000#path/obj will look for the root naming context on port 3000 of myhost.com. eg. corbaname:iiop:myhost.com#path/obj Should this look to port 2809 for the root naming context? Thanks. -- Craig Rodrigues Distributed Systems and Logistics, Office 6/304 crodrigu@bbn.com BBN Technologies (617) 873-4725 Cambridge, MA Date: Sun, 10 Jun 2001 07:49:02 +1000 (EST) From: Michi Henning To: Craig Rodrigues cc: interop@omg.org Subject: Re: Question about corbaname URL In-Reply-To: <20010608132234.A4294@bbn.com> Message-ID: Organization: IONA Technologies MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: o'jd9X5!!!JImd9?9Ke9 Status: RO On Fri, 8 Jun 2001, Craig Rodrigues wrote: > In 13.6.7.5, the corbaname URL is described. > If a corbaname URL is specified for IIOP, but the port > number is omitted, should the ORB assume that the > root naming context will be on port 2809 of the host > specified? > > eg. > corbaname:iiop:myhost.com:3000#path/obj > > will look for the root naming context on port > 3000 of myhost.com. > > eg. > corbaname:iiop:myhost.com#path/obj > > Should this look to port 2809 for the root > naming context? Not necessarily. Look at the Naming Service spec, section 2.5.3.6. It explains the resolution rules. The corbaname IIOP above is convereted to the corbaloc corbaloc:iiiop:myhost.com That corbaloc doesn't have a key, the default "NameService" is assumed. Because the corbaloc doesn't have a port, it refers to 2809. The client will now send either a locate request or the actual resolve request to 2809. At that point, the Naming Service may be running but, more likely, a bootstrap service will be running with then location forwards the client to the root naming context, on which the name "path/obj" is resolved. Cheers, Michi. -- Michi Henning +61 7 3324 9633 Chief CORBA Scientist +61 4 1118 2700 (mobile) IONA Technologies +61 7 3324 9799 (fax) Total Business Integration http://www.ooc.com.au/staff/michi Date: Wed, 13 Jun 2001 15:10:34 +1000 (EST) From: Michi Henning Reply-To: Interoperability RTF To: Interoperability RTF Subject: Proposal for 4342 Message-ID: Organization: IONA Technologies MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: 93Sd93g9e9/E~!!ejYd9 Hi, I suggest to close 4342 without change. The spec is clear on how the corbaloc and corbaname resolutions work, and no clarification is necessary, IMO. Cheers, Michi. -- Michi Henning +61 7 3324 9633 Chief CORBA Scientist +61 4 1118 2700 (mobile) IONA Technologies +61 7 3324 9799 (fax) Total Business Integration http://www.ooc.com.au/staff/michi