moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 08:45:04 -05:00
Code Issues Releases Wiki Activity

Usage of defintion lists in glossary of XEP-0278.

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@4103 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Tobias Markmann 2010-03-18 17:38:14 +00:00
parent 732073d306
commit 215e247e80
1 changed files with 22 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
xep-0278.xml
View File

@ -55,32 +55,28 @@ All signalling, request, response and publishing is done via XMPP, not requiring
</section1>
<section1 topic="Terminology" anchor="terminology">
<section2 topic="Glossary" anchor="terms-glossary">
<table caption="Glossary">
<tr>
<th>Term</th>
<th>Definition</th>
</tr>
<tr>
<td>Relay</td>
<td>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.</td>
</tr>
<tr>
<td>Jingle Relay Node</td>
<td>Is an instance of a Relay Service that is negotiable via XMPP, following the procedures described on this Extension.</td>
</tr>
<tr>
<td>Tracker</td>
<td>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.</td>
</tr>
<tr>
<td>Channel</td>
<td>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.</td>
</tr>
<tr>
<td>Requester</td>
<td>Is the Jingle Client that makes requests and make use of a Channel. The Requester receives a relay <link url="#transports">Transport Candidate</link> that can be used with &xep0176; or &xep0177;.</td>
</tr>
</table>
<dl>
<di>
<dt>Relay</dt>
<dd>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.</dd>
</di>
<di>
<dt>Jingle Relay Node</dt>
<dd>Is an instance of a Relay Service that is negotiable via XMPP, following the procedures described on this Extension.</dd>
</di>
<di>
<dt>Tracker</dt>
<dd>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.</dd>
</di>
<di>
<dt>Channel</dt>
<dd>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.</dd>
</di>
<di>
<dt>Requester</dt>
<dd>Is the Jingle Client that makes requests and make use of a Channel. The Requester receives a relay <link url="#transports">Transport Candidate</link> that can be used with &xep0176; or &xep0177;.</dd>
</di>
</dl>
</section2>
<section2 topic="Conventions" anchor="terms-conventions">
<p>In diagrams, the following conventions are used:</p>