moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

1.9rc1 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3579 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-10-28 03:34:29 +00:00
parent e508a0ba7f
commit 5007de986b
1 changed files with 24 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
xep-0124.xml
View File

@ -11,6 +11,7 @@
&LEGALNOTICE;
<number>0124</number>
<status>Draft</status>
<interim/>
<type>Standards Track</type>
<jig>Standards</jig>
<dependencies>
@ -28,6 +29,12 @@
&dizzyd;
&stpeter;
&metajack;
<revision>
<version>1.9rc1</version>
<date>in progress, last updated 2009-10-27</date>
<initials>psa</initials>
<remark><p>Added registration of port 5280 with IANA.</p></remark>
</revision>
<revision>
<version>1.8</version>
<date>2009-04-30</date>
@ -962,11 +969,26 @@ Content-Length: 68
</section2>
</section1>
<section1 topic='IANA Considerations' anchor='iana'>
<p>This document requires no interaction with &IANA;.</p>
<p>TCP port 5280 is conventionally used for communication between BOSH clients and BOSH connection managers (where the number 52 is common to ports 5222 and 5269 used in XMPP and 80 is the same as the port used in HTTP). Although use of this port is OPTIONAL, it is helpful to define this port in a standardized way so that BOSH clients can contact any given XMPP service via BOSH without the need for DNS TXT records (see &xep0156;) or more advanced methods such as U-NAPTR. Therefore, this document directs the &REGISTRAR; to register TCP port 5280 with the IANA for inclusion in its port registry at &ianaports;, in accordance with &xep0053;.</p>
<p>The following registration data will be provided at &lt;<link url='http://www.iana.org/cgi-bin/usr-port-number.pl'>http://www.iana.org/cgi-bin/usr-port-number.pl</link>&gt;, where the registrant name and email address will be "XMPP Registrar" and "registrar@xmpp.org" respectively.</p>
<div class='indent'>
<ol start='1'>
<li>Protocol-number: TCP</li>
<li>Message formats: [see XEP-0124]</li>
<li>Message types: [see XEP-0124]</li>
<li>Message op codes: [see XEP-0124]</li>
<li>Message sequences: [see XEP-0124]</li>
<li>Protocol functions: Bidirectional-streams Over Synchronous HTTP (BOSH) is a long polling method that essentially emulates TCP over HTTP, thus providing an HTTP binding for XMPP</li>
<li>Broadcast or multicast? No</li>
<li>Technical description: A complete technical description of BOSH is provided in XEP-0124, published by the XMPP Standards Foundation at &lt;http://xmpp.org/extensions/xep-0124.html&gt;</li>
<li>Proposed name: Bidirectional-streams Over Synchronous HTTP</li>
<li>Short name: xmpp-bosh</li>
</ol>
</div>
</section1>
<section1 topic='XMPP Registrar Considerations' anchor='registrar'>
<section2 topic='Protocol Namespaces' anchor='registrar-ns'>
<p>The &REGISTRAR; includes 'http://jabber.org/protocol/httpbind' in its registry of protocol namespaces.</p>
<p>The XMPP Registrar includes 'http://jabber.org/protocol/httpbind' in its registry of protocol namespaces.</p>
</section2>
</section1>
<section1 topic='XML Schema' anchor='schema'>