RE: [NGO] NETCONF Data types

Hi

This was intended as a design time definition.

Sharon 

-----Original Message-----
From: Phil Shafer [mailto:phil@juniper.net] 
Sent: Monday, January 07, 2008 12:40 PM
To: Chisholm, Sharon (CAR:ZZ00)
Cc: j.schoenwaelder@jacobs-university.de; ngo@ietf.org
Subject: Re: [NGO] NETCONF Data types

"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