Subject: [Dime] Proposed Text for Issue 43

From: Ben Campbell <[email-masked]>
Date: Mon, 20 Oct 2014 14:57:11 -0500

Steve reminded me I owned some text on issue 43. The existing text has moved to 3.6.4 in 04, but I think it stayed the same. Here are some proposed updates:

Thanks!

Ben.

--------------------

general: 

Section headings (even unnumbered ones) should be in title case. Colon missing from “Intra-Session Request” heading.

Independent Request Section:

Old:

Independent requests can be given equal treatment when making throttling decisions.

New:

Independent requests can generally be given equal treatment when making throttling decisions, unless otherwise indicated by application requirements or local policy.

Session-Initiating Requests:

Old:

Session-initiating requests represent more work than independent or intra-session requests.  Moreover, session-initiating requests are typically followed by other session-related requests.  As such, as the main objective of the overload control is to reduce the total number of requests sent to the overloaded entity, throttling decisions might favor allowing intra-session requests over session-initiating requests.  Individual session-initiating requests can be given equal treatment when making throttling decisions.

New:

Session-initiating requests often represent more work than independent or intra-session requests.  Moreover, session-initiating requests are typically followed by other session-related requests.  Since the main objective of the overload control is to reduce the total number of requests sent to the overloaded entity, throttling decisions might favor allowing intra-session requests over session-initiating requests.  In the absence of local policies or application specific requirements to the contrary, Individual session-initiating requests can be given equal treatment when making throttling decisions.

Correlated Session-Initiationg Requests and Pseudo-session requests sections:

[Existing text is fine as is]

Intra-Session Requests:

Old:

There are two classes of intra-sessions requests.  The first class consists of requests that terminate a session.  The second one contains the set of requests that are used by the Diameter client and server to maintain the ongoing session state.  Session terminating requests should be throttled less aggressively in order to gracefully terminate sessions, allow clean-up of the related resources (e.g. session state) and get rid of the need for other intra-session requests, reducing the session management impact on the overloaded entity.  The default handling of other intra-session requests might be to treat them equally when making throttling decisions.  There might also be application level considerations whether some request types are favored over others.

New:
There are two classes of intra-sessions requests.  The first class consists of requests that terminate a session.  The second class comprises requests that are used by the Diameter client and server to maintain the ongoing session state.  Implementors and operators may choose to throttle session-terminating requests less aggressively in order to gracefully terminate sessions, allow clean-up of the related resources (e.g. session state) and avoid the need for additional intra-session requests. Favoring session-termination requests may reduce the session management impact on the overloaded entity.  The default handling of other intra-session requests might be to treat them equally when making throttling decisions.  There might also be application level considerations whether some request types are favored over others.