> I may need to reread the whole thread to understand the context, but...
aha, I found the original message.
>>> Now, this would appear to be rather problematic. Some items for a router
>>> include among others setting IsRouter flag in NA's and responding to RS's.
>>> These seem to be usually implemented as global toggles; either the system
>>> is a router or it is not.
>>This seems to be an implementation bug since RFC 2461 says that all the
>>configuration knobs are per interface.
> could you point me to the text where it is specified as a
> "per-interface knob"?
>
> in KAME stack (I guess Pekka is referring to KAME), per-host
> "forwarding" flag decides whether it is a router or not (there's no
> "interface A and B are host, interface C and D are router" kind of
> configuration), and it affects outgoing IsRouter bit on NS/NA.
we do not implement "partly host, partly router" behavior.
also, since RFC2462 basically assumes single-interface host,
we do not really care about the following cases:
- autoconfigured host with multiple interfaces
- chimera (part-host, part-router) node
- autoconfigured router
we care about the following cases:
- autoconfigured host with single interface
- manually configrured host
- manually configured router
for more details, kame IMPLEMENTATION document section 1.4.2.
itojun
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
