Re: # of Signalling Processes

Ilie,

Ilie Glib wrote:                                                      (Wed, 09 May 2007 14:03:07)
> 
>    Salil,
> 
>    as  you  pointed  out yourself, there is no much sense to support more
>    than 16 M3UA ASPs within an AS for ITU-T markets.

The number of SLS values in the SLS field of the MTP routing label is
not a limit on loadsharing from ASP over SGP.  In fact, ASPs serving a
load-share AS are not required to load-share over available SGP.
Nevertheless, when an ASP load-shares over available SGP, it is coherent
traffic flows that need to be sent to the same SGP (not the SLS value
which is merely derived from the traffic flow).  For distributing
coherent flows over SGP, the OPC, DPC, NI and SI fields can also be
taken into account, permiting coherent load sharing over many more than
16 SGP.

The other way around, the SGP can also take into account OPC, DPC, NI
and SI fields in addition to SLS when loadsharing.

>    What  is  the  point to support more ASPs then? If we conclude - 16 is
>    enough,  can  this create interoperability problems for systems having
>    more  than 16 ASPs/IPSPs? For instance, can that result in overloading
>    those poor 16 ASPs that your SG accepted to go active?
>    Regards

16 is not a restriction.  AS define a number: the minimum number of
active ASPs necessary to service an AS; to permit prevention of
overloads.

--brian

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