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

Brian,

For unsent messages I agree with you, but I think this doesn't require a
change on M3UA itself  from on-the wire protocol point of view. I didn't
check the SCTP socket API document for long time, hopefully they have a
mechanism for that (not that otherwise would prevent some implementor to
provide that type of functionality in their implementation, but considering
that popular OS implementations follow it).

BTW, I also agree that time controlled switchover between associations is a
good idea to decrease probability if missequencing, but again I think it is
a local procedure AFAICS.

    Thanks,
    Tolga

> -----Original Message-----
> From: Brian F. G. Bidulock [mailto:[email protected]]
> Sent: Thursday, September 21, 2006 8:55 AM
> 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 08:31:44)
> >
> > For the configuration you are mentioning, if the ASP host is
> down, there is
> > no message retrieval possible in SS7 as well for the similar case.
>
> When a host (SP) fails in SS7, other SPs are still able to
> retrieve messages
> from their buffers and send them via alternate SPs.
>
> M3UA could too, particularly in the case where an SG fails and there
> are multiple SG as STP.
>
> Again, see:
>
>  http://www.ietf.org/internet-drafts/draft-bidulock-sigtran-corid-04.txt
>
> --brian
>
> --
> Brian F. G. Bidulock
> [email protected]
> http://www.openss7.org/
>
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/sigtran