IETF Logo Mail Archive

Re: [Dime] OVLI: comments to 4.1

"Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com> Tue, 10 December 2013 09:28 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 7485F1AD8DB for <dime@ietfa.amsl.com>; Tue, 10 Dec 2013 01:28:41 -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 c2EqKne-B3Uq for <dime@ietfa.amsl.com>; Tue, 10 Dec 2013 01:28:39 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id BC6021A1F7B for <dime@ietf.org>; Tue, 10 Dec 2013 01:28:38 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id rBA9SU8W024834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 10 Dec 2013 10:28:30 +0100
Received: from DEMUHTC002.nsn-intra.net ([10.159.42.33]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id rBA9SSpR032445 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 10 Dec 2013 10:28:29 +0100
Received: from DEMUHTC013.nsn-intra.net (10.159.42.44) by DEMUHTC002.nsn-intra.net (10.159.42.33) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 10 Dec 2013 10:28:28 +0100
Received: from DEMUMBX014.nsn-intra.net ([169.254.14.152]) by DEMUHTC013.nsn-intra.net ([10.159.42.44]) with mapi id 14.03.0123.003; Tue, 10 Dec 2013 10:28:28 +0100
From: "Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com>
To: ext Ben Campbell <ben@nostrum.com>, Steve Donovan <srdonovan@usdonovans.com>
Thread-Topic: [Dime] OVLI: comments to 4.1
Thread-Index: Ac7xvTHHIECkLcDwSDuVAh2ACeOasAAprlMAAAaV6CAAlFJBAAADLijg///yiAD//+yxwIAAG3gA///jPWCAAEcYgIAAcsEA//8+xjA=
Date: Tue, 10 Dec 2013 09:28:27 +0000
Message-ID: <5BCBA1FC2B7F0B4C9D935572D90006681519E29A@DEMUMBX014.nsn-intra.net>
References: <5BCBA1FC2B7F0B4C9D935572D90006681519DA3E@DEMUMBX014.nsn-intra.net> <6CDCFC84-3048-40B9-91A4-1451FCC65F60@gmail.com> <5BCBA1FC2B7F0B4C9D935572D90006681519DCE5@DEMUMBX014.nsn-intra.net> <09616DA2-D1ED-40EE-8E89-755DFCD81092@gmail.com> <5BCBA1FC2B7F0B4C9D935572D90006681519E02B@DEMUMBX014.nsn-intra.net> <1A402C59-E390-4C95-8E30-97F1F9D3EF0F@gmail.com> <5BCBA1FC2B7F0B4C9D935572D90006681519E05C@DEMUMBX014.nsn-intra.net> <790F1603-64D5-40E2-BC59-FD4C104EEF1B@gmail.com> <5BCBA1FC2B7F0B4C9D935572D90006681519E0D9@DEMUMBX014.nsn-intra.net> <52A5E813.60801@usdonovans.com> <7AE3F729-B987-45B1-A9AF-2F0C9A36641E@nostrum.com>
In-Reply-To: <7AE3F729-B987-45B1-A9AF-2F0C9A36641E@nostrum.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: 2171
X-purgate-ID: 151667::1386667710-000030AF-37CCB45E/0-0/0-0
Cc: "dime@ietf.org list" <dime@ietf.org>
Subject: Re: [Dime] OVLI: comments to 4.1
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 09:28:41 -0000

Steve, Ben,

thank you for the clarification.
Its definitly worth pointing out what the intended (optional) use for the sequence number is.

Do you have any clarification for the use of Sequence-Number in OC-Feature-Vectors in answer messages? 

Ulrich

-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of ext Ben Campbell
Sent: Monday, December 09, 2013 11:47 PM
To: Steve Donovan
Cc: dime@ietf.org list
Subject: Re: [Dime] OVLI: comments to 4.1


On Dec 9, 2013, at 9:56 AM, Steve Donovan <srdonovan@usdonovans.com> wrote:

> Ulrich,
> 
> Looking at the impacts of removing the sequence number from the feature vector AVP.  This would require the following logic for each request received at the reporting node:
> 
> Parse the full set of OC-Feature-Vector AVPs 
> Calculate the set of overlapping capabilities
> Generate the reporting nodes OC-Feature-Vector AVPs
> If the reporting node is in overload then generate and append the OC-OLR AVPs.
> 
> Keeping the version number requires the reporting node to do the following:
> 
> Parse the feature vector sequence number
> If the sequence number is changed from the last version number received then 
>   Parse the remaining OC-Feature-Vector AVPs
>   Calculate the set of overlapping capabilities
>   Generate the reporting nodes capability AVPs
>   Save the version number and results of capabilities exchange
> If the reporting node is in overload then generate and append the OC-OLR AVPs.
> 
> Removing the sequence number forces the reporting node to do extra work for all requests, including requests received when overloaded.  Given that the sequence number will almost never change, this seems like a bad idea.  We should be reducing the work of overloaded nodes, not increasing it.

It's worth pointing out that, if someone believes the sequence number comparison is not worth the trouble, they can always ignore it and revert to Steve's first example.

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

v2.23.0 | Report a Bug | By Email