In
<prYqvhAU+WKtGdjb/O455g(_dot_)md5(_at_)melkebalanse(_dot_)gulbrandsen(_dot_)priv(_dot_)no>
Arnt Gulbrandsen <arnt(_at_)gulbrandsen(_dot_)priv(_dot_)no> writes:
Perhaps the auto-submitted "parameter" could be elaborated a little,
mentioning two optional parameters, "generator" and "type", and saying
that "type" is "antivirus", "vacation", "new-ticket" or something else,
and generator is a string describing the product.
Auto-Submitted: auto-generated; type=antivirus; generator="sophos blah".
That would be very like e.g. content-type and content-disposition.
Yes indeed. That is the way USEFOR has been moving. _Every_ header has
provision for an arbitrary number of MIME-style headers
(ideally - it will be some years before you can rely on it for all headers
but is fine for new ones). That way, extensions can be defined in future RFCs
in a way that is upwards compatible, and without having to invent YANH
each time.
So you define your Auto-Submitted header with 'type' and 'generator'
parameters (which you foresee as being useful). And you state that all
other parameters SHOULD be simply ignored by agents which do not recognize
them. That even allows individual responders to insert their own
X-parameters for whatever reason, which recipients can then immediately
ignore.
And a 'ticket-no=123456' parameter might indeed be a useful one to have
from the start.
--
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(_at_)clerew(_dot_)man(_dot_)ac(_dot_)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