RE: RFC 4666 on Signaling System 7 (SS7) MessageTransferPart 3 (MTP3) - User Adaptation Layer (M3UA)

Brian,

The method explained in the draft is not something present in SS7
specifications.

We are talking here of two different things:
a)What to do about unsent messages.
b)How to get some information about the last received message by a failed
peer.


a) is a local procedure.

For b), if the host is not down, MTP3 changeover procedure is used for SS7.
For SIGTRAN, SCTP handles failover between the paths.

For b), if the host is down, there is no protocol support(not in SS7 and not
in SIGTRAN). Any mechanism, which can do this (or something similar) locally
is an implementation decision. For example, there is nothing preventing
people to implement a distributed SCTP, which spans multiple hosts. Is this
a good solution IMO not, is it allowed by the protocol I guess so.

     Thanks,
     Tolga
> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:[email protected]]
> Sent: Thursday, September 21, 2006 1:36 PM
> To: Tolga Asveren
> Cc: [email protected]
> Subject: Re: [Sigtran] RFC 4666 on Signaling System 7 (SS7)
> MessageTransferPart 3 (MTP3) - User Adaptation Layer (M3UA)
>
>
> Tolga,
>
> Tolga Asveren wrote:                              (Thu, 21 Sep
> 2006 11:11:40)
> > Brian,
> >
> > For unsent messages I agree with you, but I think this doesn't require a
>
> If the node has another communications path to the node ajacent
> to the failed
> association, buffer updating can be performed just as in SS7, and zero
> messages will be lost.  It can be done without waiting and unnecessarily
> delaying messages in queue.  Read the draft.
>
> --brian
>
> --
> Brian F. G. Bidulock
> [email protected]
> http://www.openss7.org/