RFC 8581 on Diameter Agent Overload and the Peer Overload Report
rfc-editor@rfc-editor.org Thu, 15 August 2019 20:07 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B26B12007C; Thu, 15 Aug 2019 13:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D4s6mHU-0x3W; Thu, 15 Aug 2019 13:07:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41E8F120071; Thu, 15 Aug 2019 13:07:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A2DE6B80E8C; Thu, 15 Aug 2019 13:07:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8581 on Diameter Agent Overload and the Peer Overload Report
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dime@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190815200718.A2DE6B80E8C@rfc-editor.org>
Date: Thu, 15 Aug 2019 13:07:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/HKLWbmOBZX_qMgAZ2laB6NKPq-Y>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2019 20:07:25 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8581
Title: Diameter Agent Overload and the
Peer Overload Report
Author: S. Donovan
Status: Standards Track
Stream: IETF
Date: August 2019
Mailbox: srdonovan@usdonovans.com
Pages: 19
Characters: 38078
Updates: RFC 7683
I-D Tag: draft-ietf-dime-agent-overload-11.txt
URL: https://www.rfc-editor.org/info/rfc8581
DOI: 10.17487/RFC8581
This specification documents an extension to the Diameter Overload
Indication Conveyance (DOIC), a base solution for Diameter overload
defined in RFC 7683. The extension defines the Peer Overload report
type. The initial use case for the peer report is the handling of
occurrences of overload of a Diameter Agent.
This document is a product of the Diameter Maintenance and Extensions Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC