Opened 5 years ago

Closed 5 years ago

#68 closed defect (fixed)

Loss as the common abatemen algorithm

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

Some text is misleading since it may imply that one feature shall be in common between reporting and reacting node to progress, but in reality we only need to have one common abatement algorithm, and in this draft, LOSS is defined as default, then there is always one common algorithm

Corrections are required in following clauses:

Original text:

4.2.3. Reporting Node Behavior (Normative)

...

The operation on the reporting node is straight forward. The reporting node learns the capabilities of the reacting node when it receives the OC-Supported-Features AVP as part of any Diameter request message. If the reporting node shares at least one common feature with the reacting node, then the DOIC can be enabled between these two endpoints. See Section 4.1 for further discussion on the capability and feature announcement between two endpoints.

Proposed modification:

4.2.3. Reporting Node Behavior (Normative)

...

The reporting node learns the capabilities of the reacting node when it receives the OC-Supported-Features AVP as part of any Diameter request message. Both reacting and reporting node MUST share at least one abatement algorithm, in fact, they share at least the loss algorithm, that is defined in this document as the default abatement algorithm, then the DOIC can always be enabled between these two endpoints at least with the default algorithm. See Section 4.1 for further discussion on the capability and feature announcement between two endpoints.

Original text:

6.1. OC-Supported-Features AVP

...

During the message exchange the overload control endpoints express their common set of supported capabilities. The reacting node includes the OC-Supported-Features AVP that announces what it supports. The reporting node that sends the answer also includes the OC-Supported-Features AVP that describes the capabilities it supports. The set of capabilities advertised by the reporting node depends on local policies. At least one of the announced capabilities MUST match. If there is no single matching capability the reacting node MUST act as if it does not implement DOIC and cease inserting any DOIC related AVPs into any Diameter messages with this specific reacting node.

Editor's note: The last sentence conflicts with the last sentence two paragraphs up. In reality, there will always be at least one matching capability as all nodes supporting DOIC must support the loss algorithm. Suggest removing the last sentence.

Proposed text:

6.1. OC-Supported-Features AVP

...

During the message exchange the overload control endpoints express their common set of supported capabilities. The reacting node includes the OC-Supported-Features AVP that announces what it supports. The reporting node that sends the answer also includes the OC-Supported-Features AVP that describes the capabilities it supports. The set of capabilities advertised by the reporting node depends on local policies. Both reacting and reporting node MUST share at least one abatement algorithm, in fact, they share at least the loss algorithm, that is defined in this document as the default abatement algorithm, then the DOIC can always be enabled between these two endpoints at least with the default algorithm. See Section 4.1 for further discussion on the capability and feature announcement between two endpoints.

Change History (1)

comment:1 Changed 5 years ago by srdonovan@…

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

Consensus reached to change the wording to the following: " Since the "loss" abatement algorithm [crossref] is mandatory to implement, DOIC can always be enabled between these two endpoints.”

Changed in both sections mentioned above with expectation that the AVP description will be updated to pull out behavior definitions.

Note: See TracTickets for help on using tickets.