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

Actually, this topic is one that came up as part of a conversation this
morning at the CalConnect confernce here in Germany this week.

I had been asking the group for help about how to solve a problem (parsing
the line DTSTART;TZID=GMT-03:00:20180822T075501 from a partner
organisation). We had a small group discussion and Ken and Mike were
advising me to tell our partner to quote the timezone when they spotted the
issue.

Thanks,

Keith Harris
https://youcanbook.me

On Wed, 26 Sep 2018 at 13:01, Eliot Lear <lear@cisco.com> wrote:

> 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> <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 listcalsify@ietf.orghttps://www.ietf.org/mailman/listinfo/calsify
>
>
>
>
> _______________________________________________
> calsify mailing listcalsify@ietf.orghttps://www.ietf.org/mailman/listinfo/calsify
>
>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>