NETCONF over WebSocket
draft-iijima-netconf-websocket-ps-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Tomoyuki Iijima , Hiroyasu Kimura , Yoshifumi Atarashi , Hidemitsu Higuchi | ||
| Last updated | 2013-04-19 (Latest revision 2012-10-16) | ||
| 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
This memo proposes a way of transporting NETCONF over WebSocket protocol. Web-related technologies are advancing and number of Web- based systems are increasing. Management systems that adopt Web- related technologies or that have browser-based management interface are getting common. It is natural to expect that there is a standard network operation and management protocol to be used over HTTP. Currently, however, there are few efforts in this area. Although NETCONF[RFC6241] once defined itself to be sent over SOAP/ HTTPS[RFC4743], supposedly due to unfamiliarity to SOAP or lack of bi-directional capability, such efforts aren't successful enough[I-D.ietf-netconf-rfc4743-rfc4744-to-historic]. But now, WebSocket protocol, the update of HTTP equipped with bi-directional capability, is available[RFC6455]. This memo describes how NETCONF should be treated over WebSocket protocol.
Authors
Tomoyuki Iijima
Hiroyasu Kimura
Yoshifumi Atarashi
Hidemitsu Higuchi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)