Do drt and rot really have a c field?

[VasiliyS]

https://trustoverip.github.io/tswg-keri-specification/#delegated-rotation-event-message-body

defines the following fields: [ v, t, d, i, s, p, kt, k, nt, n, bt, br, ba, c, a].

However, keripy's implementation lacks any references to it. The same goes for the rot message.

according to: https://trustoverip.github.io/tswg-keri-specification/#configuration-traits-field, this could potentially hold RB trait (Registrar Backers).

How should implementers interpret this? Is this something that is only planned for a future revision of KERI?
Should the implementers targeting compatibility with the current vLEI ecosystem refer to the keripy for the authoritative answers then?

[SmithSamuelM]

The 'c' field was added for KERI version 2 for both the "rot" and "drt" messages. The specs as written are forward looking for the next version version 2 not version 1. Version 1 is the production code.

[SmithSamuelM]

If you look more closely however you will see that one can generate version 2 key event messages that include all the version 2 fields. The Fields class variable in the Serder class in keri.core.serdering.py includes the field names for Vrsn_2_0 and you can see that both the 'rot" and "drt" messages include a 'c' field.