>> I don't see any point in putting details that may change or be dropped
>> entirely into an IETF header registry. If that's what you want, just
>> use Dan's registry.
> There is a difference between a casual, personal activity, versus a
> formal one operated by an organization.
Yes, there is, but that's beside the point.
I don't see any useful purpose served by a half-way registry that doesn't
contain just standardized, documented, and reviewed headers, but
simultaneously doesn't contain all the headers being used. I do see a
useful purpose served by both a registry that contains everything and a
registry that contains only well-documented and reviewed headers.
I agree, I think it should contain EVERYTHING, with an indication of the
'status' of headers - whether standard or non-standard etc.
Also, IMHO, it would be useful if, as well as people being able to submit
header entries, email software authors could say which headers their
software uses (ie. reads and/or writes). That way, it would give an
indication of whether a header is actually useful or not, and whether a
non-standard header may be worth making into a standard one. OK, I know
this won't be perfect, since lots of people write email software and don't
read standards etc, but it'd be interesting and useful.
Paul VPOP3 - Internet Email Server/Gateway
paul(_at_)pscs(_dot_)co(_dot_)uk http://www.pscs.co.uk/