Re: [NGO] NETCONF Data types

Phil Shafer <phil@juniper.net> Mon, 07 January 2008 17:46 UTC

Return-path: <ngo-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JBw3U-0002cE-F4; Mon, 07 Jan 2008 12:46:32 -0500
Received: from ngo by megatron.ietf.org with local (Exim 4.43) id 1JBw3T-0002c9-Le for ngo-confirm+ok@megatron.ietf.org; Mon, 07 Jan 2008 12:46:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JBw3T-0002c1-Bx for ngo@ietf.org; Mon, 07 Jan 2008 12:46:31 -0500
Received: from exprod7og110.obsmtp.com ([64.18.2.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JBw3S-0003uM-SM for ngo@ietf.org; Mon, 07 Jan 2008 12:46:31 -0500
Received: from source ([66.129.224.36]) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP; Mon, 07 Jan 2008 09:40:14 PST
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp56.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 7 Jan 2008 09:44:13 -0800
Received: from idle.juniper.net (idleski.juniper.net [172.25.4.26]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m07HiD925084; Mon, 7 Jan 2008 09:44:13 -0800 (PST) (envelope-from phil@idle.juniper.net)
Received: from idle.juniper.net (localhost [127.0.0.1]) by idle.juniper.net (8.13.8/8.13.8) with ESMTP id m07HeMjU085776; Mon, 7 Jan 2008 17:40:23 GMT (envelope-from phil@idle.juniper.net)
Message-Id: <200801071740.m07HeMjU085776@idle.juniper.net>
To: Sharon Chisholm <schishol@nortel.com>
Subject: Re: [NGO] NETCONF Data types
In-reply-to: <713043CE8B8E1348AF3C546DBE02C1B4127632BB@zcarhxm2.corp.nortel.com>
Date: Mon, 07 Jan 2008 12:40:22 -0500
From: Phil Shafer <phil@juniper.net>
X-OriginalArrivalTime: 07 Jan 2008 17:44:13.0755 (UTC) FILETIME=[EABF08B0:01C85154]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ngo@ietf.org
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Errors-To: ngo-bounces@ietf.org

"Sharon Chisholm" writes:
>If it is define with length=64, then you know you can't read it and
>ignore it. If it is defined with length=32, the you know you can read it
>and do.

This can't be a run-time thing.  It needs to be more cut-and-dried.
The model should give you the data types, your shouldn't be mixing
metadata into your data.

If the DML says it's a uint64 and you can't handle uint64s, you
can't handle that data module.  You need to let the user know that
up front.  You can't say "at 2am last night we started dropping
your accounting data because your value went beyond 32 bits".  The
real value in standardizing on data types comes from knowing that
things will function correctly.

Thanks,
 Phil


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