RE: [NGO] NETCONF Data types

Hi

Complex type was a poor choice of words. Sorry about that. My brain is
still in post-holiday mush mode. It's more of an appInfo which specifies
the length for those who are interested and is ignorable for those who
are not. This could potentially be done using existing base integer
types.

Sharon 

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

"Sharon Chisholm" writes:
>This was intended as a design time definition.

Then I'm lost.  You said earlier:

>> In that case, a better approach is likely a complex type which gives 
>> length and value. This way if you handle all lengths, you just need 
>> to look at the value field.

Where is the complex type?  Sounded like you meant to encode both the
length and the value in the transmitted data.  What's the value of
carrying to length if the module definition tells you the max length?
Or am I misreading you completely?

Thanks,
 Phil

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