Re: [calsify] [Technical Errata Reported] RFC5545 (5920)

[Eliot Lear <[e-mail]>]

I propose accepting this erratum.  While it is true that the recurrence set would remain unchanged, the text in RFC 5545 is very clear:

> The "DTSTART" property defines
> the first instance in the recurrence set.  The "DTSTART" property
> value SHOULD be synchronized with the recurrence rule, if
> specified.  The recurrence set generated with a "DTSTART" property
> value not synchronized with the recurrence rule is undefined.

Here that wasn’t the case, and there was no good reason for it not to be the case; and in fact the example leads us right into that undefined state.

Eliot

> On 26 Nov 2019, at 21:50, RFC Errata System <[e-mail]> wrote:
> 
> The following errata report has been submitted for RFC5545,
> "Internet Calendaring and Scheduling Core Object Specification (iCalendar)".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid5920
> 
> --------------------------------------
> Type: Technical
> Reported by: Lars Henriksen <[e-mail]>
> 
> Section: 3.8.5.3
> 
> Original Text
> -------------
> Every Friday the 13th, forever:
> 
>       DTSTART;TZID=America/New_York:19970902T090000
>       EXDATE;TZID=America/New_York:19970902T090000
>       RRULE:FREQ=MONTHLY;BYDAY=FR;BYMONTHDAY=13
> 
>       ==> (1998 9:00 AM EST) February 13;March 13;November 13
>           (1999 9:00 AM EDT) August 13
>           (2000 9:00 AM EDT) October 13
>           ...
> 
> Corrected Text
> --------------
> Every Friday the 13th, forever:
> 
>       DTSTART;TZID=America/New_York:19980213T090000
>       RRULE:FREQ=MONTHLY;BYDAY=FR;BYMONTHDAY=13
> 
>       ==> (1998 9:00 AM EST) February 13;March 13;November 13
>           (1999 9:00 AM EDT) August 13
>           (2000 9:00 AM EDT) October 13
>           ...
> 
> Notes
> -----
> The "DTSTART" property is not synchronized with the recurrence rule.
> 
> Although it may be removed from the recurrence set by an "EXDATE" property, the description at the start of section 3.8.5.3 leaves no doubt that the "DTSTART" property should still be synchronized with the recurrence rule.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC5545 (draft-ietf-calsify-rfc2445bis-10)
> --------------------------------------
> Title               : Internet Calendaring and Scheduling Core Object Specification (iCalendar)
> Publication Date    : September 2009
> Author(s)           : B. Desruisseaux, Ed.
> Category            : PROPOSED STANDARD
> Source              : Calendaring and Scheduling Standards Simplification
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG