Opened 5 years ago

Closed 5 years ago

#69 closed defect (fixed)

Report Type - Realm, with absent Destination-Host

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

In clause 6.6, host report was updated to add:

... or the Destination-Host is

not present in the request but the value of peer identity associated with the connection used to send the request matches the value of the Origin-Host AVP of the received message that contained the OC-OLR AVP.

but this clarification needs to be included as well for realm report.

Original text:

1 A realm report. The overload treatment should apply to requests

for which all of the following conditions are true:

The Destination-Host AVP is absent in the request.

...

Proposed text:

1 A realm report. The overload treatment should apply to requests

for which all of the following conditions are true:

The Destination-Host AVP is absent in the request and the the value of peer identity associated with the connection used to send the request does not match the value of the Origin-Host AVP of the received message that contained the OC-OLR AVP.

Change History (1)

comment:1 Changed 5 years ago by srdonovan@…

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

Added the following wording resulting from discussions at the interim meeting:

When a reporting node sends an OLR, it effectively delegates any necessary throttling to downstream nodes. Therefore, the reporting node SHOULD NOT apply throttling to the set of messages to which the OLR applies. That is, the same candidate set of messages SHOULD NOT be throttled multiple times.

However, when the reporting node sends and OLR downstream, it MAY still be responsible to apply other abatement methods, such as diversion, or request throttling requests for other reasons. For example, an agent or server might have a configured rate limit for each client, and throttle requests that exceed that limit, even if such requests had already been candidates for throttling by downstream nodes.

Note: See TracTickets for help on using tickets.