RFC 4355: IANA Registration for Enumservices email, fax, mms, ems, and sms
In plain English — editorial summary, not part of the RFC
This document registers the Enumservices "email", "fax", "sms", "ems", and "mms" using the URI schemes 'tel:' and 'mailto:' as per the IANA registration process defined in the ENUM specification RFC 3761. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4355
- Published
- January 2006
- Authors
- R. Brandner; L. Conroy; R. Stastny
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 16
- Also known as
- —
- Updated by:
- RFC 6118
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 2004
- RFC 2916E.164 number and DNSObsoleted
September 2000
- RFC 6117IANA Registration of Enumservices: Guide, Template, and IANA ConsiderationsCurrent
March 2011
- RFC 4255Using DNS to Securely Publish Secure Shell (SSH) Key FingerprintsCurrent
January 2006
- RFC 4470Minimally Covering NSEC Records and DNSSEC On-line SigningCurrent
April 2006
- RFC 4472Operational Considerations and Issues with IPv6 DNSCurrent
April 2006
- RFC 4509Use of SHA-256 in DNSSEC Delegation Signer (DS) Resource Records (RRs)Current
May 2006
- RFC 4159Deprecation of "ip6.int"Current
August 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?