[calsify] [Technical Errata Reported] RFC5545 (5082)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 10 August 2017 00:14 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0D34126DD9 for <calsify@ietfa.amsl.com>; Wed, 9 Aug 2017 17:14:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 QYJjI6eWzBQe for <calsify@ietfa.amsl.com>; Wed, 9 Aug 2017 17:14:30 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DF1A126C2F for <calsify@ietf.org>; Wed, 9 Aug 2017 17:14:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CAB68B81503; Wed, 9 Aug 2017 17:14:16 -0700 (PDT)
To: bernard.desruisseaux@oracle.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, lear@cisco.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: georges@mhsoftware.com, calsify@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20170810001416.CAB68B81503@rfc-editor.org>
Date: Wed, 09 Aug 2017 17:14:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/ElP3qZ9vQH8s8pPGHUke8x1S1IU>
Subject: [calsify] [Technical Errata Reported] RFC5545 (5082)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 10 Aug 2017 00:14:32 -0000
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: http://www.rfc-editor.org/errata/eid5082 -------------------------------------- Type: Technical Reported by: George Sexton <georges@mhsoftware.com> Section: 3.8.7.3 Original Text ------------- N/A Corrected Text -------------- The value must not be in the future. Notes ----- If future values are allowed for LAST-MODIFIED, it makes it very difficult for software to perform change management for a VEVENT. Say for example, an event is imported from a source and the VEVENT has a future date. For example, December 20 2017 12:00:00Z That event is then edited and assigned the actual correct date and time. Say August 9 2017 13:45:44Z. Software that examines the VEVENT's LAST-MODIFIED to determine if the VEVENT record has been modified will not see the VEVENT is updated. In order for different systems to perform change management, the value for LAST-MODIFIED should NEVER be a future date. 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
- [calsify] [Technical Errata Reported] RFC5545 (50… RFC Errata System