Moving mailserver: URI Scheme to Historic

Internet Engineering Task Force (IETF)                       A. Melnikov
Request for Comments: 6196                                 Isode Limited
Updates: <a href="./rfc1738">1738</a>                                                 March 2011
Category: Standards Track
ISSN: 2070-1721


               <span class="h1">Moving mailserver: URI Scheme to Historic</span>

Abstract

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

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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc6196">http://www.rfc-editor.org/info/rfc6196</a>.

Copyright Notice

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

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.









<span class="grey">Melnikov                     Standards Track                    [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc6196">RFC 6196</a>        Moving mailserver: URI Scheme to Historic     March 2011</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction and Overview .......................................<a href="#page-2">2</a>
   <a href="#section-2">2</a>. Security Considerations .........................................<a href="#page-2">2</a>
   <a href="#section-3">3</a>. IANA Considerations .............................................<a href="#page-2">2</a>
   <a href="#section-4">4</a>. References ......................................................<a href="#page-3">3</a>
      <a href="#section-4.1">4.1</a>. Normative References .......................................<a href="#page-3">3</a>
      <a href="#section-4.2">4.2</a>. Informative References .....................................<a href="#page-3">3</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction and Overview</span>

   <a href="./rfc1738">RFC 1738</a> [<a href="./rfc1738" title=""Uniform Resource Locators (URL)"">RFC1738</a>] registers the mailserver: URI scheme as
   provisional in the IANA URI registry defined by [<a href="./rfc4395" title=""Guidelines and Registration Procedures for New URI Schemes"">RFC4395</a>], 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.

   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 [<a href="./rfc5322" title=""Internet Message Format"">RFC5322</a>] message can instead use the mailto: URI scheme
   [<a href="./rfc6068" title=""The 'mailto' URI Scheme"">RFC6068</a>].  Implementors interested in referencing a message or a set
   of messages available from a mailstore over IMAP [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>], POP
   [<a href="./rfc1939" title=""Post Office Protocol - Version 3"">RFC1939</a>], or web [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>] can instead use the imap: [<a href="./rfc5092" title=""IMAP URL Scheme"">RFC5092</a>], pop:
   [<a href="./rfc2384" title=""POP URL Scheme"">RFC2384</a>] or http: [<a href="./rfc2616" title=""Hypertext Transfer Protocol -- HTTP/1.1"">RFC2616</a>] URIs, respectively.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Security Considerations</span>

   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.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  IANA Considerations</span>

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







<span class="grey">Melnikov                     Standards Track                    [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc6196">RFC 6196</a>        Moving mailserver: URI Scheme to Historic     March 2011</span>


<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  References</span>

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  Normative References</span>

   [<a id="ref-RFC4395">RFC4395</a>]  Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
              Registration Procedures for New URI Schemes", <a href="https://www.rfc-editor.org/bcp/bcp35">BCP 35</a>,
              <a href="./rfc4395">RFC 4395</a>, February 2006.

<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Informative References</span>

   [<a id="ref-RFC1738">RFC1738</a>]  Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
              Resource Locators (URL)", <a href="./rfc1738">RFC 1738</a>, December 1994.

   [<a id="ref-RFC1939">RFC1939</a>]  Myers, J. and M. Rose, "Post Office Protocol - Version 3",
              STD 53, <a href="./rfc1939">RFC 1939</a>, May 1996.

   [<a id="ref-RFC2384">RFC2384</a>]  Gellens, R., "POP URL Scheme", <a href="./rfc2384">RFC 2384</a>, August 1998.

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

   [<a id="ref-RFC3501">RFC3501</a>]  Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
              4rev1", <a href="./rfc3501">RFC 3501</a>, March 2003.

   [<a id="ref-RFC5092">RFC5092</a>]  Melnikov, A. and C. Newman, "IMAP URL Scheme", <a href="./rfc5092">RFC 5092</a>,
              November 2007.

   [<a id="ref-RFC5322">RFC5322</a>]  Resnick, P., Ed., "Internet Message Format", <a href="./rfc5322">RFC 5322</a>,
              October 2008.

   [<a id="ref-RFC6068">RFC6068</a>]  Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto'
              URI Scheme", <a href="./rfc6068">RFC 6068</a>, October 2010.

Author's Address

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

   EMail: [email protected]







Melnikov                     Standards Track                    [Page 3]