On Tue, Dec 4, 2018 at 9:14 AM Robert Wilton wrote:
>
> On 03/12/2018 18:13, Juergen Schoenwaelder wrote:
> > On Mon, Dec 03, 2018 at 09:56:48AM -0800, Andy Bierman wrote:
> >> On Mon, Dec 3, 2018 at 3:36 AM Juergen Schoenwaelder <
> >> j.schoenwael...@jacobs-university.de> wrote:
> >>
> >>> On M
On 03/12/2018 18:13, Juergen Schoenwaelder wrote:
On Mon, Dec 03, 2018 at 09:56:48AM -0800, Andy Bierman wrote:
On Mon, Dec 3, 2018 at 3:36 AM Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
On Mon, Dec 03, 2018 at 10:21:20AM +, Robert Wilton wrote:
On 30/11/2018 19:
On Mon, Dec 03, 2018 at 09:56:48AM -0800, Andy Bierman wrote:
> On Mon, Dec 3, 2018 at 3:36 AM Juergen Schoenwaelder <
> j.schoenwael...@jacobs-university.de> wrote:
>
> > On Mon, Dec 03, 2018 at 10:21:20AM +, Robert Wilton wrote:
> > >
> > > On 30/11/2018 19:28, Juergen Schoenwaelder wrote:
>
On Mon, Dec 3, 2018 at 3:36 AM Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> On Mon, Dec 03, 2018 at 10:21:20AM +, Robert Wilton wrote:
> >
> > On 30/11/2018 19:28, Juergen Schoenwaelder wrote:
> > > I doubt it makes sense to carry an entire yang library schema with th
On Mon, Dec 03, 2018 at 10:21:20AM +, Robert Wilton wrote:
>
> On 30/11/2018 19:28, Juergen Schoenwaelder wrote:
> > I doubt it makes sense to carry an entire yang library schema with the
> > instance data. The modules are actually known via the namespaces.
>
> Knowing the module name or name
On 30/11/2018 19:28, Juergen Schoenwaelder wrote:
I doubt it makes sense to carry an entire yang library schema with the
instance data. The modules are actually known via the namespaces.
Knowing the module name or namespace isn't sufficient to be able to
parse the data:
- E.g. if the content
Hello Andy,
Give me a few days and I will come out with -01 version of the
draft that addresses this issue. We propose 3 options:
Include the needed information as part of instance data as
defined by ietf-yang-library, that documents module name,
revi
On Fri, Nov 30, 2018 at 11:28 AM Juergen Schoenwaelder <
j.schoenwael...@jacobs-university.de> wrote:
> I doubt it makes sense to carry an entire yang library schema with the
> instance data. The modules are actually known via the namespaces. If
> you want to capture the schema, dump the relevant
I doubt it makes sense to carry an entire yang library schema with the
instance data. The modules are actually known via the namespaces. If
you want to capture the schema, dump the relevant yang library into
another instance file.
/js
On Fri, Nov 30, 2018 at 07:07:03PM +, Robert Wilton wrote:
I also think that the instance data header needs to have a way of
indicating which modules (and versions/revisions) the instance data
applies to.
It can be optional, so producers that know it is not required can leave
it out. But I think that it is required, at least for situations where
bei
Hi,
I don't see much standards value in this draft so far.
It seems the parser of the file needs to know the YANG library information
for the instance file data in some out-of-scope non-standard manner.
This is what we already have today just by naming the file in a specific
way.
Is the intent th
11 matches
Mail list logo
