[Dime] Benoit Claise's No Objection on draft-ietf-dime-drmp-05: (with COMMENT)

"Benoit Claise" <bclaise@cisco.com> Wed, 04 May 2016 17:02 UTC

Return-Path: <bclaise@cisco.com>
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 E17B912D924; Wed, 4 May 2016 10:02:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160504170252.8246.93112.idtracker@ietfa.amsl.com>
Date: Wed, 04 May 2016 10:02:52 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/dime/Ju9ok5H3sCS3MSf3jAhn6bL5VDQ>
Cc: draft-ietf-dime-drmp@ietf.org, dime-chairs@ietf.org, dime@ietf.org
Subject: [Dime] Benoit Claise's No Objection on draft-ietf-dime-drmp-05: (with COMMENT)
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.17
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, 04 May 2016 17:02:53 -0000

Benoit Claise has entered the following ballot position for
draft-ietf-dime-drmp-05: 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-drmp/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

- OLD:

   This also recognizes that more
   work has already taken place for established sessions and, as a
   result, it might be more harmful if the session update and session
   ending requests were to be throttled.


NEW:
   This also recognizes that more
   work has already taken place for established sessions and, as a
   result, it might be more harmful from a signaling point of view 
   if the session update and session ending requests were to be
throttled.

-

 1.  Request sender - The sender of a request, be it a Diameter Client
       or a Diameter Server, determines the relative priority of the
       request and includes that priority information in the request.

Question: what is the risk of DMRP ending up as the DSCP, i.e. 
Every end point changes the value to best service, and in the end, it's
useless, and uniquely set by the operator.