Re: [Dime] OVLI: comments to 4.3

"Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com> Tue, 10 December 2013 13:01 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 0B03E1AE0A1 for <dime@ietfa.amsl.com>; Tue, 10 Dec 2013 05:01:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 GISX4uqlSgmi for <dime@ietfa.amsl.com>; Tue, 10 Dec 2013 05:00:58 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id E71591AE09F for <dime@ietf.org>; Tue, 10 Dec 2013 05:00:57 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id rBAD0oN8025435 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 10 Dec 2013 14:00:50 +0100
Received: from DEMUHTC003.nsn-intra.net ([10.159.42.34]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id rBAD0oSe028983 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Dec 2013 14:00:50 +0100
Received: from DEMUHTC007.nsn-intra.net (10.159.42.38) by DEMUHTC003.nsn-intra.net (10.159.42.34) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 10 Dec 2013 14:00:49 +0100
Received: from DEMUMBX014.nsn-intra.net ([169.254.14.152]) by DEMUHTC007.nsn-intra.net ([10.159.42.38]) with mapi id 14.03.0123.003; Tue, 10 Dec 2013 14:00:49 +0100
From: "Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com>
To: ext Jouni Korhonen <jouni.nospam@gmail.com>, Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com>
Thread-Topic: [Dime] OVLI: comments to 4.3
Thread-Index: Ac7xzgT7drC0NV4iSVSEGFHx9aP+WQAl1Z0AAAfOC0AAEAghgAAWP9KAAGrqkFAAGQgrFAAWmq8AAAA0wAAAB1UlkA==
Date: Tue, 10 Dec 2013 13:00:49 +0000
Message-ID: <5BCBA1FC2B7F0B4C9D935572D90006681519E41A@DEMUMBX014.nsn-intra.net>
References: <5BCBA1FC2B7F0B4C9D935572D90006681519DB1B@DEMUMBX014.nsn-intra.net> <AA10DFBD-CAC9-4B7B-8876-A4F28E63D83F@gmail.com> <5BCBA1FC2B7F0B4C9D935572D90006681519DD2A@DEMUMBX014.nsn-intra.net> <FBC2AC60-A7A8-4D71-8B0F-ADECC10A1311@nostrum.com> <A9CA33BB78081F478946E4F34BF9AAA014D29713@xmb-rcd-x10.cisco.com> <5BCBA1FC2B7F0B4C9D935572D90006681519DF8A@DEMUMBX014.nsn-intra.net> <A9CA33BB78081F478946E4F34BF9AAA014D2D548@xmb-rcd-x10.cisco.com> <2495B298-0B49-406A-884C-0C354D87948E@nostrum.com> <087A34937E64E74E848732CFF8354B9209739F8C@ESESSMB101.ericsson.se> <651FE189-F6B1-4807-938D-67C6B7841044@gmail.com>
In-Reply-To: <651FE189-F6B1-4807-938D-67C6B7841044@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.42.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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: 1393
X-purgate-ID: 151667::1386680450-00001A6F-7F67E5EB/0-0/0-0
Cc: Ben Campbell <ben@nostrum.com>, "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] OVLI: comments to 4.3
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: Tue, 10 Dec 2013 13:01:00 -0000

MCruz, Jouni,

> and per client


my understanding was that the differentiation _per_client_ was a requirement from 3GPP that is not covered by the DIOC base version and that requires an extension.

Note that the main problem is to cover cases where a single DOIC-supporting client performs overload mitigation on behalf of two different non-supporting clients.

Ulrich



-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of ext Jouni Korhonen
Sent: Tuesday, December 10, 2013 11:18 AM
To: Maria Cruz Bartolome
Cc: Ben Campbell; dime@ietf.org
Subject: Re: [Dime] OVLI: comments to 4.3

> 
> 
> [MCruz] My understanding is that validity-period should be adjusted by reporting node depending on their expectations on traffic reduction by one client. Therefore, it should be updated towards _each_ client, based on reporting node expectations on _each_ client traffic reduction. I understand it does not mean (necessarily) that validity period has to be updated each time a message is sent, but it will depend on each overload situation and per client.
> 

This is my understanding as well (and how the text currently is written.. or 
is meant to be read ;)

- Jouni

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime