I propose we remove timezone and rely on client-side libraries to implement SQL semantics for now. I think this is similar to the decimal scale discussion, where the use cases we're building for right now don't require storing the zone that a time was written with. Almost all of the time, users care about time translated to their current zone. When we get a compelling use case that this should be representable in parquet we can tackle the problem then.