rfc-6196

Moving mailserver: URI Scheme to Historic

A. Melnikov

date2011-03 streamIETF wgnon working group statusPROPOSED STANDARD pages3 canonicalhttps://www.rfc-editor.org/rfc/rfc6196 doi10.17487/RFC6196 errataview

This document registers the mailserver: URI scheme as historic in the IANA URI registry. [STANDARDS-TRACK]

updates

rfc-1738 — Uniform Resource Locators (URL)

Extracted elements (5)

design-rationale §1

The scheme is marked Historic rather than simply left as provisional to minimize the risk of someone implementing an undocumented and incompatible variant by consulting the IANA registry. Discouraging future implementations is an explicit goal.

email, registry

interoperability-note §1

Implementors wishing to generate email messages should use the mailto: URI scheme (RFC 6068) instead. For referencing messages on IMAP, POP, or web mailstores, the imap: (RFC 5092), pop: (RFC 2384), or http: (RFC 2616) URI schemes are the appropriate alternatives.

email, http

interoperability-note §1

The mailserver: URI scheme as currently specified is not interoperable. There are no known implementations, and the scheme was never properly documented beyond a brief description in RFC 1738.

registry §3

IANA has re-registered the mailserver: URI scheme as Historic in the URI scheme registry, updating the reference to point to RFC 6196. This deprecates the provisional registration originally made in RFC 1738.

registry, email

security-consideration §2

Because the mailserver: URI scheme was never properly documented and has no known implementations, there are no specific security concerns beyond the general risk of ad-hoc implementations inventing undocumented syntax. Historic status removes this risk.

security, email