Re: [Dime] [dime] #85 (draft-ietf-dime-ovli): New error response

"dime issue tracker" <trac+dime@trac.tools.ietf.org> Tue, 21 October 2014 08:36 UTC

Return-Path: <trac+dime@trac.tools.ietf.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 4F0261A1A0A for <dime@ietfa.amsl.com>; Tue, 21 Oct 2014 01:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 yWuCoXO80KTz for <dime@ietfa.amsl.com>; Tue, 21 Oct 2014 01:36:23 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A42C21A006F for <dime@ietf.org>; Tue, 21 Oct 2014 01:27:18 -0700 (PDT)
Received: from localhost ([::1]:55224 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+dime@trac.tools.ietf.org>) id 1XgUme-00046U-DF; Tue, 21 Oct 2014 01:27:12 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: dime issue tracker <trac+dime@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-dime-ovli@tools.ietf.org, srdonovan@usdonovans.com
X-Trac-Project: dime
Date: Tue, 21 Oct 2014 08:27:12 -0000
X-URL: http://tools.ietf.org/wg/dime/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/dime/trac/ticket/85#comment:2
Message-ID: <081.b0cf784f6031add8c6ce78fe7312e32c@trac.tools.ietf.org>
References: <066.8ce734c1c66c770a886774c6bf72f7be@trac.tools.ietf.org>
X-Trac-Ticket-ID: 85
In-Reply-To: <066.8ce734c1c66c770a886774c6bf72f7be@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-dime-ovli@tools.ietf.org, srdonovan@usdonovans.com, dime@ietf.org
X-SA-Exim-Mail-From: trac+dime@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: ben@nostrum.com, jouni.nospam@gmail.com, lionel.morand@orange.com, srdonovan@usdonovans.com
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/2q8UP-XD4DpvZAAka6-9qJVtT4g
Cc: dime@ietf.org
Subject: Re: [Dime] [dime] #85 (draft-ietf-dime-ovli): New error response
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: dime@ietf.org
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: <http://www.ietf.org/mail-archive/web/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, 21 Oct 2014 08:36:25 -0000

#85: New error response


Comment (by srdonovan@usdonovans.com):

 Added the following proposed wording to the draft:

    When a DOIC node rejects a Diameter request due to throttling, the
    DOIC node needs to select the appropriate error response code.  This
    determination is made based on the probability of the request
    succeeding if retried on a different path.

    The DIAMETER_TOO_BUSY response code SHOULD be used when the request
    is likely to succeed on a different path.

       For instance, if the request arrived at the reporting node without
       a Destination-Host AVP then the reporting node might determine
       that there is an alternative Diameter node that could successfully
       process the request and that retrying the transaction would not
       negatively impact the reporting node.

    The DIAMETER_UNABLE_TO_COMPLY response code SHOULD be used to
    indicate that the request should not be retried.  This is used when
    the request is not likely to succeed on a different path and retrying
    would consume valuable resources during an occurance of overload.

       For instance, if the request arrived at the reporting node with a
       Destination-Host AVP populated with its own Diameter identity then
       the reporting node can assume that retrying the request would
       result in it coming to the same reporting node.

       A second example is when an agent that supports the DOIC solution
       is preforming the role of a reacting node for a non supporting
       client.  Requests that are rejected as a result of DOIC throttling
       in this scenario would generally be rejected with a
       DIAMETER_UNABLE_TO_COMPLY response code.

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |       Owner:  draft-ietf-dime-
  srdonovan@usdonovans.com           |  ovli@tools.ietf.org
     Type:  defect                   |      Status:  new
 Priority:  major                    |   Milestone:
Component:  draft-ietf-dime-ovli     |     Version:
 Severity:  Active WG Document       |  Resolution:
 Keywords:                           |
-------------------------------------+-------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/dime/trac/ticket/85#comment:2>
dime <http://tools.ietf.org/wg/dime/>