[Dime] OVLI: comments to 4.2

"Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com> Thu, 05 December 2013 13:56 UTC

Return-Path: <ulrich.wiehe@nsn.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 8B8D81ADFA3 for <dime@ietfa.amsl.com>; Thu, 5 Dec 2013 05:56:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] 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 BLKds5og5Pej for <dime@ietfa.amsl.com>; Thu, 5 Dec 2013 05:56:01 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id DC01F1ADEB7 for <dime@ietf.org>; Thu, 5 Dec 2013 05:56:00 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id rB5Dttrh020233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <dime@ietf.org>; Thu, 5 Dec 2013 14:55:55 +0100
Received: from DEMUHTC004.nsn-intra.net ([10.159.42.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id rB5DttBP005294 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dime@ietf.org>; Thu, 5 Dec 2013 14:55:55 +0100
Received: from DEMUHTC009.nsn-intra.net (10.159.42.40) by DEMUHTC004.nsn-intra.net (10.159.42.35) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 5 Dec 2013 14:55:55 +0100
Received: from DEMUMBX014.nsn-intra.net ([169.254.14.152]) by DEMUHTC009.nsn-intra.net ([10.159.42.40]) with mapi id 14.03.0123.003; Thu, 5 Dec 2013 14:55:54 +0100
From: "Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com>
To: "dime@ietf.org" <dime@ietf.org>
Thread-Topic: OVLI: comments to 4.2
Thread-Index: Ac7xwbbgyJZ2adciQlahKBe5mrdwfQ==
Date: Thu, 05 Dec 2013 13:55:54 +0000
Message-ID: <5BCBA1FC2B7F0B4C9D935572D90006681519DAA6@DEMUMBX014.nsn-intra.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.117]
Content-Type: multipart/alternative; boundary="_000_5BCBA1FC2B7F0B4C9D935572D90006681519DAA6DEMUMBX014nsnin_"
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 3394
X-purgate-ID: 151667::1386251756-00002466-0B230171/0-0/0-0
Subject: [Dime] OVLI: comments to 4.2
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, 05 Dec 2013 13:56:02 -0000

Dear all,

here are comments to clause 4.2:

1. there is a typo in the first line: "s" should read "is".

2. Supporting OLR_DEFAULT_ALGO means different things depending on the endpoint's role (reacting/reporting).
Proposal is to expand the text to read:


      When this flag is set by the overload control reacting endpoint it means
      that the default traffic abatement (loss) algorithm is supported by the
      reacting endpoint, i.e. the reacting endpont is able and willing to execute
      the default traffic abatement algorithm if so requested by the reporting
      endpoint.
      When this flag is set by the overload control reporting endpoint it means
      that the reporting endpoint when overloaded is able and willing to demand
      executing the default traffic abatement algorithm from the reacting endpoint.

Best regards
Ulrich