docfaraday
docfaraday
Given that RFC8853 requires a reofferer to honor the removal of rids from the answer, and given that RFC8853 also requires the answerer to honor the removal of rids from...
I should also note that if we do allow rid reordering in a reoffer, we should not mess with [[SendEncodings]] in any way as a result. We should probably just...
Generally, my preference is to follow the SDP negotiation rules in the IETF specifications wherever possible. While throwing errors when we encounter something valid-but-weird is one way to simplify the...
Some of the text in the description was not rendering the way I expected it to, but it is now fixed. Really, it boils down to whether '-' and '_'...
> So, if I understand correctly, it is `[A-Za-z0-9\-_]{1}` from 8851 vs. `[A-Za-z0-9]{1,16}` for one-byte header and `[A-Za-z0-9]{0,255}` for two-byte header from 8852 Is that correct? 8851 says [A-Za-z0-9_-]{1,} (or...
So I guess there are the following questions: 1. Do we want to specify an error to throw if the length of the rid is valid according to RFC 8852,...
> In practice, people use single-character RIDs, because anything bigger bloats the RTP header. (We also had an issue with the size of MID, which ended up recommending 16 bytes...
> I think this needs to be resolved in the RFC that create the problem. I could file an erratum on RFC 8851. We may also want to clarify in...
Filed https://www.rfc-editor.org/errata/eid7132
I discussed the possibility of restricting the size to 16 instead of 255 with abr, and he pointed out that this might be something worth doing in a bis, but...