diff --git a/xep-0176.xml b/xep-0176.xml index 650cb224..2c0e71d6 100644 --- a/xep-0176.xml +++ b/xep-0176.xml @@ -522,7 +522,7 @@ INITIATOR RESPONDER

As the initiator and responder receive candidates, they probe the various candidate transports for connectivity. In performing these connectivity checks, each party SHOULD follow the procedure specified in Section 7 of &icecore;. The following business rules apply:

    -
  1. Each party sends a STUN Binding Request (see &rfc5489;) from each local candidate it generated to each remote candidate it received.
    2. +
  2. Each party sends a STUN Binding Request (see &rfc5389;) from each local candidate it generated to each remote candidate it received.
  3. In accordance with &icecore;, the STUN Binding Request MUST include the PRIORITY attribute (computed according to Section 7.1.1.1. of &icecore;).
  4. For the purposes of the Jingle ICE-UDP Transport Method, both parties are full ICE implementations and therefore the controlling role MUST be assumed by the initiator and the controlled role MUST be assumed by the responder.
  5. The STUN Binding Requests generated by the initiator MAY include the USE-CANDIDATE attribute to indicate that the initiator wishes to cease checks for this component.
    6. diff --git a/xep-0177.xml b/xep-0177.xml index 60662531..a32d17a3 100644 --- a/xep-0177.xml +++ b/xep-0177.xml @@ -199,7 +199,7 @@ INITIATOR RESPONDER Permissive - Server reflexive or peer reflexive candidate discovered via STUN (see &rfc5489;) + Server reflexive or peer reflexive candidate discovered via STUN (see &rfc5389;) diff --git a/xep-0215.xml b/xep-0215.xml index 8912b0dd..f7bd78a3 100644 --- a/xep-0215.xml +++ b/xep-0215.xml @@ -73,7 +73,7 @@ -

    An XMPP client or other entity may need to discover services external to the XMPP network in order to complete certain XMPP-related use cases. One example is the discovery of STUN servers (see &rfc5489;) and STUN relays (see &turn;) for the sake of negotiating media exchanges via &xep0176;. The protocol specified herein is functionally equivalent to the protocol currently used in the Google Talk service for discovery of STUN servers, as documented at <http://code.google.com/apis/talk/jep_extensions/jingleinfo.html>, but has been broadened in scope to address additional use cases if desired. An XMPP entity can already discover such external services in several ways, including:

    +

    An XMPP client or other entity may need to discover services external to the XMPP network in order to complete certain XMPP-related use cases. One example is the discovery of STUN servers (see &rfc5389;) and STUN relays (see &turn;) for the sake of negotiating media exchanges via &xep0176;. The protocol specified herein is functionally equivalent to the protocol currently used in the Google Talk service for discovery of STUN servers, as documented at <http://code.google.com/apis/talk/jep_extensions/jingleinfo.html>, but has been broadened in scope to address additional use cases if desired. An XMPP entity can already discover such external services in several ways, including:

    1. The service is specified in the application's default settings.
    2. The service is manually added into the application's configuration by a human user.
      3. diff --git a/xep.ent b/xep.ent index 5a6737f2..18acd217 100644 --- a/xep.ent +++ b/xep.ent @@ -543,7 +543,7 @@ THE SOFTWARE. RFC 5054 RFC 5054: Using the Secure Remote Password (SRP) Protocol for TLS Authentication <http://tools.ietf.org/html/rfc5054>." > RFC 5081 RFC 5081: Using OpenPGP Keys for Transport Layer Security (TLS) Authentication <http://tools.ietf.org/html/rfc5081>." > RFC 5122 RFC 5122: Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP) <http://tools.ietf.org/html/rfc5122>." > -RFC 5489 RFC 5489: Session Traversal Utilities for NAT (STUN) <http://tools.ietf.org/html/rfc5489>." > +RFC 5389 RFC 5389: Session Traversal Utilities for NAT (STUN) <http://tools.ietf.org/html/rfc5389>." >