[Dime] DOIC and terminology

Jouni Korhonen <jouni.nospam@gmail.com> Thu, 28 November 2013 09:51 UTC

Return-Path: <jouni.nospam@gmail.com>
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 0E7941ABBB1 for <dime@ietfa.amsl.com>; Thu, 28 Nov 2013 01:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 tHT4JnW-rA2l for <dime@ietfa.amsl.com>; Thu, 28 Nov 2013 01:51:14 -0800 (PST)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2FCDE1A1F58 for <dime@ietf.org>; Thu, 28 Nov 2013 01:51:14 -0800 (PST)
Received: by mail-la0-f50.google.com with SMTP id el20so5756781lab.23 for <dime@ietf.org>; Thu, 28 Nov 2013 01:51:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=DOPDu8536L6+ym/19KUcYLKrFTj9NVBimI1Rv1W5KhU=; b=i6APM+ISO9zmKF1dBxck9wAc6qKiVP3dk7iVKLYPrHLYKV2lwsUlsQwyQ3jQFNi4MA S2GDNbZeJt41DTMG7tMpNKpsf1Cc3Js+p6NI0LxYWiqUC7gGZig1+96S8rA4iWBagw5W M+sCUIW9iGy+UFrtfdyAJKbY4h2hsTIpGV6V2puC2hTYp0ATOyluw2nmyKwyQZw9YFrc NBMUQl90SXWdNvvuHxvaCL87xED3PDyNeQXybDxkzlUmB2x5N2r7e5XpFOfmEzisq39G 0jO5f4fEdiYh60hR6A+5tLkuEfDm6+THUkEhuHS/ZLW+v53n0YifyInaylpUp8ymU/CX kxsA==
X-Received: by 10.112.210.197 with SMTP id mw5mr297917lbc.42.1385632272653; Thu, 28 Nov 2013 01:51:12 -0800 (PST)
Received: from [192.168.250.143] ([194.100.71.98]) by mx.google.com with ESMTPSA id bo10sm17046030lbb.16.2013.11.28.01.51.11 for <dime@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Nov 2013 01:51:12 -0800 (PST)
From: Jouni Korhonen <jouni.nospam@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <82C71989-401F-4972-8878-7D2B1052CCA0@gmail.com>
Date: Thu, 28 Nov 2013 11:51:12 +0200
To: "dime@ietf.org list" <dime@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Subject: [Dime] DOIC and terminology
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Thu, 28 Nov 2013 09:51:16 -0000

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?