> >Technically, this is not really true since links are larger scope than > >interfaces. > > Does anyone have an implementation today that has any special > handling for multi-interface links? If you want to send a > packet to a LL address, are you supposed to send it out all of > the interfaces for that link, or only one of them (if so, which > one)?
No special handling, you can just have multiple interfaces on the same link. When sending to a link local address, system picks one interface (unless application or some other configuration setting does not give some preference). > If the application has a dialogue box in which the customer can specify > an IP address (instead of a host name), the UI will need to allow the > user to enter a zone ID, as well. That isn't true in IPv4, but it will > be needed in IPv6. Actually, almost similar thing is needed in IPv4 due nasty use of private addresses (ISP offers link with 10-net addresses, and your company has also internal net with 10-net addresses (via VPN tunnel). Now, when you type in addresses, you need to specify whether you mean address within ISP space or company space... And, even nastier, you have to specify the "scope" for DNS too: resolve from ISP nameserver or company nameserver (via VPN)? Not really doably with traditional IPv4 stack, but with scoped IPv6/4 stack you can actually make it work. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
