From rfc-editor@rfc-editor.org Tue Mar 10 11:14:58 2009 Return-Path: X-Original-To: lemonade@core3.amsl.com Delivered-To: lemonade@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A16C73A6CC1; Tue, 10 Mar 2009 11:14:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.192 X-Spam-Level: X-Spam-Status: No, score=-17.192 tagged_above=-999 required=5 tests=[AWL=0.407, BAYES_00=-2.599, 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 X3CgBNbM0vw6; Tue, 10 Mar 2009 11:14:57 -0700 (PDT) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id BB4B33A6CC5; Tue, 10 Mar 2009 11:13:03 -0700 (PDT) Received: by bosco.isi.edu (Postfix, from userid 70) id 7CE1B24B696; Tue, 10 Mar 2009 11:11:46 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20090310181146.7CE1B24B696@bosco.isi.edu> Date: Tue, 10 Mar 2009 11:11:46 -0700 (PDT) Cc: lemonade@ietf.org, rfc-editor@rfc-editor.org Subject: [lemonade] RFC 5442 on LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile Email (MEM) Using Internet Mail X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Mar 2009 18:14:58 -0000 A new Request for Comments is now available in online RFC libraries. RFC 5442 Title: LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile Email (MEM) Using Internet Mail Author: E. Burger, G. Parsons Status: Informational Date: March 2009 Mailbox: eburger@standardstrack.com, gparsons@nortel.com Pages: 15 Characters: 28758 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lemonade-architecture-04.txt URL: http://www.rfc-editor.org/rfc/rfc5442.txt This document specifies the architecture for mobile email, as described by the Open Mobile Alliance (OMA), using Internet Mail protocols. This architecture was an important consideration for much of the work of the LEMONADE (Enhancements to Internet email to Support Diverse Service Environments) working group in the IETF. This document also describes how the LEMONADE architecture meets OMA's requirements for their Mobile Email (MEM) service. This memo provides information for the Internet community. This document is a product of the Enhancements to Internet email to support diverse service environments Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 From wwwrun@core3.amsl.com Mon Mar 16 09:23:55 2009 Return-Path: X-Original-To: lemonade@ietf.org Delivered-To: lemonade@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id 7189328C1C5; Mon, 16 Mar 2009 09:23:55 -0700 (PDT) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20090316162355.7189328C1C5@core3.amsl.com> Date: Mon, 16 Mar 2009 09:23:55 -0700 (PDT) Cc: lemonade mailing list , lemonade chair , Internet Architecture Board , RFC Editor Subject: [lemonade] Protocol Action: 'The Lemonade Profile' to Proposed Standard X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2009 16:23:55 -0000 The IESG has approved the following document: - 'The Lemonade Profile ' as a Proposed Standard This document is the product of the Enhancements to Internet email to Support Diverse Service Environments Working Group. The IESG contact persons are Chris Newman and Lisa Dusseault. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-profile-bis-12.txt Technical Summary This document describes a profile (a set of required extensions, restrictions and usage modes) of the IMAP and mail submission protocols. This profile allows clients (especially those that are constrained in memory, bandwidth, processing power, or other areas) to efficiently use IMAP and Submission to access and submit mail. This includes the ability to forward received mail without needing to download and upload the mail, to optimize submission and to efficiently resynchronize in case of loss of connectivity with the server. The Lemonade profile relies upon several extensions to IMAP and Mail Submission protocols. Working Group Summary There is WG consensus to publish this document. Document Quality This document has been through significant review by mail client and server vendors, often based on issues with implementing the profile, that has resulted in modified base documents and as a result modifications in this profile. In addition, the LEMONADE WG has had a liaison relationship with OMA MEM that has resulted in a vetting of the features to ensure that the profile is operationally useful. The final document is a result of a significant effort to ensure that the mobile email requirements are efficiently realized by Internet Mail. Personnel Glenn Parsons is the document shepherd. Chris Newman has reviewed this document for the IESG. Note to RFC Editor 1) Add "Updates: RFC 4469, RFC 4467" to the header 2) Change the second paragraph of the Abstract from: OLD: The Lemonade profile relies upon several extensions to IMAP and Mail Submission protocols. NEW: The Lemonade profile relies upon several extensions to IMAP, Sieve and Mail Submission protocols. The document also defines a new IMAP extension and registers several new IMAP keywords. 3) In section 7, please change the 2nd paragraph: OLD: Note that the explicit usage of [SUBMIT] means that when opening a connection to the submission server, clients MUST do so using port 587 unless explicitly configured to use an alternate port [RFC5068]. If the TCP connection to the submission server fails to open using port 587, the client MAY then immediately retry using a different port, such as 25. See [SUBMIT] information on why using port 25 is likely to fail depending on the current location of the client, and may result in a failure code during the SMTP transaction. NEW: When opening a connection to the submission server, clients MUST do so using port 587 unless explicitly configured to use an alternate port [RFC5068]. (Note that this requirement is somewhat stronger than the one specified in [SUBMIT], as [SUBMIT] didn't prescribe the exact procedure to be used by submission clients.) If the TCP connection to the submission server fails to open using port 587, the client MAY then immediately retry using a different port, such as 25. See [SUBMIT] for information on why using port 25 is likely to fail depending on the current location of the client, and may result in a failure code during the SMTP transaction. 4) Change the first paragraph of section 8 to read: OLD: Security considerations on Lemonade "forward without download" are discussed throughout Section 2. Additional security considerations can be found in [RFC3501] and other documents describing other SMTP and IMAP extensions comprising the Lemonade profile. NEW: Security considerations on Lemonade "forward without download" are discussed throughout Section 2. Additional security considerations can be found in [RFC3501], [SUBMIT], [SIEVE] and other documents ^^^^^^^^^^^^^^^^^^^ describing other SMTP, IMAP and Sieve extensions comprising the ^ ^^^^^^^^^ Lemonade profile. 5) In Section 8.4, change the 1st sentence of the 3rd paragraph to read: OLD: There are two ways to perform "forward without download" based on where the message assembly takes place. NEW: This section informatively describes two ways to perform "forward without download" based on where the message assembly takes place. 6) Replace section 12 with: 12. Changes since RFC 4550 When compared to RFC 4550, this document adds the following additional requirements on a Lemonade compliant IMAP server: A) IMAP extensions: BINARY, COMPRESS=DEFLATE, CONTEXT=SEARCH, CONTEXT=SORT, CONVERT, ENABLE, ESEARCH, ESORT, I18NLEVEL=1, NOTIFY, QRESYNC, SASL-IR, SORT, URL-PARTIAL; B) IMAP keywords: $SubmitPending, $Submitted. C) Other requirements: Require any Lemonade compliant IMAP server to support the CAPABILITY response code. When compared to RFC 4550, this document adds the following new requirements on a Lemonade compliant Message Delivery Agents: Support for the Sieve filtering language, together with the following Sieve extensions: ENOTIFY, IMAP4FLAGS, RELATIONAL, VACATION, VARIABLES, comparator-i;unicode-casemap. When compared to RFC 4550, this document recommends use of the DEFLATE compression method for TLS. All other requirements remain the same. Additionally, the following changes/improvments were done to RFC 4550 (the list might be incomplete): A new section with some additiona requirements on Lemonade Mail User Agents was added, in particular they are required to support Format=flowed parameter to to the text/plain media type. Usage of the $Forwarded IMAP keyword was clarified. Forward-without-download examples were corrected and extended. Added a new section describing in-band and out-of-band notifications from a Lemonade compliant mailstore. From wwwrun@core3.amsl.com Sun Mar 22 12:28:10 2009 Return-Path: X-Original-To: lemonade@ietf.org Delivered-To: lemonade@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 30) id E35233A6BAA; Sun, 22 Mar 2009 12:28:10 -0700 (PDT) X-idtracker: yes From: The IESG To: IETF-Announce Message-Id: <20090322192810.E35233A6BAA@core3.amsl.com> Date: Sun, 22 Mar 2009 12:28:10 -0700 (PDT) Cc: lemonade mailing list , lemonade chair , Internet Architecture Board , RFC Editor Subject: [lemonade] Protocol Action: 'Extended URLFETCH for binary and converted parts' to Proposed Standard X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2009 19:28:11 -0000 The IESG has approved the following document: - 'Extended URLFETCH for binary and converted parts ' as a Proposed Standard This document is the product of the Enhancements to Internet email to Support Diverse Service Environments Working Group. The IESG contact persons are Chris Newman and Lisa Dusseault. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-cridland-urlfetch-binary-03.txt Technical Summary The URLFETCH command defined as part of URLAUTH provides a mechanism for third-parties to gain access to data held within messages in a user's private store, however, this data is sent verbatim, which is not suitable for a number of applications. This memo specifies a method for obtaining data in forms suitable for non-mail applications. Working Group Summary There is consensus in the lemonade WG to publish this document. Document Quality The Lemonade WG has reviewed the document. The document has been checked manually and using idnits 2.08.10, and passed both checks. Personnel Eric Burger shepherds this document, has reviewed this document, and believes that this version is ready for forwarding to the IESG for publication. Chris Newman has reviewed this for the IESG. RFC Editor Replace the last 3 production of the ABNF with: url-meta-bodystruct = "BODYPARTSTRUCTURE" SP body url-meta-binary = "BINARY" SP ( nstring / literal8 ) ; If content contains a NUL octet, literal8 MUST be used. ; Otherwise, content SHOULD use nstring. ; On decoding error NIL should be used. url-meta-body = "BODY" SP nstring From root@core3.amsl.com Thu Mar 26 08:30:01 2009 Return-Path: X-Original-To: lemonade@ietf.org Delivered-To: lemonade@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 5149C3A6E07; Thu, 26 Mar 2009 08:30:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20090326153001.5149C3A6E07@core3.amsl.com> Date: Thu, 26 Mar 2009 08:30:01 -0700 (PDT) Cc: lemonade@ietf.org Subject: [lemonade] I-D ACTION:draft-ietf-lemonade-streaming-10.txt X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Mar 2009 15:30:01 -0000 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Enhancements to Internet email to Support Diverse Service Environments Working Group of the IETF. Title : Streaming Internet Messaging Attachments Author(s) : N. Cook Filename : draft-ietf-lemonade-streaming-10.txt Pages : 33 Date : 2009-3-26 This document describes a method for streaming multimedia attachments received by a resource constrained and/or mobile device from an IMAP server. It allows such clients, which often have limits in storage space and bandwidth, to play video and audio e-mail content. The document describes a profile for making use of the URLAUTH authorized IMAP URLs (RFC 5092), the Network Announcement SIP Media Service (RFC 4240), and the Media Server Control Markup Language (RFC 5022). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-lemonade-streaming-10.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-lemonade-streaming-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-3-26082615.I-D@ietf.org> --NextPart-- From eburger@standardstrack.com Fri Mar 27 09:32:07 2009 Return-Path: X-Original-To: lemonade@core3.amsl.com Delivered-To: lemonade@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C02A13A6CA1 for ; Fri, 27 Mar 2009 09:32:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.316 X-Spam-Level: X-Spam-Status: No, score=-2.316 tagged_above=-999 required=5 tests=[AWL=0.283, BAYES_00=-2.599] 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 c28oY5jD82m4 for ; Fri, 27 Mar 2009 09:32:06 -0700 (PDT) Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.252.251]) by core3.amsl.com (Postfix) with ESMTP id 1DFC928C1CC for ; Fri, 27 Mar 2009 09:32:02 -0700 (PDT) Received: from [130.129.99.253] (port=54170 helo=dhcp-63fd.meeting.ietf.org) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1LnEzE-0006qw-Ev for lemonade@ietf.org; Fri, 27 Mar 2009 09:32:52 -0700 Message-Id: <0CC4CD05-B2DA-4009-864C-906470D91B30@standardstrack.com> From: Eric Burger To: lemonade@ietf.org Content-Type: multipart/signed; boundary=Apple-Mail-25-18854708; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v930.3) Date: Fri, 27 Mar 2009 09:32:55 -0700 X-Mailer: Apple Mail (2.930.3) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - standardstrack.com X-Source: X-Source-Args: X-Source-Dir: Subject: [lemonade] Shepherd Write-Up: draft-ncook-urlauth-accessid-02 X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2009 16:32:07 -0000 --Apple-Mail-25-18854708 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Document: Internet Message Access Protocol (IMAP) - URL Access Identifier Extension draft-ncook-urlauth-accessid-02 (Standards Track) (1.a) Who is the Document Shepherd for this document? Has the Document Shepherd personally reviewed this version of the document and, in particular, does he or she believe this version is ready for forwarding to the IESG for publication? Eric Burger is the document shepherd. I have personally reviewed this version of the document, and it is ready for forwarding to the IESG for publication. (1.b) Has the document had adequate review both from key WG members and from key non-WG members? Does the Document Shepherd have any concerns about the depth or breadth of the reviews that have been performed? This document is an individual submission. However, the LEMONADE Work Group performed an open pseudo-last call review, including expert review by Alexey Melnikov, Dave Cridland, and Arnt Gulbrandsen. (1.c) Does the Document Shepherd have concerns that the document needs more review from a particular or broader perspective, e.g., security, operational complexity, someone familiar with AAA, internationalization or XML? None. (1.d) Does the Document Shepherd have any specific concerns or issues with this document that the Responsible Area Director and/or the IESG should be aware of? For example, perhaps he or she is uncomfortable with certain parts of the document, or has concerns whether there really is a need for it. In any event, if the WG has discussed those issues and has indicated that it still wishes to advance the document, detail those concerns here. Has an IPR disclosure related to this document been filed? If so, please include a reference to the disclosure and summarize the WG discussion and conclusion on this issue. None. (1.e) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? Strong consensus for publishing. This is a small update to URLAUTH (RFC 5092). (1.f) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise the areas of conflict in separate email messages to the Responsible Area Director. (It should be in a separate email because this questionnaire is entered into the ID Tracker.) None. (1.g) Has the Document Shepherd personally verified that the document satisfies all ID nits? (See http://www.ietf.org/ID-Checklist.html and http://tools.ietf.org/tools/idnits/). Boilerplate checks are not enough; this check needs to be thorough. Has the document met all formal review criteria it needs to, such as the MIB Doctor, media type and URI type reviews? Checked with ID nits 2.11.07. As this document incorporates some RFC 5092 text, the pre-RFC 5378 disclaimer is appropriate. (1.h) Has the document split its references into normative and informative? Are there normative references to documents that are not ready for advancement or are otherwise in an unclear state? If such normative references exist, what is the strategy for their completion? Are there normative references that are downward references, as described in [RFC3967]? If so, list these downward references to support the Area Director in the Last Call procedure for them [RFC3967]. The document splits the references. All Normative References are at least Proposed Standard. The Informative Reference is the Lemonade streaming draft, which has a Normative Reference on this document. Thus we hope to progress both documents at the same time. (1.i) Has the Document Shepherd verified that the document IANA consideration section exists and is consistent with the body of the document? If the document specifies protocol extensions, are reservations requested in appropriate IANA registries? Are the IANA registries clearly identified? If the document creates a new registry, does it define the proposed initial contents of the registry and an allocation procedure for future registrations? Does it suggest a reasonable name for the new registry? See [RFC5226]. If the document describes an Expert Review process has Shepherd conferred with the Responsible Area Director so that the IESG can appoint the needed Expert during the IESG Evaluation? Yes, and we have already had an IANA review. (1.j) Has the Document Shepherd verified that sections of the document that are written in a formal language, such as XML code, BNF rules, MIB definitions, etc., validate correctly in an automated checker? ABNF validated with Bill's ABNF Parser (1.k) The IESG approval announcement includes a Document Announcement Write-Up. Please provide such a Document Announcement Write-Up? Recent examples can be found in the "Action" announcements for approved documents. The approval announcement contains the following sections: Technical Summary The existing IMAP URL specification (RFC 5092) lists several identifiers and identifier prefixes, that can be used to restrict access to URLAUTH-generated URLs. However, these identifiers do not provide facilities for new services such as streaming. This document proposes a set of new identifiers as well as an IANA mechanism to register new identifiers for future applications. This document updates RFC 5092. Working Group Summary Nothing out of the ordinary happened in the WG to note. Document Quality This document received LEMONADE work group review and expert review. --Apple-Mail-25-18854708 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGPTCCBjkw ggUhoAMCAQICEC+VK1RLWxrF8KJZDR9k8p8wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYTAlVT MQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VS VFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQD Ey1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwwHhcNMDgwODEz MDAwMDAwWhcNMDkwODEzMjM1OTU5WjCB4TE1MDMGA1UECxMsQ29tb2RvIFRydXN0IE5ldHdvcmsg LSBQRVJTT05BIE5PVCBWQUxJREFURUQxRjBEBgNVBAsTPVRlcm1zIGFuZCBDb25kaXRpb25zIG9m IHVzZTogaHR0cDovL3d3dy5jb21vZG8ubmV0L3JlcG9zaXRvcnkxHzAdBgNVBAsTFihjKTIwMDMg Q29tb2RvIExpbWl0ZWQxFDASBgNVBAMTC0VyaWMgQnVyZ2VyMSkwJwYJKoZIhvcNAQkBFhplYnVy Z2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTF RRoA4LgOACMFph0aomRC/UpqoA5C/d6DUTOvTMrYSEqkjwnU4zxDtBcHlcB4AxKAov00MYsUvEU4 loz7BHjfDjv76AIkcwu33VYQbzGmarVnyaXsVb6f/cyRL3fPT0VOVO2tQAEEgwg//CX0jN8Kn2jH uXD/HEvko7cmpL3Pwevf3+DwB61v7ca79PpEZfn/WhaqRKA4uVNPj/JbieeaLo2v/0RJzrEElZK0 pHCqxiD3mQ8ossPkA9fUCSxLlbdMcPU3be5x8vt8Q8mYTXF5Z3d9RZmYrmNkvTQtdzVpfYWr/hgV Xqm9tByOOAR+hoN3FKbubR/OrAHL9yDAd4sCAwEAAaOCAhwwggIYMB8GA1UdIwQYMBaAFImCZ33E nSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBRDWgutb7b8R/L7G3Y3D+molAA3VzAOBgNVHQ8BAf8E BAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJ YIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEW HWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMIGlBgNVHR8EgZ0wgZowTKBKoEiGRmh0dHA6 Ly9jcmwuY29tb2RvY2EuY29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRF bWFpbC5jcmwwSqBIoEaGRGh0dHA6Ly9jcmwuY29tb2RvLm5ldC9VVE4tVVNFUkZpcnN0LUNsaWVu dEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMGwGCCsGAQUFBwEBBGAwXjA2BggrBgEFBQcwAoYq aHR0cDovL2NydC5jb21vZG9jYS5jb20vVVROQUFBQ2xpZW50Q0EuY3J0MCQGCCsGAQUFBzABhhho dHRwOi8vb2NzcC5jb21vZG9jYS5jb20wJQYDVR0RBB4wHIEaZWJ1cmdlckBzdGFuZGFyZHN0cmFj ay5jb20wDQYJKoZIhvcNAQEFBQADggEBAGeBR7NPCvrY3GQoIi49JOuciatY2r4st905Jw1etp6J umFFWlaCBl11tFSclk/3S45B+lUv3SEvG4CEjUByPScprVmCqHR+y8BAQaB/CV+N1y14x3MbhJ+Z 8XDGKeUXuuyGd9w0l3/t/QPid6TRXQjQFrLPFs1IALuNpNiFMHEF/xFbMG1Z2vznR/gSPlePekoZ TqcExIDBNZTBebpZqwAXzPpedNNOclbMLFLWDMOAozVRpkfjI0eiFsk8SF1Ho1Gb9Bx8DeG4peE2 KRVOR9FFnZZgBpFjXYRcglsMOSKCY8HgE+NGvbbqbrMoBV/BlYyxRXwfti71RL9Zs2Cq1eQxggP8 MIID+AIBATCBwzCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExh a2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8v d3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRp Y2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkNH2TynzAJBgUrDgMCGgUAoIICDTAYBgkqhkiG 9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTAzMjcxNjMyNTZaMCMGCSqGSIb3 DQEJBDEWBBQYIM/+koIE2r8K++Mu4+eBLAXaZjCB1AYJKwYBBAGCNxAEMYHGMIHDMIGuMQswCQYD VQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVU aGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2 MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhAv lStUS1saxfCiWQ0fZPKfMIHWBgsqhkiG9w0BCRACCzGBxqCBwzCBrjELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbAIQL5UrVEtbGsXwolkN H2TynzANBgkqhkiG9w0BAQEFAASCAQCrpyIvxGwfezN1pSDpFDfLwOZXAnyImwRXPAaT0Ui0XuCb zC9s+MAeRWiUbpKTZXWgClM1YM9I4ApUZWoKgyXYF64U/H797Puk3yIUg1d9ifdupzAGEN97bpT1 xYAaixSp1k5raa2KTW5BgP8qrpf4hgR6j/ZY9CvpTzjOYsUGHRqsV0snfH8I8pCkY+BtD13U4qtI 1NLsv2WvRdQGV5kqqVjrQI/8z6D41N7DjILxCVcUmZ5dcIAMVXvbQ00ja9W5bXleVb8aPaUR/m/i x4YNATP+QycINkJ7sS9nraqn+UohB39c2SnBtGl6HpsX7F4lD63eDTS/PAU3GPnvqu2FAAAAAAAA --Apple-Mail-25-18854708-- From rfc-editor@rfc-editor.org Fri Mar 27 14:59:49 2009 Return-Path: X-Original-To: lemonade@core3.amsl.com Delivered-To: lemonade@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBE0A3A6B67; Fri, 27 Mar 2009 14:59:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.918 X-Spam-Level: X-Spam-Status: No, score=-16.918 tagged_above=-999 required=5 tests=[AWL=0.081, 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 OyjH8HhMvBQO; Fri, 27 Mar 2009 14:59:49 -0700 (PDT) Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 10AD03A6905; Fri, 27 Mar 2009 14:59:49 -0700 (PDT) Received: by bosco.isi.edu (Postfix, from userid 70) id 4E398267867; Fri, 27 Mar 2009 15:00:26 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20090327220026.4E398267867@bosco.isi.edu> Date: Fri, 27 Mar 2009 15:00:26 -0700 (PDT) Cc: lemonade@ietf.org, rfc-editor@rfc-editor.org Subject: [lemonade] RFC 5423 on Internet Message Store Events X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2009 21:59:50 -0000 A new Request for Comments is now available in online RFC libraries. RFC 5423 Title: Internet Message Store Events Author: R. Gellens, C. Newman Status: Standards Track Date: March 2009 Mailbox: rg+ietf@qualcomm.com, chris.newman@sun.com Pages: 17 Characters: 34800 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lemonade-msgevent-07.txt URL: http://www.rfc-editor.org/rfc/rfc5423.txt One of the missing features in the existing Internet mail and messaging standards is a facility for server-to-server and server-to- client event notifications related to message store events. As the scope of Internet mail expands to support more diverse media (such as voice mail) and devices (such as cell phones) and to provide rich interactions with other services (such as web portals and legal compliance systems), the need for an interoperable notification system increases. This document attempts to enumerate the types of events that interest real-world consumers of such a system. This document describes events and event parameters that are useful for several cases, including notification to administrative systems and end users. This is not intended as a replacement for a message access facility such as IMAP. [STANDARDS TRACK] This document is a product of the Enhancements to Internet email to support diverse service environments 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 From web-usrn@ISI.EDU Mon Mar 30 00:32:26 2009 Return-Path: X-Original-To: lemonade@core3.amsl.com Delivered-To: lemonade@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 68FFA3A6A1F for ; Mon, 30 Mar 2009 00:32:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.219 X-Spam-Level: X-Spam-Status: No, score=-17.219 tagged_above=-999 required=5 tests=[AWL=0.380, BAYES_00=-2.599, 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 aCiCzU7234wn for ; Mon, 30 Mar 2009 00:32:25 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 6EE883A63EC for ; Mon, 30 Mar 2009 00:32:25 -0700 (PDT) Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n2U7WZgs014547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 30 Mar 2009 00:32:36 -0700 (PDT) Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n2U7WYkw014545; Mon, 30 Mar 2009 00:32:34 -0700 (PDT) Date: Mon, 30 Mar 2009 00:32:34 -0700 (PDT) Message-Id: <200903300732.n2U7WYkw014545@boreas.isi.edu> To: rg+ietf@qualcomm.com, chris.newman@sun.com, chris.newman@sun.com, Lisa.Dusseault@messagingarchitects.com, alexey.melnikov@isode.com, gparsons@nortel.com, eburger@standardstrack.com From: RFC Errata System X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: web-usrn@boreas.isi.edu Cc: lemonade@ietf.org, ah@TR-Sys.de, rfc-editor@rfc-editor.org Subject: [lemonade] [Technical Errata Reported] RFC5423 (1748) X-BeenThere: lemonade@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Enhancements to Internet email to support diverse service enivronments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2009 07:32:26 -0000 The following errata report has been submitted for RFC5423, "Internet Message Store Events". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5423&eid=1748 -------------------------------------- Type: Technical Reported by: Alfred Hoenes Section: 6, 3rd para Original Text ------------- Using IANA Considerations [RFC5226] terminology, entries that do not | start with "vnd." are allocated by IETF Consensus, while those starting with "vnd." are allocated First Come First Served. Corrected Text -------------- Using IANA Considerations [RFC5226] terminology, entries that do not | start with "vnd." are allocated by IETF Review, while those starting with "vnd." are allocated First Come First Served. Notes ----- Rationale: BCP 26, RFC 5226, does not define "IETF Consensus" any more; this term has been functionally replaced by "IETF Review". Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5423 (draft-ietf-lemonade-msgevent-07) -------------------------------------- Title : Internet Message Store Events Publication Date : March 2009 Author(s) : R. Gellens, C. Newman Category : PROPOSED STANDARD Source : Enhancements to Internet email to support diverse service environments Area : Applications Stream : IETF Verifying Party : IESG