 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
Hello, I am a proponent of NETCONF and am trying to promote it
within my organization, Netscaler/Citrix. I am running into some difficultly selling NETCONF to my
colleges who have build a prototype using a RESTful web services
approach. In this approach they are using JSON over
HTTP. The retrieval of individual configuration entities is handled
by mapping the request to an HTTP GET request on a particular URL (eg. GET device_ip_address/entity_X/name).
Setting of configuration entities are mapped to HTTP POST requests. Can anyone give me some ideas how I might sell the NETCONF
idea to non-believers? I think some advantages of NETCONF are: 1)
That it is a standard that has been adopted by large network vendors (ie
Juniper and Cisco) Any
others? 2)
I suspect that it has been adopted by network management vendors. Do we
have any vendor names? One question that I have been asked is how easier is it to wrap
client-side language-bindings around the NETCONF protocol. For example,
in the web services world, one has a WSDL file, and client side language
binding can be automatically generated. How does one achieve
this stub generation with NETCONF? Can this be achieve with the NETCONF
over SOAP scheme. Thank you. --Graham Phillips |