[Dime] RFC 7683 on Diameter Overload Indication Conveyance

rfc-editor@rfc-editor.org Tue, 27 October 2015 23:16 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783431B2DEC; Tue, 27 Oct 2015 16:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 i5q_5Qaqs_OP; Tue, 27 Oct 2015 16:16:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1AAFB1B2DEB; Tue, 27 Oct 2015 16:16:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A9457187E50; Tue, 27 Oct 2015 16:15:54 -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
Message-Id: <20151027231554.A9457187E50@rfc-editor.org>
Date: Tue, 27 Oct 2015 16:15:54 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/CS9IO5_bQFm8bdxiqyTQbyJ9QVY>
Cc: drafts-update-ref@iana.org, dime@ietf.org, rfc-editor@rfc-editor.org
Subject: [Dime] RFC 7683 on Diameter Overload Indication Conveyance
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 27 Oct 2015 23:16:37 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7683

        Title:      Diameter Overload Indication Conveyance 
        Author:     J. Korhonen, Ed.,
                    S. Donovan, Ed.,
                    B. Campbell,
                    L. Morand
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2015
        Mailbox:    jouni.nospam@gmail.com, 
                    srdonovan@usdonovans.com, 
                    ben@nostrum.com,
                    lionel.morand@orange.com
        Pages:      42
        Characters: 96330
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dime-ovli-10.txt

        URL:        https://www.rfc-editor.org/info/rfc7683

        DOI:        http://dx.doi.org/10.17487/RFC7683

This specification defines a base solution for Diameter overload
control, referred to as Diameter Overload Indication Conveyance
(DOIC).

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/rfc.html

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