idnits 2.17.1 draft-melnikov-mailserver-uri-to-historic-00.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 (November 16, 2010) is 4903 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 4395 (Obsoleted by RFC 7595) -- Obsolete informational reference (is this intentional?): RFC 1738 (Obsoleted by RFC 4248, RFC 4266) -- Obsolete informational reference (is this intentional?): RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) -- Obsolete informational reference (is this intentional?): RFC 3501 (Obsoleted by RFC 9051) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Melnikov 3 Internet-Draft Isode Limited 4 Intended status: Standards Track November 16, 2010 5 Expires: May 20, 2011 7 Moving mailserver: URI scheme to historic 8 draft-melnikov-mailserver-uri-to-historic-00 10 Abstract 12 This document registers the mailserver: URI scheme as historic in the 13 IANA URI registry. 15 Status of this Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on May 20, 2011. 32 Copyright Notice 34 Copyright (c) 2010 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction and overview . . . . . . . . . . . . . . . . . . 3 50 2. Security Considerations . . . . . . . . . . . . . . . . . . . 3 51 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 52 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 4.1. Normative References . . . . . . . . . . . . . . . . . . . . 3 54 4.2. Informative References . . . . . . . . . . . . . . . . . . . 3 55 Author's Address . . . . . . . . . . . . . . . . . . . . . . 4 57 1. Introduction and overview 59 RFC 1738 [RFC1738] registers the mailserver URI scheme as provisional 60 in the IANA URI registry defined by [RFC4395], defining it as "Access 61 to data available from mail servers" with no further details 62 provided. The author of this document is not aware of any other more 63 detailed definition of the mailserver URI scheme. The mailserver URI 64 scheme as currently specified is not interoperable. There is a small 65 risk that somebody would decide to implement this scheme by looking 66 at the IANA's URI scheme registry, possibly inventing some 67 undocumented syntax for it. In order to minimize such risk this 68 document discourages any future implementations of this URI scheme 69 and asks IANA to mark it as Historic in the URI scheme registry. 71 There were some previous attempts to provide detailed documentation 72 of the mailserver URI scheme, but those efforts were not successful. 73 Implementors interested in providing instructions for generating an 74 email [RFC5322] message can instead use the mailto: URI scheme 75 [mailto]. Implementors interested in referencing a message or a set 76 of messages available from a mailstore over IMAP [RFC3501], POP 77 [RFC1939] or web [RFC2616] can instead use the imap: [RFC5092], pop: 78 [RFC2384] or http: [RFC2616] URIs respectively. 80 2. Security Considerations 82 In the past the mailserver URI scheme was never properly documented 83 and thus doesn't interoperate. There are no known implementations of 84 this URI scheme. 86 3. IANA Considerations 88 This document asks IANA to re-register the mailserver URI scheme as 89 Historic in the URI scheme registry, updating the reference to point 90 to this document. 92 4. References 94 4.1. Normative References 96 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 97 Registration Procedures for New URI Schemes", BCP 35, 98 RFC 4395, February 2006. 100 4.2. Informative References 102 [RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform 103 Resource Locators (URL)", RFC 1738, December 1994. 105 [RFC1939] Myers, J. and M. Rose, "Post Office Protocol - Version 3", 106 STD 53, RFC 1939, May 1996. 108 [RFC2384] Gellens, R., "POP URL Scheme", RFC 2384, August 1998. 110 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 111 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 112 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 114 [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION 115 4rev1", RFC 3501, March 2003. 117 [RFC5092] Melnikov, A. and C. Newman, "IMAP URL Scheme", RFC 5092, 118 November 2007. 120 [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, 121 October 2008. 123 [mailto] Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto' 124 URI scheme", RFC 6068, October 2010. 126 Author's Address 128 Alexey Melnikov 129 Isode Limited 130 5 Castle Business Village 131 36 Station Road 132 Hampton, Middlesex TW12 2BX 133 UK 135 Email: Alexey.Melnikov@isode.com