Subject: [MMUSIC] RTSP: Transport model requirements (477427)

From: Rob Lanphier <[email-masked]>
Date: Thu, 31 Jan 2002 19:51:45 -0800 (Pacific Standard Time)

This is a more involved issue.

From the bug (http://rtsp.org/bug477427):
> Which connection models are required. Is non persitent TCP connections a
> MUST support, or only RECOMMENDED?

    * RESOLVED: Default is connection-oriented (thus, required), and
connectionless MAY be implemented.  We need to define header and response
for non-persistent connections.  Look into "Supported" header in SIP.

We still haven't entirely resolved this issue.  Is the "Supported" header
the right model to use?

Rob
-----
Raw notes:

477427

    * JS: We close things down, but we'd like to fix that
    * RL: how does liveness indication work
    * JS: we use RTCP
    * JS: Darwin hangs up if RTCP isn't received.
    * AJ: Correct. Some firewalls don't work well with this.
    * MW: There's a PING method request
    * TM: security issues with connectionless
    * JS: ssl is the way to solve this if that's a big issue
    * MW: what about original issue?
    * JS: needs to be negotiable option
    * MW: Use spec terminology: "persistent" and "non-persistent"
    * JS: Pragma specifically removed.
    * AK: perhaps "Supported" should be used
    * RESOLVED: define header and response for non-persistent connections.
Default is connection-oriented, and connectionless MAY be implemented.
Look into "supported" header.

_______________________________________________
mmusic mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/mmusic