Re: -01 revision of proposed sieve WG charter

"Mark E. Mallett" <mem@mv.mv.com> Tue, 05 October 2004 14:55 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 i95EtJSF020756; Tue, 5 Oct 2004 07:55:19 -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 i95EtJQU020755; Tue, 5 Oct 2004 07:55:19 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from mv.mv.com (osmium.mv.net [199.125.85.152]) by above.proper.com (8.12.11/8.12.9) with SMTP id i95EtITJ020748 for <ietf-mta-filters@imc.org>; Tue, 5 Oct 2004 07:55:18 -0700 (PDT) (envelope-from mem@mv.mv.com)
Received: (qmail 5765 invoked by uid 101); 5 Oct 2004 10:55:20 -0400
From: "Mark E. Mallett" <mem@mv.mv.com>
Date: Tue, 05 Oct 2004 10:55:20 -0400
To: Cyrus Daboo <daboo@isamet.com>
Cc: "Mark E. Mallett" <mem@mv.mv.com>, ned.freed@mrochek.com, ietf-mta-filters@imc.org
Subject: Re: -01 revision of proposed sieve WG charter
Message-ID: <20041005145520.GA4872@osmium.mv.net>
References: <01LF92HCN3OA00005R@mauve.mrochek.com> <20041001170028.GB5852@osmium.mv.net> <9FD7DA861CC9A89BD94C7CF6@ninevah.cyrusoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9FD7DA861CC9A89BD94C7CF6@ninevah.cyrusoft.com>
User-Agent: Mutt/1.4.2.1i
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>

On Fri, Oct 01, 2004 at 01:47:28PM -0400, Cyrus Daboo wrote:
> Hi Mark,
> 
> --On Friday, October 1, 2004 1:00 PM -0400 "Mark E. Mallett" 
> <mem@mv.mv.com> wrote:
> 
> >>(2) Produce updated sieve relational (RFC 3431), subaddress (RFC 3598),
> >>    spamtest/virustest (RFC 3685), and copy extension specifications,
> >
> >The "copy extensions specifications" being "draft-degener-sieve-copy" ?
> >Why is it listed in (2) and not in (3)?  (not that it really matters I
> >guess, just wanted to make sure it's included...)
> 
> That draft is currently in the RFC Editor queue waiting to be published, 
> and hopefully will be very soon - so it is correct to put it under (2) 
> thought there is no RFC number assigned to it right now.

Ah... thanks.  Saw the notice yesterday, in fact: RFC3894

   ftp://ftp.rfc-editor.org/in-notes/rfc3894.txt

mm