Re: [Dime] Message mis-sequencing over SCTP

> Sounds like a good point. Seems to me the rules should be:
> 
>   - use only stream 0 until the Diameter connection has been set up
>   - all messages relating to the same session must use the same stream.

Is the second suggested rule (same session must use the same stream) actually of any use?

IIRC, in principal, messages on the same session may take different routes to their destination (where multiple Diameter proxies are available) and that makes enforcing ordering on a single hop irrelevant to the session?

The Diameter application must either enforce ordering or cope with reordering, anyway?

Cheers,
Ralph.

> 
> That should be added to section 2.1.1.
> 
> 
> Naveen Kottapalli wrote:
> > Hi,
> > 
> > Am just wondering whether the mis-sequencing in the delivery of packets when
> > SCTP is being used as transport layer would cause any problem.  For example,
> > take an association with 5 out-streams to send out the Diameter messages.
> > Immediately after sending CEA on stream 0, all other messages are sent over
> > other streams like 1, 2, 3, and 4.
> > 
> > There is a chance that the other Diameter messages will reach the peer
> > before the CEA is processed?   Does the existing draft miss the sequencing
> > problem over SCTP?
> > 
> > Yours,
> > Naveen.
> > 
> > 
> > 
> > ------------------------------------------------------------------------
> > 
> > _______________________________________________
> > DiME mailing list
> > DiME@ietf.org
> > https://www.ietf.org/mailman/listinfo/dime
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime