(B > > Per RFC 2461 the per router list is per interface.
(B > > There is an issue for the implementations (probably all
(B > implementations)
(B > > which have a per-node default router list, but from the perspective
(B > > of the RFC 2461 specification it has already punted on all
(B > aspects of
(B > > multi-interfaced hosts.
(B >
(B > Yes, so if we allow the mixed behavior, then it is probably
(B > reasonable
(B > to allow the node to accept RAs on a "host" interface and to
(B > configure
(B > default routers on that interface. My point is that we should
(B > *explicitly* note that the rule for the multi-interfaced hosts also
(B > applies to the host-side interfaces on a mixed-behavior node.
(B
(B=> We can explicitly state it but I think an important point here is that
(Bthe spec already allows for this. We can always add more text I suppose,
(Bit's a matter of taste.
(B
(B >
(B > >> So, (if we concentrate on the "simple" cases), I think we should
(B > >> emphasize that even if an interface is not an advertising
(B > interface
(B > >> the node still acts as a router on that interface (e.g., it can
(B > >> forward from/to that interface, exchange routing
(B > information on that
(B > >> interface, etc)
(B >
(B > > Whether or not we concentrate on the "simple" case, I think it
(B > > makes sense to state that a non-advertising interface is still
(B > > one that behaves as a router e.g. the R-bit in the NA should be set
(B > > since another router might redirect hosts to use the
(B > router that doesn't
(B > > advertise itself.
(B >
(B > Hmm, I agree. Let me rephrase this point then:
(B >
(B > - if we concentrate on the "simple" cases, then we should
(B > emphasize in
(B > rfc2461bis that even if an interface is not an advertising
(B > interface
(B > the node still acts as a router on that interface (e.g., it can
(B > forward from/to that interface, exchange routing
(B > information on that
(B > interface, set the R-bit in NAs, etc)
(B
(B=> Which is stated today by virtue of having two separate flags to indicate
(Bwhether "routing" is on and whether "advertising" is on.
(B
(B >
(B > - if we allow the mixed behavior, then we should emphasize in
(B > rfc2461bis that even if a "router-behavior" interface is not an
(B > advertising interface, the node still acts as a router on that
(B > interface.
(B
(B=> Are there missing flags in order to allow this or are you suggesting
(Bmore text. If the latter, I can handle that.
(B
(BHesham
(B
(B >
(B > JINMEI, Tatuya
(B > Communication Platform Lab.
(B > Corporate R&D Center,
(B > Toshiba Corp.
(B > [EMAIL PROTECTED]
(B >
(B > --------------------------------------------------------------------
(B > IETF IPv6 working group mailing list
(B > [EMAIL PROTECTED]
(B > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
(B > --------------------------------------------------------------------
(B >
(B
(B===========================================================
(BThis email may contain confidential and privileged material for the sole use
(B of the intended recipient. Any review or distribution by others is strictly
(B prohibited. If you are not the intended recipient please contact the sender
(B and delete all copies.
(B===========================================================
(B
(B
(B--------------------------------------------------------------------
(BIETF IPv6 working group mailing list
(B[EMAIL PROTECTED]
(BAdministrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
(B--------------------------------------------------------------------
