Group,
First, I have not read this document, so please don’t shoot the
messenger.
May I add, …
If due to configuration or other reasons that the
router is late in announcing its Router ID compared to receiving Router IDs,
independent of any means that a Router ID is chosen, it MUST compare its to be
announced Router ID with ALL received Router IDs, as to identify if a Router ID
collision would occur and take the appropriate steps.
Additionally, after a router has begun announcing its
Router ID, it SHOULD ?randomly/periodicly?, if the check is not already done
with each received Router ID, compare its announced Router ID with all received
Router IDs, as to identify if a collision has occurred.
Secondly, wouldn’t any auto configuration method using
any random type generation mitigate and not prevent router id collisions?
Mitchell Erblich
On Jan 23, 2015, at 7:51 PM, Rama Darbha <[email protected]> wrote:
> A. Lindem and J. Arkko,
>
> Some feedback on this draft. In section 5:
>
> "5. OSPFv3 Router ID Selection
> A pseudo-random number SHOULD be used for the OSPFv3 Router ID."
>
> I think it would be valuable to describe why a pseudo-random number should be
> chosen. The [OSPFv3] document doesn't make any reference to selecting a
> pseudo-random number, so it would be good to justify the reasoning. Something
> along the lines of:
> "The router id in OSPFv3 is a 32-bit value [OSPFv3]. As outlined in [OSPFv3],
> a router running OSPFv3 may not have an IPv4 address to automatically select
> as the router id. Since auto-configuration cannot guarantee a unique router
> id as outlined in [OSPFv3], a pseudo-random router id is the solution for
> OSPFv3 autoconfiguration to prevent router id collision."
>
>
>
> Also, there's a small formatting error. Section 7.2 and 7.4 are not marked
> correctly as headers.
>
>
> Regards,
> Rama
>
> --
> -----
> Rama Darbha
> [email protected]
> 919 410 7262
> _______________________________________________
> OSPF mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ospf
_______________________________________________
OSPF mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ospf
