Subject: [MMUSIC] Rtspspec-bugs digest, Vol 1 #83 - 2 msgs

From: [email-masked]
Date: Tue, 15 Jul 2003 20:22:11 -0700

This is an automatic digest of bugs submitted and changed on the RTSP bug tracker.  To see a list of bugs, visit:

http://sf.net/projects/rtspspec

When replying, please make your Subject line more specific than "Re: Rtspspec-bugs digest"

Today's Topics:

   1. [ rtspspec-Bugs-771638 ] a=range in SDP to indicate live media (SourceForge.net)
   2. [ rtspspec-Feature Requests-522607 ] Need END_OF_STREAM request (SourceForge.net)

--__--__--

Message: 1
To: [email-masked]
From: "SourceForge.net" <[email-masked]>
Date: Tue, 15 Jul 2003 07:46:51 -0700
Subject: [rtspspec-bugs] [ rtspspec-Bugs-771638 ] a=range in SDP to indicate live media

Bugs item #771638, was opened at 2003-07-15 16:46
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=771638&group_id=23194

Category: None
Group: Fix for DS - Need WG Input
Status: Open
Resolution: None
Priority: 5
Submitted By: Magnus Westerlund (magwes)
Assigned to: Nobody/Anonymous (nobody)
Summary: a=range in SDP to indicate live media

Initial Comment:
Today there is some confusion on how a client should
know that media is live. To be able to indicate this in
SDP the following is proposed:

Use a=range with any timeformet but in open ended style
will indicate that the media is live, e.g.
a=range:npt=0- or a=range:npt=now-. This makes it
possible to use also for sessions using SMTPE or UTC
times. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=771638&group_id=23194

--__--__--

Message: 2
To: [email-masked]
From: "SourceForge.net" <[email-masked]>
Date: Tue, 15 Jul 2003 08:25:05 -0700
Subject: [rtspspec-bugs] [ rtspspec-Feature Requests-522607 ] Need END_OF_STREAM request

Feature Requests item #522607, was opened at 2002-02-25 20:49
Message generated for change (Comment added) made by magwes
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377747&aid=522607&group_id=23194

Category: None
>Group: Protocol Extension
Status: Open
Priority: 5
Submitted By: Thomas M Zeng (zengtm)
Assigned to: Nobody/Anonymous (nobody)
Summary: Need END_OF_STREAM request

Initial Comment:
Currently there is no way for Server to inform Client 
the completion of a presentation (VOD or Live) without 
issuing a TEARDOWN and thus release reources. What if 
the player wants to use the same resources (pertinent 
to its sessionID) to watch another clip? It would be 
wasteful to teardown and then acquire another 
sessionID immediately.

Would like to see a END_OF_STREAM method added on the 
S->C direction. E.g.:

END_OF_STREAM <p_URI> or <track_URL> RTSP/1.0
SESSION: <session_ID>
REASON: <text describing reason of EOS>

----------------------------------------------------------------------

>Comment By: Magnus Westerlund (magwes)
Date: 2003-07-15 17:24

Message:
Logged In: YES 
user_id=302620

I think this issues should be further discussed. However I
think this clearly is an protocol extension, not part of the
core. It would solve the problem for live and also enable
this to be clear in other scenarios.

The basic semantics is: The server has/will have fulfilled
the PLAY request. 

Putting this into RTSP has the advantage that it becomes
media transport agnostic, however the indication may also be
suitable to put into a media transport protocol. 

Further consideration on this is necessary. If someone has
need, please write up an draft to be an RTSP extension or go
to RTP, etc to put the functionality in. 

----------------------------------------------------------------------

Comment By: Jason Lango (jasonlango)
Date: 2002-03-14 01:55

Message:
Logged In: YES 
user_id=223672

If this makes it into the spec, it would be a useful
addition to know the last packet sequence numbers expected
for each track (to identify packet loss at the end of
stream)

Perhaps this could be conveyed in an RTP-Info header?

i.e.

END_OF_STREAM <p_URI> RTSP/1.0
Session: <session_ID>
RTP-Info: <track1_URL>;seqno=1234567,<track2_URL>;seqno=...
...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377747&aid=522607&group_id=23194

End of Rtspspec-bugs Digest

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