71th IETF meeting Experience of implementing NETCONF over SOAP (draft-iijima-netconf-soap-implementation-06)

1
71th IETF meetingExperience of implementing
NETCONF over SOAP (draft-iijima-netconf-soap-impl
ementation-06)

• Tomoyuki Iijima, Yoshifumi Atarashi,
• Hiroyasu Kimura, Makoto Kitani
• (Alaxala Networks)
• Hideki Okita
• (Hitachi Central Research Lab)

2
Objectives of our I-D

• To provide guidelines of implementing SOAP-based
  NETCONF in a form of informational RFC
• To share the knowledge obtained from our
  experience in order to help SOAP-based NETCONF be
  deployed widely

3
Changes since the last meeting

• Got AD-sponsorship
• Completed Last Call on Feb. 12
• Revised the I-D in response to comments
• Revised Introduction and Security
  considerations section
• Added a description in section 1 that makes clear
  that this document is not a product from the
  NETCONF WG but a report on the experience
• Added a reason for using Cookie field for session
  maintenance mechanism
• Got through a native check, thus became more
  readable

4
Main points of our I-D

• In the case of using SOAP as a transport protocol
  of NETCONF, developments of NETCONF client
  server are done inside Web Service framework
• By taking advantage of development tools
  available in public, APIs are automatically
  generated from XSD WSDL files selected from
  RFC4741 4743
• By using those APIs, SOAP-based NETCONF
  application are developed without being concerned
  about SOAP messaging
• Sharing those knowledge will be useful for the
  wide deployment of NETCONF client server

5
Architecture of our SOAP-based NETCONF
implementation
Network Equipment
NMS
NETCONF service provider (NETCONF server)
NETCONF application (NETCONF client)
NETCONF stub (Java API)
SOAP Implementation (Apache Axis)
SOAP Implementation
WSDL2Java
Java2WSDL
HTTP/TLS
HTTP/TLS
NETCONF request / SOAP / HTTP
NETCONF response / SOAP / HTTP
6
Conclusions

• Updated on NETCONF WG with current status of our
  I-D after the revision
• Intended status Informational RFC
• Summarized main points of our I-D
• More than a year has passed since this I-D first
  came out, but more review is appreciated