Re: AD evaluation comments: draft-ietf-sieve-variables
Alexey Melnikov <alexey.melnikov@isode.com> Thu, 18 August 2005 13:41 UTC
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j7IDfjln020984; Thu, 18 Aug 2005 06:41:45 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j7IDfjNr020983; Thu, 18 Aug 2005 06:41:45 -0700 (PDT)
X-Authentication-Warning: above.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 above.proper.com (8.12.11/8.12.9) with ESMTP id j7IDfiIm020968 for <ietf-mta-filters@imc.org>; Thu, 18 Aug 2005 06:41:44 -0700 (PDT) (envelope-from alexey.melnikov@isode.com)
Received: from [172.16.2.178] (shiny.isode.com [62.3.217.250]) by rufus.isode.com via TCP (internal) with ESMTPA; Thu, 18 Aug 2005 14:40:38 +0100
Message-ID: <43048FD4.5010901@isode.com>
Date: Thu, 18 Aug 2005 14:40:36 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
To: Scott Hollenbeck <sah@428cobrajet.net>
CC: ietf-mta-filters@imc.org
Subject: Re: AD evaluation comments: draft-ietf-sieve-variables
References: <courier.43048AB3.00007683@mail.verisignlabs.com>
In-Reply-To: <courier.43048AB3.00007683@mail.verisignlabs.com>
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>
Scott Hollenbeck wrote: >Just a small nit and a question: > >The Abstract should be more clear about the focus of the document. It >describes "This extension", but it doesn't explain what's being extended. > > The Abstract currently says: In advanced filtering rule sets, it is useful to keep state or configuration details across rules. This extension changes the interpretation of strings, adds an action to store data in variables, and supplies a new test so that the value of a string can be examined. How about the following: In advanced filtering rule sets, it is useful to keep state or configuration details across rules. This document describes a SIEVE (RFC XXXX) extension that changes the interpretation of strings, adds an action to store data in variables, and supplies a new test so that the value of a string can be examined. ? >RFC 2234 has been obsoleted. Can the reference to 2234 be updated to refer >to 2234bis instead? > > Absolutely. But I personally would prefer if the document is not delayed on this reference. In practice, this might not be an issue, as there is at least one normative reference (base Sieve document) that would have to be satisfied first. >These are minor. Please hold off on making any changes until IETF last call >comments can be addressed. > >
- AD evaluation comments: draft-ietf-sieve-variables Scott Hollenbeck
- RE: AD evaluation comments: draft-ietf-sieve-vari… Scott Hollenbeck
- Re: AD evaluation comments: draft-ietf-sieve-vari… Alexey Melnikov