RE: [NGO] NETCONF Data types

"David Harrington" <ietfdbh@comcast.net> Wed, 05 December 2007 18:56 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 1IzzQV-0005gx-QM; Wed, 05 Dec 2007 13:56:55 -0500
Received: from ngo by megatron.ietf.org with local (Exim 4.43) id 1IzzQV-0005gW-Em for ngo-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 13:56:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzzQV-0005gN-4b for ngo@ietf.org; Wed, 05 Dec 2007 13:56:55 -0500
Received: from qmta06.westchester.pa.mail.comcast.net ([76.96.62.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzzQT-0007Qc-Ht for ngo@ietf.org; Wed, 05 Dec 2007 13:56:55 -0500
Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA06.westchester.pa.mail.comcast.net with comcast id M6tQ1Y00T1HzFnQ0500R00; Wed, 05 Dec 2007 18:56:53 +0000
Received: from Harrington73653 ([130.129.64.99]) by OMTA14.westchester.pa.mail.comcast.net with comcast id M6wn1Y00728V7k20300000; Wed, 05 Dec 2007 18:56:53 +0000
X-Authority-Analysis: v=1.0 c=1 a=48vgC7mUAAAA:8 a=bMLQ_gy9gg7WcT14kEUA:9 a=P3Y6fCBf0JxXaLPW2_gA:7 a=8bdpussumhVO5pFm5imv9SfCIR4A:4 a=ZPn7O4N2MpQA:10 a=lZB815dzVvQA:10 a=ucw2XimmUOMA:10 a=f7GxY0FH8QIA:10 a=50e4U0PicR4A:10
From: David Harrington <ietfdbh@comcast.net>
To: 'Sharon Chisholm' <schishol@nortel.com>, 'Andy Bierman' <ietf@andybierman.com>
References: <713043CE8B8E1348AF3C546DBE02C1B412218939@zcarhxm2.corp.nortel.com><475661FF.7030502@ericsson.com><713043CE8B8E1348AF3C546DBE02C1B41226FBCD@zcarhxm2.corp.nortel.com><4756EA8B.7010006@andybierman.com> <713043CE8B8E1348AF3C546DBE02C1B41226FCAB@zcarhxm2.corp.nortel.com>
Subject: RE: [NGO] NETCONF Data types
Date: Wed, 05 Dec 2007 10:56:41 -0800
Message-ID: <037801c83770$93f5bf40$ca168182@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <713043CE8B8E1348AF3C546DBE02C1B41226FCAB@zcarhxm2.corp.nortel.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Thread-Index: Acg3aun7HyKdFOCRSpyt1edTK8r3WQAAVulwAADuspA=
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
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, 

> -----Original Message-----
> From: Sharon Chisholm [mailto:schishol@nortel.com] 
> Sent: Wednesday, December 05, 2007 10:31 AM
> To: Andy Bierman
> Cc: ngo@ietf.org
> Subject: RE: [NGO] NETCONF Data types
> 
> 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.

In 15 years of advising MIB writers and NMS developers, I have never
had anybody complain they didn't understand the difference between a
counter and a guage, or thought the distinction was unimportant. I
feel sad that you, as a MIB Doctor, do not understand the difference.

dbh

> 
> 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 mailing list
NGO@ietf.org
https://www1.ietf.org/mailman/listinfo/ngo