Olivier Dugeon

> Does the failed test make sense, or in other words, should the neighbor not be deleted when transitioning from UP to DOWN state? https://ci1.netdef.org/browse/FRR-PULLREQ3-TOPO5U18ARM8-2673 https://ci1.netdef.org/browse/FRR-PULLREQ3-TOPO8U18AMD64-2673 https://ci1.netdef.org/browse/FRR-PULLREQ3-ASAN7-2673 https://ci1.netdef.org/browse/FRR-PULLREQ3-TOPO1DEB10AMD64-2673 I re-run...

> Does 'remove the context when the neighbor is removed from the configuration' refer to the command 'clear isis neighbor [WORD]'? No. I'm referring to CLI `no isis router WORD`...

> I tried the scenario of a P2P link. If the link goes DOWN without deleting the neighbor table entry, the new neighbor cannot be established because the old neighbor...

I just perform a test on one of my router: set the interface down with ìp link set down dev ethX` check that we lost the IS-IS adjacency and thus...

Update the code accordingly to the review and add a new commit for Extended Link LSA parser

> Let's go ahead with this - while I would have allowed for the full extent of the sub-TLVs as allowed in the standards, I agree that the probability of...

> Could you fix frrbot styling issues before merging? Done

Rebase the PR and mention the CVE in the commit message

Got always the same error after rebasing. Some tests failed due to an unsupported `ip -J route` i.e. output of `ip route` in json format on some platform. I don't...

Got the error this time. The problem comes from a wrong TLV size verification for TE database which output the ospf_te_parse_pref() and ospf_te_parse_link() with error. Unfortunately, within ospf opaque processing,...