Re: XCAP to Proposed Standard
"Randy Presuhn" <[email protected]> Tue, 4 Jul 2006 16:21:51 -0700
| Newsgroups | gmane.ietf.ops-nm |
|---|---|
| Message-ID | <002e01c69fc0$a1c33560$6501a8c0@oemcomputer> |
Hi - > From: "Andy Bierman" <[email protected]> > To: "Romascanu, Dan (Dan)" <[email protected]> > Cc: <[email protected]>; "Ops-Nm (E-mail)" <[email protected]> > Sent: Tuesday, July 04, 2006 2:21 PM > Subject: Re: XCAP to Proposed Standard ... > 5) In a general sense there is clearly overlap between NETCONF and XCAP. > I think NETCONF tries to be more content and transport independent, > and the RPC-based architecture is more suited to standard and vendor > "specialized RPC" extensions, which provide a more natural > programming paradigm than a model based on XML document manipulation. ... However, treating configuration data as document content makes use of existing configuration management specifications (webdav / deltav) conceivable. Randy