Re: [NGO] external module properties

Martin Bjorklund <mbj@tail-f.com> Wed, 30 April 2008 06:28 UTC

Return-Path: <ngo-bounces@ietf.org>
X-Original-To: ngo-archive@optimus.ietf.org
Delivered-To: ietfarch-ngo-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A295B3A68D6; Tue, 29 Apr 2008 23:28:29 -0700 (PDT)
X-Original-To: ngo@core3.amsl.com
Delivered-To: ngo@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A7983A68D6 for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 23:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level:
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i8Wh8kCRem6m for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 23:28:28 -0700 (PDT)
Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id 438BE3A685A for <ngo@ietf.org>; Tue, 29 Apr 2008 23:28:28 -0700 (PDT)
Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id DE8DC1B80CD; Wed, 30 Apr 2008 08:28:30 +0200 (CEST)
Date: Wed, 30 Apr 2008 08:28:28 +0200
Message-Id: <20080430.082828.120924636.mbj@tail-f.com>
To: randy_presuhn@mindspring.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <00ae01c8aa2b$edee6b40$6801a8c0@oemcomputer>
References: <200804291905.m3TJ5ewb090087@idle.juniper.net> <20080429.214810.13543341.mbj@tail-f.com> <00ae01c8aa2b$edee6b40$6801a8c0@oemcomputer>
X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Cc: ngo@ietf.org
Subject: Re: [NGO] external module properties
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ngo-bounces@ietf.org
Errors-To: ngo-bounces@ietf.org

"Randy Presuhn" <randy_presuhn@mindspring.com> wrote:
> > From: "Martin Bjorklund" <mbj@tail-f.com>
> > How about adding an optional counter after the date?  So you can do
> > 
> >   2008-04-29
> >   2008-04-29:1
> >   2008-04-29:2
> > 
> > and so on.
> > 
> > It removes the arbitrary timing constraint that worries Wes, and it's
> > still simple enough for the common use case.
> ...
> 
> Even simpler - just use RFC 3339 date-time with the option of
> abbreviating it to full-date.  That should be enough for even the
> busiest believers in rapid prototyping.

That was my first thought as well, with the additional CLR to only use
UTC, in order for simple string comparison to work.  But I thought a
single integer would be simpler and do the job just fine.

If we do a single integer, we should use a dot instead of colon, as
Andy suggested.


/martin

_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo