Re: [OSPF] Mail regarding draft-ietf-ospf-ospfv3-autoconfig

[Acee Lindem <[e-mail]>]

Adding OSPF list.

On Oct 3, 2013, at 2:48 AM, Rajib Majila wrote:

Hi Acee/Arkko,

I had a few questions/comments on your draft. Please find them below and clarify.

1.    On using asynchronous hello/dead interval: Are you suggesting implementing the LLS for supporting
 async hello/dead interval as mentioned in in your reference [ASYNC-HELLO].

No

As I understand it may not
be necessary as you are simply suggesting allowing a per neighbor hold timer timer based on the
 hello/dead interval advertised by the neighbor in its hello packet.

Yes


2.    Router-id selection: It would probably be better to use a mechanism that would most likely provide
a unique id instead of a pseudo-random number. It can be a 32 bits hash of the router-hardware-
fingerprint as suggested in your draft. A regeneration of router-id can possibly use a different hash
function in case a collision was detected. Given that this fingerprint is used even for detection of
duplicates, I believe it can be expected to generate unique router-ids quite reliably.

The pseudo-random number generation is seeded with an ID such as the router-hardware-fingerprint.



3.    Duplicate router-id detection: Can a self originated hello packet be identified by looking at the source
IPv6 address and comparing the same against the IP addresses of the local interfaces. If you do not see
any issue with this approach, it can eliminate the need to have a new LSA and thereby simplifying the
implementation.

Hello are only exchanged between adjacent neighbors.  The router-id must be unique within the entire OSPF routing domain.

Acee


Rajib


<http://www.ericsson.com/email_disclaimer>