Logging Capabilities for IP Network Infrastructure
draft-cain-logging-caps-01

Document Type Expired Internet-Draft (individual)
Authors George Jones  , Patrick Cain 
Last updated 2006-09-20
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-cain-logging-caps-01.txt

Abstract

This document lists logging capabilities originally defined in RFC3871 and needed to support the current practices, including those described in the Operational Security Current Practices document[CURPRAC] Logging is defined as the delivery to another entity or system of messages about the device, the data passing through the device, or the device's interaction with another device. Capabilities are defined without reference to specific technologies. This is done to leave room for deployment of new technologies that implement the capability. Each capability cites the practices it supports. Current implementations that support the capability are cited. Special considerations are discussed as appropriate listing operational and resource constraints, limitations of current implementations, trade offs, etc.

Authors

George Jones (gmjones@mitre.org)
Patrick Cain (pcain@coopercain.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)