IETF Logo Mail Archive

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

Дилян Палаузов <dilyan.palauzov@aegee.org> Sun, 17 May 2020 14:55 UTC

Return-Path: <dilyan.palauzov@aegee.org>
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 3DBD33A07D6 for <imapext@ietfa.amsl.com>; Sun, 17 May 2020 07:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=aegee.org
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 Ih24MgJMo_Fd for <imapext@ietfa.amsl.com>; Sun, 17 May 2020 07:55:55 -0700 (PDT)
Received: from mail.aegee.org (mail.aegee.org [144.76.142.78]) (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 35AB93A07D5 for <imapext@ietf.org>; Sun, 17 May 2020 07:55:54 -0700 (PDT)
Authentication-Results: mail.aegee.org/04HEtn57422369; auth=pass (LOGIN) smtp.auth=didopalauzov
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1589727351; i=dkim+MSA-tls@aegee.org; bh=kJf7Y0aa8IM4SkdLQm6DYEBsL4PkkL5ftasdYLmUIac=; h=Subject:From:To:Date; b=dnwWblKHe/PeIXVr/jOYGk2fKh+C2cFU6FubYKab8rK0gMzy45h+jBwa+MFtijhsq uNj6uGMawlHD15I1vMLJwJuqrBvXLfWG95TdMpVFA6Aa1QjNgVigwfd0qKbpumIfLO ct312WqyTOXY2FAnlu/uvfRYwOVli/gJUZPeEieyQhiG9FGnJD0+oQQ6C9UansInYH 7dvuZfwyL0wR2daCojB7jleZHSwigiy2FX2K80p5DivHOn2wWXk3KEVezxJ6RpaO/P 5O3m6cHGjVEn+NsPOZCjydrZYQzQ8f/m7YWUG+HU7u5gojIuxCFEhvZY1FiWhLRX63 h8olxHo96gZYchwpjMHLef/3R04sSsoDpUDeN+vcXYQF22pDJDI0J8AGM/Fm3u/YQ8 2O2V/0XzDk/yKCEDieWrRZA7xn3hMax9YeYYIL8HSUW7L0yUzAzgMbE77ur5pqHPvP ln0lhkwSindBtWuqc77905axhli3fpFFE1HLzxRSivBfnPPuuEqQavbLJ2qv2ryUdy B1xc5YWRto+qJnV+353N73LN8fOwGKq/05lH1vQSHd1R55nWD88UqUDKBgxa+tjMyH HFjz4uIY5vYN58z9HPcUdRSkCcZ70CIaHKV/H6Yax3z4WQkdwIFATIulWNDjaSVLuR Gg3yaj8RhjjuljGpdkPAhrho=
Authentication-Results: mail.aegee.org/04HEtn57422369; dkim=none
Received: from Tylan (87.118.146.153.topnet.bg [87.118.146.153] (may be forged)) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id 04HEtn57422369 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <imapext@ietf.org>; Sun, 17 May 2020 14:55:50 GMT
Message-ID: <4c6ed7902d8a21b14f59864881096f44f6b3bd24.camel@aegee.org>
From: Дилян Палаузов <dilyan.palauzov@aegee.org>
To: imapext@ietf.org
Date: Sun, 17 May 2020 14:55:49 +0000
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.37.2
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.102.3 at mail.aegee.org
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/pmmFWscfBkLhbRmC0_eATqTT60s>
Subject: [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: Sun, 17 May 2020 14:55:57 -0000

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.


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.



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
  Дилян

v2.23.0 | Report a Bug | By Email