On Thu, 17 Jul 2003 [EMAIL PROTECTED] wrote: > >> to say it backwards, for the ICMPv6 redirect to work correctly, nexthop > >> address on the routing table MUST be link-local (even when manually > >> configured). i think adding this text clarifies the concern. > > > >Yes, this would fix and clarify the issue, but I think it might > >substantially change the overall assumption of the document, i.e. > >"next-hop must be onlink". > > are there any linklocal address peers that are "not onlink"? > note that it is because the defition of "onlink" is a bit vague: > - sharing the same subnet number > - same link-local scope zone > > i'm using the latter definition, and i guess you are using former. > multilink subnet folks are using the former.
This is not a problem (IMO): the problem is that certain global addresses are *also* on-link, but cause issues with redirects. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -------------------------------------------------------------------- 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] --------------------------------------------------------------------
