Comments (4)
alvestrand
commented on August 22, 2024
public: Candidates with private IP addresses [RFC1918] will be
filtered out. This prevents exposure of internal network details,
at the cost of requiring relay usage even for intranet calls, if
the NAT does not allow hairpinning as described in [RFC4787],
section 6.
from webrtc-pc.
alvestrand
commented on August 22, 2024
Proposal needs to be sent to the list.
Note: Adding the "public" value will mean that creating a PC with this new value will cause an exception when run on old browser (enum compatibility). This is seen as a feature.
from webrtc-pc.
alvestrand
commented on August 22, 2024
Related to the IP privacy issue.
from webrtc-pc.
alvestrand
commented on August 22, 2024
Changes have been merged. This is now defined in a JSEP reference.
from webrtc-pc.
Related Issues (20)
- RTCSessionDescriptionInit vs "local" RTCLocalSessionDescriptionInit HOT 2
- Review mute/unmute/ended and constraints on RTCRtpReceiver's track. HOT 2
- Alternative storage for RTCCertificates needed HOT 6
- simple webrtc connection and manual signaling (QR, JSON, Carrier pigeon) - consent time out prevents connection HOT 3
- RTCIceCandidate's relayProtocol and url members can be null but not absent
- Missing tests for candidate amendments
- Incorporate jitterBufferTarget
- Confusion over duplicates in setCodecPreferences? Why allow them? HOT 10
- receiver.getParameters().codecs is broken (regression) HOT 4
- setCodecPreferences should take sequence<RTCRtpCodec>
- setCodecPreferences should trigger negotiationneeded HOT 3
- Implementations only update getParameters().codecs when negotiation has finished HOT 3
- Comparison rules for RTCRtpCodec needs clarification on how mimeType is compared HOT 10
- Promises on the operations chain may never settle HOT 3
- RTCRtpCodecCapability is superfluous and should be deleted from the spec. HOT 3
- PC.local_description and friends - snapshot views or dynamic views? HOT 4
- Write WPT to check RTCIceCandidatePair is now an interface HOT 1
- Unspecified whether the data channel error event fires from SCTP ABORT
- Consider merging transferable RTCDataChannel from webrtc-extensions HOT 7
- RTCRtpParameters.codec matching is probably too strict HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from webrtc-pc.