From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Wed Apr 25 2001 - 14:12:01 CDT
In <87u23epko0.fsf@deneb.enyo.de> Florian Weimer <fw@deneb.enyo.de> writes:
>Russ Allbery <rra@stanford.edu> writes:
>> > A different option would be a 'Transmission-Headers: start' which
>> > indicates that the following headers are not related to the article
>> > itself, but to the transmission protocol being used.
>>
>> I think this is another solution based on the idea that Xref generalizes,
>> sort of like the current local headers stuff. My counter-argument is that
>> I think Xref is a unique problem, and would like to see an example of some
>> other header with similar properties before we go to the work of designing
>> someting into the standard to deal with it.
>Any header which transfers news database information falls into this
>category. Currently, I think no such headers are defined, but
>wouldn't it be nice if we had a header which lists the direct
>followups to an article? Or the expiration time?
It might be nice, but these would certainly be "local headers". I think
you have just given another reason why we need to retain that concept in
the draft - it gives us an opportunity to say how and when they should be
removed. In fact, I am coming to the opinion that the MAY be removed on
outgoing relaying should be upgraded to a SHOULD. At least the outgoing
site ought to be capable of recognising that they are local. I will grant
you that this is not current practice, however.
-- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl Email: chl@clw.cs.man.ac.uk Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K. PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5