RE: Explicit and unique naming of configuration target

["Chen, Weijing" <wchen@tri.sbc.com>]

First, the operation model of Enns draft should be described in a XML schema
separation from protocol encapsulation schema.  Second, the true separation
of protocol from data model give you more than just X over BEEP, or X over
SOAP over HTTP.  It gives the XML schema validation, namespace lookup,
transaction wrapper, etc as in the following:

<perform-request id="09233523-567b"
              transaction="atomic/stop-on-error/continue-on-error"
              xmlns="http://www.ietf.org/mops";
              xmlns:example="http://example.com/schema";> 



--
Weijing Chen
SBC Technology Resources
9505 Arboretum Blvd.
Austin, TX 78759
512 372 5710
wchen@tri.sbc.com


> -----Original Message-----
> From: Eliot Lear [mailto:lear@cisco.com]
> Sent: Friday, May 23, 2003 11:20 AM
> To: Chen, Weijing
> Cc: netconf@ops.ietf.org
> Subject: Re: Explicit and unique naming of configuration target
> 
> Chen, Weijing wrote:
> 
> > We all know that we want a protocol separating from data model.
However,
> > the Enns draft does imply a specific operation model (backup, running,
> > validating, global-only manipulation of XML tree, etc).
> 
> The Enns draft specifically allows for the option of each of these
> models, but does not mandate any of them other than that you use one of
> them.
> 
> >  Not all the device
> > or system follows the same model.  We are working on a draft that the
> > protocol should be able to accommodate the different data model:
> protocol
> > only specifies the encapsulation envelop and target, the data model will
> > decide the actual operation.
> 
> If that's all you want then you might as well just use straight BEEP or
> SOAP over HTTP.  No need to define protocol operations.  They could be
> in your data model.  That's what people do today and that's why we have
> N different ways to do it.
> 
> Eliot


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