idnits 2.17.1 draft-sparks-genarea-imaparch-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (Feb 21, 2012) is 4448 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-07) exists of draft-sparks-genarea-mailarch-04 -- Obsolete informational reference (is this intentional?): RFC 3501 (Obsoleted by RFC 9051) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Sparks 3 Internet-Draft Tekelec 4 Intended status: Informational Feb 21, 2012 5 Expires: August 24, 2012 7 IMAP Access to IETF Email List Archives 8 draft-sparks-genarea-imaparch-00 10 Abstract 12 The IETF makes heavy use of email lists to conduct its work. This 13 often involves accessing the archived history of those email lists. 14 Participants would like to have the ability to browse and search 15 those archives using standard IMAP clients. This memo captures the 16 requirements for providing a service that would allow such browsing 17 and searching. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on August 24, 2012. 36 Copyright Notice 38 Copyright (c) 2012 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. Requirements for IMAP access to archived IETF lists . . . . . . 3 55 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 56 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 57 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 58 6. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6.1. 00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 7. Informative References . . . . . . . . . . . . . . . . . . . . 4 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Introduction 65 The IETF makes heavy use of email lists to conduct its work. This 66 often involves accessing the archived history of those email lists. 67 Work is underway to improve the web-based browsing and searching of 68 these archives [I-D.sparks-genarea-mailarch]. Participants would 69 like to have the ability to browse and search those archives using 70 standard IMAP clients. This memo captures the requirements for 71 providing a service that would allow such browsing and searching. 73 Discussion of this memo should take place on the ietf@ietf.org 74 mailing list. 76 2. Requirements for IMAP access to archived IETF lists 78 Many participants would prefer to access the list archives using IMAP 79 [RFC3501]. Providing this access while meeting the following 80 requirements will likely require an IMAP server with specialized 81 capabilities. 83 o The system should expose the archive using an IMAP interface, with 84 each list represented as a mailbox. 86 o This interface must work with standard IMAP clients. 88 o The interface should allow users to each have their own read/ 89 unread marks for messages. Allowing other annotation is 90 desirable. 92 - If this requires the user to login, the system should use 93 datatracker login credentials 95 o The interface must have server-side searching enabled, and should 96 support multiple simultaneous extensive searches. The server 97 should facilitate the enhanced search capabilities described in 98 [I-D.sparks-genarea-mailarch] 100 3. Security Considerations 102 Allowing IMAP as an interface for browsing and searching the archives 103 of IETF email lists does not affect the security of the Internet in 104 any significant fashion. 106 4. IANA Considerations 108 This document has no actions for IANA. 110 5. Acknowledgements 112 This text was derived directly from an earlier version of 113 [I-D.sparks-genarea-mailarch] which incorporated text suggestions 114 from Alexey Melnikov, Pete Resnick, and S. Moonesamy. 116 6. Changelog 118 6.1. 00 120 1. Split this set of requirements out from the mailarch doc so that 121 this project could be pursued separately 123 7. Informative References 125 [I-D.sparks-genarea-mailarch] 126 Sparks, R., "IETF Email List Archiving and Search Tool 127 Requirements", draft-sparks-genarea-mailarch-04 (work in 128 progress), February 2012. 130 [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 131 4rev1", RFC 3501, March 2003. 133 Author's Address 135 Robert Sparks 136 Tekelec 137 17210 Campbell Road 138 Suite 250 139 Dallas, Texas 75254-4203 140 USA 142 Email: RjS@nostrum.com