Re: Naming conventions for Sieve RFCs
Alexey Melnikov <alexey.melnikov@isode.com> Mon, 13 August 2007 09:26 UTC
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 l7D9Q6r6071321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Aug 2007 02:26:06 -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 l7D9Q6lm071320; Mon, 13 Aug 2007 02:26:06 -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 l7D9Q5lJ071314 for <ietf-mta-filters@imc.org>; Mon, 13 Aug 2007 02:26:05 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <RsAjqQAn9ha3@rufus.isode.com>; Mon, 13 Aug 2007 10:26:02 +0100
Message-ID: <46BEDD40.6020009@isode.com>
Date: Sun, 12 Aug 2007 11:13:20 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Nigel Swinson <Nigel.Swinson@mailsite.com>
CC: ietf-mta-filters@imc.org
Subject: Re: Naming conventions for Sieve RFCs
References: <007f01c7db68$230c5140$d201a8c0@nigelhome>
In-Reply-To: <007f01c7db68$230c5140$d201a8c0@nigelhome>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; 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>
Nigel Swinson wrote: >Did we decide on a naming convention for Sieve extensions? > I remember we've discussed this before, but I don't remember the outcome and I am offline at the moment. >We seem to have >either "Sieve Email Filtering: ..." or "Sieve Extension: ..." and I think it >would be helpful to be consistent. Looking for a precedent from the >existing RFCs we have: > >RFC3431 Sieve Extension: Relational Tests. W. Segmuller. December 2002. > (Format: TXT=12849 bytes) (Status: PROPOSED STANDARD) > >RFC3598 Sieve Email Filtering -- Subaddress Extension. K. Murchison. > September 2003. (Format: TXT=11151 bytes) (Status: PROPOSED STANDARD) > >RFC3685 SIEVE Email Filtering: Spamtest and VirusTest Extensions. C. > Daboo. February 2004. (Format: TXT=17436 bytes) (Status: PROPOSED > STANDARD) > >RFC3894 Sieve Extension: Copying Without Side Effects. J. Degener. > October 2004. (Format: TXT=9018 bytes) (Status: PROPOSED STANDARD) > >http://www.ietf.org/html.charters/sieve-charter.html lists the other >I-Drafts out there for Sieve and I think "Sieve Email Filtering: ..." has >the majority vote just now. That means we should change these if possible: > >http://tools.ietf.org/html/draft-ietf-sieve-variables >Sieve Extension: Variables > > Your proposal should work here. >http://tools.ietf.org/html/draft-ietf-sieve-notify-08 >Sieve Extension: Notifications > > I can change the title, but I think that: SIEVE Email Filtering Extension: Notifications is slightly more informative than: SIEVE Email Filtering: Enotify Extension (who would know that enotify is about notifications?) Opinions? >http://tools.ietf.org/html/draft-ietf-sieve-3431bis-04 >Sieve Extension: Relational Tests > > The same problem as above here: I think "Relational Tests" is more informative that "Relational Extension"
- Naming conventions for Sieve RFCs Nigel Swinson
- Re: Naming conventions for Sieve RFCs Kjetil Torgrim Homme
- Re: Naming conventions for Sieve RFCs Alexey Melnikov
- Re: Naming conventions for Sieve RFCs Nigel Swinson
- Re: Naming conventions for Sieve RFCs Nigel Swinson
- Re: Naming conventions for Sieve RFCs Kjetil Torgrim Homme
- Re: Naming conventions for Sieve RFCs Aaron Stone
- Re: Naming conventions for Sieve RFCs Alexey Melnikov
- Re: Naming conventions for Sieve RFCs Ned Freed
- Re: Naming conventions for Sieve RFCs Philip Guenther
- Re: Naming conventions for Sieve RFCs Alexey Melnikov
- Re: Naming conventions for Sieve RFCs Philip Guenther
- Re: Naming conventions for Sieve RFCs Alexey Melnikov
- Re: Naming conventions for Sieve RFCs Ken Murchison
- Re: Naming conventions for Sieve RFCs Alexey Melnikov
- Re: Naming conventions for Sieve RFCs Aaron Stone