A SYSLOG Capability for NETCONF
draft-shafer-netconf-syslog-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Philip A. Shafer | ||
| Last updated | 2006-06-22 | ||
| 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
SYSLOG is the most prevalent mechanism for delivering event notification data off networking devices. NETCONF is intended to provide a standard mechanism for performing configuration operations on networking devices. The two areas will overlap, giving rise to a need for receiving notification data over NETCONF. This document presents a simple mechanism for accessing SYSLOG data over NETCONF, implemented using the existing NETCONF RPC infrastructure.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)