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

From: [email-masked]
Date: Tue, 07 Jan 2003 12:17:28 -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-663715 ] Requirement levels for Transport:SSRC needs clarification (SourceForge.net)

--__--__--

Message: 1
To: [email-masked]
From: "SourceForge.net" <[email-masked]>
Date: Tue, 07 Jan 2003 06:31:21 -0800
Subject: [rtspspec-bugs] [ rtspspec-Bugs-663715 ] Requirement levels for Transport:SSRC needs clarification

Bugs item #663715, was opened at 2003-01-07 15:31
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=377744&aid=663715&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: Requirement levels for Transport:SSRC needs clarification

Initial Comment:
The SSRC parameter in the transport header has a few
unclarities.
- Why should a client be allowed to propose a SSRC to
the server?
- If allowed as current text indicates, what is the
requirement level on the server to follow the proposed
value. MAY or SHOULD.

First I would like to know the motivation a client has
to suggest a SSRC. This can probably not be removed but
unless there is good reasons for it I think the
requirement on a server to follow the request is MAY.
With a good motivation  the level is SHOULD. 

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

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

End of Rtspspec-bugs Digest

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