draft-ietf-dime-doic-rate-control-06.txt | draft-ietf-dime-doic-rate-control-07.txt | |||
---|---|---|---|---|
Diameter Maintenance and Extensions (DIME) S. Donovan, Ed. | Diameter Maintenance and Extensions (DIME) S. Donovan, Ed. | |||
Internet-Draft Oracle | Internet-Draft Oracle | |||
Intended status: Standards Track E. Noel | Intended status: Standards Track E. Noel | |||
Expires: September 28, 2017 AT&T Labs | Expires: March 31, 2018 AT&T Labs | |||
March 27, 2017 | September 27, 2017 | |||
Diameter Overload Rate Control | Diameter Overload Rate Control | |||
draft-ietf-dime-doic-rate-control-06.txt | draft-ietf-dime-doic-rate-control-07.txt | |||
Abstract | Abstract | |||
This specification documents an extension to the Diameter Overload | This specification documents an extension to the Diameter Overload | |||
Indication Conveyance (DOIC) [RFC7683] base solution. This extension | Indication Conveyance (DOIC) [RFC7683] base solution. This extension | |||
adds a new overload control abatement algorithm. This abatement | adds a new overload control abatement algorithm. This abatement | |||
algorithm allows for a DOIC reporting node to specify a maximum rate | algorithm allows for a DOIC reporting node to specify a maximum rate | |||
at which a DOIC reacting node sends Diameter requests to the DOIC | at which a DOIC reacting node sends Diameter requests to the DOIC | |||
reporting node. | reporting node. | |||
skipping to change at page 1, line 35 ¶ | skipping to change at page 1, line 35 ¶ | |||
document are to be interpreted as described in RFC 2119 [RFC2119]. | document are to be interpreted as described in RFC 2119 [RFC2119]. | |||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on September 28, 2017. | This Internet-Draft will expire on March 31, 2018. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2017 IETF Trust and the persons identified as the | Copyright (c) 2017 IETF Trust and the persons identified as the | |||
document authors. All rights reserved. | document authors. All rights reserved. | |||
This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
publication of this document. Please review these documents | publication of this document. Please review these documents | |||
carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
described in the Simplified BSD License. | described in the Simplified BSD License. | |||
Table of Contents | Table of Contents | |||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
skipping to change at page 18, line 20 ¶ | skipping to change at page 18, line 20 ¶ | |||
11.1. Normative References | 11.1. Normative References | |||
[I-D.ietf-dime-agent-overload] | [I-D.ietf-dime-agent-overload] | |||
Donovan, S., "Diameter Agent Overload", draft-ietf-dime- | Donovan, S., "Diameter Agent Overload", draft-ietf-dime- | |||
agent-overload-00 (work in progress), December 2014. | agent-overload-00 (work in progress), December 2014. | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
<http://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an | [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an | |||
IANA Considerations Section in RFCs", BCP 26, RFC 5226, | IANA Considerations Section in RFCs", RFC 5226, | |||
DOI 10.17487/RFC5226, May 2008, | DOI 10.17487/RFC5226, May 2008, | |||
<http://www.rfc-editor.org/info/rfc5226>. | <https://www.rfc-editor.org/info/rfc5226>. | |||
[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn, | [RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn, | |||
Ed., "Diameter Base Protocol", RFC 6733, | Ed., "Diameter Base Protocol", RFC 6733, | |||
DOI 10.17487/RFC6733, October 2012, | DOI 10.17487/RFC6733, October 2012, | |||
<http://www.rfc-editor.org/info/rfc6733>. | <https://www.rfc-editor.org/info/rfc6733>. | |||
[RFC7683] Korhonen, J., Ed., Donovan, S., Ed., Campbell, B., and L. | [RFC7683] Korhonen, J., Ed., Donovan, S., Ed., Campbell, B., and L. | |||
Morand, "Diameter Overload Indication Conveyance", | Morand, "Diameter Overload Indication Conveyance", | |||
RFC 7683, DOI 10.17487/RFC7683, October 2015, | RFC 7683, DOI 10.17487/RFC7683, October 2015, | |||
<http://www.rfc-editor.org/info/rfc7683>. | <https://www.rfc-editor.org/info/rfc7683>. | |||
11.2. Informative References | 11.2. Informative References | |||
[Erramilli] | [Erramilli] | |||
Erramilli, A. and L. Forys, "Traffic Synchronization | Erramilli, A. and L. Forys, "Traffic Synchronization | |||
Effects In Teletraffic Systems", 1991. | Effects In Teletraffic Systems", 1991. | |||
[RFC7415] Noel, E. and P. Williams, "Session Initiation Protocol | [RFC7415] Noel, E. and P. Williams, "Session Initiation Protocol | |||
(SIP) Rate Control", RFC 7415, DOI 10.17487/RFC7415, | (SIP) Rate Control", RFC 7415, DOI 10.17487/RFC7415, | |||
February 2015, <http://www.rfc-editor.org/info/rfc7415>. | February 2015, <https://www.rfc-editor.org/info/rfc7415>. | |||
Authors' Addresses | Authors' Addresses | |||
Steve Donovan (editor) | Steve Donovan (editor) | |||
Oracle | Oracle | |||
17210 Campbell Road | 17210 Campbell Road | |||
Dallas, Texas 75254 | Dallas, Texas 75254 | |||
United States | United States | |||
Email: srdonovan@usdonovans.com | Email: srdonovan@usdonovans.com | |||
End of changes. 11 change blocks. | ||||
12 lines changed or deleted | 12 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |