Re: [usefor] Changes to netnews header registrations
Julien ÉLIE <julien@trigofacile.com> Fri, 13 May 2016 15:20 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 5786A12D586 for <usefor@ietfa.amsl.com>; Fri, 13 May 2016 08:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] 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 sI-ohezQAP5H for <usefor@ietfa.amsl.com>; Fri, 13 May 2016 08:20:47 -0700 (PDT)
Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0980E12D57E for <usefor@ietf.org>; Fri, 13 May 2016 08:20:44 -0700 (PDT)
Received: from macbook-pro-de-julien-elie.home ([92.170.5.52]) by mwinf5d01 with ME id trLh1s00C17Lgi403rLhV4; Fri, 13 May 2016 17:20:42 +0200
X-ME-Helo: macbook-pro-de-julien-elie.home
X-ME-Auth: anVsaWVuLmVsaWVAd2FuYWRvby5mcg==
X-ME-Date: Fri, 13 May 2016 17:20:42 +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>
From: Julien ÉLIE <julien@trigofacile.com>
Organization: TrigoFACILE -- http://www.trigofacile.com/
Message-ID: <9ea7e62b-9a21-1102-eb3e-e12b574b9e89@trigofacile.com>
Date: Fri, 13 May 2016 17:20:40 +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: <573572C7.4020408@ninebynine.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/usefor/BaK8R9SLK31wQaRorYfFJJ7OneE>
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: Fri, 13 May 2016 15:20:53 -0000
Hi Graham, First of all, thanks for reviewing the request I sent. I add the USEFOR IETF WG in copy of this message, in case they wish to comment. > As reviewer for the IANA message headers registry > (http://www.iana.org/assignments/message-headers/message-headers.xhtml), > I've received a request to change references to rename > "[Son-of-1036]" references to "[RFC1849]"? This document is now > published as a historic RFC. > > I propose to make a recommendation that goes beyond the original > request, and as such I thought I should submit my proposed > recommendation to public review. > > I think the requested change is appropriate with respect to the > following message header fields: > > Also-control > Article-names > Article-updates > See-also > > (Did I miss any?) These are indeed the 4 message header fields obsoleted by RFC1849. > I also think that RFC5536 should be cited for these headers, as it is > this document that formally declared them to be obsolete > (https://tools.ietf.org/html/rfc5536#section-6). Yes, RFC5536 can be cited instead of, or along with, RFC1849. > While we're at it, I'd suggest also citing RFC5536 for the following > header fields, also obsoleted by that document > (https://tools.ietf.org/html/rfc5536#section-3.3 and #section-6): > > Date-Received netnews obsoleted [RFC0850] > Posting-Version netnews obsoleted [RFC0850] > Relay-Version netnews obsoleted [RFC0850] > NNTP-Posting-Date netnews obsoleted > NNTP-Posting-Host netnews obsoleted [RFC2980] > > If I hear no objection within a few days, I'll pass this recommendaton > to IANA. Couldn't X-Trace and X-Complaints-To header fields also be added to that list? X-Trace netnews obsoleted [RFC5536] X-Complaints-To netnews obsoleted [RFC5536] They are indeed mentioned at the same time as NNTP-Posting-Host in Section 3.2.8 of RFC5536, and are no longer useful with Injection-Info header field: NOTE: Some of this information has previously been sent in non- standardized header fields such as NNTP-Posting-Host, X-Trace, X-Complaints-To, and others. Once a news server generates an Injection-Info header field, it should have no need to send these non-standard header fields. While we're at it, couldn't MIME-related header fields also be added as standard for netnews? MIME-Version netnews standard [RFC5536][RFC5322] Content-Type netnews standard [RFC5536][RFC5322] Content-Transfer-Encoding netnews standard [RFC5536][RFC5322] Content-Disposition netnews standard [RFC5536][RFC5322] Content-Language netnews standard [RFC5536][RFC5322] As a matter of fact, Section 3.2 of RFC5536 speaks of them, with added restrictions in syntax: None of the header fields appearing in this section are required to appear in every article, but some of them may be required in certain types of articles. Further discussion of these requirements appears in [RFC5537] and [USEAGE]. The header fields Comments, Keywords, Reply-To, and Sender are used in Netnews articles in the same circumstances and with the same meanings as those specified in [RFC5322], with the added restrictions detailed above in Section 2.2. Multiple occurrences of the Keywords header field are not permitted. comments = "Comments:" SP unstructured CRLF keywords = "Keywords:" SP phrase *("," phrase) CRLF reply-to = "Reply-To:" SP address-list CRLF sender = "Sender:" SP mailbox CRLF The MIME header fields MIME-Version, Content-Type, Content-Transfer- Encoding, Content-Disposition, and Content-Language are used in Netnews articles in the same circumstances and with the same meanings as those specified in [RFC2045], [RFC2183], and [RFC3282], with the added restrictions detailed above in Section 2.2. Thanks, -- Julien ÉLIE « Pour célébrer ce jour heureux, buvons un coup, buvons-en deux. » (Aristophane)
- Re: [usefor] Changes to netnews header registrati… Julien ÉLIE
- Re: [usefor] Changes to netnews header registrati… Graham Klyne
- Re: [usefor] [Ietf-message-headers] Changes to ne… Graham Klyne
- Re: [usefor] Changes to netnews header registrati… Julien ÉLIE
- Re: [usefor] [apps-discuss] Changes to netnews he… Graham Klyne
- Re: [usefor] [apps-discuss] Changes to netnews he… Julien ÉLIE