Hello,
is section 6.2. (Flexibility) still relevant?
I have the impression all of its statements refer to older versions and
are obsolete in the current protocol.
An originator may change many things about the makeup of Signature
and Certificate Blocks in a given reboot session. The things it
cannot change are:
* The version
* The number or arrangements of Signature Groups
Question 1: Is there anything left that can be changed inside a reboot
session? Only the redundancy, but that is always discussed in 6.1.
Question 2: Is there any reason to prevent any change? IMO no.
I would say a Signature Group is defined by the values of HOSTNAME, VER,
RSID, SG, and SPRI.
So if an originator has only one signature group and suddenly uses
different values for some Blocks then these Blocks simply will not
belong to the same signature group. No need to introduce the concept of
change only to forbid it.
It is legitimate for an originator to send short Signature Blocks to
allow the collector to verify messages quickly.
Signature Blocks are variable in length. Allowing a short one is
meaningless.
--
Martin
_______________________________________________
Syslog mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/syslog
