A SOAP Binding for NETCONF
draft-goddard-netconfsoap-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Ted Goddard | ||
Last updated | 2003-06-23 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
While the device management protocol NETCONF is generally well served by BEEP, there are environments where additional transports are desirable. The binding to SOAP described here may find application where SOAP-based tools and implementations are prevalent or where the network configuration favors HTTP. When used with multiple HTTP connections, SOAP over HTTP is sufficient for all NETCONF features except those involving asynchronous notification.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)