[Dime] [dime] #31: Sending OC-Ongoing-Throttling-Info AVP in request messages that survived a throttling

["dime issue tracker" <[e-mail]>]

#31: Sending OC-Ongoing-Throttling-Info AVP in request messages that survived a
throttling

 It has been proposed to define an OC-Ongoing-Throttling-Info AVP that is
 to be included by the reacting DOIC endpoint in request messages that
 survived a throttling. This AVP would indicate the Sequence-Number
 (TimeStamp) of the OLR according to which the throttling (which was
 survived) is performed. Absence of this AVP indicates that currently no
 throttling is performed.  Reporting DOIC endpoints may use this
 information in order to detect whether there is a need to update the
 reacting DOIC endpoint with the latest OLR.
 Absence of this feedback mechanism would result in the need for the
 reporting node to send OC-OLR AVPs in every answer as the reporting DOIC
 endpoint cannot know whether the reacting DOIC endpoint is actually doing
 the right thing with regard to throttling/not throttling.
 The feedback mechanism improves robustness as it allows the reporting DOIC
 endpoint to detect and correct inappropriate throttling by the reacting
 DOIC endpoint (caused by whatever reason).
 The feedback mechanism also allows to address REQ 18 from RFC 7068.
 In summary it is proposed to define the OC-Ongoing-Throttling-Info AVP to
 be used in request messages that survived a throttling.

-- 
--------------------------------------+--------------------------
 Reporter:  [e-mail]  |      Owner:  Ulrich Wiehe
     Type:  defect                    |     Status:  new
 Priority:  major                     |  Milestone:
Component:  draft-docdt-dime-ovli     |    Version:
 Severity:  Active WG Document        |   Keywords:
--------------------------------------+--------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/dime/trac/ticket/31>
dime <http://tools.ietf.org/wg/dime/>