Re: [usefor] Changes to netnews header registrations

Julien ÉLIE <julien@trigofacile.com> Mon, 16 May 2016 15:57 UTC

Return-Path: <julien@trigofacile.com>
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 446C212D704 for <usefor@ietfa.amsl.com>; Mon, 16 May 2016 08:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FSL_HELO_HOME=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=no 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 N2GRwZTRcqVx for <usefor@ietfa.amsl.com>; Mon, 16 May 2016 08:57:08 -0700 (PDT)
Received: from smtp.smtpout.orange.fr (smtp04.smtpout.orange.fr [80.12.242.126]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EA3612D70C for <usefor@ietf.org>; Mon, 16 May 2016 08:57:06 -0700 (PDT)
Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d07 with ME id v3x01s00G17Lgi4033x1uj; Mon, 16 May 2016 17:57:04 +0200
X-ME-Helo: macbook-pro-de-julien-elie.home
X-ME-Auth: anVsaWVuLmVsaWVAd2FuYWRvby5mcg==
X-ME-Date: Mon, 16 May 2016 17:57:04 +0200
X-ME-IP: 92.170.5.52
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, ietf-message-headers@ietf.org, usefor@ietf.org
References: <573572C7.4020408@ninebynine.org> <9ea7e62b-9a21-1102-eb3e-e12b574b9e89@trigofacile.com> <573982D3.1090106@ninebynine.org>
From: =?UTF-8?Q?Julien_=c3=89LIE?= <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
Message-ID: <44513b01-a7fa-5db7-2461-d703ff9ddb9d@trigofacile.com>
Date: Mon, 16 May 2016 17:57:00 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <573982D3.1090106@ninebynine.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/usefor/RO-1Ko6QRV14GD0k7Ko8xzp5L8s>
Cc: Graham Klyne <gk@ninebynine.org>
Subject: Re: [usefor] 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: Mon, 16 May 2016 15:57:10 -0000

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?



> 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?

-- 
Julien ÉLIE

« La différence entre un chanteur et une paire de chaussures est que
   le chanteur doit partir avant de lasser. La paire de chaussures, il
   vaut mieux les lacer avant de partir. » (Philippe Geluck)