Re: Use of message disposition notification
Russ Allbery <rra@stanford.edu> Tue, 26 May 2009 00:36 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 6426E3A7028 for <ietfarch-usefor-archive@core3.amsl.com>; Mon, 25 May 2009 17:36:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.613
X-Spam-Level:
X-Spam-Status: No, score=-6.613 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 tQ75GjfyZD-e for <ietfarch-usefor-archive@core3.amsl.com>; Mon, 25 May 2009 17:36:36 -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 54AC43A701D for <usefor-archive@ietf.org>; Mon, 25 May 2009 17:36:26 -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 n4Q0aKmt071485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 May 2009 17:36:20 -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 n4Q0aKn1071484; Mon, 25 May 2009 17:36:20 -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 smtp2.stanford.edu (smtp2.Stanford.EDU [171.67.219.82]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n4Q0aJ0r071472 for <ietf-usefor@imc.org>; Mon, 25 May 2009 17:36:19 -0700 (MST) (envelope-from eagle@windlord.stanford.edu)
Received: from smtp2.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 218E81705D4 for <ietf-usefor@imc.org>; Mon, 25 May 2009 17:36:19 -0700 (PDT)
Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134]) by smtp2.stanford.edu (Postfix) with ESMTP id E27A51705CE for <ietf-usefor@imc.org>; Mon, 25 May 2009 17:36:18 -0700 (PDT)
Received: by windlord.stanford.edu (Postfix, from userid 1000) id DD677E7935; Mon, 25 May 2009 17:36:18 -0700 (PDT)
To: ietf-usefor@imc.org
Subject: Re: Use of message disposition notification
In-Reply-To: <KHu8tA.8MM@clerew.man.ac.uk> (Charles Lindsey's message of "Thu\, 9 Apr 2009 14\:41\:34 GMT")
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux)
References: <D2BCD434C62C4A78B1C6D5DC08D75CD2@Iulius> <87bpr8cpyu.fsf@windlord.stanford.edu> <KHs9E5.5xC@clerew.man.ac.uk> <96088B3EFAFE49899F643996FBEC91B5@Iulius> <KHu8tA.8MM@clerew.man.ac.uk>
From: Russ Allbery <rra@stanford.edu>
Organization: The Eyrie
Date: Mon, 25 May 2009 17:36:18 -0700
Message-ID: <871vqcsnst.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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>
"Charles Lindsey" <chl@clerew.man.ac.uk> writes: > Julien ÉLIE <julien@trigofacile.com> writes: >> 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. > Cancel-Lock is not formally defined anywhere, hence I know of no > news-server that ever looks at it, although a few people add it in > hope :-). > Our original plan of work was that, when we were done with our present > drafts, the next jobs would be UTF-8 in newsgroup-names and a document > covering security matters - notably pgpmoose and pgpverify (which > really need to be unified) plus Cancel-Locks and, I would hope, > NoCeM. But those would rechartering, and the probability of that > happening is not, shall we say, too promising :-( . Unless someone feels very strongly otherwise, I'm going to bail on cancel lock for this document on those same "requires thought" grounds. The logical next step for Cancel-Lock would be to complete the work of publishing an RFC, which could then update this one and generate the right references in RFC listings. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
- Use of message disposition notification Julien ÉLIE
- Re: Use of message disposition notification Russ Allbery
- Re: Use of message disposition notification Charles Lindsey
- Re: Use of message disposition notification Julien ÉLIE
- Re: Use of message disposition notification Charles Lindsey
- Re: Use of message disposition notification Julien ÉLIE
- Re: Use of message disposition notification Charles Lindsey
- Re: Use of message disposition notification Julien ÉLIE
- Re: Use of message disposition notification Russ Allbery