Re: Use of message disposition notification

Julien ÉLIE <julien@trigofacile.com> Wed, 08 April 2009 18:40 UTC

Return-Path: <owner-ietf-usefor@mail.imc.org>
X-Original-To: ietfarch-usefor-archive@core3.amsl.com
Delivered-To: ietfarch-usefor-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D2483A6E5F for <ietfarch-usefor-archive@core3.amsl.com>; Wed, 8 Apr 2009 11:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.32
X-Spam-Level:
X-Spam-Status: No, score=-1.32 tagged_above=-999 required=5 tests=[AWL=0.978, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sSwSTmlO14NP for <ietfarch-usefor-archive@core3.amsl.com>; Wed, 8 Apr 2009 11:40:17 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 153CA3A6AA9 for <usefor-archive@ietf.org>; Wed, 8 Apr 2009 11:40:16 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n38IcFGE027857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Apr 2009 11:38:15 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n38IcFZ2027856; Wed, 8 Apr 2009 11:38:15 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f
Received: from 30.mail-out.ovh.net (30.mail-out.ovh.net [213.186.62.213]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n38IcDRc027848 for <ietf-usefor@imc.org>; Wed, 8 Apr 2009 11:38:14 -0700 (MST) (envelope-from julien@trigofacile.com)
Received: (qmail 16951 invoked by uid 503); 8 Apr 2009 18:38:28 -0000
Received: from gw2.ovh.net (HELO mail434.ha.ovh.net) (213.251.189.202) by 30.mail-out.ovh.net with SMTP; 8 Apr 2009 18:38:28 -0000
Received: from b0.ovh.net (HELO queue-out) (213.186.33.50) by b0.ovh.net with SMTP; 8 Apr 2009 18:38:11 -0000
Received: from amontpellier-159-1-82-22.w90-57.abo.wanadoo.fr (HELO Iulius) (julien%trigofacile.com@90.57.241.22) by ns0.ovh.net with SMTP; 8 Apr 2009 18:38:09 -0000
Message-ID: <96088B3EFAFE49899F643996FBEC91B5@Iulius>
From: Julien ÉLIE <julien@trigofacile.com>
To: Usefor WG <ietf-usefor@imc.org>
References: <D2BCD434C62C4A78B1C6D5DC08D75CD2@Iulius> <87bpr8cpyu.fsf@windlord.stanford.edu> <KHs9E5.5xC@clerew.man.ac.uk>
In-Reply-To: <KHs9E5.5xC@clerew.man.ac.uk>
Subject: Re: Use of message disposition notification
Date: Wed, 08 Apr 2009 20:36:15 +0200
Organization: TrigoFACILE -- http://www.trigofacile.com/
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049
X-Ovh-Tracer-Id: 17226550050887564729
X-Ovh-Remote: 90.57.241.22 (amontpellier-159-1-82-22.w90-57.abo.wanadoo.fr)
X-Ovh-Local: 213.186.33.20 (ns0.ovh.net)
X-Spam-Check: DONE|H 0.5/N
Sender: owner-ietf-usefor@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-usefor/mail-archive/>
List-Unsubscribe: <mailto:ietf-usefor-request@imc.org?body=unsubscribe>
List-ID: <ietf-usefor.imc.org>

Hi Charles,

>>>    It SHOULD reject any proto-article which contains a header field
>>>    deprecated for Netnews (see, for example, [RFC3798] (Hansen, T. and
>>>    G. Vaudreuil, "Message Disposition Notification," May 2004.)).
>
> RFC 3798 end of section 2.1:
>
>   Messages posted to newsgroups SHOULD NOT have a Disposition-
>   Notification-To header.
>
> The reason is that it could be used to send mail bombs. I suppose we could
> mention that reason in our Security Considerations.

Oh, thanks!
It is not easy at all to find out such headers!!  I wonder how implementors
will manage to know the headers they should look at...


By the way, as you speak about security considerations, I see that USEPRO
references both pgpmoose and pgpverify.
Wouldn't a note on Cancel-Lock be added in 6.1?  ("Currently, many sites are
ignoring all cancel control messages and Supersedes header fields due to
the difficulty of authenticating them and their widespread abuse.")
It could be said that Cancel-Lock might be used (draft-ietf-usefor-cancel-lock-01)
and also NoCeM, which is more and more spread nowadays.

-- 
Julien ÉLIE

« Les légionnaires ont adopté pour attaquer la redoutable tactique
  dite de la tortue. Pour battre en retraite, les légionnaires
  adoptent l'efficace tactique dite du lièvre. » (Astérix)