Re: [Dime] WGLC #1 for draft-ietf-dime-load-02

"A. Jean Mahoney" <> Mon, 18 July 2016 19:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 32D1F12D0E9 for <>; Mon, 18 Jul 2016 12:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id X72LkwpjKcx3 for <>; Mon, 18 Jul 2016 12:13:18 -0700 (PDT)
Received: from ( [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C8B0D12B00D for <>; Mon, 18 Jul 2016 12:13:18 -0700 (PDT)
Received: from mutabilis-2.local ([]) (authenticated bits=0) by (8.15.2/8.15.2) with ESMTPSA id u6IJDAEx010842 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 18 Jul 2016 14:13:11 -0500 (CDT) (envelope-from
X-Authentication-Warning: Host [] claimed to be mutabilis-2.local
To: Maria Cruz Bartolome <>, Steve Donovan <>, "" <>
References: <> <> <> <> <> <> <> <> <>
From: "A. Jean Mahoney" <>
Message-ID: <>
Date: Mon, 18 Jul 2016 14:13:09 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <>
Subject: Re: [Dime] WGLC #1 for draft-ietf-dime-load-02
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 18 Jul 2016 19:13:20 -0000

Hi Maria,

OK, I see your point. I keep thinking that since DNS is so cool everyone 
would use it...

On 7/18/16 2:25 AM, Maria Cruz Bartolome wrote:
> MCRUZ 2> The issue is to be able to provide a LOAD value that allows
> the client to perform load distribution. If we do not take the weight
> into account, somehow (implementation dependent), the distribution
> will be very far from even, it may cause very important traffic
> oscillations (e.g. small servers will appear as low loaded but if
> traffic is sent towards then they may reach overload threshold very
> soon) and big server will normally be underutilized. Therefore, the
> expected load distribution is far from being achieved.

In section 5, the implementer is told to find server capacity via the 
DNS SRV query and then use it to calculate load:

    The goal is make it possible to use both the load values received as
    a part of the Diameter Load mechanism and weight values received as a
    result of a DNS SRV query.  As a result, the Diameter load value has
    a range of 0-65535.  This value and DNS SRV weight values are then
    used in a distribution algorithm similar to that specified in

But what if the Diameter node does NOT use DNS [1]? According to RFC 
6733, Section 5.2, DNS is "MUST be supported" but only "MAY be used". So 
where does the peer get the weight information if all of its connections 
are manually configured? I guess weights could be manually configured, 
but that becomes difficult to maintain as peers are upgraded.

So the question becomes:  Do we make use of DNS a MUST for this 
solution, or do we have reporting peers include capacity in their load 



[1] I've seen large-scale deployments with only manual configuration for 
all Diameter connections, with no DNS servers in the network.