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

Graham Klyne <gk@ninebynine.org> Tue, 17 May 2016 08:50 UTC

Return-Path: <gk@ninebynine.org>
X-Original-To: usefor@ietfa.amsl.com
Delivered-To: usefor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E500512B050; Tue, 17 May 2016 01:50:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JlVshQbrsxCx; Tue, 17 May 2016 01:50:05 -0700 (PDT)
Received: from relay15.mail.ox.ac.uk (relay15.mail.ox.ac.uk [163.1.2.163]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44F8E12B058; Tue, 17 May 2016 01:50:05 -0700 (PDT)
Received: from smtp5.mail.ox.ac.uk ([163.1.2.207]) by relay15.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <gk@ninebynine.org>) id 1b2ahW-0000Mm-oh; Tue, 17 May 2016 09:50:02 +0100
Received: from client-8-49.eduroam.oxuni.org.uk ([192.76.8.49] helo=sasharissa.local) by smtp5.mail.ox.ac.uk with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <gk@ninebynine.org>) id 1b2ahW-0007NG-I1; Tue, 17 May 2016 09:50:02 +0100
Message-ID: <573ADB7B.4060306@ninebynine.org>
Date: Tue, 17 May 2016 09:51:07 +0100
From: Graham Klyne <gk@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: =?UTF-8?B?SnVsaWVuIMOJTElF?= <julien@trigofacile.com>
References: <573572C7.4020408@ninebynine.org> <9ea7e62b-9a21-1102-eb3e-e12b574b9e89@trigofacile.com> <573982D3.1090106@ninebynine.org> <44513b01-a7fa-5db7-2461-d703ff9ddb9d@trigofacile.com>
In-Reply-To: <44513b01-a7fa-5db7-2461-d703ff9ddb9d@trigofacile.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Oxford-Username: zool0635
Archived-At: <http://mailarchive.ietf.org/arch/msg/usefor/znoNHbjh86sH6rIiYcESaoCv6K0>
Cc: usefor@ietf.org, ietf-message-headers@ietf.org
Subject: Re: [usefor] [apps-discuss] Changes to netnews header registrations
X-BeenThere: usefor@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Ongoing discussion of usefor issues." <usefor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/usefor>, <mailto:usefor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/usefor/>
List-Post: <mailto:usefor@ietf.org>
List-Help: <mailto:usefor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/usefor>, <mailto:usefor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 08:50:07 -0000

(Trimming cc's)

On 16/05/2016 16:57, Julien ÉLIE wrote:
> Hi Graham,
>
>> TL;DR: I don't propose to recommend the additional changes you suggest
>> as I'm not seeing that they really contribute to the purpose of the
>> registry (cf. https://tools.ietf.org/html/rfc3864#section-2.2.2).
>
> 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.

>
>
>
>> 2. With reference to the X-headers you mention, I see little point in
>> adding new, non-standard headers to the registry simply to indicate they
>> are now obsolete.  (There could be a case for doing this if they are in
>> widespread use, but I think that should be a separate discussion, and a
>> new RFC with its own IANA considerations section. I suspect it's not
>> worth the effort!)
>
> It depends on when we can say a header field is "wide-spread".
> I've just had a look in two newsgroups:
>
> * last 1043 messages (roughly October 2014-May 2016) in news.software.nntp:
> 391 (37%) contain X-Trace
> 216 (21%) contain X-Complaints-To
>
> * last 1437 messages (roughly August 2014-May 2016) in soc.culture.french:
> 612 (43%) contain X-Trace
> 97 (7%) contain X-Complaints-To
>
> Of course wider stats should be done because the generation of these headers
> depend on the news servers the users connect to.
>
>
> X-Trace seems in wide-spread use, though.
> I agree that writing a new RFC to just obsolete it is probably not worth the
> effort.  However, 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.

#g
--