Hemant Singh (shemant) wrote:
Good question, Erik. To the best of my knowledge such an RFC does not
exist - at least describing total details of an aggregation router -
like unicast, mcast, and anycast data forwarding rules etc.  The closest
I have found in IETF is what IETF calls as multi-link router.

FWIW I don't find "multi-link router" in any RFC. My point was that using this undefined term doesn't help clarify things. It would have been better to talk about a router which has been configured to never send any redirects.

Now the question I asked in my presentation. I have to configure this
aggregation router to signal off-link. How do I do that?

By not to configuring it to enable the L flag for any prefix that the router advertized. Abstractly (per RFC 4861) this is done by setting AdvOnLinkFlag=False.

If you have a question on how to do that for a particular product you should ask the vendor of that product. If you are using OpenSolaris I can help.

As I said in the presentation, let's forget the aggregation router. The
host implementation bug we found is reproduced in an Ethernet LAN
network too. An RA from the router was sent where RA was NOT signaling
on-link and the host still behaved as on-link for traffic forwarding.

That is clearly a bug in the host implementation.
Have you contacted the host vendor?

The RA we used was an RA that did not send any PIO (Prefix Information
Option). BTW, such a case (RA with no PIO) is not even covered by the
definition of on- and off-link in section 2.1 of RFC 4861, especially
since section 2.1 goes to so much copious details to describe on-link.

It does cover it. If no information is know about an address (which is this case - no prefix options with L=1 and no redirects) then the host will send to a default router.

   Erik

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to