IETF Logo Mail Archive

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

Jouni Korhonen <jouni.nospam@gmail.com> Mon, 09 December 2013 11:37 UTC

Return-Path: <jouni.nospam@gmail.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 6AB271AE279 for <dime@ietfa.amsl.com>; Mon, 9 Dec 2013 03:37:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-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 754szpFrDfG1 for <dime@ietfa.amsl.com>; Mon, 9 Dec 2013 03:37:27 -0800 (PST)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id F37391ADF23 for <dime@ietf.org>; Mon, 9 Dec 2013 03:37:26 -0800 (PST)
Received: by mail-la0-f42.google.com with SMTP id ec20so1481635lab.29 for <dime@ietf.org>; Mon, 09 Dec 2013 03:37:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=Q94a/y85YlpMfovh1C3jNEJsSzkWKFquQevrs/7XIe4=; b=eOmFZO+1hWcUJN3Z0JldU4jHR+DHOfof65FgSsJ8MH2PEYe6yAezBFdJPCQuRI0Ekj U+ejC9aKncutjpEfJJxBdd01l0J/wAIExxVDF6TaZdNZWcnCvLVR/DY1nCl9dj5rSzjy IIOvyxJXN1rn7cB1guSdi45ua8HIQmTWPeLb/Bdkh0H60b+vBdUChhg1t7RGh7CclHJF OxEWAcRH6hb3bqzKT2/UVWPOJNpnGtfCWQrTA6Zy3kbuvDYo6QgzOPpYX7pPuAHm+HXb xDBmvli7O0wnobbUmuietASyauiWsujzyIx/7RCzARdJyC1WwDefDN1H1OeSGylc8Ruy cYzg==
X-Received: by 10.152.180.104 with SMTP id dn8mr2103304lac.48.1386589041480; Mon, 09 Dec 2013 03:37:21 -0800 (PST)
Received: from [188.117.15.108] ([188.117.15.108]) by mx.google.com with ESMTPSA id di11sm13917413lac.0.2013.12.09.03.37.19 for <dime@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Dec 2013 03:37:20 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <5BCBA1FC2B7F0B4C9D935572D90006681519DB1B@DEMUMBX014.nsn-intra.net>
Date: Mon, 09 Dec 2013 13:37:19 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <C66C8914-AA7A-47F5-8EA4-7B0ECEDA5368@gmail.com>
References: <5BCBA1FC2B7F0B4C9D935572D90006681519DB1B@DEMUMBX014.nsn-intra.net>
To: "dime@ietf.org list" <dime@ietf.org>
X-Mailer: Apple Mail (2.1510)
Subject: [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 11:37:28 -0000

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

v2.23.0 | Report a Bug | By Email