Re: Last Call: <draft-ietf-netmod-revised-datastores-09.txt> (Network Management Datastore Architecture) to Proposed Standard two

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



---- Original Message -----
From: "Juergen Schoenwaelder" <j.schoenwaelder@xxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, January 11, 2018 12:58 PM


> On Thu, Jan 11, 2018 at 12:32:29PM -0000, tom p. wrote:
> > ----- Original Message -----
> > From: "Juergen Schoenwaelder" <j.schoenwaelder@xxxxxxxxxxxxxxxxxxxx>
> > Sent: Wednesday, January 10, 2018 4:36 PM
> >
> > > Right. Lets see there "two" is used:
> > >
> > > - 1st paragraph in 2. Objectives: I think the text is clear since
it
> > >   talks about a concrete example of a configured value and an
> > >   operationally used value.
> > >
> > > - 2nd paragraph in 2. Objectives: This text talks about two
separate
> > >   branches in the old models, this should be fine.
> > >
> > > - 4th paragraph in 2. Objectives: I think this is potentially
> > >   causing the confusion. It says:
> > >
> > >     With the revised architectural model of datastores defined in
this
> > >     document, the data objects are defined only once in the YANG
> > schema
> > >     but independent instantiations can appear in two different
> > >     datastores, one for configured values and one for operational
> > state
> > >     values.
> > >
> > >   Perhaps a better wording would be this:
> > >
> > >     With the revised architectural model of datastores defined in
this
> > >     document, the data objects are defined only once in the YANG
> > >     schema but independent instantiations can appear in different
> > >     datastores, e.g., for a configured value and one for an
> > >     operationally used value.
> > >
> > >   This e.g. then kind of continues the example the section started
> > >   with. Would this change have avoided the question?
> >
> > Juergen
> >
> > Yes, I would find that clearer.  Perhaps even better
> >
> > OLD
> >      e.g., for a configured value and one for an
> >     operationally used value.
> > NEW
> >      e.g., one for a configured value and one (another?)  for an
> >      operationally used value.
> >
> > I would say 'one' and 'another'  but 'one' and 'one' would be clear
> > enough.
> >
>
> I now have this:
>
>   With the revised architectural model of datastores defined in this
>   document, the data objects are defined only once in the YANG schema
>   but independent instantiations can appear in different datastores,
>   e.g., one for a configured value and another for an operationally
used
>   value.
>
> OK?

OK

Tom Petch

> /js
>
> --
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]