RFC 4355 · PROPOSED STANDARD · 2006
MON · 27 JUL 2026
IANA Registration for Enumservices email, fax, mms, ems, and sms
Overview
RFC 4355, “IANA Registration for Enumservices email, fax, mms, ems, and sms”, is a Proposed Standard document published in January 2006 by R. Brandner, L. Conroy, R. Stastny. It has since been updated by RFC 6118. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
Read this RFC
The canonical text of RFC 4355 is hosted at rfc-editor.org. Available in TXT,HTML.
Relationships to other RFCs
Other RFCs from 2006
- RFC 4354 A Session Initiation Protocol Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular Service
- RFC 4356 Mapping Between the Multimedia Messaging Service and Internet Mail
- RFC 4353 A Framework for Conferencing with the Session Initiation Protocol
- RFC 4357 Additional Cryptographic Algorithms for Use with GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 Algorithms
- RFC 4352 RTP Payload Format for the Extended Adaptive Multi-Rate Wideband Audio Codec
- RFC 4358 A Uniform Resource Name Namespace for the Open Mobile Alliance
- RFC 4359 The Use of RSA/SHA-1 Signatures within Encapsulating Security Payload and Authentication Header
- RFC 4351 Real-Time Transport Protocol Payload for Text Conversation Interleaved in an Audio Stream