[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: url clarification
Andy Bierman <ietf@andybierman.com> wrote:
> Martin Bjorklund wrote:
> > >....
> >>>
> >>>
> >> I disagree.
> >> This is in there by design to support configuration servers.
> >> For example:
> >>
> >> <edit-config>
> >> <target><running/></target>
> >> <default-operation>none</default-operation>
> >> <test-option>test-then-set</test-option>
> >> <error-option>rollback-on-error</error-option>
> >> <url>https://example.com/config/myConfig.xml</url>
> >> </edit-config>
> >>
> >
> > I agree with you that this would be useful. But the text in 8.8.5.1
> > says that the url should specfiy a local file. Maybe that sentence
> > just should be removed? I don't quite see the point of that
> > restriction.
> >
>
> To be picky, it says should instead of SHOULD.
> It really doesn't mean anything normative.
Yes I noticed that. Ok, so the intention is that the url can be
remote in this case. This makes perfect sense to me.
> > Phil's reply was that <validate> needs a complete configuration. Are
> > you saying that it doesn't? The text says "... the <config> element
> > containing the configuration subtree to validate."
> >
>
> I don't think the text says that anywhere.
I should have mentioned the reference, sorry, it's in 8.6.4.1. (My
point here was that the term "configuration subtree" can be
interpreted as a partial config.)
> Certainly, the inline config XML does not have to be a complete
> configuration.
Ok. But then the validation doesn't give you much more than syntactic
checks. If you first validate a partial config and then try to apply
it with edit-config, the resulting configuration might be invalid.
So if you do <validate> on the candidate, it will validate the full
config. And <validate> on inline config will validate a partial
config (e.g. it must allow incomplete relations). Then the question
is what should <validate> on a local file do? Should it treat it as a
full config or partial?
/martin
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>