Re: [calsify] [Technical Errata Reported] RFC9073 (7380)

Michael Douglass <mikeadouglass@gmail.com> Tue, 07 November 2023 17:36 UTC

Return-Path: <mikeadouglass@gmail.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 08553C18FCBD for <calsify@ietfa.amsl.com>; Tue, 7 Nov 2023 09:36:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBKpIhsZYJq2 for <calsify@ietfa.amsl.com>; Tue, 7 Nov 2023 09:36:09 -0800 (PST)
Received: from mail-qv1-xf33.google.com (mail-qv1-xf33.google.com [IPv6:2607:f8b0:4864:20::f33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F235C18FCAF for <calsify@ietf.org>; Tue, 7 Nov 2023 09:36:09 -0800 (PST)
Received: by mail-qv1-xf33.google.com with SMTP id 6a1803df08f44-66d0ceba445so33521576d6.0 for <calsify@ietf.org>; Tue, 07 Nov 2023 09:36:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699378568; x=1699983368; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=bAv4USrk2c2IWajwfajRx8PuA8Ajv5UKdvszhA7bjwI=; b=WRYHSa8rrEqpI9i/RsZw+vi3dAdgv5Z1igWybqoPshsf3CByFjTn8cpyHKCnTxAHyu dJdsNbpzQh1BFbxUN8d8b1JxGVicJR1B7T6qMqfz82E8MoRxDf1NgW+qmBL0QbZ+XtOH 5dTSzvgP6bo1m6pgyY+TD8rswsRD8RRNZfEE50g/f0u2//ZpDT5U3kkt7VncBan93jWU ekUeI7VA+jRf7rpxBnCfaXYvuFbp0tGtu431V9SkWQNO1IE1tmK5RjPkDDG/8fdwJm2C vx7+L6RxNzhXQJclMAvLrjy7N57PEREaZoPYljeYTjtPLDsmX7Rf+QxhBDhj9n55I1YJ IpVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699378568; x=1699983368; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=bAv4USrk2c2IWajwfajRx8PuA8Ajv5UKdvszhA7bjwI=; b=orpP6wWTNzrOlqPJUbN7w84VzjCo0ySNb44N/un70dzpdGh3OjF0lWG0HGmy0Q5/b3 c1GGfw7EFog/phVKMzFiCiB9+2ETIutAb6Cc9h+aX9Zg1SE/I30k4XcZWH8k2mN20CgH ViLOUYJMGyTqTmp4hMu/eMFV6y100QVQhaCI1k+dtIPKBWj8Acgq6IJXKP1bS0Q2eGyf 34Luht4UG1dShYB+9CoV+EOergG9a24/kU25e48oO7vL47Ge3gOSk23D1Cwqr/HIcC9J r4t4G5NvhO0fT9WyurrotfQ1/drGJSgFt/rae80t6+rkX7bGyySePJQmFSQnufYc1GY7 iFAg==
X-Gm-Message-State: AOJu0YyGSG3qqrLp/BeeqyPj4+Ppq+/4PxTJ+fEJYuBMwPMTjIcSw+di ElLeXZL3veJiGvRDM6LCApHPgG+JTD0=
X-Google-Smtp-Source: AGHT+IH5AnjMKKqUUL6EFPKMSRwdlssGm10K33NEJlR+zisB3MPn71h1nY4cZF/GnweIau6G02WL0Q==
X-Received: by 2002:a05:6214:acb:b0:671:3893:f4df with SMTP id g11-20020a0562140acb00b006713893f4dfmr28108795qvi.10.1699378568337; Tue, 07 Nov 2023 09:36:08 -0800 (PST)
Received: from [192.168.1.192] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id k9-20020a05621414e900b006263a9e7c63sm96011qvw.104.2023.11.07.09.36.07 for <calsify@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Nov 2023 09:36:08 -0800 (PST)
Message-ID: <58f1e989-f3fc-4802-b99e-5f1bf8889aaa@gmail.com>
Date: Tue, 07 Nov 2023 12:36:05 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: calsify@ietf.org
References: <20230309094509.CE19F4C26B@rfcpa.amsl.com> <06550489-0fc7-4ad9-b693-557f032a5705@fastmail.com>
From: Michael Douglass <mikeadouglass@gmail.com>
In-Reply-To: <06550489-0fc7-4ad9-b693-557f032a5705@fastmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/HmJBbZpxrvLqn2TR3HkBr9um08s>
Subject: Re: [calsify] [Technical Errata Reported] RFC9073 (7380)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Calendaring and Scheduling Standards Simplification <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: Tue, 07 Nov 2023 17:36:14 -0000

I don't think this suggestion is consistent with the current specs. In 
9074 the DESCRIPTION is only valid for a couple of alarm types (display 
and email)

Same for 5545 but the suggestion applies to 9074

On 11/7/23 11:19, Ken Murchison wrote:
> I believe that this report should be verified, but Mike should have 
> the final call.
>
>
> On 3/9/23 4:45 AM, RFC Errata System wrote:
>> The following errata report has been submitted for RFC9073,
>> "Event Publishing Extensions to iCalendar".
>>
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid7380
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: Olaf Bartelt <obartelt@amtangee.com>
>>
>> Section: 4
>>
>> Original Text
>> -------------
>> The following changes to the syntax defined in iCalendar [RFC5545]
>>     are made here.  New elements are defined in subsequent sections.
>>
>>     ; Addition of PARTICIPANT, VLOCATION, and VRESOURCE
>>     ; as valid components
>>     eventc     = "BEGIN" ":" "VEVENT" CRLF
>>                  eventprop *alarmc *participantc *locationc *resourcec
>>                  "END" ":" "VEVENT" CRLF
>>
>>     ; Addition of properties STYLED-DESCRIPTION and STRUCTURED-DATA
>>     eventprop  =/ *styleddescription
>>                   *sdataprop
>>
>>     ; Addition of PARTICIPANT, VLOCATION, and VRESOURCE
>>     ; as valid components
>>     todoc      = "BEGIN" ":" "VTODO" CRLF
>>                  todoprop *alarmc *participantc *locationc *resourcec
>>                  "END" ":" "VTODO" CRLF
>>
>>     ; Addition of properties STYLED-DESCRIPTION and STRUCTURED-DATA
>>     todoprop =/ *styleddescription
>>                 *sdataprop
>>
>>     ; Addition of PARTICIPANT, VLOCATION, and VRESOURCE
>>     ; as valid components
>>     journalc   = "BEGIN" ":" "VJOURNAL" CRLF
>>                  jourprop *participantc *locationc *resourcec
>>                  "END" ":" "VJOURNAL" CRLF
>>
>>     ; Addition of properties STYLED-DESCRIPTION and STRUCTURED-DATA
>>     jourprop =/ *styleddescription
>>                 *sdataprop
>>
>>     ; Addition of PARTICIPANT, VLOCATION, and VRESOURCE
>>     ; as valid components
>>     freebusyc  = "BEGIN" ":" "VFREEBUSY" CRLF
>>                  fbprop *participantc *locationc *resourcec
>>                  "END" ":" "VFREEBUSY" CRLF
>>
>>     ; Addition of property STYLED-DESCRIPTION
>>     fbprop     =/ *styleddescription
>>
>> Corrected Text
>> --------------
>> The following changes to the syntax defined in iCalendar [RFC5545]
>>     are made here.  New elements are defined in subsequent sections.
>>
>>     ; Addition of PARTICIPANT, VLOCATION, and VRESOURCE
>>     ; as valid components
>>     eventc     = "BEGIN" ":" "VEVENT" CRLF
>>                  eventprop *alarmc *participantc *locationc *resourcec
>>                  "END" ":" "VEVENT" CRLF
>>
>>     ; Addition of properties STYLED-DESCRIPTION and STRUCTURED-DATA
>>     eventprop  =/ *styleddescription
>>                   *sdataprop
>>
>>     ; Addition of PARTICIPANT, VLOCATION, and VRESOURCE
>>     ; as valid components
>>     todoc      = "BEGIN" ":" "VTODO" CRLF
>>                  todoprop *alarmc *participantc *locationc *resourcec
>>                  "END" ":" "VTODO" CRLF
>>
>>     ; Addition of properties STYLED-DESCRIPTION and STRUCTURED-DATA
>>     todoprop =/ *styleddescription
>>                 *sdataprop
>>
>>     ; Addition of PARTICIPANT, VLOCATION, and VRESOURCE
>>     ; as valid components
>>     journalc   = "BEGIN" ":" "VJOURNAL" CRLF
>>                  jourprop *participantc *locationc *resourcec
>>                  "END" ":" "VJOURNAL" CRLF
>>
>>     ; Addition of properties STYLED-DESCRIPTION and STRUCTURED-DATA
>>     jourprop =/ *styleddescription
>>                 *sdataprop
>>
>>     ; Addition of PARTICIPANT, VLOCATION, and VRESOURCE
>>     ; as valid components
>>     freebusyc  = "BEGIN" ":" "VFREEBUSY" CRLF
>>                  fbprop *participantc *locationc *resourcec
>>                  "END" ":" "VFREEBUSY" CRLF
>>
>>     ; Addition of property STYLED-DESCRIPTION
>>     fbprop     =/ *styleddescription
>>
>>     ; Addition of property STYLED-DESCRIPTION
>>     alarmprop  =/ *styleddescription
>>
>> Notes
>> -----
>> The usage of STYLED-DESCRIPTION in VALARMs is mentioned in section 
>> 6.5, but not represented as an extension to the syntax in section 4.
>>
>> 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.
>>
>> --------------------------------------
>> RFC9073 (draft-ietf-calext-eventpub-extensions-19)
>> --------------------------------------
>> Title               : Event Publishing Extensions to iCalendar
>> Publication Date    : August 2021
>> Author(s)           : M. Douglass
>> Category            : PROPOSED STANDARD
>> Source              : Calendaring Extensions
>> Area                : Applications and Real-Time
>> Stream              : IETF
>> Verifying Party     : IESG
>>