From 215e247e80602539a07b8f28e6e74c3ae7b327bc Mon Sep 17 00:00:00 2001 From: Tobias Markmann Date: Thu, 18 Mar 2010 17:38:14 +0000 Subject: [PATCH] Usage of defintion lists in glossary of XEP-0278. git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@4103 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0278.xml | 48 ++++++++++++++++++++++-------------------------- 1 file changed, 22 insertions(+), 26 deletions(-) diff --git a/xep-0278.xml b/xep-0278.xml index 93bfbaae..536996f0 100755 --- a/xep-0278.xml +++ b/xep-0278.xml @@ -55,32 +55,28 @@ All signalling, request, response and publishing is done via XMPP, not requiring - - - - - - - - - - - - - - - - - - - - - - - - - -
TermDefinition
RelayRelays are mainly used to transfer traffic to servers located on a NAT:ed (masqueraded) network, where the IP addresses on the NAT:ed network cannot be accessed from the outside. When you use an IP address that is for local use only, you must use NAT and relays because these IP addresses cannot be accessed in any other way. Relays can also be used for non-NAT:ed networks.
Jingle Relay NodeIs an instance of a Relay Service that is negotiable via XMPP, following the procedures described on this Extension.
TrackerIs the entity that trackers Jingle Relay Nodes and also publishes the list upon request. Potentially all Jingle Clients might act as a Node Tracker.
ChannelIs the UDP/TCP Relay Channel, provided by the a Jingle Relay Node. The channel act as a NAT Traversal Channel in order to delivery and receive media.
RequesterIs the Jingle Client that makes requests and make use of a Channel. The Requester receives a relay Transport Candidate that can be used with &xep0176; or &xep0177;.
+
+ +
Relay
+
Relays are mainly used to transfer traffic to servers located on a NAT:ed (masqueraded) network, where the IP addresses on the NAT:ed network cannot be accessed from the outside. When you use an IP address that is for local use only, you must use NAT and relays because these IP addresses cannot be accessed in any other way. Relays can also be used for non-NAT:ed networks.
+ + +
Jingle Relay Node
+
Is an instance of a Relay Service that is negotiable via XMPP, following the procedures described on this Extension.
+ + +
Tracker
+
Is the entity that trackers Jingle Relay Nodes and also publishes the list upon request. Potentially all Jingle Clients might act as a Node Tracker.
+ + +
Channel
+
Is the UDP/TCP Relay Channel, provided by the a Jingle Relay Node. The channel act as a NAT Traversal Channel in order to delivery and receive media.
+ + +
Requester
+
Is the Jingle Client that makes requests and make use of a Channel. The Requester receives a relay Transport Candidate that can be used with &xep0176; or &xep0177;.
+ +

In diagrams, the following conventions are used: