Subject: [MMUSIC] Rtspspec-bugs digest, Vol 1 #71 - 1 msg

From: [email-masked]
Date: Wed, 22 Jan 2003 12:15:54 -0800

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-672160 ] Describe a interleaved RTSP channel for client RR reports (SourceForge.net)

--__--__--

Message: 1
To: [email-masked]
From: "SourceForge.net" <[email-masked]>
Date: Tue, 21 Jan 2003 16:28:52 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-672160 ] Describe a interleaved RTSP channel for client RR reports

Bugs item #672160, was opened at 2003-01-22 00:28
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=672160&group_id=23194

Category: General
Group: Fix DS - Needs clarificiation
Status: Open
Resolution: None
Priority: 5
Submitted By: Thomas M Zeng (zengtm)
Assigned to: Rob Lanphier (robla)
Summary: Describe a interleaved RTSP channel for client RR reports 

Initial Comment:
 In the section on RTP interleaved over the RTSP 
channel (section 10.13), there was no
mention of the client sending RTCP RR back to the 
server.  Are these still
present?  They did specify the sender reports from the 
server to client, but that's it.  The back channel is 
symmetric to the RTCP for server to send SRs and 
should be described as such (i.e. described in Transport 
headers).

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

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

End of Rtspspec-bugs Digest

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