[interop] next steps

[Mickael Remond]

* Peter Saint-Andre <stpeter at jabber.org> [2006-08-23 14:02:22 -0600]:

> I'd like to start working on setup of our "private network" for interop
> and compliance testing over the Internet (yes, the interop event was
> fun, but we should be able to do testing when we're not all in the same
> room). I have access to DNS for xmpp.org so it is easy for me to point
> yourserver.xmpp.org at an IP address. I think we should set this up so
> that these servers are not accessible from outside the .xmpp.org domain
> (i.e., we can do testing among servers in this private network, but
> domains on the rest of the XMPP network won't be able to do s2s with our
> test domains -- would people running servers do that via firewall rules
> or somesuch?). Also I think we want to enable client developers to have
> accounts on each domain so they can test their clients against each
> server codebase. IMHO we need to define the terms and conditions for
> developers to gain access to this private network, so I will work on a
> document describing those (essentially an NDA). We probably also need a
> registration process of some kind, which can be informal for now but
> which we'll migrate to www.xmpp.org once we've converted that site to
> Drupal.
> 
> Am I missing anything?

I think the connection restriction should probably be IP based (we might
prevent anyone from any other given IP to connect in S2S.
We will be running the server on a public IP but with a firewall setup
on the server.
Regarding the clients connection (for testing), restrictions might be
more difficult to set-up. Can we say that there an IP lists that
connection are authorized from ? It might be too difficult to maintain,
I do not know.

There is also probably a need to setup the certificate authority like
this was done during the interop event.

I hope this helps,

-- 
Mickaël Rémond
 http://www.process-one.net/