Re: [babel] Information model: fast-convergence

[Juliusz Chroboczek <[e-mail]>]

>> Please ignore this recommendation,
>> and experiment with the values most suitable in your particular network.

> A recommended value is just that: only a recommendation.
> Implementations are free to use other values and will still be
> conformant to the standard.

    3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
       may exist valid reasons in particular circumstances to ignore a
       particular item, but the full implications must be understood and
       carefully weighed before choosing a different course.

This is a quite a bit stronger than what you describe, which is why
I attempted to convince the IESG that "example values" should be used
instead.  I find it unfortunate that I didn't manage to get through.

Perhaps we should be using the terminology defined in RFC 6919:

   1.  MUST (BUT WE KNOW YOU WON'T)

       The phrase "MUST (BUT WE KNOW YOU WON'T)" is used to indicate
       requirements that are needed to meet formal review criteria (e.g.,
       mandatory-to-implement security mechanisms), when these mechanisms
       are too inconvenient for implementers to actually implement.

       This phrase is frequently used in a contracted form in which the
       parenthetical is omitted.

-- Juliusz