Re: aspcong draft -congestion levels-

Tolga,

I suppose.  But how then does the ASP know what it is telling the SGP?

I am toying with the idea of having the ASP report congestion in terms
of number of messages (or message octets) queued rather than a congestion
level.  That might avoid the problem of managing onset and abatement
thresholds in two places (i.e, the SG could manage the thresholds and just
have the ASP report an effective occupancy level).

Onset and abatement thresholds in SS7 are often tuned to an equivalent
queing delay.  A HEARTBEAT procedure from the SGP might better determine
delay (and stuck ASPs as well).

Well, hopefully I acheived some basis for discussion with the draft.  I
surely didn't mean to cast anything in concrete.  We can tune it as we
move forward.

-brian

Tolga Asveren wrote:                           (Mon, 17 Oct 2005 10:12:50)
> Brian,
> 
> I saw that you map congestion levels in ASPSTATUS message to SS7 congestion
> levels. IMO, it is better to interprete this congestion as something not
> directly related with SS7 congestion. Any mapping could be done by SG. We
> can have 8-bits of congestion indicating 256 levels. When SG maps the
> aggregated congestion status to SS7 congestion levels, 256 is overkill but
> OTOH this congestion information may be used by SG also for message
> distribution purposes.
> 
>    Thanks,
>    Tolga
> 
> 
> 
> _______________________________________________
> Sigtran mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/sigtran

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