[calsify] [Francesca] Re: [External] : [Technical Errata Reported] RFC5545 (7332)

[Rebecca VanRheenen <[e-mail]>]

Hi Francesca,

We see that you verified this errata report on 16 Jan 2024. See https://www.rfc-editor.org/errata/eid7332.

Bernard Desruisseaux suggests updating the corrected text to:

      The period starting at 18:00:00 UTC, on January 1, 1997 and lasting 5
      hours and 30 minutes would be:

       19970101T180000Z/PT5H30M

May we make this change in the report? Because you verified it already, we want to check in with you before making a change.

Thank you,
RFC Editor/rv



> On Mar 4, 2024, at 8:44 AM, Bernard Desruisseaux <[e-mail]> wrote:
> 
> Dear RFC Editor,
> 
> I've just noticed that Errata 7332 doesn't specify the Corrected Text that I had proposed and was agreed by Eliot Lear and Tobias Subklewe (reporter).
> 
> https://www.rfc-editor.org/errata_search.php?rfc=5545&eid=7332
> 
> 
> Correct Text:
> 
>       The period starting at 18:00:00 UTC, on January 1, 1997 and lasting 5
>       hours and 30 minutes would be:
> 
>        19970101T180000Z/PT5H30M
> 
> 
> Thanks,
> Bernard
> 
>> On Feb 4, 2023, at 1:37 PM, Tobias Subklewe <[e-mail]> wrote:
>> 
>> Yeah,
>> 
>> this will work. Though I think it would be nice to have two differing datetime examples. I'm fine either way.
>> 
>> The grammar issue is a nice catch. Did not see that.
>> 
>> On 04.02.23 14:29, Bernard Desruisseaux wrote:
>>> Thanks Tobias!
>>> 
>>> The issue was also present in RFC2445.
>>> 
>>> 	• https://www.rfc-editor.org/rfc/rfc2445#section-4.3.9
>>> 
>>> I would add UTC in the text rather than removing the 'Z' in the example, and fix the grammar as well!
>>> 
>>> Correct Text:
>>> 
>>>       The period starting at 18:00:00 UTC, on January 1, 1997 and lasting 5
>>>       hours and 30 minutes would be:
>>> 
>>>        19970101T180000Z/PT5H30M
>>> 
>>> Thanks,
>>> Bernard
>>> 
>>> 
>>>> On Feb 4, 2023, at 3:58 AM, RFC Errata System <[e-mail]> 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:
>>>> https://urldefense.com/v3/__https://www.rfc-editor.org/errata/eid7332__;!!ACWV5N9M2RV99hQ!L6gFuabr9gpjhMKQIgFVEpkCMd_6GmT6dQmUysMz_X0IVDYneZSkBxF3n65B4iGFzRN22CWpYpeC40Zki3siplsZ4-X-UuIc$ 
>>>> 
>>>> --------------------------------------
>>>> Type: Technical
>>>> Reported by: Tobias Subklewe <[e-mail]>
>>>> 
>>>> Section: 3.3.9
>>>> 
>>>> Original Text
>>>> -------------
>>>> The period start at 18:00:00 on January 1, 1997 and lasting 5
>>>> hours and 30 minutes would be:
>>>> 
>>>> 19970101T180000Z/PT5H30M
>>>> 
>>>> Corrected Text
>>>> --------------
>>>> The period start at 18:00:00 on January 1, 1997 and lasting 5
>>>> hours and 30 minutes would be:
>>>> 
>>>> 19970101T180000/PT5H30M
>>>> 
>>>> Notes
>>>> -----
>>>> I do not know if this is an editorial or technical issue.
>>>> 
>>>> If I understand the datetime value (Section 3.3.5) correct the last character should only be "Z" if the value is in UTC.
>>>> 
>>>> In the first example in section 3.3.9 UTC is explicitely mentioned but not in the second example.
>>>> 
>>>> 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
>>> 
>