Opened 5 years ago

Closed 5 years ago

#67 closed defect (fixed)

OCS for Reporting Nodes - Expiry Time

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

What does "Validity Duration" mean as the information stored in OCS for Reporting Nodes?

We need to store some information that allow the reporting node to calculate a Validity-Duration value to be included in each OC-OLR AVP Then, I presume we need just Expiry Time, and then value to be included in each Validation-Duration AVP is calculated based on this.

Then, original text:

4.2.1.2. Overload Control States for Reporting Nodes

A reporting node maintains per supported Diameter application and per supported (and eventually selected) Abatement Algorithm an Overload Control State.

An Overload Control State may be identified by the pair of Application-Id and supported Abatement Algorithm.

The Overload Control State for a given pair of Application and Abatement Algorithm could include the information:

o Sequence number

o Validity Duration and Expiry Time

o Algorithm specific input data (e.g. Reduction Percentage for

Loss)

Overload Control States for reporting nodes containing a validity duration of 0 sec. should not expire before any previously sent (stale) OLR has timed out at any reacting node.

Editor's note: This statement is unclear and contradictory with other statements. A validity timer of zero seconds indicates that the overload condition has ended and abatement is no longer requested.

Proposed modification:

4.2.1.2. Overload Control States for Reporting Nodes

A reporting node maintains per supported Diameter application and per supported (and eventually selected) Abatement Algorithm an Overload Control State.

An Overload Control State may be identified by the pair of Application-Id and supported Abatement Algorithm.

The Overload Control State for a given pair of Application and Abatement Algorithm could include the information:

o Sequence number

o Expiry Time

o Algorithm specific input data (e.g. Reduction Percentage for

Loss)

Expiry Time is used by the reporting node to calculate the value to be included in each Validity-Duration AVP, as part of the overload report.

Change History (1)

comment:1 Changed 5 years ago by srdonovan@…

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

From notes:

Summary: in the current text describing the OCS information elements, it is said that Validity Duration and expiry time need to maintained, whereas actually only the expiry time is required to manage the OCS, this information element derived from the validation time received in the OLR.

output of the discussion: It was agreed that OCS information discussed in the draft is given as illustration of data required to manage the OCS in reporting/reacting node and this does not imply that each of information element needs to be locally stored. For instance, some data element can be derived from others. It was also discussed how many times a reporting node needs to send an OLR with the validation duration set to "0" to indicate that the overload situation is over. It was agreed that the reporting node has to send the OLR with validation duration "0" as long as all the reacting maintaining a corresponding active OCS have received the OLR. If there is a way for the reporting node to ensure that all the nodes will receive the OLR as soon as sent, the OLR can be sent only once.

Changed one editor's note in section 4.2.1.3, removed the other editor's note.

Added the following to section 4.2.3:

All OLRs sent have an expiration time calculated by adding the

validity-duration contained in the OLR to the time the message was sent. Transit time for the OLR can be safely ignored. The reporting node can ensure that all reacting nodes have received the OLR by continuing to send it in answer messages until the expiration time for all OLRs sent for that overload contition have expired.

Note: See TracTickets for help on using tickets.