Subject: Re: [SUA issue 17 & M3UA issue #11] IPSP cases.

From: "Brian F. G. Bidulock" <[email-masked]>
Date: Sun, 9 Sep 2001 18:30:20 -0500

...resend

John,

John Loughney wrote:               (Sun, 09 Sep 2001 09:55:17)
> Hi Brian & Klaus,
> 
> > NIC failures are rarely the problem.  Netwtork path failures are.
> >
> > Gradischnig, Klaus wrote:
> > >
> > > Fine with me John. This describes a linkset. Don't need 
> > traffic modes for
> > > this.
> > > 
> > > In any case, I agree with Javier's analysis that SCTP does 
> > > away with the need for retrieval. "Link" failures are 
> > > transparently handled by SCTP. And host (aka line card) 
> > > failures are normally not going to leave anything
> > > behind to be retrieved whether SCTP or MTP2 are used.
> 
> Also, possible AS/ASP software bugs can cause lots of
> headaches ... Additionally, intervention by management
> can cause lots of trouble ... 
> 
> I think we can only focus on what is in scope for SIGTRAN,
> however.

The resilience of SIGTRAN protocols using SCTP is within the
scope per the SIGTRAN charter.

Changeover and changeback are protocol procedures which allow
resilience and allow SIGTRAN protocols to meet the network
requirements of the protocols being transported.

This discussion is far from out of scope.  All UAs describe
and advocate the use of mulitple SCTP associations to carry
traffic flows and include fail-over between associations.
It is during such a fail-over that protocol is lacking in
M3UA and SUA.  M2UA has the necessary protocol to acheive
resilience (Correlation Id and Ack).  M3UA and SUA do not.

This is the Changeover/changeback issue (which probably belongs
on the other thread).

--brian

-- 
Brian F. G. Bidulock
[email-masked]
http://www.openss7.org/

---
You are currently subscribed to sigtran as: [email-masked]
To unsubscribe send a blank email to [email-masked]