Issue 4648: GTPForwardReply needs to be forwardable (wireless-ftf)
Source: University of Helsinki (Jaakko Kangasharju, )
Nature: Uncategorized Issue
Severity: 
Summary: GTPForwardReply needs to be forwardable

Currently GTPForwardReply (section 7.2.18) is marked not forwardable.
But if there have been outstanding GTPForward messages when handoff
happens, these messages cannot then be acknowledged.  This situation
is similar to the one with OpenConnection where OpenConnectionReply is
forwardable, the reason being that outstanding requests can be
responded to after handoff.  For the same reason, GTPForwardReply
should also be forwardable.

Resolution: Make GTPForwardReply forwardable
Revised Text: 3.12.2.1	Section 7.2.18 GTPForwardReply Message
Forwardable
No. However, Access Bridges can forward forwarded messages given to them by invoking the gtp_from_terminal and gtp_to_terminal operations. Yes. This is due to the fact that outstanding GTPForwardRequests may have been in progress during a transition to a new Access Bridge.

Actions taken:
October 29, 2001: received issue
December 11, 2002: closed issue
Discussion: 

End of Annotations:=====
X-Authentication-Warning: repokari.cs.Helsinki.FI: jkangash set sender
to jkangash@cs.helsinki.fi using -f
To: issues@omg.org
Subject: Issue for Telecom Wireless FTF
X-Face:
$<.'cgqn3yPR[$(\>O2ri:FNd[]}jU-P{;d"aAZ5)bm{B7\CHE9E#x6AHuY5s=rI?9JC#kJ
 GcWhy(I.#?_5,#QM]&pPr1BxP{Xq)h7e0>EXL-^.Fswtnpc)uv>[q~rJeig'
Cc: jkangash@cs.helsinki.fi, Kimmo.Raatikainen@nokia.com
From: Jaakko Kangasharju <jkangash@cs.helsinki.fi>
Organization: University of Helsinki
Date: 29 Oct 2001 16:29:11 +0200
Message-ID: <jpvsnc2ldu0.fsf@repokari.cs.Helsinki.FI>
Lines: 20
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-UIDL: U"Ae9=%<e9cF*!!b5?!!


This issue is for the Telecom Wireless FTF regarding the current
adopted specification dtc/2001-06-02


GTPForwardReply needs to be forwardable

Currently GTPForwardReply (section 7.2.18) is marked not forwardable.
But if there have been outstanding GTPForward messages when handoff
happens, these messages cannot then be acknowledged.  This situation
is similar to the one with OpenConnection where OpenConnectionReply is
forwardable, the reason being that outstanding requests can be
responded to after handoff.  For the same reason, GTPForwardReply
should also be forwardable.


-- 
Jaakko Kangasharju, University of Helsinki
Hi!  I'm a signature virus!  Copy me into your .signature to help
me spread



Subject: Issue 4648: Proposal 
Date: Mon, 27 May 2002 09:24:55 +0300 
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issue 4648: Proposal 
Thread-Index: AcIFRzc7xZQem3EzEdauMgDQtwuWXQ== 
From: <Kimmo.Raatikainen@nokia.com> 
To: <wireless-ftf@omg.org> 
X-OriginalArrivalTime: 27 May 2002 06:24:55.0798 (UTC)
FILETIME=[37DF1960:01C20547] 
X-MIME-Autoconverted: from quoted-printable to 8bit by emerald.omg.org
id g4R6MOe08059 



GTPForwardReply needs to be forwardable



Currently GTPForwardReply (section 7.2.18) is marked not forwardable.
But if there have been outstanding GTPForward messages when handoff
happens, these messages cannot then be acknowledged.  This situation
is similar to the one with OpenConnection where OpenConnectionReply is
forwardable, the reason being that outstanding requests can be
responded to after handoff.  For the same reason, GTPForwardReply
should also be forwardable.


Proposal: Make GTPForwardReply forwardable