Skip to content
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

Parser can not read attributes with wildcards #172

Closed
atoppi opened this issue Mar 5, 2024 · 2 comments
Closed

Parser can not read attributes with wildcards #172

atoppi opened this issue Mar 5, 2024 · 2 comments

Comments

@atoppi
Copy link

atoppi commented Mar 5, 2024

Your environment.

  • Version: v3.0.6

What did you do?

Trying to negotiate RFC 8888 a=rtcp-fb:* ack ccfb feedback with a media server (Janus) that is offering the feature.

What did you expect?

Pion parses the attribute and adds it to the SDP answer

What happened?

Pion can not parse the attribute due to the presence of wildcard * (as requested by RFC 8888).

sdp/util.go

Lines 171 to 173 in 9704a3f

ptInt, err := strconv.ParseUint(ptSplit[1], 10, 8)
if err != nil {
return codec, parsingFailed

The problem is that the parsing helper is expecting a PT number, whereas the RFC 8888 mandates a wildcard:

The payload type used with "ccfb" feedback MUST be the wildcard type
   ("*").  This implies that the congestion control feedback is sent for
   all payload types in use in the session, including any Forward Error
   Correction (FEC) and retransmission payload types.
@atoppi atoppi changed the title Parser can read attributes with wildcards Parser can not read attributes with wildcards Mar 5, 2024
Sean-Der pushed a commit to thebongy/sdp that referenced this issue Mar 29, 2024
According to Chrome PSA:
https://groups.google.com/g/discuss-webrtc/c/Y_h2B-NOzW0 rtcp-fb:*
might start getting sent by chrome in M112. This was rolled back but may
land again in M114 according to maintainers.

Also, according to
https://webrtc.googlesource.com/src.git/+/8155227/#F0
Chrome may plan on sending both rtcp-fb:* and rtcp-fb:<int> variants for
some time to allow migration in downstream projects.
This change correctly parses the wildcard case to add the feedback to
all payload types found in the SDP, to maintain compatibility with Pion.

Resolves pion#172
@atoppi
Copy link
Author

atoppi commented Apr 2, 2024

FYI the ccfb attribute is now being negotiated, however pion is putting a a=rtcp-fb:X ack ccfb line even if the feedback is not being reigstered on the mediaEngine (e.g. NOT calling ConfigureCongestionControlFeedback).
Is this a regression or an intended behavior?

@Sean-Der
Copy link
Member

Sean-Der commented Apr 2, 2024

@atoppi I believe that is wrong. We should probably only respond with a rtcp-fb if we locally we support it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants