There are use cases for Diameter overload control where it would be useful for a server to be able to throttle traffic from a specific source. When the source is adjacent to the server, this can be accomplished easily enough by the server just sending the overload control information directly to the source in question.
However, when there are intermediaries between the server and the source (client), the current mechanism a way to do this. Adding a scope for origin-host would solve this issue. The way this would work would be for the server to construct the overload control information and attach the origin-host scope to it that matches the specific source of overload it wants to target. The information would be ignored by any other recipients as they would not have an origin-host that matches that scope when sending messages.
I think this could be an optional scope as it wouldn't be needed for all applications that may use Diameter overload control.
