diff --git a/xep-0156.xml b/xep-0156.xml index 1be41796..4c8be8f7 100644 --- a/xep-0156.xml +++ b/xep-0156.xml @@ -11,6 +11,7 @@ &LEGALNOTICE; 0156 Draft + Standards Track Standards Council @@ -24,6 +25,13 @@ &hildjj; &stpeter; + &lance; + + 1.1 + 2013-10-22 + ls/psa +

Defined HTTP lookup methods using well-known URIs as specified in RFC 5785.

 + 1.0 2007-06-12 @@ -92,53 +100,120 @@ -

Although &xmppcore; specifies the use of TCP as the method of connecting to an XMPP server, alternative connection methods exist, including the &xep0124; method for which &xep0206; is the XMPP profile, the &xep0025; method (now deprecated), and less common methods such as &wap;. For some of these methods, it is necessary to discover further parameters before connecting, such as the HTTP URL of an alternative connection manager. Currently, if a client application needs to discover alternative connection methods before connecting to an XMPP service, the relevant information needs to be provided manually by a human user, which is cumbersome and error-prone. Thankfully, there are several potential ways to complete this pre-connection service discovery in an automated fashion:

+

Although &xmppcore; specifies the use of TCP as the method of connecting to an XMPP server, alternative connection methods exist, including the &xep0124; method (for which &xep0206; is the XMPP profile) and &xmppoverwebsocket;. For some of these methods, it is necessary to discover further parameters before connecting, such as the HTTP URL of an alternative connection manager. Without ways to auto-discovering alternative connection methods, the relevant information would need to be provided manually by a human user, which is cumbersome and error-prone.

+

This document defines two ways to encapsulate information about alternative connection methods for auto-discovery:

    -

  1. Define a &w3wsdl; definition (or other XML file format) and a canonical URL for that definition at a domain that offers XMPP services. Unfortunately, this approach requires access to the HTTP server for the domain (and quite possibly to the root directory thereof), which can be difficult for XMPP server administrators to arrange. In addition, it requires a client to retrieve the relevant file via HTTP before performing DNS lookups and XMPP connection; it would be more efficient to use recognized DNS methods since DNS lookups are already required by RFC 6120.

    2. -

  2. Define a way to specify alternative connection methods as part of the existing DNS SRV records (see &rfc2782;) for a domain that offers XMPP services. While this approach sounds promising, it is not feasible since the DNS SRV Target field can be used only to specify domain names and cannot be used to specify full URIs (such as the URL for an HTTP connection manager).

    3. -

  3. Define a way to specify alternative connection methods using the "straightforward NAPTR" (S-NAPTR) profile of the Dynamic Delegation Discovery System (see &rfc3958; and &rfc3401;). Unfortunately, S-NAPTR also does not allow inclusion of full URIs, and thus does not meet the requirements for discovery of alternative connection methods.

    4. -

  4. Define a way to specify alternative connection methods using the "URI-enabled NAPTR" (U-NAPTR) profile of the Dynamic Delegation Discovery System (see &rfc4848;). While this is a valid approach that is worth pursuing, the authors are concerned about the deployability of such an approach given the rarity of support for DDDS and U-NAPTR, especially in client-side applications (the main focus of this specification).

    5. -

  5. Define a way to specify alternative connection methods via properly-formatted DNS TXT records (see &rfc1464;). While this approach requires an update to the DNS records for the server domain, that is usually necessary in order to establish XMPP services in the first place. Furthermore, although there are some perils to be avoided in the use of DNS TXT records (e.g., wildcards), the technology is well understood and widely deployed (e.g., it is used by the Sender Policy Framework and SenderID email server verification technologies).

    6. -
-

This document defines a way to encapsulate information about alternative connection methods in DNS TXT resource records. However, the authors will monitor the availability of DDDS-based systems supporting U-NAPTR, and might request deprecation of the DNS TXT methods defined in this document at some point in the future.

- - -

The following format for DNS TXT resource records is specified in RFC 1464:

- <"attribute name=attribute value"> - ]]> -

This document specifies that the following additional rules apply for DNS TXT resource records used to specify alternative connection methods:

-
    -
  1. It is RECOMMENDED for the owner to be "_xmppconnect".
    2. -
  2. The class field SHOULD be IN.
    3. -
  3. The ttl field is OPTIONAL.
    4. -
  4. The attribute name SHOULD begin with the string "_xmpp-client-" or "_xmpp-server-" and SHOULD be registered as described in the XMPP Registrar Considerations section of this document.
    5. -
  5. If the txt-data field contains only an attribute name (i.e., no unquoted "=" character followed by additional characters), the receiving application SHOULD interpret it as indicating the presence of the attribute or feature with no defined value.
    6. -
  6. If the txt-data field contains an unquoted "=" character, it MUST also contain an attribute value.
    7. +
  7. DNS TXT resource records
    8. +
  8. Link entries in a server's "host-meta" file
 - -

The following business rules apply:

-
    -
  1. TXT lookups MUST be used only as a fallback after the methods specified in RFC 6120 have been exhausted. The point of this rule is to prevent someone from defining a new XEP-0156 connection method like "_xmpp-client-tcp" to override the SRV records defined in the core XMPP specification.
    2. -
  2. A domain SHOULD NOT present information in DNS TXT records that is available via the DNS SRV records defined in RFC 6120.
    3. -
  3. The order of DNS TXT records SHOULD NOT be interpreted as significant by the presenting domain or the receiving entity.
    4. -
- - -

The following examples show two DNS TXT resource records: the first indicates support for the XMPP Over BOSH connection method defined in XEP-0124 and XEP-0206 and the second indicates support for WAP connections (the latter connection method is not yet defined).

- + + +

The following format for DNS TXT resource records is specified in RFC 1464:

+ <"attribute name=attribute value"> + ]]> +

This document specifies that the following additional rules apply for DNS TXT resource records used to specify alternative connection methods:

+
    +
  1. It is RECOMMENDED for the owner to be "_xmppconnect".
    2. +
  2. The class field SHOULD be IN.
    3. +
  3. The ttl field is OPTIONAL.
    4. +
  4. The attribute name SHOULD begin with the string "_xmpp-client-" or "_xmpp-server-" and SHOULD be registered as described in the XMPP Registrar Considerations section of this document.
    5. +
  5. If the txt-data field contains only an attribute name (i.e., no unquoted "=" character followed by additional characters), the receiving application SHOULD interpret it as indicating the presence of the attribute or feature with no defined value.
    6. +
  6. If the txt-data field contains an unquoted "=" character, it MUST also contain an attribute value.
    7. +
+ + + +

The following business rules apply:

+
    +
  1. TXT lookups MUST be used only as a fallback after the methods specified in RFC 6120 have been exhausted. The point of this rule is to prevent someone from defining a new XEP-0156 connection method like "_xmpp-client-tcp" to override the SRV records defined in the core XMPP specification.
    2. +
  2. A domain SHOULD NOT present information in DNS TXT records that is available via the DNS SRV records defined in RFC 6120.
    3. +
  3. The order of DNS TXT records SHOULD NOT be interpreted as significant by the presenting domain or the receiving entity.
    4. +
+ + + +

The following examples show two DNS TXT resource records: the first indicates support for the XMPP Over BOSH connection method defined in XEP-0124 and XEP-0206 and the second indicates support for WAP connections (the latter connection method is not yet defined).

+ + ]]> + + + + + + +

The HTTP lookup method uses Web Host Metadata &rfc6415; to categorize and list the URIs of alternative connection methods. It is primarily intended for use by clients in environments where the ability to perform DNS queries is restricted, such as in web browsers.

+

Each alternative connection method is specified in the host-meta (XRD) file using a distinctive link relation &rfc5988;. This specification defines several extension relation types:

+
    +
  • urn:xmpp:alt-connections:httppoll
    • +
  • urn:xmpp:alt-connections:websocket
    • +
  • urn:xmpp:alt-connections:xbosh
    • +
+ + + +

The following business rules apply:

+
    +
  1. HTTP queries for host-meta information MUST be used only as a fallback after the methods specified in RFC 6120 have been exhausted.
    2. +
  2. A domain SHOULD NOT present information in host-meta link records that is available via the DNS SRV records defined in RFC 6120.
    3. +
  3. The order of XMPP related link entries in the host-meta file records SHOULD NOT be interpreted as significant by the presenting domain or the receiving entity.
    4. +
+ + + +

The following examples show two host-meta link records: the first indicates support for the XMPP Over BOSH connection method defined in XEP-0124 and XEP-0206 and the second indicates support for the &xmppoverwebsocket; connection method.

+ + + ... + + + ... + + ]]> +

It is possible to use an alternative JSON format for host-meta information, in which case the above example would be presented as:

+ + + +

It is possible that advertisement of alternative connection methods can introduce security vulnerabilities, since a connecting entity (usually a client) might deliberately seek to connect using the method with the weakest security mechanisms (e.g., no channel encryption or relatively weak authentication). Care needs to be taken in determining which alternative connection methods are appropriate to advertise.

 + -

This document requires no interaction with &IANA;.

+

Because the link relations specified here are extension relation types rather than registered relation types (see Section 4 of RFC 5988), this document requires no interaction with &IANA;.

 + + +

The ®ISTRAR; shall include 'urn:xmpp:alt-connections' in its registry of protocol namespaces (see &NAMESPACES;).

+
    +
  • urn:xmpp:alt-connections
    • +
+ +

The ®ISTRAR; maintains a registry of attributes for use in DNS TXT resource records that advertise alternative XMPP connection methods (see &ALTCONN;).