Re: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)

["Les Ginsberg (ginsberg)" <[e-mail]>]

Sue –

(I am already starting to be sorry I waded into this thread…)

Sorry, but I find your response off topic.

It is quite legitimate for the IDR WG to consider alternatives to BGP-LS – and even consider deprecation of BGP-LS.
(By saying that I am not expressing support or opposition to the idea.)

But it is NOT legitimate for that topic to be used as a blocker for a particular BGP-LS draft.
BGP-LS is what we have – and it is widely deployed. If/when the IDR WG decides “no more BGP-LS” then clearly such drafts should no longer be written. But that state does not currently exist.

In the real world we live in, as I see it:

LSR WG decides what IGP protocol extensions will be approved.
Once those extensions are approved it is NOT the place of the IDR WG to say “BGP-LS will not be allowed for this IGP protocol extension”.
IDR WG could say “we would rather you incorporated the BGP-LS extensions directly into the corresponding LSR draft”.
But, I don’t hear you saying that. I hear you saying the IDR WG may decide to forbid BGP-LS extensions for this particular IGP extension.
Which is why I ask – where is the definition of how such a decision is made?

I deliberately am not commenting inline to your response because (no offense intended) nothing in your response is applicable to my question.

   Les


From: Susan Hares <[e-mail]>
Sent: Tuesday, June 7, 2022 4:34 PM
To: Les Ginsberg (ginsberg) <[e-mail]>; Aijun Wang <[e-mail]>
Cc: [e-mail]
Subject: RE: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)

Les:

The IDR and LSR WG chairs have agreed that LSR/BGP BGP-LS specifications often specify the same TLVs.   In this case, if the authors desire, the LSR specification can specify both ISIS TLVs, OSPF TLVs, and BGP-LS TLVS.

As part of the WG LC process for such a combination document, the IDR WG reviews BGP-LS portion of the LSR Specification.  If there is an objection to the LSR work going into BGP, then the LSR and IDR chairs handle the issue.  You may have noticed this happening in the past.  Or it may have been part of the LSR chairs back-end process you did not see.

For this draft, the authors requested a separate draft would be adopted and WG LC in IDR. Given the author’s request, I must follow the normal procedure for any IDR draft.   As you have notice from Aijun and Robert, there is growing concern the continued addition of BGP-LS TLVs.  This growing concern for this draft may have been expressed even if this was a cross-reviewed draft.

Consensus decision-making does take time and cross reviews.

I hope this helps you understand the administrative process.  The LSR and IDR chairs are trying to minimize needless drafts while providing opportunities for the two WGs to review the documents.

Cheers, Sue

From: Les Ginsberg (ginsberg) <[e-mail]<mailto:[e-mail]>>
Sent: Tuesday, June 7, 2022 6:57 PM
To: Susan Hares <[e-mail]<mailto:[e-mail]>>; Aijun Wang <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>
Subject: RE: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)


Sue –

Color me confused.

We have here a protocol extension to IS-IS that the LSR WG has approved (passed last call). Which there was sufficient belief in the WG that this protocol extension was useful for it to be approved.
But you claim there is some secondary process, managed by the IDR chairs (or perhaps IDR and LSR chairs?), that determines whether the BGP-LS extensions in support of the approved IGP extensions will be allowed?
This is completely new to me – please explain how that process works.

NOTE: I am not debating Aijun’s remark as to the “enthusiasm” showed in the LSR WG for the draft – nor was I a vocal supporter of the LSR draft in question.
But, if LSR WG approval is not sufficient to justify the corresponding BGP-LS support, please explain what is the defined process and where it is documented and describe how it has been used in the past.

Thanx.

    Les

From: Idr <[e-mail]<mailto:[e-mail]>> On Behalf Of Susan Hares
Sent: Tuesday, June 7, 2022 1:54 PM
To: Aijun Wang <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>
Subject: Re: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)

Aijun:

Thank you for your feedback on deployment issues.   It is important to know if an operator feels this option will not be deployed.

I  will contact other operators to ask them to comment on this adoption call.

Sue

From: Aijun Wang <[e-mail]<mailto:[e-mail]>>
Sent: Tuesday, June 7, 2022 10:51 AM
To: Susan Hares <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>
Subject: Re: [Idr] draft-head-idr-bgp-ls-isis-fr-01 - WG adoption call (6/6 to 6/20)


Hi, all:

I don’t support its adoption.
The corresponding IS-IS document past just the LSR WG unconvincingly and I cannot foresee which operator will deploy the flood reflection mechanism in IS-IS deployment.
Then it is doubtful also the corresponding BGP-LS extension.
There is no any description for the necessary in the document.

If the authors insist to do so, I recommend to incorporate the trivia contents into the corresponding IS-IS document.


Aijun Wang
China Telecom

On Jun 7, 2022, at 05:28, Susan Hares <[e-mail]<mailto:[e-mail]>> wrote:

This begins a 2 week WG adoption call for draft-head-idr-bgp-ls-isis-fr-01.txt

https://datatracker.ietf.org/doc/draft-head-idr-bgp-ls-isis-fr/

  This document defines one new BGP-LS (BGP Link-State) TLV for
   Flood Reflection to match the ISIS TLV for flood reduction.

   The draft is short (5 total pages).

Since this BGP-LS feature has been adopted by IS-IS,
Please consider


  1.  Is there any technical difficulty with adding this to the BGP-LS code points?
2.   Is this draft ready for publication?
3.   Does this addition help operational networks.

Cheers, Sue Hares



_______________________________________________
Idr mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/idr