Enumservice Registrations
2004-03-12
2022-01-28
Enumservice Registrations
Specification Required
Bernie Hoeneisen
When adding an entry to this registry, strong consideration
should be given to also adding an entry to the Underscored
and Globally Scoped DNS Node Names registry.
Application-Based, Ancillary
acct
acct
This Enumservice indicates that the resource
can be identified by the associated 'acct' URI .
For DNS considerations in avoiding loops when
searching for "acct" NAPTRs,
see , Section 6.
For security considerations,
see , Section 7.
COMMON
Application-Based, Common
email
mailto
mailto
This Enumservice indicates that the resource can be
addressed by the associated URI in order to send an
email.
See , Section 6.
COMMON
Application-Based, Common
ems
mailto
mailto
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using an email protocol.
EMS content is sent over SMTP using the format
specified by TS 23.140 [15] Section 8.4.4 and TS
26.140 [16] Section 4, as an MMS message. Within
such a message, EMS content is carried as either a
text or application/octet-stream MIME sub-part (see
TS 26.140 [16], Section 4.1).
For references see .
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of apply.
COMMON
Application-Based, Common
ems
tel
tel
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using the Enhanced Message
Service (EMS) [14] (For reference see
).
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of apply.
COMMON
Note that an indication of EMS can be taken as
implying that the recipient is capable of receiving
SMS messages at this address as well.
Application-Based, Subset
fax
tel
tel
This Enumservice indicates that the resource
identified by the associated URI is capable
of being contacted to provide a communication
session during which facsimile documents can be
sent.
A client selecting this NAPTR will have support
for generating and sending facsimile documents to
the recipient using the PSTN session and transfer
protocols specified in [12] and [13] in
-
in short, they will have a fax program with a local
or shared PSTN access over which they can send
faxes.
References are contained in .
See , Section 6.
COMMON
Application-Based, Subset
ft
ftp
ftp
This Enumservice indicates that the resource
identified by the associated URI is a file
service from which a file or file listing can be
retrieved.
See , Section 5.
COMMON
Protocol-Based
h323
h323
See , Section 3.
See , Section 5.
COMMON
Protocol-Based
iax
iax
The 'iax' Enumservice is used to map E.164 numbers to
IAX URIs. Such URIs identify resources capable of being
contacted to provide a communication session using the
IAX protocol .
A client selecting this NAPTR needs to be able to support
communication utilizing the IAX protocol.
See , Section 4.
COMMON
Application-Based, Common
ical-access
http
http
This Enumservice indicates that the resource identified
can be addressed by the associated URI in order to access
a user's calendar (for example free/busy status) using
the CalDAV [7] protocol for Internet calendaring.
References are contained in .
See , Section 4.
COMMON
Application-Based, Common
ical-access
https
https
This Enumservice indicates that the resource identified
can be addressed by the associated URI in order to access
a user's calendar (for example free/busy status) using
the CalDAV [7] protocol for Internet calendaring.
References are contained in .
See , Section 4.
COMMON
Application-Based, Common
ical-sched
mailto
mailto
This Enumservice indicates that the resource identified
can be addressed by the associated URI used for
scheduling using Internet calendaring via Internet mail
with the iMIP [6] protocol.
References are contained in .
See , Section 4.
COMMON
Application-Based, Subset
ifax
mailto
mailto
See , Section 1.
See , Section 3.
COMMON
The URI Scheme is 'mailto' because facsimile is a
profile of standard Internet mail and uses standard
Internet mail addressing.
Application-Based, Common
im
im
This Enumservice indicates that the resource
identified is an 'im:' URI. The 'im:' URI scheme
does not identify any particular protocol that will
be used to handle instant messaging receipt or
delivery, rather the mechanism in RFC3861 [4] is
used to discover whether an IM protocol supported by
the party querying ENUM is also supported by the
target resource.
References are contained in .
See , Section 3.
COMMON
Application-Based, Common
mms
mailto
mailto
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using an email protocol.
MMS messages are sent over SMTP using the format
specified by TS 23.140 [15] Section 8.4.4 and TS
26.140 [16] Section 4.
Within and between MMS Environments (MMSE,
network infrastructures that support the MultiMedia
Service), other pieces of state data (for example,
charging-significant information) are exchanged
between MMS Relay Servers. Thus, although these
servers use SMTP as the "bearer" for their
application exchanges, they map their internal state
to specialized header fields carried in the SMTP message
exchanges. The header fields used in such MMSE are
described in detail in [17].
For references see .
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of apply.
COMMON
The MMS Architecture describes an interface
between the MMSE and "legacy messaging systems"
(labelled as MM3) which accepts "standard" SMTP
messages. Thus although the MMS Relay Server that
supports this interface appears as a standard SMTP
server from the perspective of an Internet-based
mail server, it acts as a gateway and translator,
adding the internal state data that is used within
and between the MMS Environments. This mechanism is
described in [17], which also includes references to
the specifications agreed by those bodies
responsible for the design of the MMS.
References are contained in .
Application-Based, Common
mms
tel
tel
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using the Multimedia
Messaging Service (MMS) [15].
For references see .
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of apply.
COMMON
Note that MMS can be used as an alternative to
deliver an SMS RP-DATA RPDU if, for example, the
SMS bearer is not supported. If an entry includes
this Enumservice, then in effect this can be taken
as implying that the recipient is capable of
receiving EMS or SMS messages at this address. Such
choices on the end system de do have two small
caveats; whilst in practice all terminals supporting
MMS today support SMS as well, it might not
necessarily be the case in the future, and there may
be tariff differences in using the MMS rather than
using the SMS or EMS.
Application-Based, Common
pres
pres
See , Section 4.
See , Section 6.
COMMON
See , Section 3.
Application-Based, Common
pstn
sip
sip
These Enumservices indicate that the
resource identified can be addressed by the
associated URI in order to initiate a
telecommunication session, which may include two-way
voice or other communications, to the PSTN.
See , Section 7.
COMMON
A Number Portability Dip Indicator (npdi) should
be used in practice
(see , Section 4).
Application-Based, Ancillary
pstn
tel
tel
These Enumservices indicate that the
resource identified can be addressed by the
associated URI in order to initiate a
telecommunication session, which may include two-way
voice or other communications, to the PSTN. These
URIs may contain number portability data as
specified in RFC4694 [10].
References are contained in .
See , Section 7.
COMMON
A Number Portability Dip Indicator (npdi) should
be used in practice
(see , Section 4).
Protocol-Based
sip
sip, sips
See , Section 4.
See , Section 6.
COMMON
See , Section 3.
Application-Based, Common
sms
mailto
mailto
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using an email protocol.
SMS content is sent over SMTP using the format
specified by TS 23.140 [15] Section 8.4.4 and TS
26.140 [16] Section 4, as an MMS message. Within
such a message, SMS content is carried as either a
text or application/octet-stream MIME sub-part (see
TS 26.140 [16], Section 4.1)
For references see
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of apply.
COMMON
Application-Based, Common
sms
tel
tel
This Enumservice indicates that the resource
identified by the associated URI is capable
of receiving a message using the Short Message
Service (SMS) [14] in .
There are no specific security issues with this
Enumservice. However, the general considerations of
Section 6 of apply.
COMMON
Application-Based, Common
unifmsg
http
http
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information.
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
References are contained in .
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
unifmsg
https
https
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure
Socket Layer protocol.
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
References are contained in .
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
unifmsg
sip
sip
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a unified communication session to a unified
messaging system.
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
unifmsg
sips
sips
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a unified communication session to a unified
messaging system.
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Data Type-Based
vcard
http, https
This Enumservice indicates that the resource
identified is a plain vCard, according to RFC2426,
which may be accessed using HTTP / HTTPS [7].
Clients fetching the vCard from the resource
indicated should expect access to be
restricted. Additionally, the comprehension of the
data provided may vary depending on the client's
identity.
References are contained in .
See , Section 5.
COMMON
Application-Based, Common
videomsg
http
http
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information.
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
References are contained in .
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
videomsg
https
https
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure
Socket Layer protocol.
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even video message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
References are contained in .
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
videomsg
sip
sip
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a video communication session to a video messaging
system.
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
videomsg
sips
sips
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a video communication session to a video messaging
system.
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
voice
tel
tel
The kind of communication indicated by this
Enumservice is "Interactive Voice". From a protocol
perspective, this communication is expected to
involve bidirectional media streams carrying audio
data.
A client may imply that the person controlling
population of a NAPTR holding this Enumservice
indicates their capability to engage in an
interactive voice session when contacted using the
URI generated by this NAPTR.
See , Section 5.
COMMON
This Enumservice indicates that the person
responsible for the NAPTR is accessible via the PSTN
(Public Switched Telephone Network) or PLMN (Public
Land Mobile Network) using the value of the
generated URI.
The kind of subsystem required to initiate a
Voice Enumservice with this Subtype is a "Dialler".
This is a subsystem that either provides a local
connection to the PSTN or PLMN, or that provides an
indirect connection to those networks. The
subsystem will use the telephone number held in the
generated URI to place a voice call. The voice call
is placed to a network that uses E.164 numbers to
route calls to an appropriate destination.
Note that the PSTN/PLMN connection may be
indirect. The end user receiving this NAPTR may
have a relationship with a Communications Service
Provider that accepts call initiation requests from
that subsystem using an IP-based protocol such as
SIP or H.323, and places the call to the PSTN using
a remote gateway service. In this case the Provider
may either accept requests using "tel:" URIs or has
a defined mechanism to convert "tel:" URI values
into a "protocol-native" form.
The "tel:" URI value SHOULD be fully qualified
(using the "global phone number" form of RFC3966
[10]). A "local phone number" as defined in that
document SHOULD NOT be used unless the controller of
the zone in which the NAPTR appears is sure that it
can be distinguished unambiguously by all clients
that can access the resource record and that a call
from their network access points can be routed to
that destination.
References are contained in .
Application-Based, Common
voicemsg
http
http
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information.
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'http:' [11] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even voice message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
References are contained in .
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
voicemsg
https
https
This Enumservice indicates that the resource identified by
the associated URI scheme is capable of being a source of
information, which can be contacted using TLS or the Secure
Socket Layer protocol.
Note that the kind of information retrieved can be manifold.
Usually, contacting a resource by an 'https:' [12] URI
provides a document. This document can contain references
that will trigger the download of many different kinds of
information, such as text, audio, video, executable code, or
even voice message files. Thus, one cannot be more specific
about the kind of information expected when contacting the
resource.
References are contained in .
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
voicemsg
sip
sip
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a voice communication session to a voice messaging
system.
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
voicemsg
sips
sips
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a voice communication session to a voice messaging
system.
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Application-Based, Common
voicemsg
tel
tel
This Enumservice indicates that the resource identified can
be addressed by the associated URI scheme in order to
initiate a voice communication session to a voice messaging
system.
See , Section 3.
COMMON
Implementers should review a non-exclusive list of examples
in Section 7 of .
Data Type-Based
vpim
ldap
ldap
See , Section 3.2 - 3.3.
Malicious Redirection:
One of the fundamental dangers related to any
service such as this is that a malicious entry in a
resolver's database will cause clients to resolve
the E.164 into the wrong LDAP URI. The possible
intent may be to cause the client to connect to a
rogue LDAP server and retrieve (or fail to retrieve)
a resource containing fraudulent or damaging
information.
Denial of Service:
By removing the URI to which the E.164 maps, a
malicious intruder may remove the client's ability
to access the LDAP directory server.
COMMON
Data Type-Based
vpim
mailto
mailto
See , Section 4.2 - 4.4.
Malicious Redirection:
One of the fundamental dangers related to any
service such as this is that a malicious entry in a
resolver's database will cause clients to resolve
the E.164 into the wrong email URI. The possible
intent may be to cause the client to send the
information to an incorrect destination.
Denial of Service:
By removing the URI to which the E.164 maps, a
malicious intruder may remove the client's ability
to access the resource.
Unsolicited Bulk Email:
The exposure of email addresses through the ENUM
service provides a bulk mailer access to large
numbers of email addresses where only the telephone
number was previously known.
COMMON
Error Conditions:
E.164 number not in the numbering plan
E.164 number in the numbering plan, but no
URIs exist for that number
E2U+vpim:mailto Service unavailable of email
addresses where only the telephone number was
previously known.
Application-Based, Common
web
http
http
This Enumservice indicates that the resource
identified by the associated URI is capable
of being a source of information. It has to be
noted that the kind of information retrieved can be
manifold. Usually, contacting a resource by an
"http:" URI provides a document. This document can
contain references that will trigger download of
many different kinds of information, like audio or
video or executable code. Thus, one can not be more
specific about the kind of information that can be
expected when contacting the resource.
See , Section 5.
COMMON
Application-Based, Common
web
https
https
This Enumservice indicates that the resource
identified by the associated URI is capable
of being a source of information, which can be
contacted by using TLS or Secure Socket Layer
protocol. It has to be noted that the kind of
information retrieved can be manifold. Usually,
contacting a resource by an "https:" URI provides a
document. This document can contain all different
kind of information, like audio or video or
executable code. Thus, one can not be more specific
what information to expect when contacting the
resource.
See , Section 5.
COMMON
Protocol-Based
xmpp
xmpp
This Enumservice indicates that the resource
identified is an XMPP entity.
See , Section 6.
COMMON
Alexander Mayrhofer
enum.at GmbH
mailto:alexander.mayrhofer&enum.at
2010-06-30
Dave Crocker
Brandenburg InternetWorking
mailto:dcrocker&bbiw.net
2005-11
Don Troshynski
Acme Packet
mailto:dtroshynski&acmepacket.com
2008-07
Ed Guy
CleverSpoke, Inc
mailto:edguy&CleverSpoke.com
2011-05-11
Greg Vaudreuil
Lucent Technologies
mailto:GregV&ieee.org
2005-10
Jason Livingood
Comcast Cable Communications
mailto:jason_livingood&cable.comcast.com
2008-07
Jon Peterson
NeuStar
mailto:jon.peterson&neustar.biz
2005-01
Kiyoshi Toyoda
Panasonic Communications Co., Ltd.
mailto:toyoda.kiyoshi&jp.panasonic.com
2005-11
Klaus Darilion
nic.at
mailto:klaus.darilion&nic.at
2011-05-11
Laurent-Walter Goix
Telecom Italia
mailto:laurentwalter.goix&telecomitalia.it
2014-06-18
Lawrence Conroy
Siemens Roke Manor Research
mailto:lwc&roke.co.uk
2006-01
Orit Levin
Microsoft Corporation
mailto:oritlµsoft.com
2004-04
Richard Shockey
NeuStar
mailto:richard.shockey&neustar.biz
2006-11
Richard Stastny
Oefeg
mailto:richard.stastny&oefeg.at
2006-01
Rohan Mahy
Plantronics
mailto:rohan&ekabal.com
2007-10
Rudolf Brandner
Siemens AG
mailto:rudolf.brandner&siemens.com
2006-01