Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding <ding@gnus.org>
Subject: Re: yEnc support in Gnus?
Date: Mon, 01 Jul 2002 21:34:51 +0200	[thread overview]
Message-ID: <ilufzz3qm1w.fsf@latte.josefsson.org> (raw)
In-Reply-To: <rjsn34wtbn.fsf@zuse.dina.kvl.dk> (Per Abrahamsen's message of "Sun, 30 Jun 2002 19:49:00 +0200")

Per Abrahamsen <abraham@dina.kvl.dk> writes:

>> There's a reason that there are only binary, quoted-printable and base64
>> encoding: these are the reliable ones.
>
> There is also 8bit.  yEnc demonstrates that there is a market for an
> binary over 8bit transfer encoding.  yEnc is technically a poor
> solution for that problem.  The two honorable things to do about that
> is a) help implement a better 8bit-over-binary solution, and b) shut
> up.

That's a hint if I ever saw one. :-)

So, what would be required to implement a better solution?  What does
yEnc provide that the existing MIME binary CTE and the Content-MD5
techniques doesn't already?  Escaping of CR/LF/NUL?  Content-MD5
doesn't work with message/partial though, but I remember seeing a I-D
defining Content-Hash, or something similar, for HTTP that fixes that.

Perhaps we could ask the people that has anti-yEnc web sites if they
want to help define a better scheme (some of the web sites provide
suggested MIME aware alternatives, altough not in I-D format).




  parent reply	other threads:[~2002-07-01 19:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 16:35 Ted Zlatanov
2002-06-27 16:48 ` Matthias Andree
2002-06-28  8:58   ` Per Abrahamsen
2002-06-30 10:16     ` Matthias Andree
2002-06-30 17:49       ` Per Abrahamsen
2002-07-01 16:11         ` Ted Zlatanov
2002-07-01 21:08           ` Florian Weimer
2002-07-01 19:34         ` Simon Josefsson [this message]
2002-07-02  1:47           ` Russ Allbery
2002-07-02 10:51             ` Steinar Bang
2002-07-03  1:25               ` Russ Allbery
2002-07-02 11:47         ` Matthias Andree
2002-07-02 12:52           ` Kai Großjohann
2002-07-02 15:37           ` Stainless Steel Rat
2002-07-03 23:14             ` Matthias Andree
2002-07-04  0:44               ` Stainless Steel Rat
2002-07-04  7:49                 ` Steinar Bang
2002-07-05 13:53                   ` Stainless Steel Rat
2002-07-04 14:14                 ` Matthias Andree
2002-07-04 15:50                   ` Per Abrahamsen
2002-07-05 14:03                   ` Stainless Steel Rat
2002-07-11  8:56             ` Gerd Flaig
2002-07-01 21:07       ` Florian Weimer
2002-06-27 18:02 ` Simon Josefsson
2002-06-27 18:24   ` Stainless Steel Rat
2002-06-27 18:37     ` Ted Zlatanov
2002-06-30 10:19       ` Matthias Andree
2002-08-07  2:03   ` Jesper Harder
2002-08-07  8:22     ` Per Abrahamsen
2002-08-07 10:14     ` Simon Josefsson
2002-08-08  3:02       ` Jesper Harder
2002-08-15 10:18       ` Matthias Andree

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ilufzz3qm1w.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).