From: John Moreno (phenix@interpath.com)
Date: Mon Sep 20 1999 - 15:40:25 CDT
Charles Lindsey <chl@clw.cs.man.ac.uk> wrote:
> John Moreno <phenix@interpath.com> writes:
>
> >There isn't an example for Replaces/Supersedes being used in the same
> >article -- which, at least according to my reading, is what we are
> >going to try to encourage/require people to do. I would suggest that
> >it goes in section 6.16, but I guess it could go in 6.16.2.4.
>
> Eh? I am not sure what you are getting at here. Or do you mean that the
> examples should include both Replaces _and_ Supersedes headers as
> recommended until Replaces is widely implemented?
Precisely, and I think that part of that should be an example of them
being used together.
> BTW, Since
> Replaces: <..........>; usage=replace
> is equivalent to the present
> Supersedes: <..........>
> could we seriously consider adding the Mime-like "usage=..." to the
> present Supersedes header? Yes that is not a nice thing to do to a
> well-established existing header, but has anyone checked whether any
> existing implementations would actually barf on it?
I've just checked two servers, INN 1.7.2 and RumorMill 1.2, both barfed
(more precisely they didn't work, but the articles were accepted which
is even worse).
Original article was <supersedes@usefor.example> superseding article is
<200919991600412110%planb@newsreaders.com>.
> >> 3. Simplification of Content-Type discussion for Mime, addition of
> >> Content-Disposition, and replacement of application/news-transmission
> >> by message/news (to pacify the Mail gurus in IETF).
>
> >Shouldn't there be a SHOULD in section 6.15.5 for including a
> >Content-Disposition header? It's a SHOULD that it be obeyed, it ought
> >to at least be a SHOULD that it be included.
>
> No, I think the proper thing to do is to declare what the default is if it
> is absent. You will see that I was rather vague on what the default should
> be, since current practice is divided. I was hoping that one of you would
> stick your neck out and recommend a more definite default for us to
> specify.
I'd say attachment if not included, but I'm not big into MIME.
-- John Moreno