Issue 574:  Type extensions char code set negotiation (interop)
Source:  (, )
Nature:  Uncategorized
Severity: 
Summary: Summary: This negotiation adds 16 bytes to both request and reply messages. It"s overburdening an already obese message header scheme.

Resolution:  closed, no revision required
Revised Text: 
Actions taken:
May 14, 1997: received issue
March 26, 1998: closed issue
Discussion: 

End of Annotations:=====

Return-Path: <ter@holta.ho.lucent.com>
Date: Wed, 10 Dec 1997 16:49:32 -0500
From: ter@holta.ho.lucent.com (T E Rutt)
To: interop@omg.org
Subject: Interop 1.2 RTF Conference call (Proposed revisions and
issues)

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



Issue 574: Type	extensions char	code set
negotiation (interop)

Source:	Xerox (Mr. William C. Janssen, Jr.,
janssen@parc.xerox.com)
Nature:	Uncategorized
Severity:
Summary: This negotiation adds 16 bytes	to both	request	and
reply messages.	It's
overburdening an already obese message header scheme.
Resolution: This negotiation should be interpreted as only
needed once per	connection. (issue above needs to be
resolved regarding multiple negotiations per connection).
Revised	Text:
Actions	taken: Proposed	no revision.  Could fix	in GIOP	2.0.
May 14,	1997: received issue