Opened 6 years ago

Closed 5 years ago

#35 closed defect (wontfix)

additional report types are proposed

Reported by: lionel.morand@… Owned by: Ulrich Wiehe
Priority: major Milestone:
Component: draft-ietf-dime-ovli Version:
Severity: Active WG Document Keywords:
Cc:

Description (last modified by lionel.morand@…)

The -01 draft does not address the 3GPP requirement to allow reporting DOIC endpoints to request different amount of load reduction from different clients (see TR 29.809 clause 6.4.7). Since 3GPP is the main consumer of DOIC it is proposed to address this requirement by adding two new report types. two additional report types are proposed:

2 A host per client report. The overload treatment should apply to

requests for which all of the following conditions are true: a) The Destination-Host AVP is present in the request and its value

matches the value of the Origin-Host AVP of the received message that contained the OC-OLR AVP.

b) The value of the Destination-Realm AVP in the request matches the

value of the Origin-Realm AVP of the received message that contained the OC-OLR AVP.

c) The value of the Application-ID in the Diameter Header of the

request matches the value of the Application-ID of the Diameter Header of the received message that contained the OC-OLR AVP.

d) The values of the Origin-Host and Origin-Realm AVPs in the request

match the values of the Destination-Host and Destination-Realm AVPs respectively of the received message that contained the OC- OLR AVP.

3 A realm per client report. The overload treatment should apply to

requests for which all of the following conditions are true: a) The Destination-Host AVP is absent in the request. b) The value of the Destination-Realm AVP in the request matches the

value of the Origin-Realm AVP of the received message that contained the OC-OLR AVP.

c) The value of the Application-ID in the Diameter Header of the

request matches the value of the Application-ID of the Diameter Header of the received message that contained the OC-OLR AVP.

d) The values of the Origin-Host and Origin-Realm AVPs in the request

match the values of the Destination-Host and Destination-Realm AVPs respectively of the received message that contained the OC- OLR AVP.

Change History (4)

comment:1 Changed 6 years ago by lionel.morand@…

  • Reporter changed from lionel.morand@… to lionel.morand@…

comment:2 Changed 6 years ago by lionel.morand@…

  • Description modified (diff)

comment:3 Changed 6 years ago by jouni.nospam@…

  • Component changed from draft-docdt-dime-ovli to draft-ietf-dime-ovli

comment:4 Changed 5 years ago by srdonovan@…

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

As discussed in Toronto working group meeting and previously on the mailing list, this item is deferred to a potential extension to the DOIC solution.

Note: See TracTickets for help on using tickets.