Re: [webrtc-pc] Reject ICE servers with an authority component or / (#2998)

Among the list above:
* the following are failing because they use non-ascii hostnames, which I see no reason to consider invalid (RFC3987 would make them valid, but isn't referenced by RFC7064 or 7065, so we would have to bless them explicitly in the API)
```
  "stun:example(&!$)*+-.;_=~☺org",
  "stun:Ｇｏ.com",
  "stun:你好你好",
  "stun:faß.ExAmPlE",
```

I'm not sure why the RFC doesn't recognize this as a valid IPv6 URL:
```
  "stun:[2001::1]",
```

The following are failing because the URL spec cleans up URLs before parsing (control characters, tabs, line returns, `"`, normalization of dot across encodings, trailing dots); it probably makes sense to benefit from that clean up (given the many things that can go wrong when writing and distributing  JS code), but only if that parsing is also used to feed the ICE agent (which the spec isn't explicit about at the moment):
```
  "stun:example\t.\norg",
  "stun:example.net:\n",
  "stun:GOO​⁠\u200b\u2060\ufeffgoo.com",
  "\u0000\u001b\u0004\u0012 stun:example.com\u001f \r ",
  "stun:www.foo。bar.com",
  "stun:０Ｘｃ０．０２５０．０１",
  "stun:ho\tst",
  "stun:!\"$&'()*+,-.;=_`{}~",
  "stun:\u0001\u0002\u0003\u0004\u0005\u0006\u0007\b\u000b\f\u000e\u000f\u0010\u0011\u0012\u0013\u0014\u0015\u0016\u0017\u0018\u0019\u001a\u001b\u001c\u001d\u001e\u001f^?!\"$%&'()*+,-.;=_`{}~",
  "stun:h\to\ns\rt:9\t0\n0\r0",
  "stun:1.2.3.4.",
```


-- 
GitHub Notification of comment by dontcallmedom
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2998#issuecomment-2330963904 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 5 September 2024 08:50:25 UTC