Re: [Dime] [dime] #46 (draft-docdt-dime-ovli): Bad normative advice on not letting overload reports expire

["dime issue tracker" <[e-mail]>]

#46: Bad normative advice on not letting overload reports expire


Comment (by [e-mail]):

 Section 4.5., paragraph 3 -

 Current -02 wording:

 As a general guidance for implementations it is RECOMMENDED never to
    let any overload report to timeout.  Following to this rule, an
    overload endpoint should explicitly signal the end of overload
    condition and not rely on the expiration of the validity time of the
    overload report in the reacting node.  This is achieved by sending an
    updated overload report (meaning it must contain a new sequence
    number) with the OC-Validity-Duration AVP value set to zero ("0").

 Change to:

 When a reporting node has recovered from overload, it SHOULD invalidate
 any existing overload reports in a timely matter. This can be achieved by
 sending an updated overload report (meaning the OLR contains a new
 sequence number) with the OC-Validity-Duration AVP value set to zero
 ("0"). If the overload report is about to expire naturally, the reporting
 node MAY choose to simply let it do so.

  A reacting node MUST invalidate and remove an overload report that
   expires without an explicit overload report containing an OC-Validity-
 Duration
   value set to zero ("0").

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-docdt-dime-
  [e-mail]        |  [e-mail]
     Type:  defect       |      Status:  new
 Priority:  minor        |   Milestone:
Component:  draft-       |     Version:  1.0
  docdt-dime-ovli        |  Resolution:
 Severity:  Active WG    |
  Document               |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://tools.ietf.org/wg/dime/trac/ticket/46#comment:1>
dime <http://tools.ietf.org/wg/dime/>