Re: [Netconf] Review of draft-ietf-netconf-monitoring-02.txt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Netconf] Review of draft-ietf-netconf-monitoring-02.txt



>  
> Appendix A YANG
> 
>  <clip a long list of issues>
> 
> <sharon>
>  We probably should only have a  pointer to the yang definition stored

> elsewhere. We can't have any dependencies on  the netmod work if we 
> plan on completing on schedule. Anything we include in this ID, even 
> in non-normative form, can't help but be out of date since netmod  
> won't be done when we publish.
> 
> </sharon>
> 
{BALAZS}: I disagree. I believe making YANG informative deals with the
timing. I have already seen the first emails stating that they mostly
look at YANG not the XSD.

This isn't a beauty contest question. We have a normative language for
defining content at the moment and we have work in progress. As I
stated, we need to minimize the dependencies in the draft on work in
progress. If some people find it useful to also having netmod stuff
available, I think it makes more sense to do it outside the draft, where
it will be easier to keep up to date and the standards evolve.

Sharon
_______________________________________________
Netconf mailing list
Netconf at ietf.org
https://www.ietf.org/mailman/listinfo/netconf



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.