iCalendar for upcoming events contains floating DTSTART times

[ietf-svn-bot]

resolution_fixed type_defect | by ietf@augustcellars.com

---

I am getting events like:

BEGIN:VEVENT
UID:ietf-interim-2020-add-02-13046
SUMMARY:add - Adaptive DNS Discovery
STATUS:CONFIRMED
CLASS:PUBLIC
DTSTART:20200915T130000
DTEND:20200915T153000
DTSTAMP:20200814T114243Z
URL:https://www.ietf.org/proceedings/interim-2020-add-02/agenda/agenda-interim-2020-add-02-add-01-00
DESCRIPTION:\n
\nAgenda:
https://www.ietf.org/proceedings/interim-2020-add-02/agenda/agenda-interim-2020-add-02-add-01-00\n
END:VEVENT

Note that the DTSTART time does not have a TZID prefix, nor does it have a "Z" suffix to denote that it is UTC time. This means that it is "local-time" per section 3.3.5 of RFC 5545. My mail client (Outlook 2016) believes that this is not ok for events that are not full day events. It is also not consistent in the downloaded file as most events have either the TZID prefix or the trailing Z.

---

Issue migrated from trac:3074 at 2022-03-04 07:59:57 +0000

[ietf-svn-bot]

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

[ietf-svn-bot]

@rjsparks@nostrum.com changed resolution from `` to fixed

[ietf-svn-bot]

@rjsparks@nostrum.com commented

---

See https://mailarchive.ietf.org/arch/msg/tools-discuss/ED0zTuUn4Cmb4ZBXsPnu28a901k

[ietf-svn-bot]

@ietf@augustcellars.com commented

---

Is this supposed to have been fixed retroactively or just for new items?

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

For all items, with reservation for possible caching of .ics responses

[ietf-svn-bot]

@ietf@augustcellars.com changed status from closed to reopened

[ietf-svn-bot]

@ietf@augustcellars.com changed resolution from fixed to ``

[ietf-svn-bot]

@ietf@augustcellars.com commented

---

A new COSE meeting created today has this problem.

BEGIN:VEVENT
UID:ietf-interim-2020-cose-05-13073
SUMMARY:cose - CBOR Object Signing and Encryption
STATUS:CONFIRMED
CLASS:PUBLIC
DTSTART:20201007T160000
DTEND:20201007T170000
DTSTAMP:20200923T100916Z
URL:https://www.ietf.org/proceedings/interim-2020-cose-05/agenda/agenda-interim-2020-cose-05-cose-01-00
DESCRIPTION:\n
 Note: https://www.worldtimebuddy.com/?qm=1&lid=8\,12\,100&h=8&date=2020-10-07&sln=9-10\n
 \nAgenda:
  https://www.ietf.org/proceedings/interim-2020-cose-05/agenda/agenda-interim-2020-cose-05-cose-01-00\n
END:VEVENT

[ietf-svn-bot]

@henrik@levkowetz.com changed _comment0 which not transferred by tractive

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

Hi Jim,

I can't reproduce this -- the responses I get have timezone set:

Getting https://datatracker.ietf.org/meeting/interim-2020-cose-05/session/28399.ics:

BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
PRODID:-_IETF_datatracker.ietf.org ical agenda//EN
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
TZNAME:UTC
DTSTART:19000101T000000
RDATE:19000101T000000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:ietf-interim-2020-cose-05-13073-cose
SUMMARY:cose - CBOR Object Signing and Encryption (https://www.worldtimebuddy.com/?qm=1&lid=8,12,100&h=8&date=2020-10-07&sln=9-10)
LOCATION:None
STATUS:CONFIRMED
CLASS:PUBLIC
DTSTART;TZID=UTC:20201007T160000
DTEND;TZID=UTC:20201007T170000
DTSTAMP:20200923T100916Z
URL:https://www.ietf.org/proceedings/interim-2020-cose-05/agenda/agenda-interim-2020-cose-05-cose-01-00
DESCRIPTION:\n
 Note: https://www.worldtimebuddy.com/?qm=1&lid=8\,12\,100&h=8&date=2020-10-07&sln=9-10\n
 \nAgenda:
  https://datatracker.ietf.org/meeting/interim-2020-cose-05/materials/agenda-interim-2020-cose-05-cose-01\n
END:VEVENT
END:VCALENDAR

Am I looking in the wrong place?

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

Ok, I think I found it; I believe this was in https://datatracker.ietf.org/meeting/upcoming.ics .

I've got it fixed, and will apply a patch.

[ietf-svn-bot]

@ietf@augustcellars.com commented

---

Yes, i wa getting tis from the upcomming.ics

[ietf-svn-bot]

@henrik@levkowetz.com changed status from reopened to closed

[ietf-svn-bot]

@henrik@levkowetz.com changed resolution from `` to fixed

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

Fixed in 1b6124c:

Changed the template for /meeting/upcoming.ics to not produce floating times for meetings with UTC timezone. Fixes issue #3074.