Logging Capabilities for IP Network Infrastructure
draft-ietf-opsec-logging-caps-04
| Document | Type |
Expired Internet-Draft
(opsec WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Patrick Cain , George M. Jones | ||
| Last updated | 2015-10-14 (Latest revision 2007-08-24) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Best Current Practice | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Dead WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Ron Bonica | ||
| 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 document lists logging capabilities originally identified in Operational Security Requirements for Large Internet Service Provider (ISP) IP Network Infrastructure [RFC3871] and needed to support current operational practices, including those described in Operational Security Current Practices In Internet Service Provider Environments [RFC4778]. Logging is defined as the delivery of messages about the device, the data passing through the device, or the device's interaction with another device and has been traditionally provided via the syslog or SNMP protocols.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)