search

ircv3 / ircv3-specifications

IRCv3 specifications | Roadmap: https://git.io/IRCv3-Roadmap | Code of conduct: http://ircv3.net/conduct.html
http://ircv3.net/
778 stars 79 forks source link

Happy Eyeballs / RFC 6555 #189

Open Mikaela opened 8 years ago

Mikaela commented 8 years ago

As SNI is required, I am wondering if Happy Eyeballs could be too.

It would make the capable clients handle IPv6 transition more smoothly.

This came to mind because of https://github.com/kvirc/KVIrc/issues/1760#issuecomment-163951304 and I started wondering if many people think like that which doesn't just work as we have IPv6-only systems and Carrier Grade NATs.

I understand if this isn't possible as unlike SNI, Happy Eyeballs would most likely be more than just one line.

grawity commented 8 years ago

Speaking of lines, I wonder if any event loops support this natively, or does it usually need to be done by hand?

(Then again, it's IRC – everyone does everything by hand anyway.)

SadieCat commented 8 years ago

SNI has a strong security reason for existing as a mandatory spec, this seems like it would be better off in a BCP document somewhere.

Mikaela commented 8 years ago

From what I understood from @grawity at IRC, the IRCv3 equivalent of BCP would be either optional extension (I prefer this bwcause lf the table) or alternatively documentation/, so I am not closing this.