Re: [Dime] Issue#32 status

Ben Campbell <ben@nostrum.com> Thu, 20 February 2014 22:43 UTC

Return-Path: <ben@nostrum.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 7E75B1A0319 for <dime@ietfa.amsl.com>; Thu, 20 Feb 2014 14:43:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level:
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] 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 gbcSzK64sHN4 for <dime@ietfa.amsl.com>; Thu, 20 Feb 2014 14:43:21 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 653C61A0304 for <dime@ietf.org>; Thu, 20 Feb 2014 14:43:21 -0800 (PST)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s1KMhF1e008666 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Feb 2014 16:43:16 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <53050FE6.2090800@usdonovans.com>
Date: Thu, 20 Feb 2014 16:43:16 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E45B36C-AB19-4869-A73B-4BA98B4ED0A4@nostrum.com>
References: <5BCBA1FC2B7F0B4C9D935572D9000668151B3D63@DEMUMBX014.nsn-intra.net> <53050FE6.2090800@usdonovans.com>
To: Steve Donovan <srdonovan@usdonovans.com>
X-Mailer: Apple Mail (2.1827)
Received-SPF: pass (shaman.nostrum.com: 173.172.146.58 is authenticated by a trusted mechanism)
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/5z8pUEAcuINARErAfUcPC3dTOXQ
Cc: "dime@ietf.org list" <dime@ietf.org>
Subject: Re: [Dime] Issue#32 status
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, 20 Feb 2014 22:43:22 -0000

On Feb 19, 2014, at 2:11 PM, Steve Donovan <srdonovan@usdonovans.com> wrote:

>>> Sequence-Number is of type Time, however the value need not correspond to the point in time of generation.
>> SRD> I don't agree that the type should be time.  It should be of type Unsigned64.  A time stamp can be inserted into it but we should not prevent simple sequence numbers.  I agree with the remainder of the statement.
> 


+1. Making it type Time implies that the recipient can do something time related with the value. That is not the case here.