Re: [calsify] RFC7986 and EMAIL parameter

Neil Jenkins <neilj@fastmailteam.com> Fri, 19 February 2021 09:18 UTC

Return-Path: <neilj@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 6A6BF3A129F for <calsify@ietfa.amsl.com>; Fri, 19 Feb 2021 01:18:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=fastmailteam.com header.b=ewDlvy2A; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=obsWAOps
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 vdZxD8_D0-in for <calsify@ietfa.amsl.com>; Fri, 19 Feb 2021 01:18:53 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77B0B3A12D1 for <calsify@ietf.org>; Fri, 19 Feb 2021 01:18:53 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 648245C00DE; Fri, 19 Feb 2021 04:18:51 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute3.internal (MEProxy); Fri, 19 Feb 2021 04:18:51 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm2; bh=gbaq7pI qTXQzmyvac0i3+3MOqpA0A4xziX5wqGw9yhE=; b=ewDlvy2A9XK0yPEmRoE6K6V /OqkdClRkbIAirjKOfDaHyDQ0HsG0LuCEPqMN4veWtXmFO4gnDchM3MNRp/Ue3vI wiKqYrb61pFGZ0GvTXavsGzLgsyE8gu3BsLeJ3i+HqgbSq+KFRNGx0HdSZ1eVOA4 tgVMVnmkSxC8VuLQOeBeh6toOI8+3Pv4T+6eMTjamjp4EtCzK7RlU6xMISn/ev7a YInRChWKsiaIM5uIYCQ3+KGg/7lq9T8TZafGZ6s37WJIMBYRbZTiNxKpRwORbPye nWJKZudc/mWFT2I4QZAA7L08Nb6pmVZgWjyLnKMPOarNm5q6MUMbZt4diMo+q0Q= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=gbaq7p IqTXQzmyvac0i3+3MOqpA0A4xziX5wqGw9yhE=; b=obsWAOpsnqGLXvSlFDhWkN RhilZ0rL6ZfQ/odkddEs5tel9vmZpGiGpfoJothRirnVf9lFeHbiNpjjYM01rgcO JCznD8lRZ/9hg8zr7b3ZyqWX6NC6fpi5tJFJgFwEMmQobFmrsBqpspXdHwZ0Qk4E vjJ5LSwao12SGcMbZPpz6KGKQMXahczMSOlYU3XOSG+x1WUNI1iPgk43lhm8A/58 MoBQ5TVRd2nmCOj7eZ7q8lh44wY3QrpuPglTWRAcH5lIEgUxJ+TNr+b3xPwmT/W8 TwNu9ICKTFePpFAra2CZo9yKIlBVhtRD7fI+6eqIzUkLkoBWIQlBeJASsL4dEFbQ ==
X-ME-Sender: <xms:eoIvYPqcj3WHVW0yot5DZOR2t3qX2rAh67PX-sArlHRFKLE0_pZh9A> <xme:eoIvYJqOnN-suvBajSIYIo8H2CpW1TMlDlr-NdT-YJ7ryiamDRmstTxHxFD2ky-_W Z_oLe34DNxhHg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjeeigddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerredtnecuhfhrohhmpedfpfgvihhl ucflvghnkhhinhhsfdcuoehnvghilhhjsehfrghsthhmrghilhhtvggrmhdrtghomheqne cuggftrfgrthhtvghrnhepvedvtedvudelkefhgefhteeftedtlefhheefveffveelkedu tdduffeiveejvefhnecuvehluhhsthgvrhfuihiivgepudenucfrrghrrghmpehmrghilh hfrhhomhepnhgvihhljhesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:eoIvYMNrH9d8c8xdXWComKX4yLnFllrrX0B5HIyslybwHKwaPM9foQ> <xmx:eoIvYC6A2YkWfHDAocluFqkkzdRVawMR_iXlGpz_3IChWHw4On3J4Q> <xmx:eoIvYO6rcGXULrIfk5aQngtq8c23KSb6mYe5n-RNztnKbPMqIL-Esg> <xmx:e4IvYDgedxcn5leVIUQwos4C6ha9VK9Ww2xnoXjKEiBWpw9rjuqEEA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4303236005C; Fri, 19 Feb 2021 04:18:50 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-141-gf094924a34-fm-20210210.001-gf094924a
Mime-Version: 1.0
Message-Id: <e78529f8-22b4-49e3-8707-ee4ecfefb0ca@dogfood.fastmail.com>
In-Reply-To: <4955c116-ed6c-c06a-8dd4-c77aff9df349@gmail.com>
References: <e1e7222e-8c6e-40b3-a8cf-a45982acb00c@dogfood.fastmail.com> <f7a8cc4c-6ed7-4fff-a719-ac577ee407ab@cyrus.local> <4955c116-ed6c-c06a-8dd4-c77aff9df349@gmail.com>
Date: Fri, 19 Feb 2021 20:18:49 +1100
From: "Neil Jenkins" <neilj@fastmailteam.com>
To: "Michael Douglass" <mikeadouglass@gmail.com>, "Cyrus Daboo" <cyrus@daboo.name>, calsify@ietf.org
Content-Type: multipart/alternative; boundary=bb66e057f1dd4a38a8a8976f632076f2
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/N9ldc8tDoHwr-R0JsOtzIaKAO10>
Subject: Re: [calsify] RFC7986 and EMAIL parameter
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Fri, 19 Feb 2021 09:18:55 -0000

On Fri, 19 Feb 2021, at 15:01, Michael Douglass wrote:
> I'd personally prefer that we don't get too specific about the method. 
> Even if it looks like a regular recognizable email we might choose not 
> to use iMip.

I'm not quite sure what you mean by this. The keys are advertising what methods you support. You definitely need this, because if you are sending an invitation across federated systems, the other side has no other way to know what protocols you support for exchanging scheduling messages. If you're supplying an email that's not for iMIP, you would not include an `imip` property in the participant's `sendTo`; you would just put it in the `email` property, as discussed earlier in the thread.

Neil.