When a Protobuf message is evaluated, a google.protobuf.Timestamp field outside of the valid ranges raises an IllegalArgumentException.

The behavior is logical, but how can users determine that a Protobuf message is safe to evaluate? An invalid Timestamp serializes and parses without error, and I don't believe that there is an API to validate that a message contains only conforming Timestamp values in any OSS Protobuf implementation.

#820 adds a deprecation notice to the evaluateCanonicalTypesToNativeValues option with a note that the option will be removed. Are there perhaps any plans to consolidate the behavior between Protobuf implementations and CEL?