Hi - >From: Ladislav Lhotka <lho...@nic.cz> >Sent: Oct 1, 2015 12:24 AM >To: Juergen Schoenwaelder <j.schoenwael...@jacobs-university.de> >Cc: Randy Presuhn <randy_pres...@mindspring.com>, netmod@ietf.org >Subject: Re: [netmod] 6020bis - anydata ... >Fine by me. So here is an updated proposal: > >OLD > > The "anydata" statement is used to represent an unknown set of nodes > that can be modelled with YANG. An example of where this can be > useful is a list of received notifications, where the exact > notifications are not known as design time. > >NEW > > The "anydata" statement is used to represent an unknown set of nodes > that can be modelled with YANG but for which the data model is not > known at module design time. It is possible, though not required, for
s/know/known/ > the data model for "anydata" content to become known through protocol > signalling or other means that are outside the scope of this > document, as is the server and client behaviour. I'd end the sentence at "document." The rest of the sentence doesn't really add anything. There's still a big lump under the carpet, but no one else appears concerned about it, so I'll desist from further comment. Randy _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
