Re: [calsify] Request for preliminary review of JSContact property registrations

Robert Stepanek <rsto@fastmailteam.com> Tue, 27 February 2024 15:06 UTC

Return-Path: <rsto@fastmailteam.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 C65D8C15106A for <calsify@ietfa.amsl.com>; Tue, 27 Feb 2024 07:06:27 -0800 (PST)
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, HTML_MESSAGE=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_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=fastmailteam.com header.b="L6jC4Zis"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="PjvgHZ2i"
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 UD8xD-QQA_t0 for <calsify@ietfa.amsl.com>; Tue, 27 Feb 2024 07:06:23 -0800 (PST)
Received: from fout4-smtp.messagingengine.com (fout4-smtp.messagingengine.com [103.168.172.147]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 6FC3BC14F736 for <calsify@ietf.org>; Tue, 27 Feb 2024 07:06:23 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailfout.nyi.internal (Postfix) with ESMTP id 013CF13800D3 for <calsify@ietf.org>; Tue, 27 Feb 2024 10:06:22 -0500 (EST)
Received: from imap44 ([10.202.2.94]) by compute5.internal (MEProxy); Tue, 27 Feb 2024 10:06:22 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=cc:content-type:content-type:date:date:from :from:in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to; s=fm2; t=1709046381; x= 1709132781; bh=Sch8FgAETPuwkVNP/nTdHfbdmmySe826zqUAr6KPsy8=; b=L 6jC4ZisovUAE4Yi0o2KS8If46dJK8t5KYINtewG5RMtNXea8vARCWZzGt5lda36D QrMael8ngOVeicD8B/B2ldly7Hu072aIJxJ5WIRNf5l/D5F9FZPSKBnRSwib7M7P manb3TLIDOG/5WRdy8D12WcqTkZVGQiXwtoX57+53J9N+/qZt3j3t/xVDnNyYg6A rAWA/1T2N9DaprHegldPwSbcV4u+aDBO99pAeoP6meNh/Et7d7UiYsg5pEJ2CQRU HOhsffym1ri5QMs9EBTQliRgJk/roD4awO4Uns67EEflUGfvhE9lXh8aFzLhn2+i gJ11XsFLgEVlsQ612ERdQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1709046381; x=1709132781; bh=Sch8FgAETPuwkVNP/nTdHfbdmmyS e826zqUAr6KPsy8=; b=PjvgHZ2iCfFbey9qrQSFrLngIiUaxNuQBw0Fm9+pqWfW APN7NYw9opyQVSA7td7has06pgzPlnuTGVLhckrxKXEe8U5VHQjBCTyHorD441Js aO1tCG+NWMcET4gqKfQFSg6uJSn6Y+mOcKmI6xWueTFyLQ9yKlZH1N8GwW88Qs1n aP5tn0fRwQbCb4JGfM1XNmyYf5iGc7cIyArL/CYEnEUrpkhFg1MnO+sqGROmJzHS OUeASrrfUUGG2hTRAN6QCOfImYfasSTgxN0mW0iRN40CjWfUkDzHju9OjPLjiCKq 0wiypTgw2IySvX3G2xFjGdPSCDwiBQZCVVxbLSsa2A==
X-ME-Sender: <xms:bfrdZfhUdrjMPuKokyCvR9AmeOvWdTJBBQ9xJ_YSou-O5FArEDvlxw> <xme:bfrdZcAZT4duln_OQTVI2ORGTNGBOS6Hj4dKDaeMJfKPrsaPfertIz8dd2qT_J95t r_T_aoWV6qgvg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrgeehgdegkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreertdenucfhrhhomhepfdftohgsvghrthcuufhtvghprghnvghkfdcuoehrshhtohes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeethfffffekue ekveelleeglefhgeefjeeugeetkeejkefgtdfhheehvdehhedvhfenucffohhmrghinhep ihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomheprhhsthhosehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:bfrdZfHOMOK9CSpdEyGWQfHuXX99O-Q8ClgNgy2ys-31wZYxWUFxRQ> <xmx:bfrdZcQOxDGC141AEiT8Chb0srV8GtACd2uOCNeDVqioO3uV6cFz4Q> <xmx:bfrdZcwlsibl928XDnnqYsAY5nbVE9kAroiHju2Jh-HJ-6xWWwiI5w> <xmx:bfrdZZvEtPqohGQHuIW6Vo5MG33Xz1GP2B1CbekrsbCvQM19fDghew>
Feedback-ID: ia5d944da:Fastmail
Received: by mailuser.nyi.internal (Postfix, from userid 501) id A39EF36A0079; Tue, 27 Feb 2024 10:06:21 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.11.0-alpha0-182-gaab6630818-fm-20240222.002-gaab66308
MIME-Version: 1.0
Message-Id: <11572858-a721-4a02-a2a0-3cb5766405c7@app.fastmail.com>
In-Reply-To: <f090ffad-18ca-4ad1-8483-bae0d9117f69@dogfoodapp.fastmail.com>
References: <f090ffad-18ca-4ad1-8483-bae0d9117f69@dogfoodapp.fastmail.com>
Date: Tue, 27 Feb 2024 16:06:01 +0100
From: Robert Stepanek <rsto@fastmailteam.com>
To: calsify@ietf.org
Content-Type: multipart/alternative; boundary="9b424016fefa4adc90c1b97ad22dc51c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/EebYO1IbOMJfLNracKkpFUJatfU>
Subject: Re: [calsify] Request for preliminary review of JSContact property registrations
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, 27 Feb 2024 15:06:27 -0000

Hi Neil,

Thanks for submitting this. I see that we haven't registered these properties for JSCalendar either, so whatever we now decide for JSContact should preferably be done for JSCalendar, too.

Reserving the "id" property name is a very good choice, and irrespective if that name gets used for JMAP it's likely we'll reserve that name anyway for arbitrary protocols to use.

The "addressBookIds" and "blobId" property names seem rather too specific for JMAP to reserve them in the standard namespace. Alternatives could be (same applies for blobId):
 • "jmapAddressBookIds" in the standard name space
 • "ietf.org:rfcXXXX:addressBookIds" as vendor-extension, where XXXX stands for the RFC number of the JMAP Contacts document. The "ietf.org" vendor prefix got reserved in the JSContact document for this purpose already.
 • "jmap.io:addressBookIds" as vendor-extension
The latter two wouldn't require a IANA registry at all.

What do you think?

Cheers,
Robert


On Tue, Feb 13, 2024, at 4:27 AM, Neil Jenkins wrote:
> As per Section 3.3.1 in the latest draft of the JSContact spec <https://datatracker.ietf.org/doc/html/draft-ietf-calext-jscontact-16#section-3.3.1>, I'm requesting preliminary review of the following registrations in the JMAP Contacts draft <https://www.ietf.org/archive/id/draft-ietf-jmap-contacts-03.html#name-jscontact-property-registra>:
> 
> *6.2.1. id*
> 
> Property Name: id
> Property Type: Id
> Property Context: Card
> Intended Use: Reserved
> Since Version: 1.0
> Change Controller: IETF
> 
> *6.2.2. addressBookIds*
> 
> Property Name: addressBookIds
> Property Type: Id
> Property Context: Card
> Intended Use: Reserved
> Since Version: 1.0
> Change Controller: IETF
> 
> *6.2.3. blobId*
> 
> Property Name: blobId
> Property Type: Id
> Property Context: Media
> Intended Use: Reserved
> Since Version: 1.0
> Change Controller: IETF
> 
> -----
> 
> Please reply with any comments or feedback
> 
> Cheers,
> Neil.
> _______________________________________________
> calsify mailing list
> calsify@ietf.org
> https://www.ietf.org/mailman/listinfo/calsify
>