Re: [lemonade] [Editorial Errata Reported] RFC5524 (6214)

[Dave Cridland <[e-mail]>]

On Wed, 24 Jun 2020 at 13:37, Eric Burger <[e-mail]>
wrote:

> Resending with a better address for Dave, as he’s key to the question.
>
> On Jun 24, 2020, at 8:32 AM, Eric Burger <[e-mail]>
> wrote:
>
> Hmmmm. It has been over a *decade. *What did people implement?
>
> From the RFC:
> The capability is URLAUTH=BINARY.
> The command is URLFETCH (… BINARY …)
>
>
Yes, it's been a while.

And I'm not actually sure if anyone ever did implement this. I'm certainly
unsure how I'd find out now - Alexey would know about Isode M-Box, and if
that doesn't implement I'm not sure what else would. I've looked at both my
client (Polymer - been a while since I looked at that, too), and Panda
IMAP, and neither support it.

If Alexey doesn't support this, then my suspicion is that nobody does.

> On Jun 24, 2020, at 4:31 AM, RFC Errata System <[e-mail]>
> wrote:
>
> The following errata report has been submitted for RFC5524,
> "Extended URLFETCH for Binary and Converted Parts".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6214
>
> --------------------------------------
> Type: Editorial
> Reported by: Дилян Палаузов <[e-mail]>
>
> Section: 6
>
> Original Text
> -------------
> This document defines the URLFETCH=BINARY IMAP capability.  IANA has added
> it to the registry accordingly.
>
> Corrected Text
> --------------
> This document defines the URLAUTH=BINARY IMAP capability.  IANA is asked
> to replace URLFETCH=BINARY with URLAUTH=BINARY in the IMAP registry.
>
> Notes
> -----
> This document talks about URLAUTH=BINARY.  Mentioning URLFETCH=BINARY in
> the IANA section was not intended.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC5524 (draft-cridland-urlfetch-binary-03)
> --------------------------------------
> Title               : Extended URLFETCH for Binary and Converted Parts
> Publication Date    : May 2009
> Author(s)           : D. Cridland
> Category            : PROPOSED STANDARD
> Source              : Enhancements to Internet email to support diverse
> service environments
> Area                : Applications
> Stream              : IETF
> Verifying Party     : IESG
>
>
>
>