70 likes | 209 Vues
This presentation at IETF 80 highlights the importance of the Happy Eyeballs strategy for improving user experience in IPv6 networking. The document discusses issues encountered with the `getaddrinfo()` function, emphasizing the need for efficient address handling. Key strategies include sequential address trials, prioritizing faster connections, and demoting slower attempts. Notable updates in the working group document include adoption of community feedback and consideration for multiple address types, SRV records, and implementation testing. The goal is to streamline connectivity while addressing potential delays in connection attempts.
E N D
draft-ietf-v6ops-happy-eyeballs Trending towards success for better user experience IETF80, Prague Andrew Yourtchenko, Dan Wing
What’s the problem ? 1) Getaddrinfo(): hostname => address list 2) Try the addresses sequentially
What to do about it ? Let the quickest win
Too many requests ? The winner takes it all Delay the slow one Demote on failure
Changes (up to -01) • Became WG doc (-00) • Incorporated comments – thank you! Scott Brim, Rick Jones, StigVenaas, Erik Kline, BjoernZeeb, Matt Miller, Simon Perreault, Javier Ubillos • +: SRVrecords • + ref: draft-chen-mif-happy-eyeballs-extension • + ref: implementations • +: debug strawman (‘help me with my IPv6’)
TODO • More than one type of addresses (RFC3484) • Selection or retry. • Need more implementation testing experience • “Hysteresis” problem • Delay the conn attempts, not name resolution -> do nothing for single-stack hosts • Prefer IPv6: Decay the P value towards 0 (# conns?) • Need pluggable ‘name-based connect’ API • Write separate draft. Where ?