RE: NetConf over SOAP normative reference issue

["Rob Enns" <rpe@juniper.net>]

> New dumb questions  Does NetConf even need BEEP?  
> Why not use a WebDAV-like binding over HTTP/1.1?

There was a fair bit of discussion about this. Definitely
lots of good reasons to do it either way. RFC 3205 discusses
some pros/cons of HTTP as a substrate, and much of the NETCONF
related discussion is captured in the WG minutes and 
mailing list archive. In the end the WG picked SSH as 
the mandatory to implement transport, but given the
interest in web services I expect to see NETCONF over
SOAP/HTTP implementations as well.

Rob

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>