idnits 2.17.1 draft-sparks-genarea-imaparch-05.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 (Mar 26, 2013) is 4042 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 3501 (Obsoleted by RFC 9051) -- Obsolete informational reference (is this intentional?): RFC 6237 (Obsoleted by RFC 7377) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 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 Mar 26, 2013 5 Expires: September 27, 2013 7 IMAP Access to IETF Email List Archives 8 draft-sparks-genarea-imaparch-05 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 September 27, 2013. 36 Copyright Notice 38 Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . 4 56 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 57 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4 58 6. Changelog . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 6.1. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 6.2. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 6.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 6.4. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 6.5. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . . 5 64 6.6. 00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 65 7. Informative References . . . . . . . . . . . . . . . . . . . . 5 66 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 68 1. Introduction 70 The IETF makes heavy use of email lists to conduct its work. This 71 often involves accessing the archived history of those email lists. 72 Requirements for improved web-based browsing and searching of these 73 archives are captured in [RFC6778]. Participants would like to have 74 the ability to browse and search those archives using standard IMAP 75 clients. This memo captures the requirements for providing a service 76 that would allow such browsing and searching. 78 Discussion of this memo should take place on the ietf@ietf.org 79 mailing list. 81 2. Requirements for IMAP access to archived IETF lists 83 Many participants would prefer to access the list archives using IMAP 84 [RFC3501]. Providing this access while meeting the following 85 requirements will likely require an IMAP server with specialized 86 capabilities. 88 o The system should expose the archive using an IMAP interface, with 89 each list represented as a mailbox. 91 o This interface must work with standard IMAP clients. 93 o The interface should allow users that have provided credentials to 94 each have their own read/unread marks for messages. Allowing 95 other annotation is desirable. The implementation should consider 96 taking advantage of the IMAP extensions for ANNOTATE [RFC5257] and 97 METADATA [RFC5464]. 99 o The interface must have server-side searching enabled, and should 100 support multiple simultaneous extensive searches. The server 101 should facilitate the enhanced search capabilities described in 102 [RFC6778]. The implementation should consider taking advantage of 103 the extensions defined for IMAP SORT and THREAD [RFC5256], 104 multimailbox search [RFC6237], and fuzzy search [RFC6203]. 106 o When the system requires credentials, it must use the 107 datatracker's authentication system 109 - While the vast majority of archived lists have an open access 110 policy, some archived lists have restricted archives. The 111 system must make it possible to limit access to a restricted 112 archive based on login credentials. 114 - The system must not require credentials for accessing lists 115 with open archives. (But it is acceptable for a user to access 116 such archives while providing credentials). 118 3. Security Considerations 120 Allowing IMAP as an interface for browsing and searching the archives 121 of IETF email lists does not affect the security of the Internet in 122 any significant fashion. 124 4. IANA Considerations 126 This document has no actions for IANA. 128 5. Acknowledgements 130 This text was derived directly from an early version of the Internet 131 Draft that became [RFC6778] which incorporated text suggestions from 132 Alexey Melnikov, Pete Resnick, and S. Moonesamy. Barry Leiba 133 suggested several references to IMAP extensions for an implementation 134 to consider. 136 6. Changelog 138 6.1. 04 to 05 140 o Adapted text from RFC6778 to make it more clear that both 141 authenticated and unauthenticated access should be supported. 143 6.2. 03 to 04 145 o Incorporated suggestions from Pete Resnick and Barry Leiba. 147 6.3. 02 to 03 149 o None - expiry refresh 151 6.4. 01 to 02 153 o Minor editorial changes 155 6.5. 00 to 01 157 o Added requirements to enable controlled access to restricted 158 archives based on credentials 160 o Generalized the requirement to use the datatracker's credentials. 162 6.6. 00 164 o Split this set of requirements out from the mailarch doc so that 165 this project could be pursued separately 167 7. Informative References 169 [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 170 4rev1", RFC 3501, March 2003. 172 [RFC5256] Crispin, M. and K. Murchison, "Internet Message Access 173 Protocol - SORT and THREAD Extensions", RFC 5256, 174 June 2008. 176 [RFC5257] Daboo, C. and R. Gellens, "Internet Message Access 177 Protocol - ANNOTATE Extension", RFC 5257, June 2008. 179 [RFC5464] Daboo, C., "The IMAP METADATA Extension", RFC 5464, 180 February 2009. 182 [RFC6203] Sirainen, T., "IMAP4 Extension for Fuzzy Search", 183 RFC 6203, March 2011. 185 [RFC6237] Leiba, B. and A. Melnikov, "IMAP4 Multimailbox SEARCH 186 Extension", RFC 6237, May 2011. 188 [RFC6778] Sparks, R., "Requirements for Archiving IETF Email Lists 189 and for Providing Web-Based Browsing and Searching", 190 RFC 6778, October 2012. 192 Author's Address 194 Robert Sparks 195 Tekelec 196 17210 Campbell Road 197 Suite 250 198 Dallas, Texas 75254-4203 199 USA 201 Email: rjsparks@nostrum.com