[Dime] RFC 9390 on Diameter Group Signaling

rfc-editor@rfc-editor.org Wed, 26 April 2023 06:34 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
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 1CF60C1516F8; Tue, 25 Apr 2023 23:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.947
X-Spam-Level:
X-Spam-Status: No, score=-3.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5cemEhoiEY-m; Tue, 25 Apr 2023 23:34:31 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7F71C151541; Tue, 25 Apr 2023 23:34:31 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id B95DA11E4CD; Tue, 25 Apr 2023 23:34:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20230426063431.B95DA11E4CD@rfcpa.amsl.com>
Date: Tue, 25 Apr 2023 23:34:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/b48RCCwvei7R_tZfmNL7sf7DBwk>
Subject: [Dime] RFC 9390 on Diameter Group Signaling
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 26 Apr 2023 06:34:36 -0000

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

        
        RFC 9390

        Title:      Diameter Group Signaling 
        Author:     M. Jones,
                    M. Liebsch,
                    L. Morand
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2023
        Mailbox:    mark@azu.ca,
                    marco.liebsch@neclab.eu,
                    lionel.morand@orange.com
        Pages:      21
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dime-group-signaling-14.txt

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

        DOI:        10.17487/RFC9390

In large network deployments, a single Diameter node can support over
a million concurrent Diameter sessions.  In some use cases, Diameter
nodes need to apply the same operation to a large group of Diameter
sessions concurrently.  The Diameter base protocol commands operate
on a single session so these use cases can result in many thousands
of command exchanges enforcing the same operation on each session in
the group.  In order to reduce signaling, it is desirable to enable
bulk operations on all (or part of) the sessions managed by a
Diameter node using a single or a few command exchanges.  This
document specifies the Diameter protocol extensions to achieve this
signaling optimization.

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