Re: [Dime] Issue#35 conclusion

[Maria Cruz Bartolome <[e-mail]>]

Dear Ulrich,

See below please
Best regards
/MCruz

From: Wiehe, Ulrich (NSN - DE/Munich) [mailto:[e-mail]]
Sent: jueves, 06 de marzo de 2014 10:12
To: Maria Cruz Bartolome; [e-mail]
Subject: RE: [Dime] Issue#35 conclusion

Dear MCruz,

for my clarification:
what you say about Host reports is also true for Realm-Routed-Request reports. Can you please confirm.
[MCruz] I think this case is different. If we agree that realm reports are only generated by agents (as an aggregated report based on host reports and potentially another implementation dependent criteria), then the server itself does not require a traffic-to-realm reduction, on the contrary, the host only requests a traffic-to-host reduction. Agent may or not (I think this is up in the draft) to  forward back to the original client this host-report. Then, not sure if we really need something else here.

Proposal b) does not address the 3GPP requirement from TR 29.809 clause 6.4.7.  please confirm.
[MCruz] It does address the 3GPP requirement in general, but not for one specific case:  "There is one special case here, when the agent is acting on behalf of the client (i.e. for a non-supporting client or for an agent SFE with topology hiding)".

Also proposal b)  impacts the reporting node which must not send client specific OLRs (with separate sequence number streams for different clients)
[MCruz] I do not think so. In the case I mentioned, when the agent is acting on behalf of the client, it is always the receiver of the answers (i.e. from a host perspective, the client is the agent, and then there are not separate sequence number streams).

Also, shouldn't b) read:
We expect the agent to apply this host type / realm-routed-request type report to any non-DOIC-supporting client that is sending requests towards this host/realm.
[MCruz] Yes, any non-DOIC-supporting client.

Also, you say:
b) does not require any changes to the actual draft

I guess at least some clarification is required as some (Lionel, Nirav, but not Steve)  think it is "natural" and "implicit" that agents would do the per client behaviour as a default.
[MCruz] Agreed, at least clarification is required.

An alternative proposal that addresses the complexity argument for agents but at the same time at least partly addresses the 3GPP requirement would be to make use of a feature flag: clients allways set the flag, agents do not set the flag, reporting nodes may send client specific OLRs when the flag in the request was set. This has no big impact to clients (only always set the feature flag), no impacts to agents, and allows (if so desired) reporting nodes to make use of the client specific throttling (at least in some cases).

Best regards
Ulrich



From: DiME [mailto:[e-mail]] On Behalf Of ext Maria Cruz Bartolome
Sent: Thursday, March 06, 2014 9:00 AM
To: [e-mail]<mailto:[e-mail]>
Subject: Re: [Dime] Issue#35 conclusion



Dear all,

This mail thread started proposing new OLR reports to request reduction for one specific client.
However, the discussion clarified that as it is the draft today, Host-report is sent from a reporting node towards the client from where it receives the request. Then, reduction is requested per client in all cases already.
There is one special case here, when the agent is acting on behalf of the client (i.e. for a non-supporting client or for an agent SFE with topology hiding). In this case, the reporting node sends host-report to agent. Here we have two options:


a)     We expect the agent to apply the host-report received in an answer to specifically the client that sent the corresponding request

This requires some extra complexity at agent side.

But here we have one more option: allow the reporting node to choose whether it prefers to apply this host-report to "all-client" vs "one-client". That increases again the complexity (at reporting node, protocol-wise, and at agent).



b)     We expect the agent to apply this host-report to any client that is sending a request towards this agent

In my opinion, this is the best approach, it reduces complexity and increases robustness.

Therefore, I will be in favor of option b), which does not require any changes to the actual draft.

Let me know your opinions.
Best regards
/MCruz