Presentation is loading. Please wait.

Presentation is loading. Please wait.

Draft-ietf-dime-agent-overload- 01.txt. Agenda Extensions to DOIC Questions Review of representative use cases.

Similar presentations


Presentation on theme: "Draft-ietf-dime-agent-overload- 01.txt. Agenda Extensions to DOIC Questions Review of representative use cases."— Presentation transcript:

1 draft-ietf-dime-agent-overload- 01.txt

2 Agenda Extensions to DOIC Questions Review of representative use cases

3 New report type Peer report type used to report agent overload New feature bit defined to indicate support for the peer report type

4 Interaction with Host and Realm report types Abatement treatment for host and realm reports first Abatement treatment for peer based on remaining traffic targeted towards the peer

5 Attribution Attribution of OC-Supported-Features to determine downstream peer support – Use to determine if and when OC-OLR is sent Attribution of OC-OLR – Use to ensure that the overload report came from a peer Uses OC-SourceID AVP – Contains the DiameterIdentity of the Diameter node that includes the parent AVP

6 Abatement Algorithm Selection Algorithm selected for peer report can be different than algorithm selected for host and realm reports OC-Peer-Algo AVP added to OC-Supported- Features AVP to communicate algorithm to be used for peer overload reports

7 Question: Application scope Does peer report apply to the application for transaction or all transactions sent to peer? If all applications then is there complexity in determining which transactions are to be subject to abatement treatment?

8 Representative Use Cases

9 Message nomenclature – OC-S-F (C)(L,P) in requests OC-Supported-Features OC-SourceID=C OC-Feature-Vector=Loss, Peer – C inserted the OC-S-F AVP in the message – C supports the Loss and Peer Features

10 Message nomenclature – OC-S-F (A1)(L,P)(L) in answers OC-Supported-Features OC-SourceID=A1 OC-Feature-Vector=Loss, Peer OC-Peer-Algo=Loss – A1 inserted the OC-S-F AVP in the message – The Loss Algorithm will be used for host and realm reports – The Loss algorithm will be used for peer reports

11 Message nomenclature – OC-OLR(A1)(L) OC-OLR OC-SourceID=A1 OC-Report-Type=Peer – A1 inserted the OC-S-F AVP in the message – The report of type peer contains parameters for the algorithm specified in the OC-S-F, OC-Peer- Algo AVP. In this case that is the loss algorithm.

12 Message nomenclature – OC-OLR(L) OC-OLR OC-Report-Type=Host – Normal DOIC host report – The report of type loss contains parameters for the algorithm specified in the OC-S-F, OC-Feature- Vector AVP. In this case that is the loss algorithm.

13 Single Agent, All Nodes Support Peer C C A1 S S A2

14 Single Agent C C A1 S S OC-S-F (C)(L,P) OC-S-F (A1)(L,P) OC-S-F (S)(L,P) OC-S-F (A1)(L,P)(L) OC-OLR(A1)(P) OC-S-F (C)(L,P) OC-S-F (A1)(L,P) OC-S-F (S)(L,P) OC-Supported-Features OC-SourceID=C OC-Feature-Vector=Load,Peer OC-S-F (A1)(L,P)(L) OC-OLR(A1)(L) OC-OLR (H) OC-S-F (C)(L,P) OC-S-F (A1)(L,P) OC-S-F (S)(L,P) OC-OLR (H) OC-OLR OC-Report-Type=Host OC-Supported-Features OC-SourceID=S OC-Feature-Vector=Load,Peer OC-Supported-Features OC-SourceID=A1 OC-Feature-Vector=Load,Peer OC-Peer-Algo=Load OC-OLR OC-Source-ID=A1 OC-Report-Type=Peer 5 A1 Overloaded S Overloaded

15 Notes If a Diameter node indicates support for the peer features in the OC-Supported-Features AVP then the Diameter node MUST include the OC-SourceID AVP in the OC-Supported- Features AVP. – Note: This applies to both request and answer messages. If a Diameter node will send a Peer report when overloaded then the Diameter node MUST include the OC-Peer-Algo AVP indicating the overload abatement algorithm in all OC- Supported-Features AVPs in all answer messages. If a Diameter node sends a peer overload report – and OC- OLR with OC-Report-Type of Peer – then the Diameter node MUST include the OC-SourceID in the OC-OLR AVP.

16 A1 does not support Peer C C A1 S S A2

17 A1 Supports DOIC, does not support Peer C C A1 S S OC-S-F (C)(L,P) OC-S-F (C)(L,P) or OC-S-F (L) A1 Overloaded S Overloaded OC-S-F (C)(L,P) OC-S-F (C)(L,P) or OC-S-F (C)(L) OC-S-F (L) OC-S-F (C)(L,P) OC-S-F (C) or OC-S-F (C)(L) OC-S-F (L) OC-OLR (H) OC-S-F (L) OC-OLR (H) 1 1 Even though C knows A1 does not support peer it continues to advertise support. If C does not continue to advertise support then it will never know when A1 starts to support peer. 3 3 Features advertised by the agent depends on agent policy. It can either pass the received features or modify them based on agent capabilities. S knows A1 does not support peer thus proceeds using non peer DOIC signaling. 2 2

18 A1 Does not supports DOIC C C A1 S S OC-S-F (C)(L,P) OC-S-F (L) A1 Overloaded S Overloaded OC-S-F (C)(L,P) OC-S-F (L) Same as above as agent doesn’t have ability to report overload until it support the peer feature. OC-S-F (C)(L,P) OC-S-F (L) OC-OLR (H) OC-S-F (L) OC-OLR (H)

19 C does not support peer C C A1 S S A2

20 C does not support peer C C A1 S S OC-S-F (L) OC-S-F (A1)(L,P) OC-S-F (S)(L,P) OC-S-F (L) OC-OLR (H) OC-S-F (A1)(L,P) OC-S-F (S)(L,P) OC-OLR (H) OC-S-F (L) A1 Overloaded S Overloaded OC-S-F (L) OC-S-F (A1)(L,P) OC-S-F (S)(L,P) OC-S-F (L) 2 A1 knows C does not support peer thus proceeds using non peer DOIC signaling. A1 knows C does not support peer thus does not include the OC-OLR of type peer in answer messages for transactions received from A.

21 Agent Chain – All nodes support peer C C A11 S S A12 A21 A22

22 C C A11 A21 OC-S-F (C)(L,P)OC-S-F (A1)(L,P) OC-S-F (A2)(L,P)(L) OC-S-F (A1)(L,P)(L) Agent Chain – A2 overloaded S S OC-S-F (A2)(L,P) OC-S-F (S)(L,P) A2 Overloaded S Overloaded OC-S-F (C)(L,P)OC-S-F (A1)(L,P)OC-S-F (A2)(L,P) OC-S-F (A2)(L,P)(L) OC-OLR (A2)(L) OC-S-F (A1)(L,P)(L) OC-S-F (S)(L,P) OC-S-F (C)(L,P)OC-S-F (A1)(L,P)OC-S-F (A2)(L,P) OC-S-F (A2)(L,P)(L) OC-OLR (A2)(L) OC-OLR (H) OC-S-F (A1)(L,P)(L) OC-OLR (H) OC-S-F (S)(L,P) OC-OLR (H) 1 1 A1 strips the OC-OLR AVP of type peer received from A2.

23 Agent Chain – A11 does not support peer C C A11 S S A12 A21 A22

24 C C A11 A21 OC-S-F (C)(L,P) OC-S-F (L) OC-S-F (A1)(L,P)(L) Agent Chain – A11 does not support peer S S OC-S-F (A2)(L,P) OC-S-F (S)(L,P) A2 Overloaded S Overloaded OC-S-F (C)(L,P) OC-S-F (A2)(L,P) OC-S-F (L)OC-S-F (S)(L,P) OC-S-F (C)(L,P) OC-S-F (A2)(L,P) OC-S-F (A2)(L,P)(L) OC-OLR (A2)(L) OC-OLR (H) OC-S-F (A1)(L,P)(L) OC-OLR (H) OC-S-F (S)(L,P) OC-OLR (H) 1 3 A2 does not include the OC-OLR in answer messages sent to A1. OC-S-F (A2)(L,P)(L) 1 3 A1 passed through C’s OC-S-F AVP. 2 A2 knows that A1 does not support the peer feature and, as such, does not include peer signaling in answer messages. 2

25 Long Agent Chain C C A11 S S A12 A21 A22 A31 A32

26 Long Agent Chain C1 A1 A2 A3 S1 OC-S-F (C)(L,P)OC-S-F (A1)(L,P)OC-S-F (A2)(L,P)OC-S-F (A3)(L,P) OC-S-F (S)(L,P)OC-S-F (A3)(L,P)(L)OC-S-F (A2)(L,P)(L)OC-S-F (A1)(L,P)(L) A3 Overloaded OC-S-F (C)(L,P)OC-S-F (A1)(L,P)OC-S-F (A2)(L,P)OC-S-F (A3)(L,P) OC-S-F (S)(L,P)OC-S-F (A3)(L,P)(L)OC- OC-OLR (A3)(L) OC-S-F (A2)(L,P)(L)OC-S-F (A1)(L,P)(L) S Overloaded OC-S-F (C)(L,P)OC-S-F (A1)(L,P)OC-S-F (A2)(L,P)OC-S-F (A3)(L,P) OC-S-F (S)(L,P) OC-OLR (H) OC-S-F (A3)(L,P)(L)OC- OC-OLR (A3)(L) OC-OLR (H) OC-S-F (A2)(L,P)(L) OC-OLR (H) OC-S-F (A1)(L,P)(L) OC-OLR (H)

27 Long Agent Chain – Agent doesn’t support DOIC C C A11 S S A12 A21 A22 A31 A32

28 Long Agent Chain – Agent doesn’t support DOIC C1 A1 A2 A3 S1 OC-S-F (C)(L,P)OC-S-F (A1)(L,P) OC-S-F (A3)(L,P) OC-S-F (S)(L,P)OC-S-F (L) OC-S-F (A1)(L,P)(L) A3 Overloaded OC-S-F (C)(L,P)OC-S-F (A1)(L,P)OC-S-F (A2)(L,P)OC-S-F (A3)(L,P) OC-S-F (S)(L,P)OC-S-F (A3)(L,P)(L)OC- OC-OLR (A3)(L) OC-S-F (A2)(L,P)(L) OC-OLR (A3)(L) OC-S-F (A1)(L,P)(L) S Overloaded OC-S-F (C)(L,P)OC-S-F (A1)(L,P)OC-S-F (A2)(L,P)OC-S-F (A3)(L,P) OC-S-F (S)(L,P) OC-OLR (H) OC-S-F (A3)(L,P)(L)OC- OC-OLR (A3)(L) OC-OLR (H) OC-S-F (A2)(L,P)(L) OC-OLR (A3)(L) OC-OLR (H) OC-S-F (A1)(L,P)(L) OC-OLR (H)

29 Next Steps Working group review of draft


Download ppt "Draft-ietf-dime-agent-overload- 01.txt. Agenda Extensions to DOIC Questions Review of representative use cases."

Similar presentations


Ads by Google