RFC 6468: Sieve Notification Mechanism: SIP MESSAGE
In plain English — editorial summary, not part of the RFC
This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent over SIP MESSAGE. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6468
- Published
- February 2012
- Authors
- A. Melnikov; B. Leiba; K. Li
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8599Push Notification with the Session Initiation Protocol (SIP)Current
May 2019
- RFC 6558Sieve Extension for Converting Messages before DeliveryCurrent
March 2012
- RFC 6009Sieve Email Filtering: Delivery Status Notifications and Deliver-By ExtensionsCurrent
October 2010
- RFC 5784Sieve Email Filtering: Sieves and Display Directives in XMLCurrent
March 2010
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 5551Lemonade Notifications ArchitectureCurrent
August 2009
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 5429Sieve Email Filtering: Reject and Extended Reject ExtensionsCurrent
March 2009
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?