As it is I can TELL you most implementors are largely looking at 2822 and
ignoring 822 now.
you can TELL me whatever you wish, but I have no reason to believe you.
let's put it this way - anyone wanting to deploy X- fields and then have them
standardized later is making things considerably more difficult for themselves
than necessary.
So if there is ANYTHING in 822 NOT mentioned in 2822 of importance, it needs
to be grafted in, or mentioned. Anything else should be specifically listed
as altered or deprecated.
strongly disagree. but if your goal is to keep 2822 from being revised for
several years, that's a good way to go about it.