RFC 5437 on Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)

rfc-editor@rfc-editor.org Sun, 01 February 2009 04:00 UTC

Return-Path: <owner-ietf-mta-filters@mail.imc.org>
X-Original-To: ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com
Delivered-To: ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09DB33A6B52 for <ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com>; Sat, 31 Jan 2009 20:00:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.501
X-Spam-Level:
X-Spam-Status: No, score=-16.501 tagged_above=-999 required=5 tests=[AWL=0.498, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Gf+TUpotJn2 for <ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com>; Sat, 31 Jan 2009 20:00:25 -0800 (PST)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id D05983A6AA8 for <sieve-archive-Aet6aiqu@ietf.org>; Sat, 31 Jan 2009 20:00:24 -0800 (PST)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n113qsTA069944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Jan 2009 20:52:54 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n113qsg2069943; Sat, 31 Jan 2009 20:52:54 -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 bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n113qrYm069937 for <ietf-mta-filters@imc.org>; Sat, 31 Jan 2009 20:52:53 -0700 (MST) (envelope-from rfc-editor@rfc-editor.org)
Received: by bosco.isi.edu (Postfix, from userid 70) id 688502044BF; Sat, 31 Jan 2009 19:52:53 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5437 on Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, ietf-mta-filters@imc.org
Message-Id: <20090201035253.688502044BF@bosco.isi.edu>
Date: Sat, 31 Jan 2009 19:52:53 -0800
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>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5437

        Title:      Sieve Notification Mechanism: Extensible Messaging 
                    and Presence Protocol (XMPP) 
        Author:     P. Saint-Andre, A. Melnikov
        Status:     Standards Track
        Date:       January 2009
        Mailbox:    psaintan@cisco.com, 
                    Alexey.Melnikov@isode.com
        Pages:      14
        Characters: 28448
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sieve-notify-xmpp-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5437.txt

This document describes a profile of the Sieve extension for
notifications, to allow notifications to be sent over the Extensible
Messaging and Presence Protocol (XMPP), also known as Jabber.
[STANDARDS TRACK]

This document is a product of the Sieve Mail Filtering Language Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute