70 th IETF meeting Experience of implementing NETCONF over SOAP (...

70th IETF meeting

Experience of implementing NETCONF over SOAP

(draft-iijima-netconf-soap-implementation-04)

Tomoyuki Iijima, Yoshifumi Atarashi, Hiroyasu Kimura, Makoto Kitani

(Alaxala Networks)Hideki Okita

(Hitachi Central Research Lab)

Objective of this I-D

Provide a guideline of implementing SOAP-based NETCONF client & server as an informational RFCSince the way of developing SOAP-based

client & server can be formalized to some extent inside the framework of Web-service technology

Changes since -03

Added a detailed guideline of developing SOAP-based NETCONF client & server

And, to make the I-D persuasive...We prepared a demo of implementing very

simple NETCONF client & server for this meeting

For those who are interested in SOAP-based NETCONF implementation, we are willing to demonstrate!

Network Equipment

Demonstration overview

NMS

SO

AP

(Apache A

xis)

NE

TC

ON

F client

HT

TP

d

NETCONF client NETCONF server

NE

TC

ON

F stub

NETCONF request

NETCONF response

Both NETCONF client & server are implemented in a same computer for the purpose of demonstration

JDK

SO

AP

(Apache A

xis)

NE

TC

ON

F skeleton

HT

TP

d

JDK

Apa

che T

omca

t

Things we did for this demo

Most of the basic source codes are automatically generated from following files“netconf.xsd” from RFC4741“netconf-soap_1.0.wsdl” from RFC4743“myNetconfService.wsdl” from RFC4743

So things we did by hand were… (written in the I-D)Preparing development environments of Eclipse, Apa

che Axis, Apache Ant and Apache TomcatPreparing files of “build.xml” and “build.properties”

Source code which I needed to write was just only 10 lines for NETCONF client

But basic communication between NETCONF client and server is achieved

NETCONF messages

Captured by TCPmon, an utility tool of Apache Axis

NETCONF client & server are running correctly although source code I wrote was just 10 lines for NETCONF client

NETCONF requestfrom client to server

NETCONF responsefrom server to client

Conclusions

When using SOAP as a transport protocol of the NETCONF, basic components are automatically generated thanks to the Web-service technologyUnnecessary to care about and write SOAP-RPC part

by ourselvesRelatively easy to start developing SOAP-based

NETCONF client & server

In this I-D, we are willing to share the knowledge gained from the actual development of a NETCONF/SOAP-based network management system

For those interested in SOAP-based implementation demo which is developed based on our I-D, we are willing to demonstrate