IMAP Access to IETF Email List Archives
draft-sparks-genarea-imaparch-08

Abstract

The IETF makes heavy use of email lists to conduct its work. This often involves accessing the archived history of those email lists. Participants would like to have the ability to browse and search those archives using standard IMAP clients. This memo captures the requirements for providing a service that would allow such browsing and searching, and it is intended as input to a later activity for the design and development of such a service.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on January 16, 2014.

Copyright Notice

Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. Requirements for IMAP access to archived IETF lists
• 3. Internationalized Address Considerations
• 4. Security Considerations
• 5. IANA Considerations
• 6. Acknowledgements
• 7. Changelog
• 7.1. 06 to 07
• 7.2. 05 to 06
• 7.3. 04 to 05
• 7.4. 03 to 04
• 7.5. 02 to 03
• 7.6. 01 to 02
• 7.7. 00 to 01
• 7.8. 00
• 8. Informative References
• Author's Address

1. Introduction

The IETF makes heavy use of email lists to conduct its work. This often involves accessing the archived history of those email lists. Requirements for improved web-based browsing and searching of these archives are captured in [RFC6778]. Participants would like to have the ability to browse and search those archives using standard IMAP clients. This memo captures the requirements for providing a service that would allow such browsing and searching, and it is intended as input to a later activity for the design and development of such a service.

2. Requirements for IMAP access to archived IETF lists

Many participants would prefer to access the list archives using IMAP [RFC3501]. Providing this access while meeting the following requirements will likely require an IMAP server with specialized capabilities.

o

The system should expose the archive using an IMAP interface, with each list represented as a mailbox.

o

This interface must work with standard IMAP clients.

o

The interface should allow users that have provided credentials to each have their own read/unread marks for messages. Allowing other annotation is desirable. The implementation should consider taking advantage of the IMAP extensions for ANNOTATE [RFC5257] and METADATA [RFC5464].

o

It must be possible for administrators to set per-user storage quotas, limiting the space a user can consume with annotations.

o

The interface must not allow users to modify the underlying message or metadata other than the read/unread marks and annotations described above. Specifically, users must not be able to delete or insert messages, or move them between mailboxes in the archive. (Clients will, of course, be able to make local copies of messages from the archive.)

o

The interface must have server-side searching enabled, and should scale to support multiple simultaneous extensive searches. The server should provide the enhanced search capabilities described in [RFC6778]. The implementation should consider taking advantage of the extensions defined for IMAP SORT and THREAD [RFC5256], multimailbox search [RFC6237], and fuzzy search [RFC6203].

o

When the system requires credentials, it must use the datatracker's authentication system

-

While the vast majority of archived lists have an open access policy, some archived lists have restricted archives. The system must make it possible to limit access to a restricted archive based on login credentials.

-

The system must allow access to open archives with or without providing credentials. Specifically, the system will allow anonymous access using the SASL ANONYMOUS authentication mechanism [RFC4505] or a LOGIN command with a special username (such as "anonymous") determined by the administrator.

3. Internationalized Address Considerations

The implementation should anticipate internationalized email addresses as discussed in the following three documents [RFC6532] [RFC6531] [RFC6855]. There is no firm requirement at this time.

4. Security Considerations

Allowing IMAP as an interface for browsing and searching the archives of IETF email lists does not affect the security of the Internet in any significant fashion.

Searching can be I/O and CPU intensive. Clients that make local copies of all messages in a mailbox can also present an I/O burden, particularly when syncronizing for the first time. The implementors of this interface should consider the potential for maliciously crafted searches attempting to consume a damaging amount of resources. The implementors should consider the potential for denial of service attacks through making many connections to the interface. The implementors should consider ways to rate limit I/O due to making local copies of messages.

Storing read/unread marks and other annotations requires potentially unbounded storage space. The implementors of this interface should consider the potential for maliciously crafted annontations attempting to consume a damaging amount of storage space. The implementers should consider making it easy to alert the administrator when a user begins consuming exceptional amounts of space.

5. IANA Considerations

This document has no actions for IANA.

6. Acknowledgements

This text was derived directly from an early version of the Internet Draft that became [RFC6778] which incorporated text suggestions from Alexey Melnikov, Pete Resnick, and S. Moonesamy. Barry Leiba suggested several references to IMAP extensions for an implementation to consider. Reviews were provided by Martin Duerst, Carl Wallace, Wassim Haddad, and Juergen Schoenwaelder.

7. Changelog

7.1. 06 to 07

• Editorial tweaks and clarifications based on IETF LC reviews.

7.2. 05 to 06

• Added a requirement making it explicit that this interface won't allow users to delete, insert, or move messages between archives.
• Clarified how the would allow access without credentials (at Alexey's suggestion).
• Pointed to potential resource abuse issues in the security considerations section.

7.3. 04 to 05

• Adapted text from RFC6778 to make it more clear that both authenticated and unauthenticated access should be supported.

7.4. 03 to 04

• Incorporated suggestions from Pete Resnick and Barry Leiba.

7.5. 02 to 03

• None - expiry refresh

7.6. 01 to 02

• Minor editorial changes

7.7. 00 to 01

• Added requirements to enable controlled access to restricted archives based on credentials
• Generalized the requirement to use the datatracker's credentials.

7.8. 00

• Split this set of requirements out from the mailarch doc so that this project could be pursued separately

8. Informative References

Author's Address