Internet Engineering Task Force (IETF) R. Sparks
Request for Comments: 7017 Oracle
Category: Informational August 2013
ISSN: 2070-1721
Internet Engineering Task Force (IETF) R. Sparks
Request for Comments: 7017 Oracle
Category: Informational August 2013
ISSN: 2070-1721
IMAP Access to IETF Email List Archives
IMAP访问IETF电子邮件列表存档
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.
IETF大量使用电子邮件列表来开展工作。这通常涉及访问这些电子邮件列表的存档历史记录。参与者希望能够使用标准IMAP客户端浏览和搜索这些档案。此备忘录捕获了提供允许此类浏览和搜索的服务的要求，旨在作为设计和开发此类服务的后续活动的输入。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7017.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7017.
Copyright Notice
版权公告
Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2013 IETF信托基金和确定为文件作者的人员。版权所有。
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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements for IMAP Access to Archived IETF Lists . . . . . 2
3. Internationalized Address Considerations . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
6. Informative References . . . . . . . . . . . . . . . . . . . 4
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements for IMAP Access to Archived IETF Lists . . . . . 2
3. Internationalized Address Considerations . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 3
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
6. Informative References . . . . . . . . . . . . . . . . . . . 4
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.
IETF大量使用电子邮件列表来开展工作。这通常涉及访问这些电子邮件列表的存档历史记录。[RFC6778]中描述了改进基于web的浏览和搜索这些档案的要求。参与者希望能够使用标准IMAP客户端浏览和搜索这些档案。此备忘录捕获了提供允许此类浏览和搜索的服务的要求，旨在作为设计和开发此类服务的后续活动的输入。
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.
许多参与者希望使用IMAP[RFC3501]访问列表存档。在满足以下要求的同时提供此访问可能需要具有专门功能的IMAP服务器。
o The system should expose the archive using an IMAP interface, with each list represented as a mailbox.
o 系统应使用IMAP接口公开存档，每个列表表示为邮箱。
o This interface must work with standard IMAP clients.
o 此接口必须与标准IMAP客户端配合使用。
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 该界面应允许向每个用户提供凭据的用户都有自己的消息读/未读标记。允许其他注释是可取的。实现应该考虑利用IMAP扩展来注释[RCF5257]和元数据[RFC5664 ]。
o It must be possible for administrators to set per-user storage quotas, limiting the space a user can consume with annotations.
o 管理员必须能够设置每个用户的存储配额，从而限制用户使用注释所能占用的空间。
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 界面不得允许用户修改除上述已读/未读标记和注释之外的底层消息或元数据。特别是，用户不能删除或插入邮件，也不能在存档中的邮箱之间移动邮件。（当然，客户端将能够从存档中制作邮件的本地副本。）
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 该接口必须启用服务器端搜索，并应扩展以支持多个同时的广泛搜索。服务器应提供[RFC6778]中所述的增强搜索功能。实现应该考虑利用IMAP排序和线程[RCF5256]、多邮箱搜索[RFC627]和模糊搜索[RCF6203]定义的扩展。
o When the system requires credentials, it must use the datatracker's authentication system.
o 当系统需要凭据时，它必须使用datatracker的身份验证系统。
- 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 Simple Authentication and Security Layer (SASL) ANONYMOUS mechanism [RFC4505] or a LOGIN command with a special username (such as "anonymous") determined by the administrator.
- 系统必须允许在提供或不提供凭据的情况下访问打开的存档。具体而言，系统将允许使用简单身份验证和安全层（SASL）匿名机制[RFC4505]或具有管理员确定的特殊用户名（如“匿名”）的登录命令进行匿名访问。
The implementation should anticipate internationalized email addresses as discussed in the following three documents: [RFC6532], [RFC6531], and [RFC6855]. There is no firm requirement at this time.
实现应预期国际化电子邮件地址，如以下三个文档中所述：[RFC6532]、[RFC6531]和[RFC6855]。目前没有明确的要求。
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.
允许IMAP作为浏览和搜索IETF电子邮件列表档案的界面不会以任何显著方式影响互联网的安全。
Searching can be input/output (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 synchronizing 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.
搜索可以是输入/输出（I/O）和CPU密集型的。为邮箱中的所有邮件制作本地副本的客户端也可能带来I/O负担，尤其是在首次同步时。这个接口的实现者应该考虑恶意搜索的潜在企图消耗有害的资源量。实现者应该考虑通过与接口进行许多连接来拒绝拒绝服务攻击的可能性。实现者应该考虑由于制作本地消息副本而限制I/O的方法。
Storing read/unread marks and other annotations requires potentially unbounded storage space. The implementors of this interface should consider the potential for maliciously crafted annotations attempting to consume a damaging amount of storage space. The implementors should consider making it easy to alert the administrator when a user begins consuming exceptional amounts of space.
存储读/未读标记和其他注释可能需要无限的存储空间。该接口的实现者应该考虑恶意篡改的注释试图消耗破坏性的存储空间的可能性。实现者应该考虑在用户开始消耗额外数量的空间时，容易提醒管理员。
This text was derived directly from an early version of the document 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.
该文本直接来源于文件的早期版本，即[RFC6778]，其中包含了Alexey Melnikov、Pete Resnick和S.Moonesay的文本建议。Barry Leiba提出了一些关于IMAP扩展的参考，以供考虑。评论由Martin Duerst、Carl Wallace、Wassim Haddad和Juergen Schoenwaeld提供。
[RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1", RFC 3501, March 2003.
[RFC3501]Crispin，M.，“互联网消息访问协议-版本4rev1”，RFC 35012003年3月。
[RFC4505] Zeilenga, K., "Anonymous Simple Authentication and Security Layer (SASL) Mechanism", RFC 4505, June 2006.
[RFC4505]Zeilenga，K.，“匿名简单身份验证和安全层（SASL）机制”，RFC4505，2006年6月。
[RFC5256] Crispin, M. and K. Murchison, "Internet Message Access Protocol - SORT and THREAD Extensions", RFC 5256, June 2008.
[RFC5256]Crispin，M.和K.Murchison，“互联网消息访问协议-排序和线程扩展”，RFC 5256，2008年6月。
[RFC5257] Daboo, C. and R. Gellens, "Internet Message Access Protocol - ANNOTATE Extension", RFC 5257, June 2008.
[RFC5257]Daboo，C.和R.Gellens，“互联网消息访问协议-注释扩展”，RFC 5257，2008年6月。
[RFC5464] Daboo, C., "The IMAP METADATA Extension", RFC 5464, February 2009.
[RFC5464]Daboo，C.，“IMAP元数据扩展”，RFC 5464，2009年2月。
[RFC6203] Sirainen, T., "IMAP4 Extension for Fuzzy Search", RFC 6203, March 2011.
[RFC6203]Sirainen，T.，“模糊搜索的IMAP4扩展”，RFC62032011年3月。
[RFC6237] Leiba, B. and A. Melnikov, "IMAP4 Multimailbox SEARCH Extension", RFC 6237, May 2011.
[RFC6237]Leiba，B.和A.Melnikov，“IMAP4多邮箱搜索扩展”，RFC 6237，2011年5月。
[RFC6531] Yao, J. and W. Mao, "SMTP Extension for Internationalized Email", RFC 6531, February 2012.
[RFC6531]Yao，J.和W.Mao，“国际化电子邮件的SMTP扩展”，RFC 65312012年2月。
[RFC6532] Yang, A., Steele, S., and N. Freed, "Internationalized Email Headers", RFC 6532, February 2012.
[RFC6532]Yang，A.，Steele，S.，和N.Freed，“国际化电子邮件标题”，RFC 6532，2012年2月。
[RFC6778] Sparks, R., "Requirements for Archiving IETF Email Lists and for Providing Web-Based Browsing and Searching", RFC 6778, October 2012.
[RFC6778]Sparks，R.“存档IETF电子邮件列表和提供基于Web的浏览和搜索的要求”，RFC 6778，2012年10月。
[RFC6855] Resnick, P., Newman, C., and S. Shen, "IMAP Support for UTF-8", RFC 6855, March 2013.
[RFC6855]Resnick，P.，Newman，C.，和S.Shen，“UTF-8的IMAP支持”，RFC 68552013年3月。
Author's Address
作者地址
Robert Sparks Oracle 17210 Campbell Road Suite 250 Dallas, Texas 75254-4203 USA
美国德克萨斯州达拉斯市坎贝尔路250号17210室，邮编75254-4203
EMail: rjsparks@nostrum.com
EMail: rjsparks@nostrum.com