Re: Chris Newman's comment on draft-ietf-sieve-notify
Peter Saint-Andre <stpeter@stpeter.im> Thu, 27 December 2007 15:31 UTC
Return-path: <owner-ietf-mta-filters@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J7uhh-0003h5-7c for sieve-archive-Aet6aiqu@lists.ietf.org; Thu, 27 Dec 2007 10:31:25 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J7uhg-0002Mb-Ja for sieve-archive-Aet6aiqu@lists.ietf.org; Thu, 27 Dec 2007 10:31:25 -0500
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id lBRFKhbH016575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Dec 2007 08:20:43 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id lBRFKhpe016574; Thu, 27 Dec 2007 08:20:43 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from dizzyd.com (dizzyd.com [207.210.219.225]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id lBRFKflB016563 for <ietf-mta-filters@imc.org>; Thu, 27 Dec 2007 08:20:42 -0700 (MST) (envelope-from stpeter@stpeter.im)
Received: from dialup-4.227.193.93.Dial1.Denver1.Level3.net (dialup-4.227.193.93.Dial1.Denver1.Level3.net [4.227.193.93]) (Authenticated sender: stpeter) by dizzyd.com (Postfix) with ESMTP id AC37240077; Thu, 27 Dec 2007 08:20:36 -0700 (MST)
Message-ID: <4773C2C2.3000200@stpeter.im>
Date: Thu, 27 Dec 2007 08:20:34 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
CC: MTA filtering mailing list <ietf-mta-filters@imc.org>
Subject: Re: Chris Newman's comment on draft-ietf-sieve-notify
References: <476A5D8E.3020509@isode.com> <1198171016.6869.38.camel@localhost> <476AAE58.2000701@stpeter.im> <4773B416.7080100@isode.com>
In-Reply-To: <4773B416.7080100@isode.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="sha1"; boundary="------------ms010005090809050609070003"
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b6657e60309a1317174c9db2ae5f227
Alexey Melnikov wrote: > > Peter Saint-Andre wrote: >> Aaron Stone wrote: >> >>> On Thu, 2007-12-20 at 12:18 +0000, Alexey Melnikov wrote: >>> >>>> Chris has posted the following comment during the IESG review: >>>> >>>>> An issue with nomenclature that I recommend fixing. This >>>>> document uses the term "importance" with a completely different >>>>> meaning from the "importance" header in the Header Registry. >>>>> Indeed, in this document, the term "importance" has the same >>>>> meaning as the "priority" header in the mail headers registry and >>>>> the "urgency" header in the XMPP registry. I would prefer this >>>>> used consistent terminology. I recommend ":urgency" or >>>>> ":priority" instead of ":importance". I understand the change >>>>> would be annoying this late in the process given the notify XMPP >>>>> document has to be updated as well, which is why I'm not making >>>>> this a discuss issue. But please consider this seriously. >>>>> >>>> Are people Ok with changing the tag name? Are there any >>>> implementations of the latest draft? >>>> >>>> If there is no WG consensus to change the tag name, authors can >>>> update the tag description to use consistent terminology. >>>> >>> I am comfortable with a change to either name. Matching the keyword >>> and terminology of both mail and xmpp should be a priority, IMHO. (If >>> that means a vote for ':urgency' then so it is :) >>> >> Just to be clear, a tag name of ":priority" would not necessarily cause >> confusion in XMPP. >> > Speaking as a WG member (and not as a co-editor/chair): I dislike > changing the document to use :priority, because :priority was used in an > older version of the document and is already deployed. > So I would prefer to either change to :urgency or keep :importance, but > adjust terminology in order to clear any confusion. > > Any other opinions? I don't have a preference. Peter
- Chris Newman's comment on draft-ietf-sieve-notify Alexey Melnikov
- Re: Chris Newman's comment on draft-ietf-sieve-no… Peter Saint-Andre
- Re: Chris Newman's comment on draft-ietf-sieve-no… Aaron Stone
- Re: Chris Newman's comment on draft-ietf-sieve-no… Peter Saint-Andre
- Re: Chris Newman's comment on draft-ietf-sieve-no… Alexey Melnikov
- Re: Chris Newman's comment on draft-ietf-sieve-no… Peter Saint-Andre