Re: Chris Newman's comment on draft-ietf-sieve-notify
Alexey Melnikov <alexey.melnikov@isode.com> Thu, 27 December 2007 14:27 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 1J7ti1-00058I-ME for sieve-archive-Aet6aiqu@lists.ietf.org; Thu, 27 Dec 2007 09:27:41 -0500
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J7ti0-0001Ao-2a for sieve-archive-Aet6aiqu@lists.ietf.org; Thu, 27 Dec 2007 09:27:41 -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 lBREALDC009335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Dec 2007 07:10:21 -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 lBREAKOW009334; Thu, 27 Dec 2007 07:10:20 -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 rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id lBREAJhA009328 for <ietf-mta-filters@imc.org>; Thu, 27 Dec 2007 07:10:20 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [192.168.0.11] (atomnet2.ttr.ru [195.245.249.86]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <R3OyRQAMlsaa@rufus.isode.com>; Thu, 27 Dec 2007 14:10:18 +0000
Message-ID: <4773B416.7080100@isode.com>
Date: Thu, 27 Dec 2007 17:17:58 +0300
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
To: Peter Saint-Andre <stpeter@stpeter.im>
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>
In-Reply-To: <476AAE58.2000701@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: 3.3 (+++)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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?
- 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