[Dime] [dime] #57: Handling of "Realm-Routed" Overload report type

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

#57: Handling of "Realm-Routed" Overload report type

 I'm assuming the name of the realm overload report in the -01 version will
 be changed to realm-routed.  This issue applies independent of the actual
 name of the report.

 The current behavior assumed for the realm-routed report is that the
 reacting node, generally the client, will reduce the percentage of realm
 routed requests sent to the reporting node.

 This is actually bad behavior and could result in the client throttling
 traffic that could have been handled by the full set of servers for that
 Diameter application.

 Consider the case where there are n servers for a Diameter application and
 all of those server are able to handle any transaction for that
 application.

 When one of those servers becomes overloaded and wishes to decrease the
 number of new sessions, the primary use of realm-routed requests.  The
 server will generate an OLR of type realm-routed.

 Assume in this case that the other servers are all healthy and able to
 handle new sessions.

 Clients will not have the knowledge that there are other servers in the
 network able to handle the new session and will have no choice but the
 throttle a percentage of the new session requests.  Even when these
 throttled requests could have been handled by any of the non overloaded
 servers.

 The proposal is to specify that realm-routed reports must be handled by
 DOIC-supporting agents.  Agents will understand if there are other servers
 able to handle the new session and, if so, can adjust the percentage of
 requests routed to the overloaded server.

 Agents that handle the realm-routed OLR must remove the request from the
 answer before relaying the answer to client.  This prevents the report
 from being acted on by either multiple agents (if multiple are in the
 path) or by an agent and a client.

 Clients that receive the realm-routed OLR must handle the OLR by
 throttling the requested percentage.

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

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