Internet Engineering Task Force (IETF)                       A. Melnikov
Request for Comments: 6196                                 Isode Limited
Updates: 1738                                                 March 2011
Category: Standards Track
ISSN: 2070-1721
        
Internet Engineering Task Force (IETF)                       A. Melnikov
Request for Comments: 6196                                 Isode Limited
Updates: 1738                                                 March 2011
Category: Standards Track
ISSN: 2070-1721

Moving mailserver: URI Scheme to Historic

将mailserver:URI方案移动到历史

Abstract

摘要

This document registers the mailserver: URI scheme as historic in the IANA URI registry.

本文档在IANAURI注册表中将mailserver:URI方案注册为历史。

Status of This Memo

关于下段备忘

This is an Internet Standards Track document.

这是一份互联网标准跟踪文件。

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). Further information on Internet Standards is available in Section 2 of RFC 5741.

本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（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/rfc6196.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6196.

Copyright Notice

版权公告

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

版权所有（c）2011 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 and Overview .......................................2
   2. Security Considerations .........................................2
   3. IANA Considerations .............................................2
   4. References ......................................................3
      4.1. Normative References .......................................3
      4.2. Informative References .....................................3
        
   1. Introduction and Overview .......................................2
   2. Security Considerations .........................................2
   3. IANA Considerations .............................................2
   4. References ......................................................3
      4.1. Normative References .......................................3
      4.2. Informative References .....................................3
1. Introduction and Overview
1. 导言和概述

RFC 1738 [RFC1738] registers the mailserver: URI scheme as provisional in the IANA URI registry defined by [RFC4395], defining it as "Access to data available from mail servers" with no further details provided. The author of this document is not aware of any other more detailed definition of the mailserver: URI scheme. The mailserver: URI scheme as currently specified is not interoperable. There is a small risk that somebody would decide to implement this scheme by looking at IANA's URI scheme registry, possibly inventing some undocumented syntax for it. In order to minimize such risk, this document discourages any future implementations of this URI scheme and asks IANA to mark it as Historic in the URI scheme registry.

RFC 1738[RFC1738]在[RFC4395]定义的IANA URI注册表中将mailserver:URI方案注册为临时方案，并将其定义为“从邮件服务器访问可用数据”，无需提供更多详细信息。本文作者不知道mailserver:URI方案的任何其他更详细的定义。当前指定的mailserver:URI方案不可互操作。有一个小风险是，有人会决定通过查看IANA的URI方案注册表来实现这个方案，可能会为它发明一些未记录的语法。为了将此类风险降至最低，本文档不鼓励该URI方案的任何未来实现，并要求IANA在URI方案注册表中将其标记为历史。 

   There were some previous attempts to provide detailed documentation
   of the mailserver: URI scheme, but those efforts were not successful.
   Implementors interested in providing instructions for generating an
   email [RFC5322] message can instead use the mailto: URI scheme
   [RFC6068].  Implementors interested in referencing a message or a set
   of messages available from a mailstore over IMAP [RFC3501], POP
   [RFC1939], or web [RFC2616] can instead use the imap: [RFC5092], pop:
   [RFC2384] or http: [RFC2616] URIs, respectively.
        
   There were some previous attempts to provide detailed documentation
   of the mailserver: URI scheme, but those efforts were not successful.
   Implementors interested in providing instructions for generating an
   email [RFC5322] message can instead use the mailto: URI scheme
   [RFC6068].  Implementors interested in referencing a message or a set
   of messages available from a mailstore over IMAP [RFC3501], POP
   [RFC1939], or web [RFC2616] can instead use the imap: [RFC5092], pop:
   [RFC2384] or http: [RFC2616] URIs, respectively.
2. Security Considerations
2. 安全考虑

In the past, the mailserver: URI scheme was never properly documented and thus doesn't interoperate. There are no known implementations of this URI scheme.

在过去，mailserver:URI方案从未正确记录，因此无法进行互操作。此URI方案没有已知的实现。

3. IANA Considerations
3. IANA考虑

IANA has re-registered the mailserver: URI scheme as Historic in the URI scheme registry and updated the reference to point to this document.

IANA已在URI方案注册表中将mailserver:URI方案重新注册为历史方案，并更新了指向此文档的引用。

4. References
4. 工具书类
4.1. Normative References
4.1. 规范性引用文件

[RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Registration Procedures for New URI Schemes", BCP 35, RFC 4395, February 2006.

[RFC4395]Hansen，T.，Hardie，T.，和L.Masinter，“新URI方案的指南和注册程序”，BCP 35，RFC 4395，2006年2月。

4.2. Informative References
4.2. 资料性引用

[RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.

[RFC1738]Berners Lee，T.，Masinter，L.，和M.McCahill，“统一资源定位器（URL）”，RFC 17381994年12月。

[RFC1939] Myers, J. and M. Rose, "Post Office Protocol - Version 3", STD 53, RFC 1939, May 1996.

[RFC1939]迈尔斯，J.和M.罗斯，“邮局协议-第3版”，STD 53，RFC 1939，1996年5月。

[RFC2384] Gellens, R., "POP URL Scheme", RFC 2384, August 1998.

[RFC2384]Gellens，R.，“POP URL方案”，RFC 2384，1998年8月。

[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.

[RFC2616]菲尔丁，R.，盖蒂斯，J.，莫卧儿，J.，弗莱斯蒂克，H.，马斯特，L.，利奇，P.，和T.伯纳斯李，“超文本传输协议——HTTP/1.1”，RFC 2616，1999年6月。

[RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1", RFC 3501, March 2003.

[RFC3501]Crispin，M.，“互联网消息访问协议-版本4rev1”，RFC 35012003年3月。

[RFC5092] Melnikov, A. and C. Newman, "IMAP URL Scheme", RFC 5092, November 2007.

[RFC5092]Melnikov，A.和C.Newman，“IMAP URL方案”，RFC 5092，2007年11月。

[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, October 2008.

[RFC5322]Resnick，P.，Ed.“互联网信息格式”，RFC5222008年10月。

[RFC6068] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' URI Scheme", RFC 6068, October 2010.

[RFC6068]Duerst，M.，Masinter，L.，和J.Zawinski，“mailto”URI方案”，RFC 6068，2010年10月。

Author's Address

作者地址

Alexey Melnikov Isode Limited 5 Castle Business Village 36 Station Road Hampton, Middlesex TW12 2BX UK

英国米德尔塞克斯郡汉普顿车站路36号城堡商业村5号Alexey Melnikov Isode Limited TW12 2BX 

   EMail: Alexey.Melnikov@isode.com
        
   EMail: Alexey.Melnikov@isode.com