RE: [NGO] NETCONF Data types
"Sharon Chisholm" <schishol@nortel.com> Wed, 05 December 2007 18:31 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 1Izz2F-0001Dk-14; Wed, 05 Dec 2007 13:31:51 -0500
Received: from ngo by megatron.ietf.org with local (Exim 4.43) id 1Izz2D-0000xz-PJ for ngo-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 13:31:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Izz2D-0000s3-89 for ngo@ietf.org; Wed, 05 Dec 2007 13:31:49 -0500
Received: from zcars04f.nortel.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Izz2B-00053S-Lh for ngo@ietf.org; Wed, 05 Dec 2007 13:31:49 -0500
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com [47.129.230.99]) by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id lB5IVi719270; Wed, 5 Dec 2007 18:31:44 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [NGO] NETCONF Data types
Date: Wed, 05 Dec 2007 13:31:29 -0500
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B41226FCAB@zcarhxm2.corp.nortel.com>
In-Reply-To: <4756EA8B.7010006@andybierman.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [NGO] NETCONF Data types
Thread-Index: Acg3aun7HyKdFOCRSpyt1edTK8r3WQAAVulw
References: <713043CE8B8E1348AF3C546DBE02C1B412218939@zcarhxm2.corp.nortel.com> <475661FF.7030502@ericsson.com> <713043CE8B8E1348AF3C546DBE02C1B41226FBCD@zcarhxm2.corp.nortel.com> <4756EA8B.7010006@andybierman.com>
From: Sharon Chisholm <schishol@nortel.com>
To: Andy Bierman <ietf@andybierman.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
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
Hi My logic is that most of the value in types comes from building up complex types, not by redefining base types. I don't understand why you are proposing redefining xs:dateTime to map to what we had in SNMP for example. I want to make sure we understand the requirements of the space we are in now and not just auto-translate data types from where we were a few years ago. Honestly, I don't know the differences between a counter and a gauge and I suspect the a lot of people who read SNMP MIBs who were in the same boat. Sharon -----Original Message----- From: Andy Bierman [mailto:ietf@andybierman.com] Sent: Wednesday, December 05, 2007 1:15 PM To: Chisholm, Sharon (CAR:ZZ00) Cc: balazs.lengyel@ericsson.com; ngo@ietf.org Subject: Re: [NGO] NETCONF Data types Sharon Chisholm wrote: > Hi > > But just because they are used in programming, doesn't mean we need to > distinguish them in the XSD. I'm going to check with some of my apps > people to see whether they would find this distinction useful or if a > single integer which could be as large as 64 bit is fine at this later > point in time. But I was more specifically worried about counter > versus gauge versus integer versus unsigned integer versus. > Historically these turned into CLRs. > I totally disagree. I remember several times, NMS programmers at Cisco asking for int8, int16, uint8, uint16. It is very useful to have these 'extra' types. I also think it has been very useful to distinguish between gauges, counters, and simple numbers in SMIv2. If one followed your logic to the end, we would only have 'string', since that is the only 'real' content in an XML simpleType. > An advantage here if we don't limit the length of our integers, we > won't need to rewrite our Schema when we need 128bit integers ;-) > > We can add them later if and when somebody has a compelling use case. > Sharon > Andy > -----Original Message----- > From: Balazs Lengyel [mailto:balazs.lengyel@ericsson.com] > Sent: Wednesday, December 05, 2007 3:32 AM > To: Chisholm, Sharon (CAR:ZZ00) > Cc: ngo@ietf.org > Subject: Re: [NGO] NETCONF Data types > > Hello Sharon, > The uint32, int64 etc. integer types are not a left-overs from SMI. They > are the integer types that people normally use in programing. Names like > uint16, int32 are better then short or long. They tell you exactly what > you deal with. I see this as an improvement over the XSD types. > Balazs > > Sharon Chisholm wrote: > >> Hi >> >> 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? I prefer focusing >> our efforts on defining higher level data types. >> >> Sharon Chisholm >> Nortel >> Ottawa, Ontario >> Canada >> >> >> _______________________________________________ >> NGO mailing list >> NGO@ietf.org >> https://www1.ietf.org/mailman/listinfo/ngo >> > > > _______________________________________________ > NGO mailing list > NGO@ietf.org > https://www1.ietf.org/mailman/listinfo/ngo > > > _______________________________________________ NGO mailing list NGO@ietf.org https://www1.ietf.org/mailman/listinfo/ngo
- [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- Re: [NGO] NETCONF Data types Andy Bierman
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Andy Bierman
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- Re: [NGO] NETCONF Data types Martin Bjorklund
- Re: [NGO] NETCONF Data types Balazs Lengyel
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Andy Bierman
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Ladislav Lhotka
- Re: [NGO] NETCONF Data types Martin Bjorklund
- Re: [NGO] NETCONF Data types Andy Bierman
- RE: [NGO] NETCONF Data types David Harrington
- Re: [NGO] NETCONF Data types Ladislav Lhotka
- RE: [NGO] NETCONF Data types Mehmet Ersue
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- Re: [NGO] NETCONF Data types tom.petch
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- Re: [NGO] NETCONF Data types Andy Bierman
- Re: [NGO] NETCONF Data types Andy Bierman
- RE: [NGO] NETCONF Data types Natale, Bob
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- RE: [NGO] NETCONF Data types Sharon Chisholm
- RE: [NGO] NETCONF Data types Ladislav Lhotka
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder
- Re: [NGO] NETCONF Data types Phil Shafer
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Phil Shafer
- RE: [NGO] NETCONF Data types Sharon Chisholm
- Re: [NGO] NETCONF Data types Juergen Schoenwaelder