You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice to determine the best way to handle the case where sdp.Addr is empty string. To the best of my knowledge, that shouldn't happen during parsing, and is most likely indicative of an the calling function failing to supply the value. See also:
Nevertheless, as you said a empty "c" line addr shouldn't happen and at least in the WebRTC space I think most ppl would just set it to IP6 :: (former it was IP4 0.0.0.0)
It is worth noting that the use of IP6 :: has been selected over IP4
0.0.0.0, even though [RFC3264] already gives the latter semantics
appropriate for such use. The reason for this choice is the historic
use of 0.0.0.0 as a means of putting a stream on hold [RFC2543] and
the ambiguity that this may cause with legacy libraries and
applications.
It'd be nice to determine the best way to handle the case where
sdp.Addr
is empty string. To the best of my knowledge, that shouldn't happen during parsing, and is most likely indicative of an the calling function failing to supply the value. See also:gosip/sdp/sdp.go
Line 302 in 5219113
The text was updated successfully, but these errors were encountered: