Hi, Alper,

Your description does sound like a SHOULD, but something like your description should go into the "SHOULD ... unless <doing link-specific timers>"...

Thanks,

Spencer

From: "Alper Yegin" <[EMAIL PROTECTED]>


> 5.2.  Sequence Number and Retransmission
>
> Spencer: If the retransmission timer calculation is a SHOULD, some
guidance
> about when to use different timer calculations needs to be given ("why
is
> this not a MUST?"). At the very least, these retransmission timers (as
> computed in these documents) are specified to include a randomization
> factor to prevent sustained synchronization - I'm assuming that any
> alternative method chosen should include a randomization factor, but it
> would be good to provide explicit guidance.
>
>   The retransmission timers SHOULD be calculated as described in
>   [RFC2988] to provide congestion control.  See Section 9 for default
>   timer and maximum retransmission count parameters.

I don't come up with a special circumstance where different timer
calculation algorithms are used.  We can simply make it a MUST if
there is no objection.

A given deployment may take into account things like the link
characteristics (radio behavior) and choose to have its own retransmission
timers -- possibly more optimized. In order to leave the door open to such
enhancements, I think it is best if we don't mandate retransmission timers.

Alper






_______________________________________________
Gen-art mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/gen-art

Reply via email to