[Netconf] FW: RFC 5381 on Experience of Implementing NETCONF over SOAP

["Romascanu, Dan (Dan)" <[e-mail]>]

 

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of
[e-mail]
Sent: Saturday, November 01, 2008 12:25 AM
To: [e-mail]; [e-mail]
Cc: [e-mail]
Subject: RFC 5381 on Experience of Implementing NETCONF over SOAP


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5381

        Title:      Experience of Implementing NETCONF over 
                    SOAP 
        Author:     T. Iijima, Y. Atarashi,
                    H. Kimura, M. Kitani,
                    H. Okita
        Status:     Informational
        Date:       October 2008
        Mailbox:    [e-mail], 
                    [e-mail], 
                    [e-mail],
                    [e-mail], 
                    [e-mail]
        Pages:      22
        Characters: 47724
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iijima-netconf-soap-implementation-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5381.txt

This document describes how the authors developed a SOAP (Simple Object
Access Protocol)-based NETCONF (Network Configuration
Protocol) client and server.  It describes From [e-mail]  Sun Nov  2 03:51:51 2008
Return-Path: <[e-mail]>
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 882C33A6846;
	Sun,  2 Nov 2008 03:51:51 -0800 (PST)
X-Original-To: [e-mail]
Delivered-To: [e-mail]
Received: from localhost (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id F3EF63A67D9;
	Sun,  2 Nov 2008 03:51:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level: 
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5
	tests=[AWL=-0.077, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32])
	by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id JlmDk5UbHdGS; Sun,  2 Nov 2008 03:51:50 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com
	(de307622-de-outbound.net.avaya.com [198.152.71.100])
	by core3.amsl.com (Postfix) with ESMTP id 4FAD13A67D0;
	Sun,  2 Nov 2008 03:51:49 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,529,1220241600"; d="scan'208";a="126989161"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	02 Nov 2008 06:51:45 -0500
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.13])
	by nj300815-nj-erheast-out.avaya.com with ESMTP;
	02 Nov 2008 06:51:45 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 2 Nov 2008 12:51:43 +0100
Message-ID: <[e-mail]>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RFC 5381 on Experience of Implementing NETCONF over SOAP
Thread-Index: Ack7p6+JbUB3ATGSSe6+4/X6OyTvZwBOacnA
From: "Romascanu, Dan (Dan)" <[e-mail]>
To: <[e-mail]>,
	<[e-mail]>
Subject: [Netconf] FW: RFC 5381 on Experience of Implementing NETCONF over
	SOAP
X-BeenThere: [e-mail]
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netconf>,
	<mailto:[e-mail]?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/netconf>
List-Post: <mailto:[e-mail]>
List-Help: <mailto:[e-mail]?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>,
	<mailto:[e-mail]?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: [e-mail]
Errors-To: [e-mail]

 

-----Original Message-----
From: [e-mail]
[mailto:[e-mail]] On Behalf Of
[e-mail]
Sent: Saturday, November 01, 2008 12:25 AM
To: [e-mail]; [e-mail]
Cc: [e-mail]
Subject: RFC 5381 on Experience of Implementing NETCONF over SOAP


A new Request for Comments is now available in online RFC libraries.

        
        RFC 5381

        Title:      Experience of Implementing NETCONF over 
                    SOAP 
        Author:     T. Iijima, Y. Atarashi,
                    H. Kimura, M. Kitani,
                    H. Okita
        Status:     Informational
        Date:       October 2008
        Mailbox:    [e-mail], 
                    [e-mail], 
                    [e-mail],
                    [e-mail], 
                    [e-mail]
        Pages:      22
        Characters: 47724
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iijima-netconf-soap-implementation-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5381.txt

This document describes how the authors developed a SOAP (Simple Object
Access Protocol)-based NETCONF (Network Configuration
Protocol) client and server.  It describes an altan 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.


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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see
http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
Netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf


ernative 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.


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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see
http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
Netconf mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/netconf