Re: [Jmap] Submission

Ted Lemon <mellon@fugue.com> Fri, 21 April 2017 13:44 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3A1127077 for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 06:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=fugue-com.20150623.gappssmtp.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 Y1eWZIon4onM for <jmap@ietfa.amsl.com>; Fri, 21 Apr 2017 06:43:59 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d:c09::22f]) (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 4C5B71205F1 for <jmap@ietf.org>; Fri, 21 Apr 2017 06:43:59 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id d80so7201410qke.3 for <jmap@ietf.org>; Fri, 21 Apr 2017 06:43:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=y5jUCrwkFpnHODxuP87YQi+Hp70YGm5TI7UEzLThx+c=; b=rFD5PGhukLijqy1lk8AAP4DZ7ewTMGQA78LBLi65Uh8ylUphHGf52gRZUAonYOxfx1 ju6PWMnftl+Lt+yXaVWUBY+mH7uVvg+/I79sHSDYQOG89C1GxbxvjfvrBkbZK7vYdhZT sTiazZD31TJNOeBWkSlnFw6VrUw6Kdi5Q3D1q1ePkXFqrBH4HdepJ0BiJApu+2CbuN1b ozEfyZOSuIaZtYsA/PZpHCRR1q6r0yf7Z4SdAJz05mVOmANjzE80jZ//QKWbkzL5u0YT kfldBnFVW6hcNE+Wf8kDsN8lWAARVYSSWxXte8V9l4Iy2AE8OgFyAb5rfRDD/OdGQB+G nbYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=y5jUCrwkFpnHODxuP87YQi+Hp70YGm5TI7UEzLThx+c=; b=fVhSwRyQ3z5egD1i9mq5QSK6cW+7py6X2DpLiAt9fEGEPVE09rScWBTGRSgqiq+XZN Y23bR15mLYvPRabGXnDHmOW+Nte17S6QsjLDR/c7VrcO1rS9oGA9bxXn4Z1c7dJq+oP6 J+YczO8vt/MewVGak9QlyWjii45QVK8T4ySUh2hU1jSasCAn9yLxJDyFjEbkG9/Q8DR3 uel5tE/BAnp3PEdiL+SUsfigYNEVBxUYD8xyMOSdFTRfjWw8UVcRGCzFkzyYLU+a3bUL JrTGRtTt7ymmxOc1/ch7DIwForpm/gj288v0cooNhoibWjMOxvz3Z2Ua3OOZ79CLaUkj XSWQ==
X-Gm-Message-State: AN3rC/54vR+2t/rpDcsdNaUdrt7hsr20MIqqYYCDgfejcYOeFAmZxJG7 15llDyBqH01LGQ==
X-Received: by 10.55.77.209 with SMTP id a200mr13613892qkb.11.1492782238460; Fri, 21 Apr 2017 06:43:58 -0700 (PDT)
Received: from [10.0.30.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 36sm247459qtz.16.2017.04.21.06.43.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Apr 2017 06:43:57 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <BC098A22-2837-4316-822A-27232A896EF1@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3130D1D1-FA0E-4271-9430-149EBD674FDD"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 21 Apr 2017 09:43:56 -0400
In-Reply-To: <01QDEV2QM6XC00005O@mauve.mrochek.com>
Cc: John R Levine <johnl@taugh.com>, jmap@ietf.org, Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Ned Freed <ned.freed@mrochek.com>
References: <20170419163429.8556.qmail@ary.lan> <87d1c873cf.fsf@fifthhorseman.net> <alpine.OSX.2.20.1704191353500.43511@ary.qy> <01QDEV2QM6XC00005O@mauve.mrochek.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/yT7Zpq809TEbl-YgYvg2N-UbidY>
Subject: Re: [Jmap] Submission
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Apr 2017 13:44:01 -0000

On Apr 20, 2017, at 11:06 PM, Ned Freed <ned.freed@mrochek.com> wrote:
> More generally, the only difference between a JMAP capability tied to, say,
> a magic header and a SUBMIT extension is syntax. But if you specify things
> in a way that makes it difficult to map from one to the other, you'll pay
> the price for that as long as either protocols continue to evolve - and that's
> going to be a long time.

I think the distinction comes from whether you actually think that the SMTP submission protocol is always going to be what's behind a message submitted via JMAP.   If you think that, then it's going to look really weird to not just replicate that exact paradigm with the JMAP submission process.

However, it's not at all clear to me that that makes any general sense.   I'm sure it makes sense in some implementations, but if we were to go that route, we would essentially be nailing JMAP to SMTP submission.   There's some value to doing this in that it avoids reinventing the wheel, but there is also damage, in that the SMTP submission paradigm really isn't particularly congruent to the general paradigm of JMAP.

The point is that whichever choice we make, we are going to pay a price for it.   It's worth asking what that price is, and also asking what the advantages are to the choices we have, and then deciding on that basis.   The fact that we would pay a price for not replicating SMTP submission can definitely be taken as a given.