From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Mon Sep 04 2000 - 04:34:27 CDT
In <20000901124030.W39226@demon.net> "Clive D.W. Feather" <clive@demon.net> writes:
>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;
>> posting-date="965243133: Wed 2 Aug 2000 20:05:33 -0100 (BST)";
>> serial="news2.isp.net:2427"; complaints-to="abuse@isp.net"
>would become:
> 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"
>to show that it was account "myuser", or:
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. 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.
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. 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.
> Injector-Info: isp.net; posting-host="modem-15.pop.isp.net 23401273";
> posting-date="965243133: Wed 2 Aug 2000 20:05:33 -0100 (BST)";
> serial="news2.isp.net:2427"; complaints-to="abuse@isp.net"
>to give a Radius log entry number.
-- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Email: chl@clw.cs.man.ac.uk Web: http://www.cs.man.ac.uk/~chl Voice/Fax: +44 161 437 4506 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