Re: [NGO] NETCONF Data types

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 05 December 2007 01:15 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 1Izire-00006X-DO; Tue, 04 Dec 2007 20:15:50 -0500
Received: from ngo by megatron.ietf.org with local (Exim 4.43) id 1Izirc-00006M-QF for ngo-confirm+ok@megatron.ietf.org; Tue, 04 Dec 2007 20:15:48 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izirc-00006A-F8 for ngo@ietf.org; Tue, 04 Dec 2007 20:15:48 -0500
Received: from hermes.jacobs-university.de ([212.201.44.23]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Izirb-0000Uc-Sk for ngo@ietf.org; Tue, 04 Dec 2007 20:15:48 -0500
Received: from localhost (demetrius.jacobs-university.de [212.201.44.32]) by hermes.jacobs-university.de (Postfix) with ESMTP id 50978865CE; Wed, 5 Dec 2007 02:15:47 +0100 (CET)
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 29638-06; Wed, 5 Dec 2007 02:15:42 +0100 (CET)
Received: from elstar.local (elstar.iuhb02.iu-bremen.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 8B93086632; Wed, 5 Dec 2007 02:15:42 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 8AD53409DAA; Wed, 5 Dec 2007 02:15:42 +0100 (CET)
Date: Wed, 05 Dec 2007 02:15:42 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Sharon Chisholm <schishol@nortel.com>
Subject: Re: [NGO] NETCONF Data types
Message-ID: <20071205011542.GA21999@elstar.local>
References: <713043CE8B8E1348AF3C546DBE02C1B412218939@zcarhxm2.corp.nortel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B412218939@zcarhxm2.corp.nortel.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
X-Virus-Scanned: amavisd-new 2.3.3 (20050822) at jacobs-university.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: ngo@ietf.org
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@jacobs-university.de
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

On Tue, Dec 04, 2007 at 07:33:55PM -0500, Sharon Chisholm wrote:
 
> One of the things that people seemed to agree on early in the NETCONF
> content discussion was that SNMP & SMI defined too many similar data
> types and we didn't want to do that in NETCONF. Do people still agree
> that we don't want 30 flavours of integers defined? 

In SMI land, we defined many types in an attempt to express
relationships which are otherwise not expressable. The reason we have
things such as InterfaceIndex and InterfaceIndexOrZero is that we
wanted to capture 'hey this number here actually identifies an
interface'. With a different data modeling language, you might not
need to do this anymore via the type system since you might have other
mechanisms to express the information that a value is actually
identifying an interface.

<soap>
  This is actually an nice example demonstrating that the features of
  a data modeling language will influence the way other features of a
  language are used. The INET-ADDRESS-MIB is another example demoing
  how we had to hack around the lack of unions in the SMI. You can of
  course convert all this stuff algorithmically to XSD; whether the
  result is useful in other contexts (say for NETCONF configuration)
  needs to be considered.
</soap>

That said, I take most of the blame for the collection of data types
in the YANG modules contained in the YANG draft. I tries to create a
core collection of reusable types, but I am sure the result is
somewhat biased and I might have simply overlooked something. I like
to encourage people to take a look at the defined types in the YANG
document and if you think something is wrong, missing, or should not
be there, please drop a note so we can work things out.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


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