IETF Logo Mail Archive

Re: [Dime] [dime] #32 (draft-docdt-dime-ovli): Sequence-Number Time-Stamp values within OC-OLR

Steve Donovan <srdonovan@usdonovans.com> Fri, 07 March 2014 16:44 UTC

Return-Path: <srdonovan@usdonovans.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 8733F1A0205 for <dime@ietfa.amsl.com>; Fri, 7 Mar 2014 08:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.28
X-Spam-Level:
X-Spam-Status: No, score=0.28 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, SPF_NEUTRAL=0.779] autolearn=no
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 B4FbasqccLMb for <dime@ietfa.amsl.com>; Fri, 7 Mar 2014 08:44:17 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [173.247.247.114]) by ietfa.amsl.com (Postfix) with ESMTP id 9A4BA1A00A8 for <dime@ietf.org>; Fri, 7 Mar 2014 08:44:17 -0800 (PST)
Received: from [109.144.221.15] (port=50438 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <srdonovan@usdonovans.com>) id 1WLxsY-0001fh-JG; Fri, 07 Mar 2014 08:44:12 -0800
Message-ID: <5319F759.1080602@usdonovans.com>
Date: Fri, 07 Mar 2014 16:44:09 +0000
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dime@ietf.org, lionel.morand@orange-ftgroup.com
References: <066.f8b7ffcffcd55b9e56fa2bfc281d4649@trac.tools.ietf.org> <081.778acab79112f9ddcd125eafacc00df9@trac.tools.ietf.org>
In-Reply-To: <081.778acab79112f9ddcd125eafacc00df9@trac.tools.ietf.org>
Content-Type: multipart/alternative; boundary="------------010303080508010504030407"
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz131.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - usdonovans.com
X-Get-Message-Sender-Via: biz131.inmotionhosting.com: authenticated_id: srdonovan@usdonovans.com
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/msDgvBcR7se8Vk5vWGp6UTd8Fzc
Subject: Re: [Dime] [dime] #32 (draft-docdt-dime-ovli): Sequence-Number Time-Stamp values within OC-OLR
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: Fri, 07 Mar 2014 16:44:18 -0000

All,

One note on these changes to the draft based on issue #32.  This issue
was closed without proposing alternative text, so I have taken the
liberty of proposing the text included in these messages.

If I have missed the mark on this wording please re-open the ticket.

I believe there is no proposed text in this one because the guidance to
include proposed text happened after this ticket was closed.

Regards,

Steve

On 3/7/14 4:32 PM, dime issue tracker wrote:
> #32: Sequence-Number Time-Stamp values within OC-OLR
>
>
> Comment (by srdonovan@usdonovans.com):
>
>  Further updated to change "previously recieved" to "currently active
>  overload report".
>
>  The new text is as follows:
>
>  It is possible to replay the same OC-OLR AVP multiple times between the
>  overload control endpoints, however, when the OC-OLR AVP content changes
>  or the
>  sending endpoint otherwise wants the receiving endpoint to update
>  its overload control information in an active overload report,
>  then the OC-Sequence-Number AVP MUST contain
>  a new value which is greater than the last value received for that
>  overload report.
>  The receiver SHOULD discard an OC-OLR AVP with a sequence number that is
>  less than or equal to any currently active overload report previously
>  received from the reporting node.
>

v2.23.0 | Report a Bug | By Email