Subject: [MMUSIC] RTSP 2.0 Issue: 503 issues (see also SIP)

From: "Martin Stiemerling" <[email-masked]>
Date: Tue, 29 Jun 2010 14:54:27 +0200

Hi,

There is one open issue related to the 503 response in RTSP 2.0 (raise by Wolfgang Beck). From the tracker:
"Section 15.5.4
Response 503 has caused some headache in SIP. Some implementors tried the next IP address as returned in the DNS answer, some just gave up."
(see also RFC 5390)

Section 15.5.4. 503 Service Unavailable
   The server is currently unable to handle the request due to a
   temporary overloading or maintenance of the server.  The implication
   is that this is a temporary condition which will be alleviated after
   some delay.  If known, the length of the delay MAY be indicated in a
   Retry-After header.  If no Retry-After is given, the client SHOULD
   handle the response as it would for a 500 response.

Any thoughts on this? 

I assume that we need to fix this NOW, as we otherwise will have to fix this during the IESG review. 

You can find this also in the tracker:
https://sourceforge.net/tracker/?func=detail&aid=3007825&group_id=23194&atid=377744

  Martin

[email-masked]

NEC Laboratories Europe - Network Research Division
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014