[Dime] [dime] #65 (draft-ietf-dime-ovli): Definition of messages impacted by host overload report

"dime issue tracker" <trac+dime@trac.tools.ietf.org> Wed, 23 April 2014 15:03 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 BCA6D1A03E7 for <dime@ietfa.amsl.com>; Wed, 23 Apr 2014 08:03:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level:
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] 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 BRdCt6Db4qtj for <dime@ietfa.amsl.com>; Wed, 23 Apr 2014 08:03:26 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 12DCD1A03DE for <dime@ietf.org>; Wed, 23 Apr 2014 08:03:18 -0700 (PDT)
Received: from localhost ([127.0.0.1]:43248 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+dime@trac.tools.ietf.org>) id 1WcyhV-00038w-Ij; Wed, 23 Apr 2014 17:03:05 +0200
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: Wed, 23 Apr 2014 15:03:05 -0000
X-URL: http://tools.ietf.org/wg/dime/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/dime/trac/ticket/65
Message-ID: <066.a99805710f0922547f49ff6eb5d6c0fa@trac.tools.ietf.org>
X-Trac-Ticket-ID: 65
X-SA-Exim-Connect-IP: 127.0.0.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 grenache.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/GcSlcoyQBcazKp4ZRkLxZz1T4dM
Cc: dime@ietf.org
Subject: [Dime] [dime] #65 (draft-ietf-dime-ovli): Definition of messages impacted by host overload report
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: Wed, 23 Apr 2014 15:03:31 -0000

#65: Definition of messages impacted by host overload report

 The current definition of a host overload needs to be enhanced.

 The following is what is currently in the -02 draft:

    0  A host report.  The overload treatment should apply to requests
       for which all of the following conditions are true:

       The Destination-Host AVP is present in the request and its value
       matches the value of the Origin-Host AVP of the received message
       that contained the OC-OLR AVP.

       The value of the Destination-Realm AVP in the request matches the
       value of the Origin-Realm AVP of the received message that
       contained the OC-OLR AVP.

       The value of the Application-ID in the Diameter Header of the
       request matches the value of the Application-ID of the Diameter
       Header of the received message that contained the OC-OLR AVP.


 The second paragraph says that only requests that contain a Destination-
 Host AVP can be used for overload treatment.

 This does not address the case where there is no agent between the
 reacting and reporting nodes.  In other words, the reacting node has a
 direct connection to the reporting node.  In this case the reacting node
 should include all messages that would be sent to the reporting node,
 including those that do not contain a Destination-Host AVP and those that
 the reacting node would sent to the reporting node through normal route
 selection for requests that do not contain a Destination-Host AVP.

 I propose that the second paragraph be changed to the following:

 "The reacting node knows that the request will be routed to the overloaded
 Diameter node identified by the Diameter ID in the OLR.  This is the value
 of the Origin-Host AVP in the message that carried the OLR.  There are two
 cases where the reacting node will know that the request will be routed to
 the overloaded node.  The first is the request contains a Destination-Host
 AVP that matches the Diameter ID contained in the OLR.  The second is when
 the reacting node selects a route that is a direct connection to the
 overloaded Diameter node."

-- 
-------------------------------------+-------------------------------------
 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       |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://tools.ietf.org/wg/dime/trac/ticket/65>
dime <http://tools.ietf.org/wg/dime/>