Re: [calsify] [External] : [IANA #1306185] [Errata Verified] RFC5545 (7332)

[Bernard Desruisseaux <[e-mail]>]

Hi Amanda,

You can list this errata report as an additional reference.

That being said, I've just sent an email to RFC Editor to "fix" the Corrected Text as was agreed during the verification of the reported errata (See attached).

Thanks,
Bernard




> On Mar 1, 2024, at 8:55 PM, Amanda Baber via RT <[e-mail]> wrote:
>
> Hi Bernard, all,
>
> There's an iCalendar registration that refers to this section:
>
> Value Data Type: PERIOD
> Status: Current
> Reference: [RFC5545, Section 3.3.9]
>
> Bernard, as a designated expert for this registry, do you want us to list this errata report as an additional reference for the registration?
>
> The registry is here: https://urldefense.com/v3/__https://www.iana.org/assignments/icalendar__;!!ACWV5N9M2RV99hQ!NSVo-7pntazpR4Xj61j8jP27Dug95CbwE0O5TwY0r0HVvEie7VLgfMOvZo_owyD56HVA_1egEdsJKbFL2fyQ69wgjyze$
>
> thanks,
>
> Amanda Baber
> IANA Operations Manager
>
> On Tue Jan 16 14:34:16 2024, [e-mail] wrote:
>> The following errata report has been verified 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!NSVo-7pntazpR4Xj61j8jP27Dug95CbwE0O5TwY0r0HVvEie7VLgfMOvZo_owyD56HVA_1egEdsJKbFL2fyQ61YIG-LM$
>>
>> --------------------------------------
>> Status: Verified
>> Type: Editorial
>>
>> Reported by: Tobias Subklewe <[e-mail]>
>> Date Reported: 2023-02-04
>> Verified by: Francesca Palombini (IESG)
>>
>> 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.
>>
>> --------------------------------------
>> 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

--- Begin Message ---

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 <https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc2445*section-4.3.9__;Iw!!ACWV5N9M2RV99hQ!NnpEFnJVegpo2sx4ecXTCP5_qy1qWtlUrbzcHb5Nkx_oegMiOQc3O1-4ng87YTv5KT0sCMOHvThE2cK0lhz6JXVKUIY$>
>> 
>> 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] <mailto:[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] <mailto:[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
>> 

--- End Message ---