>A node MUST be able to detect whether two of its local internal
>interfaces are connected, e.g., by detecting an identical remote
>interface being part of the Common Links of both local interfaces.
>
> What should the node do if it detects that two interfaces are on the same
> link?
James:
> Doesn’t section 6.3.1 already spell that out?
>
> Set of Shared Links: […] When multiple interfaces are
> detected as belonging to the same Common Link, prefix assignment
> is disabled on all of these interfaces except one.
Steven:
> How about adding "In this case the r
On Aug 18, 2015, at 10:45, Juliusz Chroboczek
wrote:
>
>>> Section 6.1 says:
>>>
>>> A node MUST be able to detect whether two of its local internal
>>> interfaces are connected, e.g., by detecting an identical remote
>>> interface being part of the Common Links of both local interfaces.
>
Am 18.08.2015 um 19:45 schrieb Juliusz Chroboczek:
> That's too weak -- it also needs to take care to perform prefix assignment
> only once (although it will probably want to perform address assignment on
> both interfaces, especially if they're in ad-hoc mode), to run only one
> instance of RA and
>> Section 6.1 says:
>>
>> A node MUST be able to detect whether two of its local internal
>> interfaces are connected, e.g., by detecting an identical remote
>> interface being part of the Common Links of both local interfaces.
> Seems like this could be improved by rephrasing it to the ef
On Aug 18, 2015, at 06:38, Juliusz Chroboczek
wrote:
>
> Section 6.1 says:
>
> A node MUST be able to detect whether two of its local internal
> interfaces are connected, e.g., by detecting an identical remote
> interface being part of the Common Links of both local interfaces.
>
> What
Section 6.1 says:
A node MUST be able to detect whether two of its local internal
interfaces are connected, e.g., by detecting an identical remote
interface being part of the Common Links of both local interfaces.
What should the node do if it detects that two interfaces are on the same
