IETF Logo Mail Archive

Re: [Dime] [dime] #46: Bad normative advice on not letting overload reports expire

Jouni Korhonen <jouni.nospam@gmail.com> Mon, 10 February 2014 11:16 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 869291A0813 for <dime@ietfa.amsl.com>; Mon, 10 Feb 2014 03:16:19 -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 tLpCyNqaMPLf for <dime@ietfa.amsl.com>; Mon, 10 Feb 2014 03:16:17 -0800 (PST)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) by ietfa.amsl.com (Postfix) with ESMTP id 40FDF1A080B for <dime@ietf.org>; Mon, 10 Feb 2014 03:16:17 -0800 (PST)
Received: by mail-lb0-f180.google.com with SMTP id n15so4719285lbi.11 for <dime@ietf.org>; Mon, 10 Feb 2014 03:16:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7sZzUcY+YycH/kzFEX0dg8eukEplZFbdzMB2xnubI1k=; b=T0ILNWOUlH9LUEPiO1m+uxqx6vLJZrcTWV2sbTWsBk3VdbebmkLDnMoPmCn9+uI2IF yIL4yg3fEJTP797KLxTndIVzAemuTUqiDT2IJ701sn4U+WeH/e9xfNqt/hN8w2dvQxGs Hp7MVFzrw3hkwPXcvDpteWKnl+0LiO/NjZbKckxmw4FIwkxc0EqGJ/xZRRpFbdb2cWbi /0AWwxTsrJB3XGFD/pjOXg9MUXe9qOeSrEv8OBuDHuq+eR/pjuE0nhFkU9e5T8IAbk1M 4OPNRs65cPcIUtm2lV7JgdoOWbKuiOeRI6mFEXOiPLm2du6J42k/+pEq9/B8j4uxkxiP KF5w==
X-Received: by 10.152.209.7 with SMTP id mi7mr1213404lac.42.1392030976544; Mon, 10 Feb 2014 03:16:16 -0800 (PST)
Received: from [188.117.15.108] ([188.117.15.108]) by mx.google.com with ESMTPSA id bl3sm15443004lbd.7.2014.02.10.03.16.13 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Feb 2014 03:16:13 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <057.8b248d3cb5db23879c2730b80d4657d7@trac.tools.ietf.org>
Date: Mon, 10 Feb 2014 13:16:12 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B08CCDA3-4E2B-444A-AE27-9DE2D9C0B458@gmail.com>
References: <057.8b248d3cb5db23879c2730b80d4657d7@trac.tools.ietf.org>
To: dime@ietf.org
X-Mailer: Apple Mail (2.1510)
Cc: ben@nostrum.com, draft-docdt-dime-ovli@tools.ietf.org
Subject: Re: [Dime] [dime] #46: Bad normative advice on not letting overload reports expire
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: Mon, 10 Feb 2014 11:16:19 -0000

My reasoning for explicit termination was that knowing the implementation
folks they will let overload conditions expire unless advised otherwise.
And having unnecessary stuff hanging around waiting for a cleanup is not
a good thing in general. But I am open here for other options..

- Jouni


On Feb 7, 2014, at 11:59 PM, dime issue tracker <trac+dime@trac.tools.ietf.org> wrote:

> #46: Bad normative advice on not letting overload reports expire
> 
> Section 4.5 says " As a general guidance for implementations it is
> RECOMMENDED never to let any overload report to timeout." In my opinion,
> this is bad advice. If an overload report is close to expiring anyway,
> it's better to just let it expire than to generate a new report to end the
> condition.
> 
> Furthermore, this falls into the category of normative language that does
> not effect interoperability. That is forbidden by RFC 2119, except for
> situations where not following it does significant harm. If we believe
> letting reports expire does significant harm, we should explain why.
> 
> -- 
> -------------------------+-------------------------------------------------
> Reporter:               |      Owner:  draft-docdt-dime-
>  ben@nostrum.com        |  ovli@tools.ietf.org
>     Type:  defect       |     Status:  new
> Priority:  minor        |  Milestone:
> Component:  draft-       |    Version:  1.0
>  docdt-dime-ovli        |   Keywords:
> Severity:  Active WG    |
>  Document               |
> -------------------------+-------------------------------------------------
> 
> Ticket URL: <http://trac.tools.ietf.org/wg/dime/trac/ticket/46>
> dime <http://tools.ietf.org/wg/dime/>
>

v2.23.0 | Report a Bug | By Email