draft-ietf-opsec-logging-caps-03

[Ron Bonica <rbonica@juniper.net>]

Folks,

The following are a few comments from AD review:

- In Section 2.16, all sensitive configuration information needs to be
protected. This includes thinks like cryptographic keys as well as
passwords.

- Do we need another requirement that says that it should be difficult,
if not impossible, to alter the local copy of a log?

- How should the system behave if some components spews 1,000,000
instances of the same log message in a 5 second period?

- How should the system behave if some component spews 1,000,000
different messages in a 5 second period.

- How should the system behave when all of the space for local logging
is exhausted. Drop oldest messages? Tail drop?

- We will probably have to decide if this doc is BCP or INFO.

                                     Ron