RFC 4743: Using NETCONF over the Simple Object Access Protocol (SOAP)
In plain English — editorial summary, not part of the RFC
The Network Configuration Protocol (NETCONF) is applicable to a wide range of devices in a variety of environments. Web Services is one such environment and is presently characterized by the use of the Simple Object Access Protocol (SOAP). NETCONF finds many benefits in this environment: from the reuse of existing standards, to ease of software development, to integration with deployed systems. Herein, we describe SOAP over HTTP and SOAP over Blocks Exchange Extensible Protocol (BEEP) bindings for NETCONF. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4743
- Published
- December 2006
- Authors
- T. Goddard
- Status
- HISTORIC
- Stream
- IETF
- Area
- ops
- Pages
- 20
- Also known as
- —
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5277NETCONF Event NotificationsCurrent
July 2008
- RFC 4744Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)Updated
December 2006
- RFC 4741NETCONF Configuration ProtocolObsoleted
December 2006
- RFC 6020YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)Updated
October 2010
- RFC 6022YANG Module for NETCONF MonitoringCurrent
October 2010
- RFC 6087Guidelines for Authors and Reviewers of YANG Data Model DocumentsObsoleted
January 2011
- RFC 6241Network Configuration Protocol (NETCONF)Updated
June 2011
- RFC 3017XML DTD for Roaming Access Phone BookCurrent
December 2000
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?