1 / 6

NETCONF SOAP Binding: Protocol Overview and Implementation Details

This draft presents the NETCONF SOAP Binding protocol, detailing how managers initiate SOAP/HTTP connections to agents. It describes session establishment using multiple connections and the ability to manage time-extended synchronous operations. The document encompasses NETCONF SOAP interface definitions in WSDL, showcasing structuring of requests and responses in XML format. Key topics include reliable syslog usage and the integration of device-specific WSDL for configuration management. This guide serves as a comprehensive reference for implementing NETCONF over SOAP in network devices.

maitland
Télécharger la présentation

NETCONF SOAP Binding: Protocol Overview and Implementation Details

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A SOAP Binding for NETCONF Ted Goddard ted.goddard@windriver.com draft-goddard-netconfsoap-00.txt

  2. NETCONF SOAP Fundamentals • Manager initiates SOAP/HTTP connection to agent • Multiple SOAP/HTTP connections with the same credentials and session identifier in SOAPAction constitute a session • Multiple connections allow management of time-extended synchronous operations • This is not effective for asynchronous notification • A polling form of <rpc-progress> would be useful • Use reliable syslog • Use SOAP/HTTP from the agent to the manager • NETCONF SOAP interface is defined in WSDL • Base netconf/1.0/soap.wsdl defining message types • Device-specific WSDL giving device address and port

  3. NETCONF Machine Readable Document Relationships http://www.ietf.org/netconf/1.0/base.xsd IETF standard data model XSD netconf/1.0/soap.wsdl netconf/1.0/beep.dtd http://www.example.com/datamodel.xsd http://device/netconf.wsdl Note: www.ietf.org can host DTD, XSD, and WSDL just as it now hosts RFC Primarily extension Primarily inclusion/aggregation

  4. NETCONF SOAP Request POST /netconf HTTP/1.0 Content-Type: text/xml; charset=utf-8 SOAPAction: "netconfsession:123" Content-Length: 470 <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <rpc id="101" xmlns="http://ietf.org/netconf/1.0/base"> <get-config> <source> <running/> </source> <config xmlns="http://example.com/schema/1.2/config"> <users/></config> <format>xml</format> </get-config> </rpc> </soapenv:Body> </soapenv:Envelope>

  5. NETCONF SOAP Response HTTP/1.0 200 OK Content-Type: text/xml; charset=utf-8 <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <rpc-reply id="101" xmlns="http://ietf.org/netconf/1.0/base"> <config xmlns="http://example.com/schema/1.2/config"> <users> <user><name>root</name><type>superuser</type></user> <user><name>fred</name><type>admin</type></user> <user> <name>barney</name> <type>admin</type> </user> </users> </config> </rpc-reply> </soapenv:Body> </soapenv:Envelope>

  6. A sequence of valid XML documents: <?xml version="1.0" encoding="UTF-8"?> <rpc> ... </rpc> <?xml version="1.0" encoding="UTF-8"?> <rpc> ... </rpc> or a single document with a special root element: <?xml version="1.0" encoding="UTF-8"?> <rpcSequence> <rpc> ... </rpc> <rpc> ... </rpc> </rpcSequence> SSH Transport Candidates

More Related