Re: [MMUSIC] FW: I-D Action:draft-stiemerling-rtsp-announce-01.txt

[Joe Pallas <pallas at cs.stanford.edu>]

On Mar 7, 2008, at 5:01 AM, Martin Stiemerling wrote:

>> 2.  This draft mandates that the connections should be
>> persistent between client and server for ANNOUNCE to work.
>
> Right. However, mandates is too strong. It just says that in order  
> to get this working, client and server do need an open and running  
> TCP connection. Otherwise, the server has no means to send the  
> asynchronous notification to the client.

One thing I think should be included is some discussion about how the  
server associates a TCP connection with an RTSP session.  Obviously,  
the TCP connection that a SETUP request comes in on would be used for  
that session while the connection is active.  If that connection is  
terminated before the session is torn down, and a client establishes  
a new TCP connection before the session times out, the server needs  
to recognize that the new connection is associated with that session.

This doesn't need to be complicated: the last connection that  
received a request with the session-id should probably be the  
connection associated with the session, and the client can achieve  
this by sending a keep-alive style SET_PARAMETER.  But saying so  
explicitly might be a good idea.

joe

_______________________________________________
mmusic mailing list
mmusic at ietf.org
https://www.ietf.org/mailman/listinfo/mmusic