Browse Prior Art Database

Experience of Implementing NETCONF over SOAP (RFC5381)

IP.com Disclosure Number: IPCOM000176025D
Original Publication Date: 2008-Oct-01
Included in the Prior Art Database: 2008-Nov-02
Document File: 23 page(s) / 48K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Iijima: AUTHOR [+5]

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Network Working Group                                          T. Iijima Request for Comments: 5381                                   Y. Atarashi Category: Informational                                        H. Kimura                                                                M. Kitani                                                   Alaxala Networks Corp.                                                                 H. Okita                                                            Hitachi, Ltd.                                                             October 2008

               Experience of Implementing NETCONF over SOAP

Status of This Memo

   This memo provides information for the Internet community.  It does    not specify an Internet standard of any kind.  Distribution of this    memo is unlimited.

IESG Note

   This document discusses implementation experience of NETCONF over    SOAP.  Note that Section 2.4 of RFC 4741 states, "A NETCONF    implementation MUST support the SSH transport protocol mapping".    Therefore, a NETCONF implementation that only supports the SOAP    transport described in this document and not (at least) also SSH is    not in compliance with the NETCONF standards.

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.

Iijima, et al.               Informational                      [Page 1]
 RFC 5381        Experience of Implementing NETCONF/SOAP     October 2008

 Table of Contents

   1. Introduction ....................................................3

      1.1. NETCONF over SOAP ...............................