Currently we have a field User.timezone (a Charfield(max_length=15) and nothing else. TIM start and end times of a session refer to that time zone. Which is wrong if the user travels. We can (a) add such a timezone field to Session or (b) add a choicelist Timezones. Solution (b) is more complex but uses only 2 instead of 15 bytes per session record.