[VCARDDAV] [Errata Held for Document Update] RFC6350 (4261)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 03 March 2015 00:25 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: vcarddav@ietfa.amsl.com
Delivered-To: vcarddav@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 66B761A8AEC; Mon, 2 Mar 2015 16:25:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.312
X-Spam-Status: No, score=-101.312 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_36=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id E3PDOzkxSZhM; Mon, 2 Mar 2015 16:25:45 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 5293F1A8AEB; Mon, 2 Mar 2015 16:25:45 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1B30D180204; Mon, 2 Mar 2015 16:25:01 -0800 (PST)
To: ivan.enderlin@fruux.com, simon.perreault@viagenie.ca
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150303002501.1B30D180204@rfc-editor.org>
Date: Mon, 02 Mar 2015 16:25:01 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/vcarddav/QBG18kZLDxtq-rz5rYgNUD-Y0yU>
Cc: barryleiba@computer.org, iesg@ietf.org, vcarddav@ietf.org, rfc-editor@rfc-editor.org
Subject: [VCARDDAV] [Errata Held for Document Update] RFC6350 (4261)
X-BeenThere: vcarddav@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF vcarddav wg mailing list <vcarddav.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vcarddav/>
List-Post: <mailto:vcarddav@ietf.org>
List-Help: <mailto:vcarddav-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vcarddav>, <mailto:vcarddav-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Mar 2015 00:25:46 -0000

The following errata report has been held for document update 
for RFC6350, "vCard Format Specification". 

You may review the report below and at:

Status: Held for Document Update
Type: Technical

Reported by: Ivan Enderlin <ivan.enderlin@fruux.com>
Date Reported: 2015-02-05
Held by: Barry Leiba (IESG)

Section: 4.3

Original Text
In RFC6351 (Appendice A), we have a Relax NG Schema defining date and
time format:

# 4.3.1
value-date = element date {
    xsd:string { pattern = "\d{8}|\d{4}-\d\d|--\d\d(\d\d)?|---\d\d" }

# 4.3.2
value-time = element time {
    xsd:string { pattern = "(\d\d(\d\d(\d\d)?)?|-\d\d(\d\d?)|--\d\d)"
                         ~ "(Z|[+\-]\d\d(\d\d)?)?" }

# 4.3.3
value-date-time = element date-time {
    xsd:string { pattern = "(\d{8}|--\d{4}|---\d\d)T\d\d(\d\d(\d\d)?)?"
                         ~ "(Z|[+\-]\d\d(\d\d)?)?" }

# 4.3.4
value-date-and-or-time = value-date | value-date-time | value-time

We assume this is the format from ISO.8601.2004 mentioned in RFC6350.
There is no link on ISO.8601.2004 because ISO documents are not free.
So this is our guess: These formats are very close based on different
examples in RFC6350 and RFC6351.

Corrected Text
See notes.

Question: --10 is October or 10 seconds?

--10 can fit into value-date and value-time:

  * From value-date, the 3rd element in the disjunction is --\d\d(\d\d)?, so it matches --10,
  * From value-time, the last element in the first disjunction is --\d\d, so it matches --10.

value-date-and-or-time matches value-date before value-time. Conclusion: --10 is always October and never 10 seconds. Is it a technical error in the RFC.

PS: This erratum can be applied on RFC6350 and RFC6351.
PPS: Consider the following erratum http://www.rfc-editor.org/errata_search.php?rfc=6351&eid=4247 on value-time also.

----- Verifier Notes -----
This errata report highlights a real problem that was not foreseen by the working group at the time when the RFC was published. Interoperability issues could result, so it's important to take note of this.

Fixing the problem will require revising the RFC, possibly in a non-backward-compatible manner. The fix is not trivial and discussion and a document update will be necessary.

RFC6350 (draft-ietf-vcarddav-vcardrev-22)
Title               : vCard Format Specification
Publication Date    : August 2011
Author(s)           : S. Perreault
Category            : PROPOSED STANDARD
Source              : vCard and CardDAV
Area                : Applications
Stream              : IETF
Verifying Party     : IESG