RFC 5546, "iCalendar Transport-Independent Interoperability Protocol (iTIP)", December 2009

Note: This RFC has been updated by RFC 6638

Errata ID: 3932
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfie John
Date Reported: 2014-03-25
Verifier Name: Barry Leiba
Date Verified: 2014-03-28

Section 3.1.2 says:

   |   DAYLIGHT         | 0+       | MUST be one or more of either     |
   |                    |          | STANDARD or DAYLIGHT.             |
   |     COMMENT        | 0+       |                                   |
   |     DTSTART        | 1        | MUST be local time format.        |
   |     RDATE          | 0+       |                                   |
   |     RRULE          | 0 or 1   |                                   |
   |     TZNAME         | 0+       |                                   |

It should say:

   |   DAYLIGHT         | 0+       | MUST be one or more of either     |
   |                    |          | STANDARD or DAYLIGHT.             |
   |     COMMENT        | 0+       |                                   |
   |     DTSTART        | 1        | MUST be local time format.        |
   |     RDATE          | 0+       | If present, RRULE MUST NOT be     |
   |                    |          | present                           |
   |     RRULE          | 0 or 1   | If present, RDATE MUST NOT be     |
   |                    |          | present                           |
   |     TZNAME         | 0+       |                                   |

Notes:

The corrected text appeared in RFC 2446, however I couldn't find the reasoning as to why it was omitted in RFC 5546.

The correct comments also appear a few lines below, under "STANDARD".

Report New Errata