Re: [Ietf-message-headers] [usefor] [apps-discuss] Changes to netnews header registrations

[Julien ÉLIE <[e-mail]>]

Hi Graham,

>> OK, Content-* header fields used by netnews are not supposed to be
>> registered. Yet, is it the same for MIME-Version, that is not
>> mentioned in neither Section 1 nor Section 2.2.2 of RFC3864?
>
> I believe so:  "MIME-Version" is registered as a "MIME" header field in
> the registry.

OK, I was a bit confused by the existence of "http" and "mail" protocols 
related to Content-* headers or MIME-Version in the registry.

Incidentally, RFC4021 marks Content-Identifier and Content-Return 
obsolete for the mail protocol (see Sections 2.1.42 and 2.1.47 of 
RFC4021).  Shouldn't the registry reflect that status?

Same thing for Encrypted, Obsoletes and Expiry-Date headers fields, 
marked as obsolete.  Maybe a pass on IANA Considerations of RFC4021 
should be done to make sure everything is correctly marked in the registry?


>> maybe X-Trace (and maybe other headers) could be added in IANA
>> considerations section of an update of RFC 5536 if we ever move it
>> to Draft Standard?
>
> Sure.  That would be subject to normal IETF review.  If it passed that,
> then (as registry reviewer) I would have no problem recommending its
> acceptance.

I'm fine with that.  Thanks, Graham.
(If other people in the USEFOR mailing-list have another opinion, do not 
hesitate to tell.)

-- 
Julien ÉLIE

« – Ce n'était pas ma question.
   – C'était p'têt pas vot'question, oui, mais c'est ma
     réponse ! » (Georges Marchais répondant à Alain Duhamel)