RFC 5381: Experience of Implementing NETCONF over SOAP
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5381
- Published
- October 2008
- Authors
- T. Iijima; Y. Atarashi; H. Kimura; M. Kitani; H. Okita
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5557Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent OptimizationCurrent
July 2009
- RFC 5607Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) ManagementCurrent
July 2009
- RFC 4742Using the NETCONF Configuration Protocol over Secure SHell (SSH)Obsoleted
December 2006
- RFC 4741NETCONF Configuration ProtocolObsoleted
December 2006
- RFC 6242Using the NETCONF Protocol over Secure Shell (SSH)Current
June 2011
- RFC 6243With-defaults Capability for NETCONFCurrent
June 2011
- RFC 6244An Architecture for Network Management Using NETCONF and YANGCurrent
June 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?