%% You should probably cite draft-iijima-netconf-websocket-ps-04 instead of this revision.
@techreport{iijima-netconf-websocket-ps-01,
    number =    {draft-iijima-netconf-websocket-ps-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-iijima-netconf-websocket-ps/01/},
    author =    {Tomoyuki Iijima and Hiroyasu Kimura and Yoshifumi Atarashi and Hidemitsu Higuchi},
    title =     {{NETCONF over WebSocket}},
    pagetotal = 19,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This memo proposes transporting NETCONF over WebSocket protocol{[}I-D.ietf-hybi-thewebsocketprotocol{]}. The use of HTTP and Web-based applications are increasing with the emergence of advanced drawing technologies and cloud computing. IT management systems supporting browser-based interface are getting common. It's natural for network management systems to support Web-based interface. Currently, however, few network management protocols support the transportation over HTTP. Although NETCONF{[}RFC6241{]} was defined to be sent over SOAP/HTTPS{[}RFC4743{]}, it was excluded from the options of realizing notification mechanism{[}RFC5277{]} since HTTP lacks bi- directional capabilty. At present, WebSocket protocol, the update of HTTP with bi-directional capability, is available. This memo describes the way NETCONF is sent over WebSocket protocol.},
}