[Standards-JIG] Why is S2S on 5269 and not 5222?

Chris Mullins chris.mullins at coversant.net
Fri Dec 1 22:41:08 UTC 2006

The only reason I bring it up is that getting clients to open firewall
ports is difficult.

... and getting them to open 2 ports is twice as hard as getting them to
open one. 

Merging these onto the same port eliminates this problem.

Chris Mullins

-----Original Message-----
From: standards-jig-bounces at jabber.org
[mailto:standards-jig-bounces at jabber.org] On Behalf Of Peter Saint-Andre
Sent: Friday, December 01, 2006 2:32 PM
To: XMPP Extension Discussion List
Subject: Re: [Standards-JIG] Why is S2S on 5269 and not 5222?

Chris Mullins wrote:
> I'm scoping some upcoming S2S work in our server, and I keep wondering
> why S2S connections are on a different port than standard connections?

A few reasons:

1. It's always been that way and it ain't going to change. Extra points
if you know why those two numbers were chosen. :-)

2. The ability to open only c2s or s2s traffic enables server
administrators to do things like open up s2s to/from an internal server
via firewall rules.

3. Why does it really matter since we have SRV?


Peter Saint-Andre
Jabber Software Foundation

More information about the Standards mailing list