Re: Section 4.7 of RFC#7752 bis

Hi Balaji,

I have personally no issue changing the MUST to SHOULD in the following text so that using the solution you propose for the very specific use-case that you have in mind is possible without being non-compliant to the specification.

   A BGP-LS Producer MUST withdraw all link-state objects advertised by
   it in BGP when the node that originated its corresponding LSP/LSAs is
   determined to have become unreachable in the IGP and it MUST re-
   advertise those link-state objects only after that node becomes
   reachable again in the IGP domain.

Would that completely address your concerns?

However, if you also wish to add this other option then we ought to at least explain that mechanism properly to enable review by the WG. When you say “advertise the links from both the partitions using ADD-PATH”, it is not really intuitive for reader of the document to understand this and its implications in the BGP-LS context.

In Montreal, I put together some slides<https://datatracker.ietf.org/meeting/105/materials/slides-105-idr-sessa-draft-ketant-idr-rfc7752bis-01> with your help to try and explain your proposal (solution B) and still it was difficult for many experts in the room to understand the need and motivation for it – the minutes<https://datatracker.ietf.org/meeting/105/materials/minutes-105-idr-01.htm> and the recording<https://www.youtube.com/watch?v=7tgD-hPPIhI> are available to refresh our collective memory.

In full disclosure, I personally find your proposed solution B very complex with little or no benefit – even though, IIRC, I did not express that opinion during the session in order to not influence. I do agree though that you should have the flexibility to implement your solution for the use-cases you have in mind while the draft tries to capture the simpler and consensus solution for most of the broad use-cases.

So if you wish to still put forward your alternate mechanism, then please provide a good text that enables review by the WG. However, if you are happy with just the above text change that I’ve proposed then we are good and this can be posted in the next update for the draft.

Thanks,
Ketan

From: Balaji Rajagopalan <[email protected]>
Sent: 15 November 2019 09:28
To: Ketan Talaulikar (ketant) <[email protected]>
Cc: 'idr wg' <[email protected]>
Subject: Re: Section 4.7 of RFC#7752 bis

Hi Ketan,

>> So, my suggestion would be the following:
>>Clearly describe the problem, as the current draft does
>>Describe both the solutions (ADD-PATH & the current text), and make them both optional behaviours available to an originator
>> [KT] Could you propose the text to describe the ADD-PATH solution? We can get the WG feedback for its inclusion as another alternative in the document.

Please see below suggested replacement text for the last paragraph of section 4.7. Please feel free to massage the text.

A BGP-LS Producer has two ways to cope with the above problem:

  *   Do not advertise the links of unreachable nodes
  *   Advertise the links from both the partitions using ADD-PATH, so the consumer has enough information to identify the stale entries.


--
Balaji Rajagopalan

_______________________________________________
Idr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/idr