[sip-overload] draft-ietf-soc-overload-control-09

["Vijay K. Gurbani" <[e-mail]>]

Folks: The last iteration of the loss-based draft's default algorithm
[1] was presented in the Paris IETF.  List discussions right before the
meeting [2] indicated that the algorithm will need to go through one
more revision.  The reasons for this revision are outlined as the
last two bullet items in [2].

I believe that to address these two bullet items, we have to make the
algorithm responsive to the traffic mix, i.e., category 1 and category
2 prioritization markers need to reflect the mix of the traffic at any
point in time.  That way, the algorithm can adequately respond to any
situation.  In an emergency situation, the number of category 2
requests will dominate, so the reduction will occur from these whereas
in non-emergency situations, normal messages will dominate the traffic
mix and it makes sense to cull requests from category 1 as much as we
can before moving to category 2.

An updated algorithm that takes the changing traffic mix into account
is now part of the revised version of the draft, version -09 [3].  I
would appreciate review of the updated algorithm by the WG to make sure
it is on the right track.

I have also attended to all but two of the comments in [2].  I need to
think on how to attend to the comments related to S5.4 in [2].  Besides
these, I do not believe that there are any other outstanding comments.

[1] 
http://tools.ietf.org/html/draft-ietf-soc-overload-control-08#section-6.3
[2] http://www.ietf.org/mail-archive/web/sip-overload/current/msg00764.html
[3] http://tools.ietf.org/html/draft-ietf-soc-overload-control-09

Thanks,

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / [e-mail]
Web:   http://ect.bell-labs.com/who/vkg/