Re: [calsify] PROPOSAL: recharter CALEXT and bring contact work and maintenance in charter
Michael Douglass <mikeadouglass@gmail.com> Thu, 18 November 2021 06:08 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 931CE3A041D for <calsify@ietfa.amsl.com>; Wed, 17 Nov 2021 22:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level:
X-Spam-Status: No, score=-3.949 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=-1.852, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ukyz8_i8PYNR for <calsify@ietfa.amsl.com>; Wed, 17 Nov 2021 22:08:44 -0800 (PST)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D174D3A043A for <calsify@ietf.org>; Wed, 17 Nov 2021 22:08:43 -0800 (PST)
Received: by mail-qk1-x732.google.com with SMTP id de30so5298354qkb.0 for <calsify@ietf.org>; Wed, 17 Nov 2021 22:08:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to; bh=SByEbkU6KuDFUJT4z3mBBzmjqoBwhkZ6BK0ajWvfpHk=; b=o08hXRReNpiP4VBgxedj1gNUmt+dLPWq42PQ6Cid1Qvp75VP9LFItA/LA3Ku2TRisE c/aDQXc+78CEWPQ9HpuY5bELfJo2sUHgPefhurqJJYOOKdxrOnNE4BooXlINXjQ6XB93 auCiDX3FLMa1r5RE1jDHWi+E6XzeGCu26SowYsTSgoiPiJpkPlc9AdTDaUmcWDYmjoR4 027g2VhhzEZIThK2OUwOwGzAjdBiQn73X6lY2OkJVEkVF+zkRYlTx482wVQcxEPR5rG5 pR0wKYTLIlhA9cPlEb5xoTvlsagSiafqxka6C4NMwDWRJuI5Rebbqojv0E8+vDKnchZQ u2Fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to; bh=SByEbkU6KuDFUJT4z3mBBzmjqoBwhkZ6BK0ajWvfpHk=; b=xffzVoVGd5m+4cFly+S6b8lZG228+wgLxc2AXzWqDdtYjdf9VAdVkOEh4SuMfF6Xm3 vq3sf5cAUV/e01rSAvP7a7wybUvkBAiK4i3dbqdUd5JZfxtlm/w6waCUuon7+x3doTuX fdVVGSSS5YVUMWo1m/IYiltTuGaEUOC32N78mh7o4cxt9uBUBHOPSMmcdDSHCvt2s2jP xnHkH36THYcZxF83GQNRlfubmJ46+XVKOxrKMBL1tEcKFIdqcoGmq1BL2fZTu547n+U7 kFFUXLklzDu/IZzrq5OOLjGni2N60PpU1WsFgUDc1KaxZLfTBaXwaB4OTxKt3hAU/hc9 yYpg==
X-Gm-Message-State: AOAM533ry4RjaMFz0O/mgbmg5Fdmko6gyRl2ZKqfKrdWVqbISYvbuElV pJ8dMfNoz4QQ/zfGXg1VpRIEN096mDo=
X-Google-Smtp-Source: ABdhPJwwGt1u3hi/OnOWua55W3ZDYLH5uAWBJxFTKMlWm50NQg0dAahdc8IJ5NWoK3hAbEkh/Zpm4w==
X-Received: by 2002:a05:620a:298a:: with SMTP id r10mr18542563qkp.381.1637215721618; Wed, 17 Nov 2021 22:08:41 -0800 (PST)
Received: from [192.168.1.149] (cpe-74-70-70-237.nycap.res.rr.com. [74.70.70.237]) by smtp.googlemail.com with ESMTPSA id 73sm1136681qkm.94.2021.11.17.22.08.40 for <calsify@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 Nov 2021 22:08:41 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------dMwoYJKwKTorMhcVgiDIQuqh"
Message-ID: <72827edc-3640-b046-1cde-5efa8244729b@gmail.com>
Date: Thu, 18 Nov 2021 01:08:40 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.0
Content-Language: en-US
To: calsify@ietf.org
References: <283e06dd-9bbe-41af-b9bf-9326ed91c131@dogfood.fastmail.com>
From: Michael Douglass <mikeadouglass@gmail.com>
In-Reply-To: <283e06dd-9bbe-41af-b9bf-9326ed91c131@dogfood.fastmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/QmMVb8N6lLBJNNNwnWoKW-sY4t0>
Subject: Re: [calsify] PROPOSAL: recharter CALEXT and bring contact work and maintenance in charter
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Nov 2021 06:08:49 -0000
I agree with this proposal - and the mailing list approach suggested by Alexey On 11/17/21 05:13, Bron Gondwana wrote: > Hi - both JMAP and CALEXT working groups, > > I'm emailing both groups, because this proposal includes taking the > current jscontact work and moving it from JMAP to CALEXT where it will > be maintained on an ongoing basis - along with the icalendar, vcard > and jscalendar specs as well as the caldav and carddav protocols. > This new charter anticipates a long lived maintenance working group > for all the contacts, calendars, and related data formats. The > reasons for taking on the VCARD and CardDAV work are pretty obvious: > > * Both have *DAV protocols. > * Both have similar syntax model (VOBJECT) > * Could move maintenance of JSContact over from JMAP where it > doesn’t really fit either. > * Frequently implemented together. > * Both handled by CalConnect as well, maintain the relationship. > * Better than starting another group for contacts! We already have > enough groups. > > We also propose to close the 'calsify' mailing list and move all the > subscribers to a list called 'calext@ietf.org' so that the mailing > list name matches the working group name, because this is an ongoing > source of confusion to new people. > > We have deliberately left the "out of scope" a little loose so that > things like tasks or even file synchronization (which is needed for > managed attachments in calendars among other things) might come into > scope - so long as it's related to the documents that this group > currently maintains and isn't better suited to another existing group, > then it's a candidate to be worked on in CALEXT. That's hopefully a > good balance between too much charter lawyering for things we should > be working on, while not opening the door to do arbitrary stuff here. > > The CALEXT chairs and our two ADs (Francesca and Murray) would love > any feedback you have on this charter text over the next couple of > weeks before we formally propose this charter to the IESG. *Please > send feedback by December 1st (earlier is better so we can iterate)* > > Thanks, > > Bron. > > https://notes.ietf.org/calext-proposed-charter-2021 - pasted below > > > Charter Text: > > The CALEXT working group is chartered to maintain and extend the > specifications for formats and protocols related to calendaring and > contacts within the IETF, starting from the basis of: > > * CalDAV (RFC 4791) > * iCalendar (RFC 5545) > * iTIP (RFC 5546) > * VCARD (RFC 6350) > * CardDAV (RFC 6352) > * JSCalendar (RFC 8984) > * JSContact (draft-ietf-jmap-jscontact) > > and the many existing extensions and companion documents to these. > > This working group is envisaged to be long-running, and deal with a > steady slow flow of changes. Experience has shown that these > specifications are still seeing significant need for updates, as new > use-cases are identified and user requirements change. > > > This working group will do the following: > > * maintain existing standards and proposed standards, processing > errata and refreshing them as required > * evaluate and develop extensions to the existing standards to > provide for new use-cases where there is demand > * publish informative documents describing existing implementations > of non-standard extensions, where vendors have already shipped an > implementation and with which our protocols will need to interoperate > > > The working group will work under the following parameters: > > * The extensions developed are expected to be backwards-compatible > with the existing standards. Incompatibilities must be identified, > minimized, and justified. > * Any extensions to icalendar or jscalendar must include a > representation in both formats, and define a robust mapping > between them. > * Any extensions to vcard or jscontact must include a representation > in both formats, and define a robust mapping between them. > * All calendar extensions must examine their impact on the iTIP > protocol (RFC 5546), and define any necessary extensions to iTIP > to accommodate such impact. > > > The working group will maintain relationships with other working > groups: > > * HTTPBIS and HTTPAPI: when extending the CalDAV or CardDAV > protocols to ensure that changes are consistent with good http > practices. > * JMAP: when making updates to JSCalendar and JSContact to ensure > that the changes are compatible with the JMAP methods for managing > data in these formats. > * EXTRA, DMARC and EMAILCORE: for changes related to iTIP delivery > via email. > * Other working groups as appropriate, when their work interacts > with ours. > > > The following are out of scope for the working group: > > * Any attempt to develop non-Gregorian calendar systems/calculations. > * Work which is in scope for any other ART area working group, and > better suited to that group. > * Work which is unrelated to anything that this group is currently > maintaining. > > > -- > Bron Gondwana, CEO, Fastmail Pty Ltd > brong@fastmailteam.com > > > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify
- [calsify] PROPOSAL: recharter CALEXT and bring co… Bron Gondwana
- Re: [calsify] PROPOSAL: recharter CALEXT and brin… Alexey Melnikov
- Re: [calsify] PROPOSAL: recharter CALEXT and brin… Alexey Melnikov
- Re: [calsify] PROPOSAL: recharter CALEXT and brin… Ken Murchison
- Re: [calsify] PROPOSAL: recharter CALEXT and brin… Daniel Migault
- Re: [calsify] PROPOSAL: recharter CALEXT and brin… Bron Gondwana
- Re: [calsify] PROPOSAL: recharter CALEXT and brin… Michael Douglass
- Re: [calsify] PROPOSAL: recharter CALEXT and brin… Ronald Tse
- Re: [calsify] PROPOSAL: recharter CALEXT and brin… Bron Gondwana