
Enumservice Registrations

(last updated 2007-10-17)

Enumservice specifications contain the functional specification (i.e.
what it can be used for), the valid protocols, and the URI schemes
that may be returned.

Registration Template
---------------------

   Enumservice Type:

   Enumservice Subtype(s):

   URI Scheme(s):

   Functional Specification:

   Security considerations:

   Intended usage: (One of COMMON, LIMITED USE or OBSOLETE)

   Author:

   Any other information that the author deems interesting:


Assigned Enumservice Values
---------------------------

Service Name: "H323"
     URI Scheme(s): "h323:"
     Functional Specification:  See Section "3. The E2U+H323 ENUM Service" of [RFC3762]
     Security considerations: see section "5. Security Considerations" of [RFC3762]
     Intended usage: COMMON
     Author: Orit Levin
     [RFC3762]

Service Name: "SIP"
     Type(s): "SIP"
     Subtype(s): N/A
     URI Scheme(s): "sip", "sips:"
     Functional Specification: see Section 4 of [RFC3764]
     Security considerations: see Section 6 of [RFC3764]
     Intended usage: COMMON
     Author: Jon Peterson (jon.peterson&neustar.biz)
     Any other information that the author deems interesting: see Section 3 of [RFC3764]
     [RFC3764]

Service Name: "ifax"
    Type: "ifax"
    Subtype: "mailto"
    URI Scheme: "mailto"
    The URI Scheme is "mailto" because facsimile is a profile of  
    standard Internet mail and uses standard Internet mail addressing.
    Functional Specification: see section 1 of [RFC4143]
    Security Considerations: see section 3 of [RFC4143]
    Intended usage: COMMON
    Author: Kiyoshi Toyoda(toyoda.kiyoshi&jp.panasonic.com)
            Dave Crocker(dcrocker&brandenburg.com)
    [RFC4143]

Service Name: "pres"
    URI Scheme(s): "pres:"
    Functional Specification: see Section 4 of [RFC3953]
    Security considerations: see Section 6 of [RFC3953]
    Intended usage: COMMON
    Author: Jon Peterson (jon.peterson&neustar.biz)
    Any other information that the author deems interesting: See
    Section 3 of [RFC3953]
    [RFC3953]

Service Name: "web"
    Type: "web"
    Subtype: "http"
    URI Scheme: 'http:'
    Functional Specification:
    This ENUMservice indicates that the resource identified by the
    associated URI scheme 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.
    Security Considerations:
    See section 5 of [RFC4002].
    Intended Usage: COMMON
    Authors:
    Rudolf Brandner (rudolf.brandner&siemens.com)
    Lawrence Conroy (lwc&roke.co.uk) 
    Richard Stastny (richard.stastny&oefeg.at)
    Any other information the author deems interesting:  None
    [RFC4002]

Service Name: "web"
    Type: "web"
    Subtype: "https"
    URI Scheme: 'https:'
    Functional Specification:
    This ENUMservice indicates that the resource identified by the
    associated URI scheme 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.
    Security Considerations:
    See section 5 of [RFC4002].
    Intended Usage: COMMON
    Authors: 
    Rudolf Brandner (rudolf.brandner&siemens.com)
    Lawrence Conroy (lwc&roke.co.uk) 
    Richard Stastny (richard.stastny&oefeg.at)
    Any other information the author deems interesting:  None
    [RFC4002]

Service Name: "ft"
    Type: "ft"
    Subtype: "ftp"
    URI Scheme: 'ftp:'
    Functional Specification:
    This ENUMservice indicates that the resource identified by the
    associated URI scheme is a file service from which a file or file
    listing can be retrieved.
    Security Considerations:
    See section 5 of [RFC4002].
    Intended Usage: COMMON
    Authors: 
    Rudolf Brandner (rudolf.brandner&siemens.com)
    Lawrence Conroy (lwc&roke.co.uk) 
    Richard Stastny (richard.stastny&oefeg.at)
    Any other information the author deems interesting:    None
    [RFC4002]

Enumservice Name: "email"
   Enumservice Type: "email"
   Enumservice Subtype: "mailto"
   URI Scheme: 'mailto:'
   Functional Specification:
      This Enumservice indicates that the remote resource can be
      addressed by the associated URI scheme in order to send an email.
   Security Considerations:
      See Section 6 of [RFC4355]
   Intended Usage: COMMON
   Authors:
      Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
      contact detail see [RFC4355])
   Any other information the author deems interesting:
      None

Enumservice Name: "fax"
   Enumservice Type: "fax"
   Enumservice Subtype: "tel"
   URI Scheme: 'tel:'
   Functional Specification:
      This Enumservice indicates that the resource identified by the
      associated URI scheme 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 
      [RFC4355]  - in short, they will have a fax 
      program with a local or shared PSTN access over which they can send faxes.
   Security Considerations:
      See Section 6 of [RFC4355]
   Intended Usage: COMMON
   Authors:
      Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
      contact detail see  [RFC4355])
   Any other information the author deems interesting:
      None

Enumservice Name: "sms"
   Enumservice Type: "sms"
   Enumservice Subtypes: "tel"
   URI Scheme: 'tel:'
   Functional Specification:
      This Enumservice indicates that the resource identified by the
      associated URI scheme is capable of receiving a message using the
      Short Message Service (SMS) [14] in [RFC4355].
   Security Considerations:
      There are no specific security issues with this Enumservice.
      However, the general considerations of Section 6 apply.
   Intended Usage: COMMON
   Authors:
      Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
      contact detail see [RFC4355])
   Any other information the author deems interesting:
      None


Enumservice Name: "sms"
   Enumservice Type: "sms"
   Enumservice Subtypes: "mailto"
   URI Scheme: 'mailto:'
   Functional Specification:
      This Enumservice indicates that the resource identified by the
      associated URI scheme 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 (for references 
      see [RFC4355]), 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 [RFC4355].
   Security Considerations:
      There are no specific security issues with this Enumservice.
      However, the general considerations of Section 6 apply, see
      [RFC4355].
   Intended Usage: COMMON
   Authors:
      Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
      contact detail see [RFC4355])
   Any other information the author deems interesting:
      None

Enumservice Name: "ems"
   Enumservice Type: "ems"
   Enumservice Subtype: "tel"
   URI Scheme: 'tel:'
   Functional Specification:
      This Enumservice indicates that the resource identified by the
      associated URI scheme is capable of receiving a message using the
      Enhanced Message Service (EMS) [14] (For reference see [RFC4355]).
   Security Considerations:
      There are no specific security issues with this Enumservice.
      However, the general considerations of Section 6 apply.
      See [RFC4355]
   Intended Usage: COMMON
   Authors:
      Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
      contact detail see [RFC4355])
   Any other information the author deems interesting:
      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.

Enumservice Name: "ems"
   Enumservice Type: "ems"
   Enumservice Subtypes: "mailto"
   URI Scheme: 'mailto:'
   Functional Specification:
      This Enumservice indicates that the resource identified by the
      associated URI scheme 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 [RFC4355]
   Security Considerations:
      There are no specific security issues with this Enumservice.
      However, the general considerations of Section 6 of [RFC4355]
      apply.
   Intended Usage: COMMON
   Authors:
      Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
      contact detail see [RFC4355])
   Any other information the author deems interesting:
      None


Enumservice Name: "mms"
   Enumservice Type: "mms"
   Enumservice Subtype: "tel"
   URI Scheme: 'tel:'
   Functional Specification:
      This Enumservice indicates that the resource identified by the
      associated URI scheme is capable of receiving a message using the
      Multimedia Messaging Service (MMS) [15]. 
      For references see [RFC4355]
   Security Considerations:
      There are no specific security issues with this Enumservice.
      However, the general considerations of Section 6 of [RFC4355]
      apply.
   Intended Usage: COMMON
   Authors:
      Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
      contact detail see [RFC4355])
   Any other information the author deems interesting:
      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 design
      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.

Enumservice Name: "mms"
   Enumservice Type: "mms"
   Enumservice Subtypes: "mailto"
   URI Scheme: 'mailto:'
   Functional Specification:
      This Enumservice indicates that the resource identified by the
      associated URI scheme 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 specialised headers carried in the SMTP message
      exchanges.  The headers used in such MMSE are described in detail
      in [17].
      For references see [RFC4355]
   Security Considerations:
      There are no specific security issues with this Enumservice.
      However, the general considerations of Section 6 of [RFC4355]
      apply.
   Intended Usage: COMMON
   Authors:
      Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
      contact detail see [RFC4355])
   Any other information the author deems interesting:
      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.


Service Name: E.164 to VPIM MailTo: URL 
   URI Type: "Mailto:" 
   Type: VPIM 
   Subtype: MAILTO 
   Functional Specification: See section 4.2 through 4.4 of [RFC4238]
   Intended Usage: COMMON 
   Author: Greg Vaudreuil (gregv&ieee.org) 
   Error Conditions: 
      o E.164 number not in the numbering plan 
      o E.164 number in the numbering plan, but no URLs exist for that number 
      o E2U+VPIM:Mailto Service unavailable 
   Security Considerations: 
      o 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 URL. The possible 
        intent may be to cause the client to send the information to an 
        incorrect destination. 
      o Denial of Service 
        By removing the URL to which the E.164 maps, a malicious intruder 
        may remove the client's ability to access the resource. 
      o 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.   

Service Name: E.164 to VPIM LDAP URL 
   URI Type: "LDAP:" 
   Type: VPIM 
   Subtype: LDAP 
   Functional Specification: See section 3.2 through 3.3 of [RFC4238]
   Intended Usage: COMMON 
   Author: Greg Vaudreuil (gregv&ieee.org) 
   Security Considerations: 
      o 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 URL. 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. 
      o Denial of Service 
        By removing the URL to which the E.164 maps, a 
        malicious intruder may remove the client's ability to 
        access the LDAP directory server. 


Enumservice Name: "voice"
  Enumservice Type: "voice"
  Enumservice Subtype: "tel"
  URI Scheme: 'tel:'
  Functional Specification:
      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.
  Security Considerations:
      See Section 5 of [RFC4415]
  Intended Usage: COMMON
  Authors:  Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author
            contact detail see Authors' Addresses section)
  Any other information the author deems interesting:
    o 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.
    o The kind of subsystem required to initiate a Voice Enumservice
      with this sub-type 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.
    o 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.
    o 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.


Enumservice Name: "pstn"
   Enumservice Type: "pstn"
   Enumservice Subtype: "tel"
   URI Scheme: 'tel:'
   Functional Specification:
		These Enumservices indicate that the remote resource identified can
		be addressed by the associated URI scheme 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 RFC 4694 [10].
   Security Considerations: See Section 7 of [RFC4769]. 
   Intended Usage: COMMON
   Authors:
		Jason Livingood (jason_livingood&cable.comcast.com)
		Richard Shockey (richard.shockey&neustar.biz)
   Any other information the author deems interesting:
		A Number Portability Dip Indicator (npdi) should be used in
		practice (see examples below in Section 4 of [RFC4769]).


Enumservice Name: "pstn"
   Enumservice Type: "pstn"
   Enumservice Subtype: "sip"
   URI Scheme: 'sip:'
   Functional Specification:
		These Enumservices indicate that the remote resource identified can
		be addressed by the associated URI scheme in order to initiate a
		telecommunication session, which may include two-way voice or other
		communications, to the PSTN.
   Security Considerations: See Section 7 of [RFC4769].
   Intended Usage: COMMON
   Authors:
		Jason Livingood (jason_livingood&cable.comcast.com)
		Richard Shockey (richard.shockey&neustar.biz)
   Any other information the author deems interesting:
		A Number Portability Dip Indicator (npdi) should be used in
		practice (see examples below in Section 4 of [RFC4769]).
		

Enumservice Name: "vCard"
   Enumservice Name: "vCard"
   Enumservice Type: "vcard"
   Enumservice Subtype: n/a
   URI Schemes: "http", "https"
   Functional Specification:
      This Enumservice indicates that the resource identified is a plain
      vCard, according to RFC 2426, 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.
   Security Considerations: see Section 5 [RFC4969]
   Intended Usage: COMMON
   Author: Alexander Mayrhofer <alexander.mayrhofer&enum.at>


Enumservice Name: "XMPP"
   Enumservice Type: "xmpp"
   Enumservice Subtype: n/a
   URI Schemes: "xmpp"
   Functional Specification:
      This Enumservice indicates that the resource identified is an XMPP
      entity.
   Security Considerations: see Section 6 of [RFC4979]
   Intended Usage: COMMON
   Author: Alexander Mayrhofer <alexander.mayrhofer&enum.at>


Enumservice Name: "im"
Enumservice Type: "im"
Enumservice Subtypes: N/A
URI scheme(s): "im:"
Functional Specification:
   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 RFC 3861 [4] is used to discover whether an IM protocol 
   supported by the party querying ENUM is also supported by 
   the target resource.
Security considerations: See section 3 of [RFC5028]
Intended usage: COMMON
Author: Rohan Mahy (rohan&ekabal.com)


References
----------
[RFC3761]  P. Falstrom, M. Mealling, "The E.164 to URI DDDS Application (ENUM)",
           RFC 3761, April 2004.

[RFC3762]  O. Levin, "ENUM Service Registration for H.323 URL", RFC 3762, 
           April 2004.

[RFC3764]  J. Peterson, "enumservice registration for SIP Addresses-of-Record",
           RFC 3764, April 2004.

[RFC3953]  J. Peterson, "Enumservice Registration for Presence Services", RFC 3953,
           January 2005.

[RFC4143]  K. Toyoda and D. Crocker, "IFAX service of ENUM", RFC 4143, November 2005.

[RFC4002]  R. Brandner, L. Conroy, and R. Stastny, "IANA Registration for ENUMservices 
           web and ft", RFC 4002, February 2005.

[RFC4238]  G. Vaudreuil, "Voice Message Routing Service", RFC 4238, October 2005.

[RFC4355]  R. Brandner, L. Conroy, and R. Stastny, "IANA Registration for Enumservices 
           email, fax, mms, ems and sms", RFC 4355, January 2006.

[RFC4415]  R. Brandner, L. Conroy and R. Stastny, "IANA Registration for Enumservice 
           Voice", RFC 4415, February 2006.

[RFC4769]  J. Livingood, R. Shockey,"IANA Registration for an Enumservice 
           Containing PSTN Signaling Information", RFC 4769, November 2006.

[RFC4969]  A. Mayrhofer, "IANA Registration for vCard Enumservice", RFC 4969,
           August 2007.

[RFC4979]  A. Mayrhofer, "IANA Registration for Enumservice 'XMPP'", RFC 4979,
           August 2007.

[RFC5028]  R. Mahy, "A Telephone Number Mapping (ENUM) Service Registration 
           for Instant Messaging (IM) Services", RFC 5028, October 2007.

(created 2004-03-12)

[]
