Internet Assigned Numbers Authority Enumservice Registrations Created 2004-03-12 Last Updated 2022-01-28 Available Formats [IMG] XML [IMG] HTML [IMG] Plain text Registry included below * Enumservice Registrations Enumservice Registrations Registration Procedure(s) Specification Required Expert(s) Bernie Hoeneisen Reference [RFC6117] Note 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. Available Formats [IMG] CSV Class Type Subtype URI Functional Specification Security Intended Enumservice Requester(s) Further Scheme(s) Considerations Usage Specification(s) Information For DNS considerations in avoiding This Enumservice loops when indicates that the searching for Application-Based, acct N/A acct resource can be "acct" NAPTRs, COMMON [RFC7566] [Laurent_Walter_Goix] Ancillary identified by the see [RFC7566], associated 'acct' URI Section 6. For [RFC7565]. security considerations, see [RFC7566], Section 7. This Enumservice indicates that the [Rudolf_Brandner] Application-Based, email mailto mailto resource can be See [RFC4355], COMMON [RFC4355] [Lawrence_Conroy] Common addressed by the Section 6. [RFC6118] [Richard_Stastny] associated URI in order to send an email. This Enumservice indicates that the resource identified by the associated URI is capable of receiving a message using an email protocol. There are no specific EMS content is sent over security issues SMTP using the format with this specified by TS 23.140 Enumservice. [Rudolf_Brandner] Application-Based, ems mailto mailto [15] Section 8.4.4 and However, the COMMON [RFC4355] [Lawrence_Conroy] Common TS 26.140 [16] Section general [RFC6118] [Richard_Stastny] 4, as an MMS message. considerations Within such a message, of Section 6 of EMS content is carried [RFC4355] as either a text or apply. application/octet-stream MIME sub-part (see TS 26.140 [16], Section 4.1). For references see [RFC4355]. This Enumservice There are no indicates that the specific Note that an resource identified by security issues indication of EMS the associated URI is with this can be taken as Application-Based, capable of receiving a Enumservice. [RFC4355] [Rudolf_Brandner] implying that the Common ems tel tel message using the However, the COMMON [RFC6118] [Lawrence_Conroy] recipient is Enhanced Message Service general [Richard_Stastny] capable of (EMS) [14] (For considerations receiving SMS reference see of Section 6 of messages at this [RFC4355]). [RFC4355] address as well. apply. 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 [Rudolf_Brandner] Application-Based, fax tel tel sending facsimile See [RFC4355], COMMON [RFC4355] [Lawrence_Conroy] Subset documents to the Section 6. [RFC6118] [Richard_Stastny] recipient using the PSTN session and transfer protocols specified in [12] and [13] in [RFC4355] - 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 [RFC4355]. This Enumservice indicates that the Application-Based, resource identified by See [RFC4002], [RFC4002] [Rudolf_Brandner] Subset ft ftp ftp the associated URI is a Section 5. COMMON [RFC6118] [Lawrence_Conroy] file service from which [Richard_Stastny] a file or file listing can be retrieved. Protocol-Based h323 N/A h323 See [RFC3762], Section See [RFC3762], COMMON [RFC3762] [Orit_Levin] 3. Section 5. [RFC6118] 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 See [RFC6315], [Ed_Guy] Protocol-Based iax N/A iax session using the IAX Section 4. COMMON [RFC6315] [Klaus_Darilion] protocol [RFC5456]. A client selecting this NAPTR needs to be able to support communication utilizing the IAX protocol. This Enumservice indicates that the resource identified can be addressed by the associated URI in order to access a user's Application-Based, ical-access http http calendar (for example See [RFC5333], COMMON [RFC5333] [Rohan_Mahy] Common free/busy status) using Section 4. [RFC6118] the CalDAV [7] protocol for Internet calendaring. References are contained in [RFC5333]. This Enumservice indicates that the resource identified can be addressed by the associated URI in order to access a user's Application-Based, ical-access https https calendar (for example See [RFC5333], COMMON [RFC5333] [Rohan_Mahy] Common free/busy status) using Section 4. [RFC6118] the CalDAV [7] protocol for Internet calendaring. References are contained in [RFC5333]. This Enumservice indicates that the resource identified can be addressed by the associated URI used for Application-Based, ical-sched mailto mailto scheduling using See [RFC5333], COMMON [RFC5333] [Rohan_Mahy] Common Internet calendaring via Section 4. [RFC6118] Internet mail with the iMIP [6] protocol. References are contained in [RFC5333]. The URI Scheme is 'mailto' because facsimile is a Application-Based, ifax mailto mailto See [RFC4143], Section See [RFC4143], COMMON [RFC4143] [Kiyoshi_Toyoda] profile of Subset 1. Section 3. [RFC6118] [Dave_Crocker] standard Internet mail and uses standard Internet mail addressing. 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 Application-Based, im N/A im delivery, rather the See [RFC5028], COMMON [RFC5028] [Rohan_Mahy] Common mechanism in RFC3861 [4] Section 3. [RFC6118] 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 [RFC5028]. The MMS This Enumservice Architecture indicates that the describes an resource identified by interface between the associated URI is the MMSE and capable of receiving a "legacy messaging message using an email systems" protocol. (labelled as MM3) which accepts MMS messages are sent "standard" SMTP over SMTP using the messages. Thus format specified by TS although the MMS 23.140 [15] Section Relay Server that 8.4.4 and TS 26.140 [16] supports this Section 4. interface appears as a standard Within and between MMS There are no SMTP server from Environments (MMSE, specific the perspective network infrastructures security issues of an that support the with this Internet-based MultiMedia Service), Enumservice. [Rudolf_Brandner] mail server, it Application-Based, mms mailto mailto other pieces of state However, the COMMON [RFC4355] [Lawrence_Conroy] acts as a gateway Common data (for example, general [RFC6118] [Richard_Stastny] and translator, charging-significant considerations adding the information) are of Section 6 of internal state exchanged between MMS [RFC4355] data that is used Relay Servers. Thus, apply. within and although these servers between the MMS use SMTP as the "bearer" Environments. for their application This mechanism is exchanges, they map described in their internal state to [17], which also specialized header includes fields carried in the references to the SMTP message exchanges. specifications The header fields used agreed by those in such MMSE are bodies described in detail in responsible for [17]. the design of the MMS. For references see [RFC4355]. References are contained in [RFC4355]. 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 This Enumservice There are no as implying that indicates that the specific the recipient is resource identified by security issues capable of the associated URI is with this receiving EMS or capable of receiving a Enumservice. [Rudolf_Brandner] SMS messages at Application-Based, mms tel tel message using the However, the COMMON [RFC4355] [Lawrence_Conroy] this address. Common Multimedia Messaging general [RFC6118] [Richard_Stastny] Such choices on Service (MMS) [15]. considerations the end system de of Section 6 of do have two small For references see [RFC4355] caveats; whilst [RFC4355]. apply. 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, pres N/A pres See [RFC3953], Section See [RFC3953], COMMON [RFC3953] [Jon_Peterson] See [RFC3953], Common 4. Section 6. [RFC6118] Section 3. These Enumservices indicate that the resource identified can A Number be addressed by the Portability Dip Application-Based, associated URI in order See [RFC4769], [RFC4769] [Jason_Livingood] Indicator (npdi) Common pstn sip sip to initiate a Section 7. COMMON [RFC6118] [Richard_Shockey] should be used in telecommunication practice (see session, which may [RFC4769], include two-way voice or Section 4). other communications, to the PSTN. These Enumservices indicate that the resource identified can be addressed by the associated URI in order to initiate a A Number telecommunication Portability Dip session, which may Indicator (npdi) Application-Based, pstn tel tel include two-way voice or See [RFC4769], COMMON [RFC4769] [Jason_Livingood] should be used in Ancillary other communications, to Section 7. [RFC6118] [Richard_Shockey] practice (see the PSTN. These URIs may [RFC4769], contain number Section 4). portability data as specified in RFC4694 [10]. References are contained in [RFC4769]. Protocol-Based sip N/A sip, sips See [RFC3764], Section See [RFC3764], COMMON [RFC3764] [Jon_Peterson] See [RFC3764], 4. Section 6. [RFC6118] Section 3. This Enumservice indicates that the resource identified by the associated URI is capable of receiving a message using an email protocol. There are no specific SMS content is sent over security issues SMTP using the format with this specified by TS 23.140 Enumservice. [Rudolf_Brandner] Application-Based, sms mailto mailto [15] Section 8.4.4 and However, the COMMON [RFC4355] [Lawrence_Conroy] Common TS 26.140 [16] Section general [RFC6118] [Richard_Stastny] 4, as an MMS message. considerations Within such a message, of Section 6 of SMS content is carried [RFC4355] as either a text or apply. application/octet-stream MIME sub-part (see TS 26.140 [16], Section 4.1) For references see [RFC4355] There are no This Enumservice specific indicates that the security issues resource identified by with this Application-Based, the associated URI is Enumservice. [RFC4355] [Rudolf_Brandner] Common sms tel tel capable of receiving a However, the COMMON [RFC6118] [Lawrence_Conroy] message using the Short general [Richard_Stastny] Message Service (SMS) considerations [14] in [RFC4355]. of Section 6 of [RFC4355] apply. 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:' Implementers [11] URI provides a should review a Application-Based, document. This document See [RFC5278], [RFC5278] [Jason_Livingood] non-exclusive Common unifmsg http http can contain references Section 3. COMMON [RFC6118] [Don_Troshynski] list of examples that will trigger the in Section 7 of download of many [RFC5278]. 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 [RFC5278]. 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 Implementers resource by an 'https:' should review a Application-Based, unifmsg https https [12] URI provides a See [RFC5278], COMMON [RFC5278] [Jason_Livingood] non-exclusive Common document. This document Section 3. [RFC6118] [Don_Troshynski] list of examples can contain references in Section 7 of that will trigger the [RFC5278]. 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 [RFC5278]. This Enumservice indicates that the Implementers resource identified can should review a Application-Based, be addressed by the See [RFC5278], [RFC5278] [Jason_Livingood] non-exclusive Common unifmsg sip sip associated URI scheme in Section 3. COMMON [RFC6118] [Don_Troshynski] list of examples order to initiate a in Section 7 of unified communication [RFC5278]. session to a unified messaging system. This Enumservice indicates that the Implementers resource identified can should review a Application-Based, be addressed by the See [RFC5278], [RFC5278] [Jason_Livingood] non-exclusive Common unifmsg sips sips associated URI scheme in Section 3. COMMON [RFC6118] [Don_Troshynski] list of examples order to initiate a in Section 7 of unified communication [RFC5278]. session to a unified messaging system. 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 Data Type-Based vcard N/A http, vCard from the resource See [RFC4969], COMMON [RFC4969] [Alexander_Mayrhofer] https indicated should expect Section 5. [RFC6118] access to be restricted. Additionally, the comprehension of the data provided may vary depending on the client's identity. References are contained in [RFC4969]. 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:' Implementers [11] URI provides a should review a Application-Based, document. This document See [RFC5278], [RFC5278] [Jason_Livingood] non-exclusive Common videomsg http http can contain references Section 3. COMMON [RFC6118] [Don_Troshynski] list of examples that will trigger the in Section 7 of download of many [RFC5278]. 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 [RFC5278]. 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 Implementers resource by an 'https:' should review a Application-Based, videomsg https https [12] URI provides a See [RFC5278], COMMON [RFC5278] [Jason_Livingood] non-exclusive Common document. This document Section 3. [RFC6118] [Don_Troshynski] list of examples can contain references in Section 7 of that will trigger the [RFC5278]. 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 [RFC5278]. This Enumservice indicates that the Implementers resource identified can should review a Application-Based, be addressed by the See [RFC5278], [RFC5278] [Jason_Livingood] non-exclusive Common videomsg sip sip associated URI scheme in Section 3. COMMON [RFC6118] [Don_Troshynski] list of examples order to initiate a in Section 7 of video communication [RFC5278]. session to a video messaging system. This Enumservice indicates that the Implementers resource identified can should review a Application-Based, be addressed by the See [RFC5278], [RFC5278] [Jason_Livingood] non-exclusive Common videomsg sips sips associated URI scheme in Section 3. COMMON [RFC6118] [Don_Troshynski] list of examples order to initiate a in Section 7 of video communication [RFC5278]. session to a video messaging system. 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 The kind of appropriate communication indicated destination. by this Enumservice is "Interactive Voice". Note that the From a protocol PSTN/PLMN perspective, this connection may be communication is indirect. The end expected to involve user receiving bidirectional media this NAPTR may streams carrying audio have a Application-Based, data. See [RFC4415], [RFC4415] [Rudolf_Brandner] relationship with Common voice tel tel Section 5. COMMON [RFC6118] [Lawrence_Conroy] a Communications A client may imply that [Richard_Stastny] Service Provider the person controlling that accepts call population of a NAPTR initiation holding this Enumservice requests from indicates their that subsystem capability to engage in using an IP-based an interactive voice protocol such as session when contacted SIP or H.323, and using the URI generated places the call by this NAPTR. 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 [RFC4415]. 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:' Implementers [11] URI provides a should review a Application-Based, document. This document See [RFC5278], [RFC5278] [Jason_Livingood] non-exclusive Common voicemsg http http can contain references Section 3. COMMON [RFC6118] [Don_Troshynski] list of examples that will trigger the in Section 7 of download of many [RFC5278]. 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 [RFC5278]. 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 Implementers resource by an 'https:' should review a Application-Based, voicemsg https https [12] URI provides a See [RFC5278], COMMON [RFC5278] [Jason_Livingood] non-exclusive Common document. This document Section 3. [RFC6118] [Don_Troshynski] list of examples can contain references in Section 7 of that will trigger the [RFC5278]. 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 [RFC5278]. This Enumservice indicates that the Implementers resource identified can should review a Application-Based, be addressed by the See [RFC5278], [RFC5278] [Jason_Livingood] non-exclusive Common voicemsg sip sip associated URI scheme in Section 3. COMMON [RFC6118] [Don_Troshynski] list of examples order to initiate a in Section 7 of voice communication [RFC5278]. session to a voice messaging system. This Enumservice indicates that the Implementers resource identified can should review a Application-Based, be addressed by the See [RFC5278], [RFC5278] [Jason_Livingood] non-exclusive Common voicemsg sips sips associated URI scheme in Section 3. COMMON [RFC6118] [Don_Troshynski] list of examples order to initiate a in Section 7 of voice communication [RFC5278]. session to a voice messaging system. This Enumservice indicates that the Implementers resource identified can should review a Application-Based, be addressed by the See [RFC5278], [RFC5278] [Jason_Livingood] non-exclusive Common voicemsg tel tel associated URI scheme in Section 3. COMMON [RFC6118] [Don_Troshynski] list of examples order to initiate a in Section 7 of voice communication [RFC5278]. session to a voice messaging system. 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 Data Type-Based vpim ldap ldap See [RFC4238], Section server and COMMON [RFC4238] [Greg_Vaudreuil] 3.2 - 3.3. retrieve (or [RFC6118] 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. 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 Error Conditions: may be to cause the client to E.164 number not send the in the numbering information to plan an incorrect destination. E.164 number in the numbering Denial of plan, but no URIs See [RFC4238], Section Service: By [RFC4238] exist for that Data Type-Based vpim mailto mailto 4.2 - 4.4. removing the COMMON [RFC6118] [Greg_Vaudreuil] number URI to which the E.164 maps, E2U+vpim:mailto a malicious Service intruder may unavailable of remove the email addresses client's where only the ability to telephone number access the was previously resource. known. 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. 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 Application-Based, an "http:" URI provides See [RFC4002], [RFC4002] [Rudolf_Brandner] Common web http http a document. This Section 5. COMMON [RFC6118] [Lawrence_Conroy] document can contain [Richard_Stastny] 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. 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 Application-Based, retrieved can be See [RFC4002], [RFC4002] [Rudolf_Brandner] Common web https https manifold. Usually, Section 5. COMMON [RFC6118] [Lawrence_Conroy] contacting a resource by [Richard_Stastny] 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. This Enumservice Protocol-Based xmpp N/A xmpp indicates that the See [RFC4979], COMMON [RFC4979] [Alexander_Mayrhofer] resource identified is Section 6. [RFC6118] an XMPP entity. Contact Information ID Name Organization Contact URI Last Updated [Alexander_Mayrhofer] Alexander Mayrhofer enum.at GmbH mailto:alexander.mayrhofer&enum.at 2010-06-30 [Dave_Crocker] Dave Crocker Brandenburg InternetWorking mailto:dcrocker&bbiw.net 2005-11 [Don_Troshynski] Don Troshynski Acme Packet mailto:dtroshynski&acmepacket.com 2008-07 [Ed_Guy] Ed Guy CleverSpoke, Inc mailto:edguy&CleverSpoke.com 2011-05-11 [Greg_Vaudreuil] Greg Vaudreuil Lucent Technologies mailto:GregV&ieee.org 2005-10 [Jason_Livingood] Jason Livingood Comcast Cable Communications mailto:jason_livingood&cable.comcast.com 2008-07 [Jon_Peterson] Jon Peterson NeuStar mailto:jon.peterson&neustar.biz 2005-01 [Kiyoshi_Toyoda] Kiyoshi Toyoda Panasonic Communications Co., Ltd. mailto:toyoda.kiyoshi&jp.panasonic.com 2005-11 [Klaus_Darilion] Klaus Darilion nic.at mailto:klaus.darilion&nic.at 2011-05-11 [Laurent_Walter_Goix] Laurent-Walter Goix Telecom Italia mailto:laurentwalter.goix&telecomitalia.it 2014-06-18 [Lawrence_Conroy] Lawrence Conroy Siemens Roke Manor Research mailto:lwc&roke.co.uk 2006-01 [Orit_Levin] Orit Levin Microsoft Corporation mailto:oritlµsoft.com 2004-04 [Richard_Shockey] Richard Shockey NeuStar mailto:richard.shockey&neustar.biz 2006-11 [Richard_Stastny] Richard Stastny Oefeg mailto:richard.stastny&oefeg.at 2006-01 [Rohan_Mahy] Rohan Mahy Plantronics mailto:rohan&ekabal.com 2007-10 [Rudolf_Brandner] Rudolf Brandner Siemens AG mailto:rudolf.brandner&siemens.com 2006-01 Licensing Terms