Re: [Dime] [dime] #44 (draft-docdt-dime-ovli): Incorrect sequence number behavior

<lionel.morand@orange.com> Thu, 27 March 2014 14:43 UTC

Return-Path: <lionel.morand@orange.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 C820E1A06C1 for <dime@ietfa.amsl.com>; Thu, 27 Mar 2014 07:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 PGsMMxwbOT29 for <dime@ietfa.amsl.com>; Thu, 27 Mar 2014 07:43:50 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id D913F1A06B2 for <dime@ietf.org>; Thu, 27 Mar 2014 07:43:49 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 3D96A18C5E8; Thu, 27 Mar 2014 15:43:47 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 1BB5E238059; Thu, 27 Mar 2014 15:43:47 +0100 (CET)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0174.001; Thu, 27 Mar 2014 15:43:46 +0100
From: <lionel.morand@orange.com>
To: Ben Campbell <ben@nostrum.com>, Steve Donovan <srdonovan@usdonovans.com>
Thread-Topic: [Dime] [dime] #44 (draft-docdt-dime-ovli): Incorrect sequence number behavior
Thread-Index: AQHPSccM2lp5E3z4602fR2jbhSI6rJr1AlYQ
Date: Thu, 27 Mar 2014 14:43:45 +0000
Message-ID: <13008_1395931427_53343923_13008_5391_1_6B7134B31289DC4FAF731D844122B36E5214FE@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <057.7c5fb5d661b97d2b4cb140cc4965cf36@trac.tools.ietf.org> <072.6892b07263eb158352dabe97ef8b9ed4@trac.tools.ietf.org> <5332F680.9030102@usdonovans.com> <C010A857-7447-4739-ADE7-F3942A2FB3EC@nostrum.com>
In-Reply-To: <C010A857-7447-4739-ADE7-F3942A2FB3EC@nostrum.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.3.27.135115
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/Ux2O20rKoeAnSUWLOXlxN5m4WT0
Cc: "dime@ietf.org" <dime@ietf.org>, "draft-docdt-dime-ovli@tools.ietf.org" <draft-docdt-dime-ovli@tools.ietf.org>
Subject: Re: [Dime] [dime] #44 (draft-docdt-dime-ovli): Incorrect sequence number behavior
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, 27 Mar 2014 14:43:53 -0000

ok

-----Message d'origine-----
De : DiME [mailto:dime-bounces@ietf.org] De la part de Ben Campbell
Envoyé : jeudi 27 mars 2014 15:16
À : Steve Donovan
Cc : dime@ietf.org; draft-docdt-dime-ovli@tools.ietf.org
Objet : Re: [Dime] [dime] #44 (draft-docdt-dime-ovli): Incorrect sequence number behavior

WFM

On Mar 26, 2014, at 10:47 AM, Steve Donovan <srdonovan@usdonovans.com> wrote:

> All,
> 
> When looking to make the change documented below, I realized that this wording had already been changed as a result of a previous agreed to change.  I haven't searched down which one, but the new wording in the current -02 snapshot is as following.  I believe that this is consistent with the proposed wording below and, as such, have not further updated the paragraph.
> 
> If the value of the OC-Sequence-Number AVP contained in the received
>    OC-OLR AVP is equal to or less than the value stored in an existing
>    overload condition state, the received OC-OLR AVP SHOULD be silently
>    discarded.  If the value of the OC-Sequence-Number AVP contained in
>    the received OC-OLR AVP is greater than the value stored in an
>    existing overload condition state or there is no previously recorded
>    sequence number, the reacting node MUST update the overload condition
>    state associated with the realm or the specific node is the realm.
> 
> Regards,
> 
> Steve
> On 3/24/14 3:17 PM, dime issue tracker wrote:
>> #44: Incorrect sequence number behavior
>> 
>> Changes (by 
>> srdonovan@usdonovans.com
>> ):
>> 
>>  * status:  new => closed
>>  * resolution:   => fixed
>> 
>> 
>> Comment:
>> 
>>  Change the last sentence of section 4.3, paragraph 3 to "The reacting node
>>  SHOULD discard an OC-OLR AVP with a sequence number that is less than or
>>  equal to the previously received sequence number."
>> 
>> 
> 

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

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.