Opened 5 years ago

Closed 5 years ago

#71 closed defect (fixed)

Active overload report even if OC-OLR is not received

Reported by: maria.cruz.bartolome@… Owned by: draft-ietf-dime-ovli@…
Priority: minor Milestone:
Component: draft-ietf-dime-ovli Version:
Severity: Active WG Document Keywords:
Cc:

Description

Answer message may not include OC-OLR and still the reporting node be overloaded, since it is considered as "no change", as documented in 4.2.1.3:

Reacting nodes do not delete an OCS when receiving an answer message that does not contain an OC-OLR AVP (i.e. absence of OLR means "no change").

Original text:

4.1.1. Reacting Node Behavior (Normative)

... Note that the loss abatement algorithm is the only feature described in this document and it does not require action to be taken by the reacting node except when the answer message also has an overload report. This behavior is described in Section 4.2 and Section 5.

Proposed text:

4.1.1. Reacting Node Behavior (Normative)

... Note that the loss abatement algorithm is the only feature described in this document and it does not require action to be taken by the reacting node except when there is an active overload report. This behavior is described in Section 4.2 and Section 5.

Change History (1)

comment:1 Changed 5 years ago by srdonovan@…

  • Resolution set to fixed
  • Status changed from new to closed

Updated with the above suggested wording.

Note: See TracTickets for help on using tickets.