Draft reminder emails need to show UTC times, and show draft submission tool closures if relevant

[ietf-svn-bot]

keyword_sprint type_defect | by lloyd.wood@yahoo.co.uk

---

(had a lot of trouble creating a login and getting ticket privileges to create this bug report. Never mind finding the bug link at datatracker - bottom of page.)

email reminders say when a draft expires, but not that you can't submit?

From Ryan Cross via RT ietf-info@ietf.org

To: Wood L Dr (Elec Electronic Eng);

Thu 22/10/2015 4:45 AM

Hello Lloyd,

Thank you for your submission. This is an issue the IETF Tools Team should
address. Please use the "Report a Bug" link at the bottom of this page:
http://datatracker.ietf.org/ to raise this with the tools team. This way you
will be notified of changes in status of the issue. If you are unable to do
enter the bug for any reason let me know and I can enter it on your behalf.

Thank You,
Ryan Cross
AMS

On Mon Oct 19 22:58:53 2015, L.Wood@surrey.ac.uk wrote:

Well, this is mildly irritating.

Had a bunch of warnings about drafts expiring:

---

IETF Secretariat ietf-secretariat-reply@ietf.org
To draft-wood-tsvwg-saratoga@ietf.org Oct 19 at 10:42 PM
The following draft will expire soon:

Name: draft-wood-tsvwg-saratoga
Title: Saratoga: A Scalable Data Transfer Protocol
State: I-D Exists
Expires: 2015-10-20 (in 19 hours, 17 minutes)

---

Drafts were expiring sometime on the 20th of October (in, one
presumes, the US, because no timezone was given, and the IETF is
very much a US organisation. I live in Australia, no timezone for
expiry time given on these emails.)

So I refreshed the draft ready to do the necessary six-month
accounting. Only to discover that I-D submission had already closed
at midnight UTC on the 19th because of the upcoming IETF meeting.
Which wasn't mentioned in the email.

Why not state the earlier submission deadline as well as a hard limit?
Why aren't timezones stated?

Bravo for https://datatracker.ietf.org/submit/ stating timezones, if
not consistently.

Please file lack of timezones and lack of consideration of early
submission deadlines as a bug.

thanks
Lloyd Wood
http://about.me/lloydwood

---

Issue migrated from trac:1825 at 2022-03-04 04:47:37 +0000

[ietf-svn-bot]

@lloyd.wood@yahoo.co.uk uploaded file ietf-login.PNG (40.6 KiB)

created login, got told no privileges to create ticket

[ietf-svn-bot]

@rjsparks@nostrum.com changed priority from n/a to minor

[ietf-svn-bot]

@rjsparks@nostrum.com changed keywords from `` to sprint

[ietf-svn-bot]

@rjsparks@nostrum.com changed status from new to accepted

[richsalz]

Should we make everything be UTC?

diff --git a/ietf/utils/timezone.py b/ietf/utils/timezone.py
index a396b5e82..308c8f0ef 100644
--- a/ietf/utils/timezone.py
+++ b/ietf/utils/timezone.py
@@ -12,12 +12,12 @@ from django.utils import timezone
 # require code changes.
 #
 # Default time zone for deadlines / expiration dates.
-DEADLINE_TZINFO = ZoneInfo('PST8PDT')
+DEADLINE_TZINFO = ZoneInfo('UTC')
 
 # Time zone for dates from the RPC. This value is baked into the timestamps on DocEvents
 # of type="published_rfc" - see Document.pub_date() and ietf.sync.refceditor.update_docs_from_rfc_index()
 # for more information about how that works.
-RPC_TZINFO = ZoneInfo('PST8PDT')
+RPC_TZINFO = ZoneInfo('UTC')
 
 
 def _tzinfo(tz: Union[str, datetime.tzinfo, None]):

Probably need to update the text in some places to indicate it is UTC.

[rjsparks]

This will get integrated into a more general issue about how we represent deadlines. Note that we will be shifting to "Anywhere on Earth" but making that explicit with the equivalent UTC.