Re: url clarification

[Andy Bierman <ietf@andybierman.com>]

Martin Bjorklund wrote:
> Phil Shafer <phil@juniper.net> wrote:
>   
> > Martin Bjorklund writes:
> >     
> > > > So you could copy-config a file, but
> > > > not edit-config or lock-config it.
> > > >         
> > > Aha, not even edit-config?  That's explicitly allowed by 8.8.5.1.   
> > >       
> > Hmmm.... that's a bug in the draft IMHO.
> >     
>
> Sorry, I got it wrong.  8.8.5.1 allows <url> instead of <config> in an
> <edit-config>. <url> is not allowed as an <edit-config> target.  An
> example is given in D.1.5.  (the schema is wrong though).
>
> However, the example in D.1.5 should probably use <copy-config>
> instead of <edit-config>, since an <edit-config> w/o operation
> attributes (which is used in the example) will use the default
> "merge", which may give different results than <copy-config>.  An
> alternative is to set default-operation to "replace" on the
> <edit-config>.
>   

Did we ever resolve all the issues here? (A: no)

Here are the operations that use rpcOperationTargetType:

 operation            text-allows-url     notes
 ------------------------------------------------
 edit-config                N               1
 copy-config                Y               2
 delete-config              Y               3
 lock                       N               4
 unlock                     N               4


Notes:

1) The WG never explicitly allowed or disallowed local or remote files
  as the target of an edit-config.  The intent was as Phil described.
  The rationale is that edit-config involves partial editing, which is
  an attribute of configuration databases, not files.

2) An implementation does not have to support remote to remote copies 
via URLs.

3) This is mandatory to support if :url capability is advertised; 
otherwise there
  is no way to delete local files, after they have been copied to the 
device
  via copy-config.

4) It was never the intent of the WG that remote URLs could be locked 
and unlocked
  But this is not explicitly allowed or disallowed.

Summary Issues:

A) Which is right: The text or the XSD?
  Should the edit-config, lock, and unlock XSD definitions change from
  rpcOperationTargetType to configNameType?  This will explicitly
  disallow URL as <target> in these operations.

B) If an agent advertises the :url capability, what operations
  MUST, SHOULD, or MAY it apply to?  What if an agent only
  supports URLs as the <source> parameter and not the <target> parameter
  on some or all operations?



> /martin
>
>   

Andy

> -


--
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/>