Re: [calsify] [Technical Errata Reported] RFC5545 (5505)

Eliot Lear <lear@cisco.com> Wed, 26 September 2018 11:01 UTC

Return-Path: <lear@cisco.com>
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 B4D19130E84 for <calsify@ietfa.amsl.com>; Wed, 26 Sep 2018 04:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 vqxyS0N1kz8O for <calsify@ietfa.amsl.com>; Wed, 26 Sep 2018 04:01:13 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17131130E7F for <calsify@ietf.org>; Wed, 26 Sep 2018 04:01:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9613; q=dns/txt; s=iport; t=1537959673; x=1539169273; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=zG1rdTFZOywQqecCa4AiYI0Y+JxDCupFMwoOy8Fy4qs=; b=gEFmldasBXCNhrkA89lbI5rubpgSosWLi3+5W9Y+NHIV3OtMPlgLxxm/ PV9DUGDAOTZeYYvyEsF5yQuRhbJdA+2WtsMJ8vfvSqA5nUm6p/+sZSgzA 2FBc2559fE5H6gOmJwazP9FHAFLHS25odn65s+R9Lp5cNRHrfIkgiUfRK o=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BbAACcZqtb/xbLJq0WAUIZAQEBAQEBAQEBAQEBBwEBAQEBAYREbRIog3SIdI0wLZEThzYIAxgBCoQDRgKEGzgUAQMBAQIBAQJtHAyFOQEBAQMBASFLGwsOCioCAicwBgEMBgIBAYMdAYIBD4VjnHyBLh+Jbg+CbYgkggCBEieCa4FBgVoBAYRiglcCiEgkhkuNUAmEAYFlikEGF4FGhFKCYYY7h3yNFYFZIYFVMxoIGxUaIYJsCYIcDAuIWoVAPTCNQgEB
X-IronPort-AV: E=Sophos;i="5.54,306,1534809600"; d="asc'?scan'208,217";a="6749765"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Sep 2018 11:01:10 +0000
Received: from [10.61.109.219] (dhcp-10-61-109-219.cisco.com [10.61.109.219]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id w8QB19hA022340; Wed, 26 Sep 2018 11:01:09 GMT
To: Michael Douglass <mikeadouglass@gmail.com>, calsify@ietf.org
References: <20180926090958.74B27B8108E@rfc-editor.org> <983178de-f430-2115-0579-be861b198059@cisco.com> <bc3b0401-7a31-7cc1-d169-7511bdff0319@gmail.com>
From: Eliot Lear <lear@cisco.com>
Openpgp: preference=signencrypt
Autocrypt: addr=lear@cisco.com; prefer-encrypt=mutual; keydata= xsBNBFMe1UQBCADdYOS5APDpIpF2ohAxB+nxg1GpAYr8iKwGIb86Wp9NkK5+QwbW9H035clT lpVLciExtN8E3MCTPOIm7aITPlruixAVwlBY3g7U9eRppSw9O2H/7bie2GOnYxqmsw4v1yNZ 9NcMLlD8raY0UcQ5r698c8JD4xUTLqybZXaK2sPeJkxzT+IwupRSQ+vXEvFFGhERQ88zo5Ca Sa1Gw/Rv54oH0Dq2XYkO41rhxQ60BKZLZuQK1d9+1y3I+An3AJeD3AA31fJZD3H8YRKOBgqe ILPILbw1mM7gCtCjfvFCt6AFCwEsjITGx55ceoQ+t5B5XGYJEppMWsIFrwZsfbL+gP31ABEB AAHNJUVsaW90IExlYXIgPGxlYXJAb2Zjb3Vyc2VpbXJpZ2h0LmNvbT7CwJEEEwECADsCGwMC HgECF4ACGQEWIQSY0L2QRh2wkqeyYR2HtmtG2dJ6MwUCWxJwMwULCQgHAgYVCAkKCwIEFgID AQAKCRCHtmtG2dJ6MyMyCACXvtFjAYGMtOkD9MD4nI3ifFpkrj8xTMbXjrv5hdqmzRmQ0wqA 1U/OlZux+P/NaVMiZNZc8zw0nsx/INAqDOVd4/tLWF+ywTkeRFR0VnaUxLwCReZAZOaRS+md +52u/6ddoFja2RnjZ43qbbuvVUARQVIyMJz+GbR6mEZQHR0psD7dDYZDyrpivCxm8zHQwmB6 AZUlO7OJgljDvVPVDCabg/ZnJw1qS0OzSiNb0MySk1D5A7FdwDgeKxuMYUOOoVVTTMWNWcME UkRX9LxElswEt0PQWiz/j3FYXTxiFfl/1vKcHx4pM+E5C5mhTbrdFUFLJC3Y5fLID7stK/Ch aEaBzsBNBFMe1UQBCAC0WV7Ydbv95xYGPhthTdChBIpPtl7JPCV/c6/3iEmvjpfGuFNaK4Ma cj9le20EA5A1BH7PgLGoHOiPM65NysRpZ96RRVX3TNfLmhGMFr5hPOGNdq+xcGHVutmwPV9U 7bKeUNRiPFx3YdEkExddqV2E8FltT0x2FSKe2xszPPHB6gVtMckX5buI9p1K3fbVhXdvEkcY Y/jB0JEJGyhS5aEbct5cHUvDAkT81/YFK5Jfg8RRwu1q1t1YuIJSOWAZQ9J9oUsg6D9RpClU +tIFBoe3iTp1AUfJcypucGKgLYKtpu/aygcpQONHYkYW5003mPsrajFhReVF5veycMbHs4u5 ABEBAAHCwF8EGAECAAkFAlMe1UQCGwwACgkQh7ZrRtnSejOSuQgA27p2rYB7Kh20dym6V8c6 2pWpBHHTgxr/32zevxHSiXl6xvUCg5T8WUwfUk8OvgDcBErK/blDAMXQzSg3sp450JhR8RnX HXF5Zz2T04X7HnlIVJGwf2CjnwyEAJCqMzaCmI+g3Imvg/8L4nyBFvhlFHDv+kIvMiujyycj PAu7xxKplBs1/IEwmDoAMjneFmawvfeQnwdMhSKK8PjKSuzGU5uUmxj3GBfRqvTM0qpmhMPF OmDhJSmH55HLAky2MlmqJYXJPt/9EfSEhFiua1M6gLiuNEuPkp+8jcnHQqKr0IeHt8UqcwLt 2mGfIyl0FVdF9hvWPjNRzGbgqoT1Di03RQ==
Message-ID: <52b5ebfd-cf74-d765-3ea6-e5c30d071465@cisco.com>
Date: Wed, 26 Sep 2018 13:01:16 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <bc3b0401-7a31-7cc1-d169-7511bdff0319@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="REb7lCISU7Bohbl0npLst3XbieQbnlqWY"
X-Outbound-SMTP-Client: 10.61.109.219, dhcp-10-61-109-219.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/vGtUXwGNwxY7BciWFZ6eOBkRZ6k>
Subject: Re: [calsify] [Technical Errata Reported] RFC5545 (5505)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 26 Sep 2018 11:01:16 -0000

Would it make sense for folks at Calconnect to chime in on this?


On 26.09.18 13:00, Michael Douglass wrote:
>
>
>
> On 9/26/18 11:16, Eliot Lear wrote:
>> While I agree with Ken in principle, I'm a little nervous about the
>> backward compatibility implications here, if parsers are now not
>> expecting quoted text.
> My belief is that parsers are already expecting this. Certainly ical4j
> and libical already accept quoted values.
>
> In any case it's broken as it stands. Parameter escaping isn't an
> option as it assumes parameter value quoting is an option.
>> On 26.09.18 11:09, RFC Errata System wrote:
>>> 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/eid5505
>>>
>>> --------------------------------------
>>> Type: Technical
>>> Reported by: Ken Murchison <murch@fastmail.com>
>>>
>>> Section: 3.2.19
>>>
>>> Original Text
>>> -------------
>>>        tzidparam  = "TZID" "=" [tzidprefix] paramtext
>>>
>>>
>>> Corrected Text
>>> --------------
>>>        tzidparam  = "TZID" "=" [tzidprefix] param-value
>>>
>>>
>>> Notes
>>> -----
>>> TZID appears to be the only parameter defined 5545 whose value can not be a quoted string.  This is problematic in that time zone IDs such as "GMT-03:00" are beginning to appear (note the embedded colon).  RFC 6868 has no mechanism to quote a colon character, as it relies on such characters appearing within a quoted string.  I see no technical reason why a TZID parameter can not be quoted, and existing implementations already accept quoted TZIDs.
>>>
>>> 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 mailing list
>> calsify@ietf.org
>> https://www.ietf.org/mailman/listinfo/calsify
>
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify