[Stox] 503 / <service-unavailable/>

Peter Saint-Andre <stpeter@stpeter.im> Tue, 30 July 2013 12:24 UTC

Message-ID: <51F7B073.9050101@stpeter.im>
Date: Tue, 30 Jul 2013 14:24:19 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "stox@ietf.org" <stox@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [Stox] 503 / <service-unavailable/>
Precedence: list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Sparks pointed out to me in person today that the usage of SIP
error 503 is broken in stox-core.

RFC 3261 says:

21.5.4 503 Service Unavailable

   The server is temporarily unable to process the request due to a
   temporary overloading or maintenance of the server.  The server MAY
   indicate when the client should retry the request in a Retry-After
   header field.  If no Retry-After is given, the client MUST act as if
   it had received a 500 (Server Internal Error) response.

   A client (proxy or UAC) receiving a 503 (Service Unavailable) SHOULD
   attempt to forward the request to an alternate server.  It SHOULD NOT
   forward any other requests to that server for the duration specified
   in the Retry-After header field, if present.

   Servers MAY refuse the connection or drop the request instead of
   responding with 503 (Service Unavailable).

Thus the applicability of 503 in SIP is quite different from that of
<service-unavailable/> in XMPP. In XMPP, a client (or, more often, a
server on its behalf) can return <service-unavailable/> to mean
"sorry, I can't provide the service you've requested for the user@host
you've tried to contact, but that applies only to that user@host". If
the XMPP-to-SIP gateway returns <service-unavailable/> for a single
account in that way, the SIP-to-XMPP gateway on the other side won't
be able to send *anything* to the peer domain. This breaks all
server-to-server communication. Thus Robert suggested that we take a
very close look at our mapping into SIP 503, and very probably never
use it (or only in very rare cases). I haven't had time yet to look at
this in detail, but I will do so before the STOX session on Thursday.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJR97BzAAoJEOoGpJErxa2poNsQAJSUWcTdBymR3H3UrWe490vY
Q5aX7WEiljJ8ZiORPA+DEJdnlxhR0DJ5WGBMrJ6SLW+cDELTtb0q1bs7nTyG6ozH
ys7Cy7sbWFL7MBnUDQP4xcSwQXQURe728TIjLl5rZOXsvKz7ItgkogRHCpavPEea
tcL153WA0hpNdYemq2j1dDDwnhpygy2HqJLWOntUs060jPXXgTEsr9+dl2s92rWF
YfXe6qFYVtRslMk7joIh3gmBFDTXz7YtwTflBqpx0BinsQ3tbKMIY683qeFeZRSR
zvyf6X6cZAs26/oOtzUwVH95oDvdFaXfNbS2f25XOHOwv8fcL9hOcOIyDgxO1BOJ
AB+9j2T4hGnwWxagtYq/kDUiUuQuCHb/XV6dgOtkRoFxYRkNpCMGqcbtsWMZAMFR
tkMG3W+w0uyQCbnx+S6vZVwFV6yIE2JfTPCh3bRJUmSH9WKM4XsGNMhbhC0TNXCF
RbpvobMgSRXJ9n8gFIHx4g8GfTYVEkctYQC5yf6tvL4hFJ4ZIbRpYw26x0BMtFjc
H83QTfvmRobKnC4Ga8QiOjP4HymUyfqgMOuLj2HilitbeggkPGi9KcIOTwTHT9WR
ib5X6AeyDc9rVfiV39OxJMQgxoN9Zz5QNNJ7sjE3jPwYV6dvx3aUmUdtQjF8zqCv
mz2huiy0YOm9vnTuLjB0
=yvwy
-----END PGP SIGNATURE-----

[Stox] 503 / <service-unavailable/> Peter Saint-Andre