[calsify] [Errata Verified] RFC5546 (3932)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 28 March 2014 19:55 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B7D01A0732; Fri, 28 Mar 2014 12:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0mOHpVmL2bRd; Fri, 28 Mar 2014 12:55:30 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 0897D1A0723; Fri, 28 Mar 2014 12:55:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 27F137FC395; Fri, 28 Mar 2014 12:55:18 -0700 (PDT)
To: alfiej@fastmail.fm, cyrus@daboo.name
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140328195523.27F137FC395@rfc-editor.org>
Date: Fri, 28 Mar 2014 12:55:18 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/calsify/G7aY17RnQiEHn1fXE0QHfvftkl8
Cc: rfc-editor@rfc-editor.org, barryleiba@computer.org, iesg@ietf.org, calsify@ietf.org
Subject: [calsify] [Errata Verified] RFC5546 (3932)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Mar 2014 19:55:31 -0000

The following errata report has been verified for RFC5546,
"iCalendar Transport-Independent Interoperability Protocol (iTIP)". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5546&eid=3932

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Alfie John <alfiej@fastmail.fm>
Date Reported: 2014-03-25
Verified by: Barry Leiba (IESG)

Section: 3.1.2

Original Text
-------------
   |   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+       |                                   |

Corrected Text
--------------
   |   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".

--------------------------------------
RFC5546 (draft-ietf-calsify-2446bis-10)
--------------------------------------
Title               : iCalendar Transport-Independent Interoperability Protocol (iTIP)
Publication Date    : December 2009
Author(s)           : C. Daboo, Ed.
Category            : PROPOSED STANDARD
Source              : Calendaring and Scheduling Standards Simplification
Area                : Applications
Stream              : IETF
Verifying Party     : IESG