From nobody Mon Jan 11 06:45:43 2021 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4692E3A0E12; Mon, 11 Jan 2021 06:45:37 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 7.24.0 Auto-Submitted: auto-generated Precedence: bulk CC: dime-chairs@ietf.org, dime@ietf.org, draft-ietf-dime-group-signaling@ietf.org, jounikor@gmail.com, rwilton@cisco.com Reply-To: last-call@ietf.org Sender: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-ID: <161037633720.7970.16687345640758099591@ietfa.amsl.com> Date: Mon, 11 Jan 2021 06:45:37 -0800 Archived-At: Subject: [Dime] Last Call: (Diameter Group Signaling) to Proposed Standard X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.29 List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jan 2021 14:45:37 -0000 The IESG has received a request from the Diameter Maintenance and Extensions WG (dime) to consider the following document: - 'Diameter Group Signaling' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2021-01-25. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract In large network deployments, a single Diameter node can support over a million concurrent Diameter sessions. Recent use cases have revealed the need for Diameter nodes 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 could result in many thousands of command exchanges to enforce the same operation on each session in the group. In order to reduce signaling, it would be 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. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-dime-group-signaling/ No IPR declarations have been submitted directly on this I-D. From nobody Tue Jan 26 08:56:20 2021 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BEE753A0ADA; Tue, 26 Jan 2021 08:56:18 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Catherine Meadows via Datatracker To: Cc: dime@ietf.org, draft-ietf-dime-group-signaling.all@ietf.org, last-call@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.24.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <161168017872.21141.3982625411769831365@ietfa.amsl.com> Reply-To: Catherine Meadows Date: Tue, 26 Jan 2021 08:56:18 -0800 Archived-At: Subject: [Dime] Secdir last call review of draft-ietf-dime-group-signaling-13 X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.29 List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2021 16:56:19 -0000 Reviewer: Catherine Meadows Review result: Ready I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. This draft presents the commands a Diameter node could use to communicate with multiple sessions of the Diameter simultaneously. The Security Considerations section mentions two issues. One is that the use of bulk commands introduces increases the ease of implementing certain types of DoS attacks because a single command, e.g. to terminate a session, could affect multiple sessions instead of just one. The other is that current security mechanisms employed by Diameter do not enforce end-to-end security, and so make it difficult to trust information received from non-adjacent nodes. Work is ongoing on end-to-end security for Diameter, so it is premature to address end-to-end security in this document, which instead relies on available security mechanisms. I think this is a reasonable summary of the security considerations. Since end-to-end security for Diameter is a work in progress, it would be premature to attempt to address it in this document. I consider this document Ready. From nobody Thu Jan 28 16:00:19 2021 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 66CF93A1801; Thu, 28 Jan 2021 16:00:15 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Martin Duke via Datatracker To: "The IESG" Cc: draft-ietf-dime-group-signaling@ietf.org, dime-chairs@ietf.org, dime@ietf.org, jounikor@gmail.com X-Test-IDTracker: no X-IETF-IDTracker: 7.24.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Martin Duke Message-ID: <161187841539.26744.16694158082239595671@ietfa.amsl.com> Date: Thu, 28 Jan 2021 16:00:15 -0800 Archived-At: Subject: [Dime] Martin Duke's No Objection on draft-ietf-dime-group-signaling-13: (with COMMENT) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.29 List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2021 00:00:16 -0000 Martin Duke has entered the following ballot position for draft-ietf-dime-group-signaling-13: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-dime-group-signaling/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Sec 4.2.3 "The server responds with a service-specific auth response and includes one or multiple Session- Group-Info AVP with the SESSION_GROUP_ALLOCATION_ACTION flag set and the Session-Group-Id AVP identifying the session group, to which the identified session is to be assigned. With the same response message, the server may send one or multiple Session-Group-Info AVPs with the SESSION_GROUP_ALLOCATION_ACTION flag cleared and the Session-Group-Id AVP identifying the session groups from which the identified session is to be removed." s/may/MAY, to match similar text in 4.2.2. Much as in that section, it is a little subtle that the state can be totally inferred by the first requirement, and the second MAY requirement is purely advisory. From nobody Sat Jan 30 18:03:02 2021 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CD5D3A12FD; Sat, 30 Jan 2021 18:03:01 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Erik Kline via Datatracker To: "The IESG" Cc: draft-ietf-dime-group-signaling@ietf.org, dime-chairs@ietf.org, dime@ietf.org, jounikor@gmail.com X-Test-IDTracker: no X-IETF-IDTracker: 7.24.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Erik Kline Message-ID: <161205858110.13585.13307125040418788418@ietfa.amsl.com> Date: Sat, 30 Jan 2021 18:03:01 -0800 Archived-At: Subject: [Dime] Erik Kline's No Objection on draft-ietf-dime-group-signaling-13: (with COMMENT) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.29 List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jan 2021 02:03:01 -0000 Erik Kline has entered the following ballot position for draft-ietf-dime-group-signaling-13: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-dime-group-signaling/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- [[ nits ]] [ section 10 ] * s/Session-group-Control-Vector/Session-Group-Control-Vector/ From nobody Sun Jan 31 11:57:40 2021 Return-Path: X-Original-To: dime@ietf.org Delivered-To: dime@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB143A11FB; Sun, 31 Jan 2021 11:57:38 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: Barry Leiba via Datatracker To: "The IESG" Cc: draft-ietf-dime-group-signaling@ietf.org, dime-chairs@ietf.org, dime@ietf.org, jounikor@gmail.com X-Test-IDTracker: no X-IETF-IDTracker: 7.24.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Barry Leiba Message-ID: <161212305848.21181.8553749177220111509@ietfa.amsl.com> Date: Sun, 31 Jan 2021 11:57:38 -0800 Archived-At: Subject: [Dime] Barry Leiba's No Objection on draft-ietf-dime-group-signaling-13: (with COMMENT) X-BeenThere: dime@ietf.org X-Mailman-Version: 2.1.29 List-Id: Diameter Maintanence and Extentions Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Jan 2021 19:57:39 -0000 Barry Leiba has entered the following ballot position for draft-ietf-dime-group-signaling-13: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-dime-group-signaling/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I have to say that I found this to be challenging to read: much of it is very dense, with paragraphs giving sometimes-subtly-different conditions, and I would be reading it thinking, “Does this paragraph apply to my situation? I don’t think so, but what about the next one? Wait, maybe it was the other one after all.” I just have to assume that someon actually implementing Diameter would have an easier time following it. I have some editorial comments that won’t help with that aspect, but that I hope will help with clarity in general: — Section 3.1 — A session group, which has sessions assigned, can be deleted, e.g., due to a change in multiple users' subscription profile so that the group's assigned sessions do not share certain characteristics It appears that “has sessions assigned” is restrictive (it’s a required description, not just extra information). If so, it should say, “A session group that has sessions assigned can be deleted, e.g., due to...” without the internal commas. Another way to put it might be, “A session group can be deleted even if it has sessions assigned, e.g., due to...” — Section 3.3 — This specification follows the most flexible model where both, a Diameter client and a Diameter server can create a new group and Nit: no comma here Either the client and the server can assign a session to a group. Nit: “Either the client or the server can”, or “Both the client and the server can”. Details about enforcing a more constraint permission model I think the word you want is “constrained”. — Section 4.2 — Diameter AAA applications typically assign client and server roles to the Diameter nodes, which are referred to as relevant Diameter nodes to utilize session grouping and issue group commands. I’m having trouble parsing this sentence and determining what you’re trying to tell me. Can you please rephrase or repunctuate it to make it clearer? What are referred to as “relevant Diameter nodes”? What goes with “to utilize session grouping”? Diameter nodes, which are group-aware, MUST store and maintain an entry about the group assignment together with a session's state. Similar to earlier: is “are group aware” meant to be restrictive (there are Diameter nodes that are group aware and those that are not, and you’re talking about the former), or non-restrictive (all Diameter nodes are group aware, and you’re just pointing that fact out). It is currently written as non-restrictive, but I think you mean it to be restrictive. If that is correct, remove both commas and change “which” to “that”. A Diameter node MUST also keep a record about sessions, which have been assigned to a session group by itself. The comma shouldn’t be there, and “which” should be “that”. But it’s a bit awkward anyway: may I suggest rephrasing in active voice as, “Each Diameter node MUST also keep a record about sessions that it has assigned to a session group.” — Section 4.2.1 — If the response from the server indicates success in the result code but solely the assignment of the session to a session group has been rejected by the server, the client treats the session as single session without group assignment. What does “solely” mean in this sentence? A Diameter client, which sent a request for session initiation Please remove the comma (and change “which” to “that”). — Section 4.2.2 — The session, which is to be removed from a group, is Make it, “The session that is to be removed from the group is” When a Diameter client decides to remove a session from all session groups, to which the session has been previously assigned, Remove the comma after “groups”. The session, which is to be removed from all groups, to which the session has been previously assigned, is identified in the Session-Id AVP of the command request. Make it, “The session that is to be removed from all groups to which it had been previously assigned is identified in the Session-Id AVP of the command request.” — Section 7.3 — The portion of the Session-Group-Id MUST identify the Diameter node, which owns the session group. Please remove the comma and change “which” to “that”.