From: Clive D.W. Feather (clive@demon.net)
Date: Wed Sep 06 2000 - 02:27:59 CDT
Charles Lindsey said:
>> What about allowing further tokens after the address to allow the ISP to
>> include the relevant data right there ? So the following example:
>> Injector-Info: isp.net; posting-host="modem-15.pop.isp.net myuser";
>> posting-date="965243133: Wed 2 Aug 2000 20:05:33 -0100 (BST)";
>> serial="news2.isp.net:2427"; complaints-to="abuse@isp.net"
> My intention was that sort of stuff should go in the "serial" parameter,
> so that the parsing of 'posting-date' would not get confused by extraneous
> stuff.
I read "serial" as being data recorded by the news server to do with the
*posting* (e.g. box and process ID within a cluster), and not to do with
the *identity* (IP address or hostname plus some link to who was using that
address at that moment). In other words, there's more data than you've
allowed for.
> Generally, I reckon is is better to have a largish number of
> parameters, each with a recognisable and parsable syntax to do one
> specific job.
That's fine by me.
> Agreed that my "serial" parameter has a very loose syntax. I did toy with
> the idea of having a "server" parameter. The "sender" parameter was
> supposed to identify the user, but maybe a "user" parameter is also
> needed.
"posting-host" and "posting-account" ?
> One can expect many ISPs to add their own x-parameters, but we
> should try any provide sufficient well-chosen ones to make this mostly
> unnecessary.
Agreed.
-- Clive D.W. Feather | Work: <clive@demon.net> | Tel: +44 20 8371 1138 Internet Expert | Home: <clive@davros.org> | Fax: +44 20 8371 1037 Demon Internet | WWW: http://www.davros.org | DFax: +44 20 8371 4037 Thus plc | | Mobile: +44 7973 377646