Re: query on SUA RFC 3868 : Sequence Control

"Brian F. G. Bidulock" <[email protected]>
Newsgroups gmane.ietf.sigtran
Organization http://www.openss7.org/
Message-ID <[email protected]>
JEYASEELAN,

RFC 3868 Section 3.10.22 Sequence Control:

3.10.22.  Sequence Control

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |         Tag = 0x0116          |             Length = 8        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                        Sequence  Control         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Sequence Control (6.2.2.2.2/Q.711)

   The field is coded with the value of the sequence control parameter
   associated with a group of messages and are chosen so as to ensure
   proper loadsharing of message groups over SLS values while ensuring
   that sequence control values within message groups have the sequence
   control value coded with the same value as the initial message of the
   message group.


So, pick a value that ensures proper loadsharing over SLS for your
protocol class 0 messages.

--brian


JEYASEELAN Samuel Durairaj wrote:                                               (Sat, 21 Mar 2009 16:02:10)
> 
>    Hi,
>    The CLDT msg mentions the parameter 'Sequence Control' as a  mandatory
>    in the rfc, but as per the Q.711, section 6.2.2.2.2 it is an optional
>    parameter for the protocol class 0.
>    So the qtn is, what shall be the value to be stored in the sequence
>    control while sending the CLDT to ASP?
>    Thanks & Regards
>    Samuel

> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/sigtran


-- 
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.