RE: [RPRWG] Initial value of hopsToCongestion and allowedRateCongested variables
John,
In that case, it might make sense to recommend an initial value
of 0 for them in the spec, but not require it.
-Anoop
> -----Original Message-----
> From: John Lemon [mailto:JLemon@xxxxxxxxxxxx]
> Sent: Thursday, November 06, 2003 10:54 AM
> To: Fredrik Davik; stds-802-17@xxxxxxxx
> Subject: RE: [RPRWG] Initial value of hopsToCongestion and
> allowedRateCongested variables
>
>
>
> Fredrik,
>
> I see no one else has replied, so I'll give my opinion.
>
> While I think it would be most polite to start with these set
> 0, I believe that it doesn't really matter what these
> variables are initialized to. They will fairly quickly
> converge to the correct value.
>
> jl
>
> -----Original Message-----
> From: Fredrik Davik [mailto:bjornfd@xxxxxxxxx]
> Sent: Wednesday, November 05, 2003 3:22 AM
> To: stds-802-17@xxxxxxxx
> Subject: [RPRWG] Initial value of hopsToCongestion and
> allowedRateCongested variables
>
>
>
> The initial value of hopsToCongestion variable is not defined. For
> agressive mode, this means that a station on the ring will either
> start sending at maxAllowedRate or allowedRateCongested.
>
> (depending on whatever the initial value of hopsToCongestion is in the
> specific implementation and which stations the sending node sends to
> following the start-up).
>
> Initial value of allowedRateCongested does not seem to be
> initialized either.
>
> If a ramp-up is desired, the hopsToCongestion and allowedRateCongested
> should both be set to 0.
>
> Any thoughts on this issue?
>
> Best Regards,
> Fredrik