Issue 2794:  Alternate Protocol Specifications within URIs                                                                                                                                                          (naming_ftf)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: Object URIs should accommodate multiple protocols. This is important for a
 wide range of present day systems, such as embedded and real-time systems
 that do not or cannot use TCP/IP, and will accommodate future expansion of
 CORBA beyond TCP/IP networks. 
 
 Object URIs should
 - be extensible to allow additional addressing schemes for, at least, GIOPs
 over transports other than TCP/IP. A default of IIOP that results in a
 shorter form is allowable. 
 - accommodate additional standardized addressing schemes as transports and
 protocols become adopted. (similar to that provided by the present IOR
 structure through the adoption of new standard profiles)
 - accommodate additional proprietary addressing schemes targeted for
 markets for which standardization might be inappropriate or too costly. In
 particular, it should allow assignment of partitions of the naming space to
 entities (similar to the current provision for vendor-specific profile tags)

Resolution: Support for multiple protocols is required. changed iioploc/iiopname to corbaloc/corbaname and chang
Revised Text: Significant changes to iioploc/iiopname descriptions in Core Chapter 4. See final submission edit document for
details.
Actions taken:
July 8, 1999: received issue
May 4, 2000: closed issue
Discussion: 

End of Annotations:=====
X-Sender: giddiv@gamma
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Thu, 08 Jul 1999 11:13:08 -0400
To: issues@omg.org
From: Victor Giddings <victor.giddings@ois.com>
Subject: Naming FTF: Alternate Protocol Specifications within URIs
Cc: Victor Giddings <victor.giddings@ois.com>

This is an issue under discussion in the Interoperable Naming FTF. 

Object URIs should accommodate multiple protocols. This is important for a
wide range of present day systems, such as embedded and real-time systems
that do not or cannot use TCP/IP, and will accommodate future expansion of
CORBA beyond TCP/IP networks. 

Object URIs should
- be extensible to allow additional addressing schemes for, at least, GIOPs
over transports other than TCP/IP. A default of IIOP that results in a
shorter form is allowable. 
- accommodate additional standardized addressing schemes as transports and
protocols become adopted. (similar to that provided by the present IOR
structure through the adoption of new standard profiles)
- accommodate additional proprietary addressing schemes targeted for
markets for which standardization might be inappropriate or too costly. In
particular, it should allow assignment of partitions of the naming space to
entities (similar to the current provision for vendor-specific profile tags) 
Victor Giddings                             Phone: 703-295-6500
Senior Product Engineer                Fax: 703-295-6501
Objective Interface Systems           victor.giddings@ois.com