19 Jul 20:44
IETF tools list issues (update)
From: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz <at> gmail.com>
Subject: IETF tools list issues (update)
Newsgroups: gmane.ietf.tools
Date: 2008-07-19 18:47:40 GMT
Subject: IETF tools list issues (update)
Newsgroups: gmane.ietf.tools
Date: 2008-07-19 18:47:40 GMT
Hi, an updated list of issues from my POV: * the RFC-I problem was fixed (= ietf.org unlisted), an update sent via GMaNe might be trapped in the moderation queue or in a meeting with Dave Null: <http://article.gmane.org/gmane.discuss/11839> * various errata are still AWOL, for a complete list of 667 RFCs with reported errata as of 2008-07-08 see <g502oa$btu$1 <at> ger.gmane.org>, available in <http://article.gmane.org/gmane.ietf.tools/1109> <http://www.ietf.org/mail-archive/web/tools-discuss/current/msg01563.html> * the "challenge" wasn't identified as challenge by GMaNe, I'm not sure if that is a bug or a feature in practice. Here is the "raw" challenge message: <http://article.gmane.org/gmane.ietf.tools/1114/raw> RFC 3834 issues in this "challenge": 1 - The envelope sender address was the ordinary list address, the list bounce address might be better, see RFC 3834 chapter 3.3 2 - There was no OPTIONAL (RFC 3834 chapter 3.1.8) Precedence: list (or similar) header field 3 - There was no RECOMMENDED (3.1.7) Auto-Submitted header field 4 - There were no RECOMMENDED (3.1.6) References and In-Reply-To header fields with the Message-ID of the challenged article, IMO that would be good 5 - There was no OPTIONAL (3.1.5) Auto: subject tag 6 - There was no RECOMMENDED (3.1.2) Reply-To header field, that's bad in conjunction with the next points 7 - The 2822-From was not a list owner address or say tools-discuss-request <at> ietf.org as RECOMMENDED in 3.1.1, it was the list address, IMO that's wrong. * GMaNe considered the challenge as ordinary mail from the list to all members, and that is how I got it, as ordinary "article" in a "newsgroup" gmane.ietf.tools. At that time I had no idea what is wrong and decided to send a "response" as requested, but "just in case" I used another route: Via Gmail corresponding to the 2822-From in the mail that triggered the challenge, a bad idea on my side. The list identified my address as subscribed, missed that it was "response" to its prior "challenge", and sent the response to all IETF Tools list members not limited to GMaNe: <http://article.gmane.org/gmane.ietf.tools/1115> <http://www.ietf.org/mail-archive/web/tools-discuss/current/msg01568.html> Likely the C/R system is still waiting for a response via GMaNe, I'll test that later. RFC 3834 does not mention the problem of a "response" on another route, but I think C/R systems should find such responses - especially if the "challenge" claims to use only the subject to find "responses", not the envelope sender. Frank
RSS Feed