On Thu, 17 Jul 2003, Erik Nordmark wrote: > > However, section 8 on redirect basically requires: > > - routers know each others' link-local addresses (not an issue from > > hosts' perspective, just use routing protocols or other mechanisms) > > - hosts are able to verify that the redirect comes from the link-local > > address the host is currently using as its next-hop > > > > The latter is a bit problematic. How could the host know this in the case > > where the next-hop has been configured using e.g. a _global_ (but on-link) > > address? > > > > What's the deal here? > > Per rfc 2461 the source address of the redirect must be a link-local address. > Thus if you want to create a static route on the host and make > redirects work at the same time you'd better use the link-local address > of the router in the static route. > > So apart from this requirement on the manually added static routes, what > is the issue?
I think the question whether: - we want to specify next-hops must be link-locals - we want to clearly state that redirects work only when using link-locals, and when the link-locals are the same as used in next-hops - we want to figure out whether it's worth exploring the details needed to make redirects work with global/anycast next-hops. -- 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] --------------------------------------------------------------------
