3.4 Change control
Change control of a header registration is subject to the same
condition as the initial registration; i.e. publication of an IESG-
approved RFC for a Normative Message Header, or on request of the
indicated author/change controller for a Provisional Message Header.
I can see problems with this. If a certain header is at the
same time non-standard, and widely used, you cannot allow
the person who happpens to register it first to have change
control. After it has been put into the registry, IETF (or
some other standards organisation) must in some way have
change control, to stop people changing the definition of
widely used, non-standard headers in ways which are not
good and not in accordance with existing use.
--
Jacob Palme <jpalme(_at_)dsv(_dot_)su(_dot_)se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/