Issue 382:  Use of dynamic ports (interop)
Source:  (, )
Nature:  Uncategorized
Severity: 
Summary: Summary: Static port # should not be mandated-unworkable.It would be nice if a "standard" IIOP port # was registered with IANA

Resolution:  closed with no revision required
Revised Text: 
Actions taken:
December 2, 1996: received issue
March 26, 1998: closed issue
Discussion: 

End of Annotations:=====


To: Interop 1.2	RTF
Subject: Dec 19, Conference Call
From: Tom Rutt,	RTF Chair

I have attached	my proposed Resolutions	of Issues for ORB
Interoperability 1.2 Revision Task Force.  There was no
meeting	of the RTF at the NJ meeting, since everyone is	so
busy I decided to take a whack at coming up with resolutions
for the	issues.

We need	further	discussion on some of these issues, as
indicated in the actions section of each issue.

A conference Call is scheduled for Friday, December 19,	at
11:00 EST.  I have the bridge reserved for 2 hours.

The bridge phone number	(16 ports reserved) is:
+1 630 224 444	Conference Code	674 369
Let me know if you will	participate, so	I can ensure 16	is
enough ports.

Tom Rutt

------------------------------

List of	issues:

Issue 55: IIOP object pointer resetting
Issue 74: Type ids in OBJECT_FORWARD return message
Issue 77: LOCATION_FORWARD byte	alignment
Issue 89: Correct IIOP marshalling of union TypeCodes
Issue 382: Use of dynamic ports
Issue 383: Callbacks in	IIOP
Issue 460: IORs	and identifying	Object Keys
Issue 465: Transport Level Bridge
Issue 488: Problem with	GIOP CancelRequest when	fragments
are used
Issue 543: IIOP	server-initiated connection closure problem
Issue 573: Type	Extensions and code set	negotiation
Issue 574: Type	extensions char	code set negotiation
Issue 589: Fragment improvements (1)
Issue 590: Fragment improvements (2)
Issue 591: 1.0 backward	compat (1)
Issue 592: 1.0 backward	compat (2)
Issue 593: CloseConnection messages
Issue 651: Issue with service context
Issue xxx: Unknown received system exception



Issue 382: Use of dynamic ports	(interop)

Source:	IONA (Mr. Justin Mason,	jmason@iona.com)
Nature:	Uncategorized
Severity:
Summary: Static	port # should not be mandated-unworkable.It
would be nice if a "standard" IIOP port	# was registered
with IANA

Resolution: When static	port is	registered for IIOP, we	can
revise document	then.
Revised	Text:
Actions	taken: Proposed	No revision
December 2, 1996: received issue