IETF Logo Mail Archive

Re: [imapext] IMAP Capability Registry and RFC 5524: URLFETCH=BINARY vs URLAUTH=BINARY

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 19 May 2020 15:49 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBF083A097B for <imapext@ietfa.amsl.com>; Tue, 19 May 2020 08:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 (1024-bit key) header.d=isode.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 dDwMnx0Yxz7X for <imapext@ietfa.amsl.com>; Tue, 19 May 2020 08:49:14 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 424633A09E7 for <imapext@ietf.org>; Tue, 19 May 2020 08:49:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1589903340; d=isode.com; s=june2016; i=@isode.com; bh=+S23i37LilFcyr5BHah9zJv9OZmORiW/yZw0YFx7jeI=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=WpHWKt8mQSENfz/Qt7OPvl9hhTXF3o43J3X48dLhbptijkVU3gDGDuItWizUbN0d9DakXI iaz22ikTIpzRzvrBC80M4UVaz38d+IHrIqiuuBUHS25ebF6db3wcyYauHTwldnT0jcuD33 GrH+FXRDAxv9lCPjIB4rjZvXrjtSIGg=;
Received: from [172.27.249.29] (connect.isode.net [172.20.0.72]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <XsP=6wBqwQjY@waldorf.isode.com>; Tue, 19 May 2020 16:49:00 +0100
To: Дилян Палаузов <dilyan.palauzov@aegee.org>, Dave Cridland <dave@cridland.net>
References: <4c6ed7902d8a21b14f59864881096f44f6b3bd24.camel@aegee.org>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Cc: imapext@ietf.org
Message-ID: <d3c1e1ba-9917-c7b0-085b-a658a5f36615@isode.com>
Date: Tue, 19 May 2020 16:48:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
In-Reply-To: <4c6ed7902d8a21b14f59864881096f44f6b3bd24.camel@aegee.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------6005C6505DCB80810C267D8F"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/mGoHV5m8zdlXoQ8wF5psBWVd4WA>
Subject: Re: [imapext] IMAP Capability Registry and RFC 5524: URLFETCH=BINARY vs URLAUTH=BINARY
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 May 2020 15:49:17 -0000

Hi Дилян,

On 17/05/2020 15:55, Дилян Палаузов wrote:
> Hello,
>
> The Internet Message Access Protocol (IMAP) Capabilities Registry at
> https://www.iana.org/assignments/imap-capabilities/imap-capabilities.xhtml
> says:
>
> URLFETCH=BINARY 	[RFC5524]
>
> and RFC 5524, https://tools.ietf.org/html/rfc5524 says:
>
>
> 3.  Extended URLFETCH
>
>     This extension is available in any IMAP server implementation that
>     includes URLAUTH=BINARY within its capability string.
>
> 5. Formal Syntax
>
>     capability       =/ "URLAUTH=BINARY"
>
> 6.  IANA Considerations
>
>     This document defines the URLFETCH=BINARY IMAP capability.  IANA has
>     added it to the registry accordingly.
>
> My reading is, that the URLAUTH=BINARY and URLFETCH=BINARY capabilities
> mean the same.
I think one of these is a typo. I suspect "URLFETCH=BINARY" should be 
"URLAUTH=BINARY", because "URLAUTH" is already registered as a 
Capability. Dave?
> Please comment within a month on the following proposal for erratum:
>
> New text:
>
> 3.  Extended URLFETCH
>
>     This extension is available in any IMAP server implementation that
>     includes URLAUTH=BINARY or URLFETCH=BINARY within its capability
>     string.
>
> 5.  Formal Syntax
>
>   capability       =/ "URLAUTH=BINARY" / "URLFETCH=BINARY"
>
>        ; Command parameters; see Section 3.1
>
> 6.  IANA Considerations
>
>     This document defines the URLFETCH=BINARY and the URLAUTH=BINARY
> IMAP capabilities.  Both capabilities mean the same. IANA has added
> URLFETCH=BINARY and will add URLAUTH=BINARY to the registry
> accordingly.

If it is a typo, I would edit your suggestion to recommend one or 
another, not both.

Best Regards,

Alexey

> I do not insist to do the wording, anybody can take this over.
>
> If there is knowledge, that all implementations have consolidated on a
> single capability wording, then the erratum can get smaller.
>
> Greetings
>    Дилян
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext

v2.26.15 | Report a Bug | By Email | System Status