Re: [Jcardcal] [Technical Errata Reported] RFC7265 (6360)

Barry Leiba <barryleiba@computer.org> Thu, 24 December 2020 18:41 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: jcardcal@ietfa.amsl.com
Delivered-To: jcardcal@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F19BF3A0637 for <jcardcal@ietfa.amsl.com>; Thu, 24 Dec 2020 10:41:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 ABqSU9pft-eK for <jcardcal@ietfa.amsl.com>; Thu, 24 Dec 2020 10:41:07 -0800 (PST)
Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com [209.85.167.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 614493A02BD for <jcardcal@ietf.org>; Thu, 24 Dec 2020 10:41:07 -0800 (PST)
Received: by mail-lf1-f47.google.com with SMTP id y19so6233291lfa.13 for <jcardcal@ietf.org>; Thu, 24 Dec 2020 10:41:07 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=FiI89j1YlJWD2h8LWSpLxmBrJJKQFF3seWDc/TNot20=; b=R1iLNi9R4DOA/cJoE9Lq9V0/92iAqkCW2ftBSQKwr1gu13PC7ifgzozciM5njW20VI jko53Rwx/4C2CeecmGw0wsny5aq4splNGhyI9S+tSBNX2QJiQlCrZy6azdP9rmi/j0Vv au2U9vUbWFvv3lMujN1KsjA99tQGNGBJja2rDBF/UAubg3hRyvE8lNzYso+aHs4YEv5K TUB3xG3Iir2qOhxgRUdb395sJHHcz4L6fgOysV9y3vl8LwTwpd8ul0/zCk8wA9+djTkz L4CkhEvMxnp99Tr2akMPN86npuVuX91f9gCEDagqkMuQEMlHSC/VDWYPxuzvZ2wWZ2Ik eYjA==
X-Gm-Message-State: AOAM530BC1lfJxwtL4get5NXVSHSzkw3By9PIbmzsGowYBJm2Zg3l0Ep /E/loBZMoGlh2omzSU32obYZNvtd7uPzBBrdiv4pNH8eXM4wTw==
X-Google-Smtp-Source: ABdhPJyuLyNyfaB9XUEcpYBgjq0SXxmJv0294IbPsZjLqG1N69vr8ACU53GcrZ+L8HWcTX7n0x+LVe5VAhicnHctgqQ=
X-Received: by 2002:a05:6512:786:: with SMTP id x6mr12313176lfr.643.1608835265493; Thu, 24 Dec 2020 10:41:05 -0800 (PST)
MIME-Version: 1.0
References: <20201221054019.A5FB7F4073A@rfc-editor.org>
In-Reply-To: <20201221054019.A5FB7F4073A@rfc-editor.org>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 24 Dec 2020 13:40:53 -0500
Message-ID: <CALaySJJ_sa_72ER=UKkAy4ChhdD4hq=H5NTucyWCGNYZ86UbAA@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: Philipp Kewisch <mozilla@kewis.ch>, Cyrus Daboo <cyrus@daboo.name>, Murray Kucherawy <superuser@gmail.com>, Peter Saint-Andre <stpeter@stpeter.im>, julesreid@gmail.com, jcardcal@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/jcardcal/TzxB0xy46UwnqD-su60Rip0qbgY>
Subject: Re: [Jcardcal] [Technical Errata Reported] RFC7265 (6360)
X-BeenThere: jcardcal@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON data formats for vCard and iCalendar WG <jcardcal.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jcardcal>, <mailto:jcardcal-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jcardcal/>
List-Post: <mailto:jcardcal@ietf.org>
List-Help: <mailto:jcardcal-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jcardcal>, <mailto:jcardcal-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Dec 2020 18:41:09 -0000

I believe this is incorrect, in that...

      VERSION:2.0\;2.9

...*is* the only correct way to represent that option in iCalendar.
It doesn't help, I guess, that there's no example of a VERSION
property that looks like that, but see RFC 5545 Section 3.3.11, which says
this:

      A SEMICOLON character in a "TEXT" property value MUST
      be escaped with a BACKSLASH character.

...and Section 3.8.8.3, which gives this example for REQUEST-STATUS:

       REQUEST-STATUS:2.8; Success\, repeating event ignored. Scheduled
        as a single event.;RRULE:FREQ=WEEKLY\;INTERVAL=2

Does anyone think this analysis is incorrect?

Barry, ART AD

On Mon, Dec 21, 2020 at 12:40 AM RFC Errata System
<rfc-editor@rfc-editor.org> wrote:
>
> The following errata report has been submitted for RFC7265,
> "jCal: The JSON Format for iCalendar".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6360
>
> --------------------------------------
> Type: Technical
> Reported by: Julian Cowley <julesreid@gmail.com>
>
> Section: GLOBAL
>
> Original Text
> -------------
>
>
> Corrected Text
> --------------
>
>
> Notes
> -----
> In RFC 5545, one of the allowable values for the VERSION property is a minimum version and a maximum version, separated by a semicolon (;).  The value type is TEXT.  When the jCal value is converted back to iCalendar, the text is subject to escape with a backslash.  This yields a result which is not valid for the VERSION property.
>
> Example:
>
> [ "version", {}, "text", "2.0;2.9" ]
>
> becomes
>
> VERSION:2.0\;2.9
>
> which is invalid because it contains the backslash.
>
> 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.
>
> --------------------------------------
> RFC7265 (draft-ietf-jcardcal-jcal-10)
> --------------------------------------
> Title               : jCal: The JSON Format for iCalendar
> Publication Date    : May 2014
> Author(s)           : P. Kewisch, C. Daboo, M. Douglass
> Category            : PROPOSED STANDARD
> Source              : JSON data formats for vCard and iCalendar
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG