Support unmarshalling SDP containing unknown attributes or values about sdp HOT 3 CLOSED

If anyone is interested in this I think it would be a great idea to export the lexer. Users could override specific steps in the state machine if needed.

I haven't seen/heard any demand for this in the 3 years since this issues has opened. I am going to close as 'not planned'. If someone has an interest to take this on I would love to help them though!

from sdp.

I am worried if we make a permissive path it may result in bad SDPs getting through the non-permissive path.

What do you think of maybe providing a tokenizer so that users can go line by line themselves. That way we don't have two Unmarshal functions. Users that want to take the risk can go do it, but not complicate the API maybe?

from sdp.

I am worried if we make a permissive path it may result in bad SDPs getting through the non-permissive path.

From my point of view, it really depends on what you want to do when parsing SDP. For instance, what I'm working with right now only cares about getting a Go structure that it can manipulate (e.g. append candidates retrieved separately) and then marshal into a string it can pass on; in which case the extra validation is nice to have (as long as it doesn't get in the way, e.g. with bandwidth types) but not what I'm primarily looking for.

To be perfectly honest I've suggested to have a second Unmarshal function because that's the only idea I had (and didn't have a lot of time to write this issue) but other solutions might be better as long as they can serve the same goal.

from sdp.