Re: [Dime] Conclusion for Sequence Numbers - was Re: OVLI: comments to 4.3

Steve Donovan <srdonovan@usdonovans.com> Mon, 09 December 2013 16:00 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 BF4A41AE347 for <dime@ietfa.amsl.com>; Mon, 9 Dec 2013 08:00:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.779
X-Spam-Level:
X-Spam-Status: No, score=0.779 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 kWFIo9OHFXqX for <dime@ietfa.amsl.com>; Mon, 9 Dec 2013 08:00:13 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [173.247.247.114]) by ietfa.amsl.com (Postfix) with ESMTP id E9EBD1AE357 for <dime@ietf.org>; Mon, 9 Dec 2013 08:00:09 -0800 (PST)
Received: from cpe-76-187-100-94.tx.res.rr.com ([76.187.100.94]:55087 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <srdonovan@usdonovans.com>) id 1Vq3Fa-0001cV-88 for dime@ietf.org; Mon, 09 Dec 2013 08:00:03 -0800
Message-ID: <52A5E902.20605@usdonovans.com>
Date: Mon, 09 Dec 2013 10:00:02 -0600
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.1.1
MIME-Version: 1.0
To: dime@ietf.org
References: <5BCBA1FC2B7F0B4C9D935572D90006681519DB1B@DEMUMBX014.nsn-intra.net> <C66C8914-AA7A-47F5-8EA4-7B0ECEDA5368@gmail.com>
In-Reply-To: <C66C8914-AA7A-47F5-8EA4-7B0ECEDA5368@gmail.com>
Content-Type: multipart/alternative; boundary="------------070802010606000707000700"
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
Subject: Re: [Dime] Conclusion for Sequence Numbers - was Re: 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: Mon, 09 Dec 2013 16:00:15 -0000

Jouni,

I propose that we keep the name OC-Sequence-Number but that we use the
Time type for OC-Sequence-Number.  It is misleading and potentially
confusing to call it OC-Time-Stamp. 

We might consider expanding on the format of the AVP to make it
something like Session-ID, where it is a concatenation of the
Diameter-ID of the generating node and a timestamp.  This might help the
reacting node keep track of which sequence number it has received.

Steve

On 12/9/13 5:37 AM, Jouni Korhonen wrote:
> Folks
>
> Could we conclude on the sequence number vs. time stamp vs. something else?
> We got more important places to spend our energy than this ;)
>
> My proposal is the following (based on the original pre-00 design):
>
> o We change the OC-Sequence-Number to OC-Time-Stamp in all occurrences
>   in the -01.
> o We use RFC6733 Time type for the OC-Time-Stamp. RFC6733 gives us
>   already exact definition how to handle the AVP.
> o Define that the OC-Time-Stamp is the time of the creation of the 
>   "original" AVP within whose context the time stamp is present.
> o The OC-Time-Stamp AVP uniqueness is still considered to be in scope
>   of the communicating endpoints.
> o The time stamp can be used to quickly determine if the content of
>   the encapsulating AVP context has changed (among other properties).
>   This would be useful specifically in the future when the encapsulating
>   grouped AVPs  grow in size and functionality.
>
>
> - Jouni
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>