[Dime] RFC 8583 on Diameter Load Information Conveyance
rfc-editor@rfc-editor.org Thu, 15 August 2019 20:08 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF66120850; Thu, 15 Aug 2019 13:08:09 -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=unavailable 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 dLi0r9Qrca3G; Thu, 15 Aug 2019 13:08:04 -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 85662120123; Thu, 15 Aug 2019 13:08:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E77A5B80EC5; Thu, 15 Aug 2019 13:07:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20190815200759.E77A5B80EC5@rfc-editor.org>
Date: Thu, 15 Aug 2019 13:07:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/FUuZyYmEZKJiEzK9aZTmLr-HRvM>
Subject: [Dime] RFC 8583 on Diameter Load Information Conveyance
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2019 20:08:14 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8583
Title: Diameter Load Information Conveyance
Author: B. Campbell,
S. Donovan, Ed.,
JJ. Trottin
Status: Standards Track
Stream: IETF
Date: August 2019
Mailbox: ben@nostrum.com,
srdonovan@usdonovans.com,
jean-jacques.trottin@nokia.com
Pages: 23
Characters: 46149
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dime-load-09.txt
URL: https://www.rfc-editor.org/info/rfc8583
DOI: 10.17487/RFC8583
RFC 7068 describes requirements for Overload Control in Diameter.
This includes a requirement to allow Diameter nodes to send "load"
information, even when the node is not overloaded. The base solution
defined in RFC 7683 (Diameter Overload Information Conveyance (DOIC))
describes a mechanism meeting most of the requirements but does not
currently include the ability to send load information. This
document defines a mechanism for the conveying of Diameter load
information.
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