Re: [calsify] Roadmap for JsCalendarbis, iTip and iMip

Michael Douglass <mikeadouglass@gmail.com> Thu, 28 July 2022 15:51 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 95327C18571D for <calsify@ietfa.amsl.com>; Thu, 28 Jul 2022 08:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 t8QRPzfzKpqq for <calsify@ietfa.amsl.com>; Thu, 28 Jul 2022 08:51:50 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 01519C136304 for <calsify@ietf.org>; Thu, 28 Jul 2022 08:51:49 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id e5so1412036qts.1 for <calsify@ietf.org>; Thu, 28 Jul 2022 08:51:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc; bh=1FriFgAvTAEKU+WKNLNmjipBtXJLoIbXeTDdXf7FM/Y=; b=BdtjMKuG4zMd27EKnGmgElxOrm2WAmGAn2DpqBzU45a53HGt2EReeuBXf4K7y7uMeI 2Yqe2co/WYqokiGl2KNwl8wlcbudRdDW6GVtCGOKNwGXMh+8Iu0j55mH9PJUPYkv8k6X x5a1abPkUhMcWS4RT5HpN0+nrmWjzwHilOrOzRG+Aw4z1UUIl0nJzTUxbdnBVkoLjj7Z GgK5NVtBOE36O7eBA0crV5mi0ituS16Kfa0n1II1e8rtt21lHmNrTyv8uYv27qrbq8nO u0aDg80WpWskekkcyGFb5mcbFAd5NEcStAnh6NMpmKl9r6qjL5K3vOt9+V2Fw6RdM/sY CmgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc; bh=1FriFgAvTAEKU+WKNLNmjipBtXJLoIbXeTDdXf7FM/Y=; b=xj4ZKXami3wfSRjspB39jLVMUVAR0xJLXQ8+XJEAFTe+D51Z92WNRTRtox9z4six6Q J+EZXuVjxhE6qWLVSsXh8ukK5aI1q/CX/RQSC41L9Loew+ToIMdL1UQFPorO3j/tCKhi hIOJMo2ZkWz+n/6GiMzugRMRZZZE7rpEQmYvQySy641gERsbFRI0BrCQpC5C3IJGyq3b XxR4pbUYVJhslUMUHFabmDNasOwN43rZttfjfJOjXWqKjlVpRmLIMfxRcdbGP5NKEqg4 GMub3Z2nXgROIy5AFFmmQOYWQGFXkgVTlyyqvJnGNgHsjcun2nJonaJsonwH4gBFY2Tq +oQA==
X-Gm-Message-State: AJIora+0o8+l6U/tvSoZAg7w+C4ngiN1hQRuf7xjxDC2HYgfDT8Pd8Mc oQqmaJGGd6WV7lcgTMkqOJTuwSwJ0rM=
X-Google-Smtp-Source: AGRyM1vSKYUDrUVbtNo2IWwi+HT3kZx4EXQjTToz2uFEB8fAoEiUt0xHn3YWNqsf0q+Bp6vy1fQR8Q==
X-Received: by 2002:a05:622a:1a85:b0:31e:f623:7b39 with SMTP id s5-20020a05622a1a8500b0031ef6237b39mr23349138qtc.151.1659023509008; Thu, 28 Jul 2022 08:51:49 -0700 (PDT)
Received: from [192.168.1.150] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id h16-20020a05620a245000b006aedb35d8a1sm750367qkn.74.2022.07.28.08.51.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 Jul 2022 08:51:48 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------DdsqrgWOtZSb5ouPNtXY3Gr5"
Message-ID: <a7e6ab6f-6f62-954f-fce2-69b3d2e3487f@gmail.com>
Date: Thu, 28 Jul 2022 11:51:47 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Content-Language: en-US
To: Robert Stepanek <rsto@fastmailteam.com>, calsify@ietf.org
References: <838c49d7-da82-6a3e-2b52-fd605ec4e57d@gmail.com> <6726c44b-b897-46fe-b2a1-b56e76ce7326@dogfoodapp.fastmail.com> <a982e12e-bcab-4650-8f38-e22e079ae187@www.fastmail.com> <5ae1db65-7339-4ea1-8c80-855d18be0f19@dogfood.fastmail.com> <bd02e797-b165-41ae-ae41-e5889dcd2614@www.fastmail.com> <4eb8c354-ebd5-47be-8c91-4b660d51d0b3@www.fastmail.com>
From: Michael Douglass <mikeadouglass@gmail.com>
In-Reply-To: <4eb8c354-ebd5-47be-8c91-4b660d51d0b3@www.fastmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/MJS5IxwWNq1EnWoM4FF5OTh6--w>
Subject: Re: [calsify] Roadmap for JsCalendarbis, iTip and iMip
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: Thu, 28 Jul 2022 15:51:50 -0000

On 7/28/22 10:11, Robert Stepanek wrote:
> On Thu, Jul 7, 2022, at 4:52 AM, Robert Stepanek wrote:
>> The deadline for draft submissions for IETF 114 is getting very close 
>> now: Do we have consensus on any of the discussed options (keep 
>> as-is, keep multi-valued but use |itip|, change to single-valued 
>> property)? If so, I will try to update the jscalendarbis draft 
>> accordingly before the deadline. If not, we will continue the 
>> discussion here and during the calext session.
>
> We did not reach unequivocal consensus, but let's be realistic: there 
> is no point in a calendaring standard if there is no consensus how to 
> do scheduling with it.
>
> I say that any scheduling method, either as part of jscalendarbis or 
> as an extension, must clearly describe:
>
>   * How scheduling is done such that multiple systems can interoperate.
>   * How it relates to the already defined scheduling methods that are
>     in use (that being iTIP and iMIP until further scheduling
>     standards are defined).
>   * How it maps from and to iCalendar (as required by the charter), or
>     define why this is not necessary.
>   * Once consensus has been reached to add the scheduling method,
>     provide the necessary RFC documents and updates to existing standards.
>
> I understood the majority of people in yesterday's meeting to agree 
> that the |replyTo| and |sendTo| properties should stay multi-valued, 
> but the only defined scheduling method to be the |itip| method for 
> now. This is 100% compatible with  ticks all checkboxes for the 
> requirements outlined above, except for the last bullet, and for the 
> latter I volunteer to write the relevant document updates if someone 
> is willing to co-author.

I think I volunteered to try to do iTip. I've always found it an 
unwieldy document. Most of those large tables are unnecessary and I 
think a clearer document might help.


>
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify