Re: [Extra] [EXT] Benjamin Kaduk's No Objection on draft-ietf-extra-imap-fetch-preview-09: (with COMMENT)

Benjamin Kaduk <kaduk@mit.edu> Wed, 23 September 2020 15:37 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB2A3A1234; Wed, 23 Sep 2020 08:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 R0Bt7ki5UU2p; Wed, 23 Sep 2020 08:37:25 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5598C3A1203; Wed, 23 Sep 2020 08:36:53 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 08NFahBk026586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 23 Sep 2020 11:36:45 -0400
Date: Wed, 23 Sep 2020 08:36:42 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Barry Leiba <barryleiba@computer.org>
Cc: Michael Slusarz <michael.slusarz=40open-xchange.com@dmarc.ietf.org>, Benjamin Kaduk via Datatracker <noreply@ietf.org>, The IESG <iesg@ietf.org>, extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>, extra-chairs@ietf.org, draft-ietf-extra-imap-fetch-preview@ietf.org
Message-ID: <20200923153642.GF89563@kduck.mit.edu>
References: <160080490190.9778.18063295243922914906@ietfa.amsl.com> <954798175.17578.1600838053373@appsuite.open-xchange.com> <CALaySJJUxM5dQeF0WzsTSJkPYaFVXikmocN2DUuF9ykCSnYOaw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CALaySJJUxM5dQeF0WzsTSJkPYaFVXikmocN2DUuF9ykCSnYOaw@mail.gmail.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/2-pNFrtpF93mbZiC-odUgAZ6sVQ>
Subject: Re: [Extra] [EXT] Benjamin Kaduk's No Objection on draft-ietf-extra-imap-fetch-preview-09: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Sep 2020 15:37:31 -0000

On Wed, Sep 23, 2020 at 07:36:31AM -0400, Barry Leiba wrote:
> > > Section 8
> > >
> > > Does it go without saying that a given user should only have access to
> > > preview content for messages that it has access to the full content of?
> >
> > The base IMAP4rev1 document doesn't even have this kind of warning.
> >  If we think that this is necessary here then we should probably also
> > push this idea to Alexey and Barry as they are working on the new IMAP
> > revision, since this warning would apply to message data in general.
> >
> > I don't believe this draft fundamentally changes anything in IMAP.  If
> > you can access a mail in a mailbox, you can access its full body.
> >  This extension just provides an alternative view of that body data,
> > so it doesn't provide a novel way of accessing data.
> 
> Put in terms of Ben's phrasing: Yes, it goes without saying.  There's
> no partial access in IMAP: if you can do any FETCH command on a
> message, you can do all FETCH commands on a message.  I don't think
> anything further needs to be said.  We can consider whether it's worth
> being more wordy about that in the imap4rev2 draft, which the IESG
> should see fairly soon.  (I don't think more is needed there either,
> but we can chat about that.)

Agreed, and sounds good.  ("You took the words right out of my mouth.")

Thanks,

Ben