You're right, we were out of sync; >3. the parser passes "fe80::1_de0" to getaddrinfo(), and gets a > sockaddr_in6 structure (whose sin6_addr member is "fe80::1" and > sin6_scope_id member is the link ID corresponding to interface > "de0"). The browser uses the sockaddr_in6 structure with > connect(2) to connect to the remote web server.
I was assuming that the parser would have to turn fe80::1_de0 into fe80::1%de0 before passing to getaddrinfo(), so would have to parse out the zone explicitly. RFC 4007 says that in the general case, applications shouldn't have to know about hacking zones off - but this is format is explicitly for a special case. Bill -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
