-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "RTP Sending Rules" section #473
Comments
@ibc I'm assuming that one of the things that needs to be covered in the "sending rules" is use of SSRC attributes. For example, when calling receive(), there are reasons why it might make sense to require that if SSRCs are included in parameters.encodings[].ssrc, then they can't be omitted from parameters.encodings[].rtx.ssrc or parameter.encodings[].fec.ssrc (e.g. all or nothing). Do you think that similar logic applies to the send() method? |
I think similar rationale applies. Does it make sense to call |
The specification has added some common checks for both send() and receive() in Section 5.4. If additional checks are needed, please file an issue. |
The spec already includes a "RTP matching rules" so implementors can follow, step by step, and figure out how to deal with received RTP given
receive(parameters)
. So I suggest the spec should also include a "RTP sending rules" for implementors to figure out what exactly to do whensend(parameters)
is called, step by step.After all the rationale given in #471 I do understand what the spec tries to state, but I consider it extremely difficult to be understood by newcomers by just reading the spec. So I mean guidelines such as:
encodings
create an empty one withcodecPayloadType
pointing to the first media codec (no DTMF, CN, etc) in the codecs list.muxId
orssrc
is filled into anencoding
generate random ones and fill those fields.encoding
with nodependencyEncodingId
field a new RTP stream is required, so uniqueness of theirssrc
values is required (or fill them following that requirement).The text was updated successfully, but these errors were encountered: