RE: TID Label Issues - Issue #2

"Haresign Lincoln" <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <849535E338E99741B7F7413F73253EDB04E8BCF9@us-nj-mail1.comverse.com>
Brian,

Our proprietary solution rests on a layer above SUA and it not really
relevant.  I agree that TID routing will not solve problems related to
linked transactions and they need to be solve in another way.  There are
many problems that can occur with M3UA users and SUA users that are not
solved by the existing specifications.  That doesn't mean that we should
not use the specifications where appropriate.

Regards,
Lincoln

-----Original Message-----
From: Brian F. G. Bidulock [mailto:[email protected]] 
Sent: Wednesday, October 11, 2006 4:22 PM
To: Haresign Lincoln
Cc: Barry Nagelberg; [email protected]
Subject: Re: TID Label Issues - Issue #2

Lincoln,

Perhaps you could contribute your procedure to solve the issue.

Otherwise, it needs to be state that TID labels are inapplicable and
must not be applied where linked transactions are involved.

--brian


Haresign Lincoln wrote:                      (Wed, 11 Oct 2006 16:16:29)
> 
> Since there is no RFC to solve linked transactions, right now we must 
> solve them on our own.  And we have.  We used TID routing with a 
> proprietary mechanism that ensure that the messages arrive at the 
> correct ASP.
> 

--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.