Experience of Implementing NETCONF over SOAP
RFC 5381, “Experience of Implementing NETCONF over SOAP”, is an Informational document published in October 2008 by T. Iijima, Y. Atarashi, H. Kimura, M. Kitani, H. Okita. The canonical text is published by the RFC Editor.
Abstract
This document describes how the authors developed a SOAP (Simple Object Access Protocol)-based NETCONF (Network Configuration Protocol) client and server. It describes an alternative SOAP binding for NETCONF that does not interoperate with an RFC 4743 conformant implementation making use of cookies on top of the persistent transport connections of HTTP. When SOAP is used as a transport protocol for NETCONF, various kinds of development tools are available. By making full use of these tools, developers can significantly reduce their workload. The authors developed an NMS (Network Management System) and network equipment that can deal with NETCONF messages sent over SOAP. This document aims to provide NETCONF development guidelines gained from the experience of implementing a SOAP-based NETCONF client and server. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5381 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5380 Hierarchical Mobile IPv6 Mobility Management
- RFC 5382 NAT Behavioral Requirements for TCP
- RFC 5383 Deployment Considerations for Lemonade-Compliant Mobile Email
- RFC 5378 Rights Contributors Provide to the IETF Trust
- RFC 5384 The Protocol Independent Multicast Join Attribute Format
- RFC 5377 Advice to the Trustees of the IETF Trust on Rights to Be Granted in IETF Documents
- RFC 5376 Inter-AS Requirements for the Path Computation Element Communication Protocol
- RFC 5386 Better-Than-Nothing Security: An Unauthenticated Mode of IPsec