Re: [Dime] DOIC and terminology

Ben Campbell <> Tue, 03 December 2013 21:35 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id B30C71AE11D for <>; Tue, 3 Dec 2013 13:35:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rQvCVB9gdbCw for <>; Tue, 3 Dec 2013 13:35:23 -0800 (PST)
Received: from ( [IPv6:2001:470:1f03:267::2]) by (Postfix) with ESMTP id 606571ADFD9 for <>; Tue, 3 Dec 2013 13:35:23 -0800 (PST)
Received: from [] ( []) (authenticated bits=0) by (8.14.3/8.14.3) with ESMTP id rB3LZ7Cf038389 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 3 Dec 2013 15:35:09 -0600 (CST) (envelope-from
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ben Campbell <>
In-Reply-To: <>
Date: Tue, 3 Dec 2013 15:35:07 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Jouni Korhonen <>
X-Mailer: Apple Mail (2.1822)
Received-SPF: pass ( is authenticated by a trusted mechanism)
Cc: " list" <>
Subject: Re: [Dime] DOIC and terminology
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 03 Dec 2013 21:35:24 -0000

IMHO, the term "server farm" is useful, but the term SFE is not. In fact, I suspect that people will read more into SFE than intended, and think it means something special, or that we are defining a new architectural element.

On Nov 28, 2013, at 3:51 AM, Jouni Korhonen <> wrote:

> Folks,
> In the terminology there is an open issue:
>          [OpenIssue: We used the concept of a server farm and SFE for
>          internal discussions. Do we still need those concepts to explain the
>          mechanism? It doesn't seem like we use them much.]
> The terms server farm and SFE are mainly used within the terminology
> section itself. If we were to remove e.g. SFE only, then the following are
> also in the list for removal:
>   Load Management:
>      This functionality ensures that the consolidated load state for
>      the server farm is collected, and processed.  The exact algorithm
>      for computing the load at the SFE is implementation specific but
>      enough semantic of the conveyed load information needs to be
>      specified so that deterministic behavior can be ensured.
>   Overload Management:
>      The SFE is the entity that understands the consolidated overload
>      state for the server farm.  Just as it is outside the scope of
>      this document to specify how a Diameter server calculates its
>      overload state, it is also outside the scope of this document to
>      specify how an SFE calculates the overload state for the set of
>      servers.  This document describes how the SFE communicates
>      Overload information to Diameter Clients.
>   Server Farm Identity Management:
>      Server Farm Identity Management (SFIM) is a mechanism that can be
>      used by the SFE to present a single Diameter identity that can be
>      used by clients to send Diameter requests to the server farm.
>      This requires that the SFE modifies Origin-Host information in
>      answers coming from servers in the server farm.  An agent that
>      performs SFIM appears as a server from the client's perspective.
> There are also other impacts but those can be reworded with a minor effort.
> Opinions?
> _______________________________________________
> DiME mailing list