Re: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control - PLEASE COMMENT!

[Janet P Gunn <[e-mail]>]

(Coming out from under analysis of the Boston Bombing overload, the 
Oklahoma Tornado overload, etc.)

I am working on some more detailed comments, but here are a couple of 
higher level things

Needs to be made clearer that the "default algorithms" are simply 
"existence" examples, and that other rate based algorithms can be used.

Need to be clearer about what the constraints (how strictly they limit 
traffic) are on other algorithms (and for the default algorithms too - if 
you make TAU too big , you are not really limiting to a specific rate)

Need to make it clearer that only "T" (the target rate) is transmitted in 
the "oc" value.  The other parameters (TAU, TAU0, TAU1, TAU2) are not part 
of the message protocol. 
Are you expecting that there will be some external negotiation between the 
client and the server on appropriate values for these "tolerance" 
parameters? 
 Or are you expecting that the client will pick values for these 
parameters on its own, without involving the server in the decision?

Since they are default algorithms, it would make sense (and make it easier 
to follow) to give default, or recommended,  values for TAU, TAU0, TAU1, 
TAU2.

More later, and hoping these thunderstorms don't lead to more overloads!

Janet
.

[e-mail] wrote on 06/12/2013 09:36:17 AM:

> From: Salvatore Loreto <[e-mail]>
> To: Volker Hilt <[e-mail]>
> Cc: "[e-mail]" <[e-mail]>
> Date: 06/12/2013 09:36 AM
> Subject: [sip-overload] WGLC: draft-ietf-soc-overload-rate-control -
> PLEASE COMMENT!
> Sent by: [e-mail]
> 
> Dear SoC WG participants
> 
> we are trying to finalize all the SIP Overload efforts before the next 
> IETF meeting in Berlin.
> 
> The Overload-Rate-Control is the last wg-item we have, and in order to 
> progress it,
> we need people reading and reviewing and a clear evidence that people 
> have done it.
> Comments and especially full and deep reviews of the draft are really 
> appreciate, but also simple feedback
> like "I have read the draft and I think is ready for IESG" would be 
enough.
> 
> We haven't received any comments from the first call so we are extending 

> the WGLC till Fri Jun 21th.
> 
> This is our last draft, let's make a final push to get this done.
> 
> Thanks
> Salvatore
> 
> On 5/24/13 12:59 PM, Volker Hilt wrote:
> > Folks,
> >
> > with draft-ietf-soc-overload-control-13 getting close to finalization, 

> > we are ready to start the WGLC for our last remaining draft:
> >
> > http://www.ietf.org/id/draft-ietf-soc-overload-rate-control-04.txt
> >
> > The WGLC will end on Fri Jun 7.
> >
> > Please review the draft and send your comments to the mailing list. It 

> > is very important that the WG reviews this draft. YOUR comments are 
> > important - even if it is just to say you agree!
> >
> > This is our last draft, let's make a final push to get this done.
> >
> > Thanks,
> >
> > Salvatore and Volker
> > SOC WG co-chairs
> >
> 
> 
> _______________________________________________
> sip-overload mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sip-overload